Autodesk Revit Quiz: Copy Monitor
10 questions · exam conditions
0:00
Copy MonitorQuestion 1 of 10

A structural model already contains levels that were created manually at the correct elevations. The architect later supplies a linked model containing corresponding levels. The structural team wants change notifications but must not create duplicate levels.

What should the structural designer do in Copy/Monitor?

Copy each linked level, then delete the original structural level at the same elevation.
Monitor each existing structural level against its corresponding level in the architectural link.
Copy each linked level with a zero offset and allow Revit to merge the matching levels.
Pin the existing structural levels and reload the architectural link after every design change.
← Back to quizzes

Autodesk Revit Quiz

Autodesk Revit Quiz: Copy Monitor

Practice Copy Monitor in Autodesk Revit with focused quiz questions that help you check what you know, review explanations, and build confidence with test-style prompts.

What this quiz covers

This quiz focuses on Copy Monitor, giving you a quick way to practice the rules, question types, and explanations that matter most for Autodesk Revit.

How to use this quiz

Try each quiz question before looking at the correct answer. Use the explanations to review missed ideas, then come back to similar questions until the pattern feels familiar.

All questions

Question 1

A structural model already contains levels that were created manually at the correct elevations. The architect later supplies a linked model containing corresponding levels. The structural team wants change notifications but must not create duplicate levels.

What should the structural designer do in Copy/Monitor?

  1. Copy each linked level, then delete the original structural level at the same elevation.
  2. Monitor each existing structural level against its corresponding level in the architectural link. (correct answer)
  3. Copy each linked level with a zero offset and allow Revit to merge the matching levels.
  4. Pin the existing structural levels and reload the architectural link after every design change.
Explanation: When working with Copy/Monitor in Revit, you need to distinguish between two separate workflows: copying elements from a linked model into your project, and monitoring existing elements against their linked counterparts. This question tests whether you understand that distinction — specifically, what to do when the elements you need already exist. Since the structural model already has correctly placed levels, the goal isn't to create new ones — it's to establish a live relationship between the existing structural levels and the architectural link so that any changes in the link trigger a coordination warning. That's exactly what Monitor does. By selecting each structural level and monitoring it against its corresponding architectural level, you create that notification link without touching or duplicating any geometry. Option B is correct. Option A is a dangerous workaround: copying linked levels and then deleting your originals risks breaking references that other elements — floors, walls, structural framing — may already be hosted to. You'd be orphaning hosted components. Option C reflects a common misconception that Revit will "merge" levels during a Copy operation if elevations match. Revit doesn't auto-merge on copy; it creates a duplicate, which is exactly the problem the team is trying to avoid. Option D misunderstands the purpose of pinning and reloading. Pinning prevents accidental movement of elements, and reloading a link refreshes its data — neither establishes a monitoring relationship that generates change notifications. A useful rule of thumb: use Copy when you need to bring elements into your model, and use Monitor when those elements already exist and you simply want to watch them against a linked source.

Question 2

Levels have been copied and monitored from a linked architectural model. The architect raises one source level, saves the model, and sends the updated file. The structural designer reloads the link.

What is the expected Copy/Monitor behavior?

  1. The structural level moves automatically and all hosted elements move without requiring review.
  2. The architectural level returns automatically to the elevation of the monitored structural level.
  3. Revit reports a coordination change so the structural designer can review and resolve the difference. (correct answer)
  4. The monitoring relationship ends automatically because the two level elevations no longer match.
Explanation: When working with Copy/Monitor in Revit, it's important to understand that the tool creates a watchful relationship, not an automatic sync. Revit monitors for discrepancies between linked and host model elements, but it never silently overrides the structural designer's work — human review is always required. When the architect raises a level and the structural designer reloads the link, Revit detects that the monitored source element has changed. It flags this through a Coordination Review warning, prompting the structural designer to open the Coordination Review dialog and choose how to resolve the difference — accept the change, reject it, or postpone. This is exactly what C describes, making it the correct answer. A is wrong because Copy/Monitor never moves hosted elements automatically. Structural elements like beams, columns, and foundations hosted to a level don't silently shift — that would create serious unreviewed changes to the structural model, which Revit deliberately prevents. B describes the opposite of how the tool works. The architectural model drives the change; Revit doesn't force the source level back to match the structural copy. The link is read-only from the structural model's perspective. D is a common misconception. A mismatch in elevation does not break the monitoring relationship. The whole point of Copy/Monitor is to survive and report such discrepancies so they can be resolved intentionally. As a study tip, remember that Copy/Monitor is a notification system, not an automation system. On the exam, any answer suggesting automatic resolution without designer review should be treated with skepticism.

Question 3

A monitored architectural grid is deleted from the linked model because the architect believes it is no longer required. The structural host still contains the native grid copied from that source, and structural columns reference it.

What should the structural designer expect after reloading the link?

  1. The host grid is deleted automatically, including constraints that reference the grid.
  2. The source grid is restored automatically from the monitored copy in the host model.
  3. A coordination issue is reported, allowing the host team to decide how to handle its grid. (correct answer)
  4. The host grid becomes an imported line and loses its datum behavior without warning.
Explanation: When working with Copy/Monitor in Revit, you need to understand that the workflow is designed around coordination and communication, not automatic synchronization. The tool flags discrepancies between linked and host models so teams can make informed decisions — it never silently modifies your native model. When a monitored element is deleted from the source (linked) model, Revit detects the mismatch upon reloading that link and raises a Coordination Review warning. This is exactly what C describes: the structural team receives a coordination issue, giving them the agency to decide whether to delete their native grid, ignore the change, or take another action. This protects structural work — columns and beams referencing that grid are not silently broken. A is wrong because Revit will never automatically delete a native element in your host model, especially one that other elements depend on. Doing so would corrupt the structural model without user consent, which contradicts Revit's non-destructive philosophy. B is wrong because Copy/Monitor does not sync data back from host to source. The monitored copy in the host cannot "restore" anything in the linked file — the relationship is one-directional for change detection, not bidirectional restoration. D is wrong because grids do not silently downgrade to imported lines. Revit's coordination tools are explicit: they surface warnings rather than quietly degrading element behavior. A grid without a monitored counterpart simply remains a valid native grid until you act on the coordination review. For the exam, remember this principle: Copy/Monitor = flag, not fix. It reports divergence; it never auto-resolves it.

Question 4

A project has copied and monitored grids from a consultant link. To improve performance temporarily, the link is unloaded. Several days later, an updated version of the link is loaded again.

How does unloading and later reloading the link affect the grid monitoring relationships?

  1. Unloading permanently removes the relationships, so all grids must be copied again after reloading.
  2. Unloading converts the copied grids to ordinary detail lines until the link is loaded again.
  3. The relationships remain associated with the link, and changes can be detected after it is reloaded. (correct answer)
  4. The copied grids remain monitored, but Revit updates their positions while the link is unloaded.
Explanation: When working with linked files in Revit, it helps to understand that Copy/Monitor creates a persistent relationship stored in your host project — not in the link itself. The monitoring association is essentially a record within your file that says, "this grid corresponds to that element in the linked file." That relationship doesn't depend on the link being actively loaded. Because of this, unloading a link is a non-destructive, temporary action. The copied grids remain fully intact in your project as monitored elements, and the monitoring relationships are preserved in the project data. When you reload the link — even an updated version — Revit can compare the current state of the linked elements against the monitored copies. If anything has changed (a grid was moved or renamed, for example), the Coordination Review tool will flag those discrepancies for you to resolve. That's exactly what answer C describes, and it's correct. Answer A is wrong because unloading is explicitly designed to be reversible — it does not delete or break monitoring relationships. Answer B introduces a false behavior: copied grids never convert to detail lines under any circumstance related to link loading status; they remain model elements with monitoring flags. Answer D contains a subtle but important error — Revit does not silently reposition monitored elements while a link is unloaded. Revit only flags changes for your review after the link is reloaded; it never auto-updates positions without user action. As a study tip, remember that in Revit, unloading ≠ deleting. Any question about Copy/Monitor and linked file management is testing whether you understand that monitoring is host-side data, making it resilient to link availability.

Question 5

A copied grid is monitored against a grid in a linked model. Coordination responsibility for that grid is transferred permanently to the host team, but the host grid and its dimensions must remain in the project.

Which action best meets the requirement?

  1. Delete the linked grid so the host grid remains without a coordination source.
  2. Stop monitoring the grid while retaining the native host grid in the project. (correct answer)
  3. Unpin the host grid and move it slightly so the monitoring relationship is released.
  4. Unload the link permanently so the host grid is no longer checked for changes.
Explanation: When working with Copy/Monitor in Revit, you need to distinguish between ending a monitoring relationship and removing the elements involved. The scenario here is specific: the host team now owns the grid permanently, but the host grid and its dimensions must stay in the project. That means you need a clean break from the link — without deleting anything the host team relies on. Stopping the monitoring relationship (answer B) does exactly this. In Revit, you can use the Stop Monitoring command to sever the coordination link between the host grid and the linked model's grid. The host grid remains fully intact in the project — dimensions, annotations, and all — it simply no longer reports changes from the linked model. Coordination responsibility effectively transfers to the host team because the element is now independently managed. Answer A fails because deleting the linked grid may affect the linked model itself, and it doesn't address the monitoring relationship in the host file cleanly. Answer C — unpinning and moving the grid — is a workaround, not an official workflow. Moving the grid would break dimension relationships and potentially disrupt the model, violating the requirement to retain the grid and its dimensions unchanged. Answer D unloads the link entirely, which is a blunt instrument: it affects all monitored elements, not just this grid, and the monitoring relationship still technically exists — it's just dormant until the link reloads. As a study tip, remember that Stop Monitoring is the precise, element-level tool for releasing coordination without deleting or repositioning anything. If the question says "retain the element but end coordination," Stop Monitoring is almost always your answer.

Question 6

A host model contains monitored copies of consultant grids. A designer pins all host grids to prevent accidental dragging. In the next consultant issue, one source grid is moved.

Which statement correctly describes the effect of pinning on this workflow?

  1. Pinning suspends monitoring, so the source-grid movement is not reported until the host grid is unpinned.
  2. Pinning locks the linked source grid, preventing the consultant from moving it in the linked model.
  3. Pinning forces the host grid to follow the linked grid automatically when the link is reloaded.
  4. Pinning protects the host grid from local movement, while Copy/Monitor can still report the source change. (correct answer)
Explanation: When working with Copy/Monitor in Revit, it helps to think of two completely separate systems operating side by side: the pinning tool and the coordination monitoring tool. Understanding that these systems are independent is the key to answering this question correctly. Pinning a host grid simply locks its position in the host model — it prevents anyone from accidentally dragging that element locally. It has absolutely no effect on the Copy/Monitor relationship. When you reload the consultant link and a source grid has moved, Revit's Coordination Monitor still detects the discrepancy and flags it in the Coordination Review dialog. The host grid stays put (because it's pinned), and the monitor reports the conflict — exactly what D describes. Pinning actually supports this workflow by ensuring that any flagged change is a real consultant change, not an accidental local drag. A introduces a false dependency: pinning has no ability to pause, suspend, or delay monitoring. Coordination Review runs whenever you reload the link, regardless of pin status. B confuses which model the pin affects — you can only pin elements in your own host model; you have zero control over elements inside a linked file. The consultant can freely move grids in their model. C describes automatic synchronization, which doesn't exist in Revit's Copy/Monitor workflow. Monitored elements never move automatically; that would defeat the purpose of controlled coordination review. As a study tip, remember this distinction: pinning = local position lock, monitoring = change detection. On the exam, any answer that conflates these two functions — suggesting one interrupts or enables the other — is a trap.

Question 7

An architectural model is linked into a new structural model. The structural model does not yet contain levels, and the team wants its new levels to remain coordinated with the architectural levels.

Which workflow should the structural designer use?

  1. Start Copy/Monitor, choose Select Link, select the architectural model, and copy the required levels. (correct answer)
  2. Start Copy/Monitor, choose Use Current Project, and copy the required levels from the active model.
  3. Open the linked architectural model, copy the levels to the clipboard, and use Paste Aligned in the structural model.
  4. Bind the architectural link, ungroup the resulting group, and retain only the required level elements.
Explanation: Whenever you see a question about coordinating elements across linked Revit models, think about the Copy/Monitor tool — it's specifically designed to maintain a live coordination relationship between elements in separate models, not just duplicate geometry. Copy/Monitor works in two modes: Use Current Project (for monitoring elements within the same model) and Select Link (for reaching into a linked file). Since the structural team wants their new levels to stay coordinated with levels that exist in the linked architectural model, they must choose Select Link and then pick that architectural link. This is exactly what option A describes — and it's the correct workflow. Once levels are copied this way, Revit tracks any changes to the original architectural levels and alerts the structural team through Coordination Review if discrepancies arise. Option B is wrong because Use Current Project only monitors elements already in the active structural model — there are no levels there yet, and it cannot reach into the linked file. Option C (copy to clipboard and Paste Aligned) is a static duplication: it creates independent levels with no ongoing coordination link, so future architectural changes would go undetected. Option D (binding the link) imports all architectural geometry into the structural model, which is architecturally intrusive, inflates file size, and still doesn't establish a Copy/Monitor relationship — it's a destructive workaround that defeats the purpose of linking. Your study tip: on the Revit exam, whenever a question mentions keeping elements coordinated across models, Copy/Monitor with Select Link is almost always the answer. The word "coordinated" is your signal.

Question 8

A consultant's linked model uses a level type named Consultant Datum. Levels copied into the host must use the host type Shared Level Head and must be placed with a consistent vertical offset.

Which action should be completed before copying the linked levels?

  1. Configure the level type mapping and copy offset in the Copy/Monitor Options dialog. (correct answer)
  2. Change the link's instance type and elevation properties in the host model.
  3. Copy the levels first, then edit the linked level types through Manage Links.
  4. Create plan views for every host level and assign the required view template.
Explanation: When working with linked models in Revit, the Copy/Monitor workflow is your primary tool for coordinating elements like levels, grids, and columns between a host model and a consultant's linked file. The key principle is that before you copy anything, you must define the rules for how those copied elements will behave — otherwise Revit has no way of knowing how to translate the linked elements into host-appropriate equivalents. This is exactly why A is correct. The Copy/Monitor Options dialog lets you pre-configure type mapping (so the consultant's "Consultant Datum" type gets mapped to your host's "Shared Level Head" type) and specify a consistent elevation offset. Setting this up first means every level you copy in that session automatically inherits the correct type and offset — no manual cleanup needed afterward. B is incorrect because instance properties on the linked file itself don't control how copied elements are typed or offset in the host. You'd be editing the link, not the copying rules. C is wrong because copying first without configuring options means levels will be copied using default or mismatched types, requiring tedious one-by-one corrections — and Manage Links doesn't provide type-mapping tools for this purpose anyway. D is a distractor that references a legitimate Revit task (creating plan views and assigning view templates) but has nothing to do with the preparation required before copying monitored levels. A useful study tip: on Copy/Monitor questions, always ask yourself "what needs to be configured before the action, not after?" Revit's coordination tools reward upfront setup — configure options first, execute second.

Question 9

An engineer uses Copy/Monitor to copy six levels from a linked model. The Project Browser shows the copied levels, but no new floor plan views appear.

Which conclusion and next action are appropriate?

  1. The copy failed; delete the levels and repeat Copy/Monitor from an elevation view.
  2. The result is expected; create the required plan views separately for the copied levels. (correct answer)
  3. The link is unloaded; reload it to generate plan views for all monitored levels.
  4. The level types are incompatible; remap them so Revit can generate the plan views.
Explanation: When working with Copy/Monitor in Revit, it helps to understand exactly what the tool does — and what it doesn't do. Copy/Monitor copies elements (like levels, grids, or columns) from a linked model into your host project so you can track changes to them. It handles the element geometry and monitoring relationship, but it does not automatically generate views associated with those elements. This is why B is correct. When you copy levels via Copy/Monitor, Revit places the level datums in the host model and begins monitoring them against the linked source. However, floor plan views are not created automatically — that's a separate step. You need to go to the View tab and use Plan Views → Floor Plan to generate views for the newly copied levels. This is expected, intentional behavior, not a failure. A is wrong because the copy didn't fail — the Project Browser confirming the levels are present proves the operation succeeded. Redoing it from an elevation view wouldn't change this behavior anyway. C is wrong because the link's load status has nothing to do with view creation; even a fully loaded link won't auto-generate plan views. D is a distractor that sounds technical, but type incompatibility would affect whether the levels copy at all, not whether plan views appear afterward. A useful tip to remember: in Revit, creating an element and creating a view of that element are always two separate actions. Whenever you see a question about Copy/Monitor or linked model workflows, ask yourself whether the complaint is about the element itself or the views — those are distinct issues with distinct solutions.

Question 10

A linked model contains forty grids. The host team needs native monitored copies of thirty adjacent grids but must exclude ten temporary layout grids.

Which Copy/Monitor workflow most efficiently creates the required monitored grids?

  1. Activate Copy, enable Multiple, select the thirty required linked grids, finish the selection, and finish Copy/Monitor. (correct answer)
  2. Use the standard Copy command, window-select the thirty grids, and paste them aligned into the host model.
  3. Monitor all forty linked grids, then hide the ten temporary grids through a host view template.
  4. Bind the link, select the thirty required grids from the group, and delete the remaining linked elements.
Explanation: When working with linked models in Revit, Copy/Monitor is the tool designed specifically to create native elements in the host model that remain synchronized with their linked counterparts. The key skill being tested here is knowing how to use Copy/Monitor selectively and efficiently — not just that the tool exists. The correct approach is A. Within the Copy/Monitor workflow, enabling the Multiple option lets you hand-pick individual elements from the linked model one by one (or using filter-based selection), then commit them all in a single operation. This gives you precise control — you select exactly the thirty grids you need, skip the ten temporary ones, and finish the command. The result is thirty monitored grids in the host model, properly linked to the source. B is a trap for students who conflate copying geometry with establishing a monitoring relationship. The standard Copy/Paste workflow duplicates geometry but creates no monitoring link whatsoever — changes in the linked model won't alert the host team. C sounds like a workaround, but it fundamentally misunderstands what monitoring means. Hiding the ten grids in a view template doesn't remove their monitored status — Revit will still generate coordination warnings for all forty grids, adding unnecessary noise to the project's coordination workflow. D involves binding the entire link, which converts all linked elements into a local group and is a destructive, irreversible action in most workflows. It also far exceeds the scope of what's needed and introduces significant cleanup work. As a study tip: on Revit exam questions involving linked models, always ask yourself whether the answer establishes a live monitoring relationship — that distinction separates Copy/Monitor from every other selection or copy method.