Autodesk Revit Quiz: Linking Cad Files
10 questions · exam conditions
0:00
Linking Cad FilesQuestion 1 of 10

A site consultant issues a DWG every week. The file must remain aligned with the Revit model, and the project team wants to display each revision without placing a new copy of the DWG.

Which initial workflow best supports these requirements?

Import the DWG, then overwrite the imported geometry whenever the consultant issues a revision.
Link the DWG, then reload the existing reference whenever the consultant issues a revision.
Import the DWG into a drafting view, then copy its geometry into each required model view.
Link the DWG separately into every view, then replace each instance when the source changes.
← Back to quizzes

Autodesk Revit Quiz

Autodesk Revit Quiz: Linking Cad Files

Practice Linking Cad Files 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 Linking Cad Files, 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 site consultant issues a DWG every week. The file must remain aligned with the Revit model, and the project team wants to display each revision without placing a new copy of the DWG.

Which initial workflow best supports these requirements?

  1. Import the DWG, then overwrite the imported geometry whenever the consultant issues a revision.
  2. Link the DWG, then reload the existing reference whenever the consultant issues a revision. (correct answer)
  3. Import the DWG into a drafting view, then copy its geometry into each required model view.
  4. Link the DWG separately into every view, then replace each instance when the source changes.
Explanation: When a question asks about managing a repeatedly updated external file that must stay aligned with a Revit model, you should immediately think about the distinction between importing and linking in Revit. Importing embeds a static snapshot of the file into the project, while linking creates a live reference to an external file that can be refreshed. Linking is the right approach here because it lets you simply reload the existing reference when the consultant delivers a new version — Revit updates the display automatically, keeping alignment intact, without you placing anything new. That's exactly what B describes, and it satisfies both requirements: maintained alignment and no duplicate placements. A fails because importing embeds the geometry permanently. Every revision would require you to delete the old import and re-import the new file, which is tedious, error-prone, and risks misalignment — the opposite of a clean workflow. C compounds the import problem by placing it in a drafting view and manually copying geometry into model views, which creates disconnected, unmanageable copies that won't update at all when the consultant sends a new file. D starts correctly by linking, but linking separately into every view creates multiple independent instances, each of which must be individually replaced — eliminating the very efficiency linking is supposed to provide. A useful rule of thumb: if the external file will change over time, always link, never import. Linking treats the external file like a subscription — reload once and everything updates. Keep this in mind any time you see exam scenarios involving consultants issuing recurring deliverables.

Question 2

During an internal review, a project manager wants a linked DWG to disappear from every project view. The reference will be needed again later, and its saved path and placement should be retained.

Which action best meets the requirement?

  1. Remove the DWG from Manage Links and link it again after the internal review is complete.
  2. Unload the DWG from the CAD Formats tab of Manage Links and reload it when needed. (correct answer)
  3. Hide the DWG by element in the active view and propagate that setting to all project views.
  4. Turn off Imported Categories in Object Styles and restore the category after the review.
Explanation: When working with linked files in Revit, the key distinction to understand is the difference between visibility, existence, and load state. Questions like this test whether you know how to temporarily suppress a linked file without destroying its relationship to the project. The Manage Links dialog (Insert tab) gives you precise control over every linked file. Within the CAD Formats tab, each linked DWG has an Unload option that removes the file from display across all views simultaneously while preserving its path, placement, and all settings. When the internal review ends, a single Reload restores everything exactly as it was. This makes B the correct answer — it's non-destructive, project-wide, and fully reversible without rework. A is wrong because removing a link from Manage Links permanently severs the reference. When you re-link it later, you must re-establish the path and reposition it, which defeats the requirement to retain saved path and placement. C is tempting but flawed — hiding by element only affects the active view, and while you can propagate visibility overrides using View Templates, this is a view-by-view workaround rather than a single project-wide toggle. It also risks inconsistency. D misunderstands Object Styles: turning off imported categories affects all imported/linked CAD files of that category type globally, lacks precision, and isn't the intended use of that tool. A useful study rule: when a Revit question mentions "retain" and "all views," think Manage Links → Unload. It's the cleanest, most reversible solution for temporarily suppressing linked files.

Question 3

A linked DWG is visible in a coordination plan but not in a permit plan. Both views cover the same level, and the link is not set to Current view only. In the permit plan, the Imported Categories controls in Visibility/Graphics are disabled because a view template controls them.

What should be checked first to make the DWG visible while preserving the office's template-based standards?

  1. Edit the assigned view template and enable the required DWG or layers under Imported Categories. (correct answer)
  2. Change the DWG positioning method to Center to Center and reload it into the permit plan.
  3. Open Manage Links and enable a permit-plan visibility option for the linked CAD reference.
  4. Convert the CAD link to an import so its layers are no longer controlled by the template.
Explanation: When a linked DWG appears in one view but not another in Revit, and Visibility/Graphics controls are grayed out, the culprit is almost always a view template. View templates override per-view settings, which is why the Imported Categories panel is disabled in the permit plan — the template owns those settings. The right approach is to work within the template system, not around it. Since the template controls Imported Categories, the correct fix is A: open the assigned view template and enable the DWG's category or its specific layers there. This restores visibility while keeping the template-based workflow intact — every view using that template benefits from a consistent, managed change. B is wrong because positioning methods like Center to Center affect how the DWG is placed in model space, not whether it's visible in a particular view. Changing it wouldn't toggle visibility and wouldn't address the template override at all. C is a common trap. Manage Links controls whether a linked file is loaded, unloaded, or reloaded globally — it has no per-view or per-template visibility setting. The DWG is clearly loaded since it shows up in the coordination plan. D would break template-based control entirely. Converting a link to an import makes it a permanent part of the file and removes it from the linked CAD workflow. This defeats the purpose of maintaining office standards and is a destructive workaround. The key study takeaway: whenever controls in Visibility/Graphics are grayed out, trace the override to its source — usually a view template. Always edit the template itself rather than trying to bypass it.

Question 4

A current-view-only DWG is linked into a floor plan as a tracing reference. Its dense hatch patterns obscure Revit walls and annotations, but the CAD graphics must remain visible beneath the Revit graphics.

Which link option most directly establishes the required display order?

  1. Set the DWG to Foreground so its hatch patterns remain above the Revit model graphics.
  2. Set the DWG colors to Invert so the hatch patterns move behind the Revit annotations.
  3. Set the DWG to Background so the Revit model graphics display over the CAD reference. (correct answer)
  4. Set the positioning to Origin to Origin so the Revit walls take drawing-order priority.
Explanation: Whenever you see a Revit question involving a linked CAD file and visibility conflicts, focus on drawing order controls — specifically the Foreground/Background setting found in the CAD link's properties or the Visibility/Graphics Overrides dialog. In Revit, a linked DWG can be placed in one of two display layers: Foreground (drawn on top of Revit model graphics) or Background (drawn beneath them). When your goal is to keep CAD graphics visible as a tracing reference without obscuring Revit walls and annotations, setting the link to Background is the direct solution. Revit then renders all native model elements — walls, doors, annotations — on top of the CAD file automatically. This is exactly what option C describes, making it the correct answer. Option A is the opposite of what you need. Setting the DWG to Foreground places it above Revit graphics, which is precisely what causes the hatch-pattern obstruction you're trying to solve — not fix. Option B is a trap. Inverting DWG colors affects color display only; it has no influence on the stacking order between CAD and Revit graphics. Hatch patterns would remain in the same drawing layer regardless. Option D confuses positioning with display order. Origin to Origin is a placement method that aligns coordinate systems — it carries no logic that would change which graphics render on top. A useful study tip: on Revit exam questions about CAD link visibility, always distinguish between what you see (color, line weight overrides) and where in the stack you see it (Foreground vs. Background). These are separate controls that solve different problems.

Question 5

A consultant states that a DWG was drawn in millimeters. When it is linked using automatic unit detection, the reference appears at an obviously incorrect scale, although its insertion point is in the expected area.

Which adjustment most directly addresses the problem during the linking operation?

  1. Choose Black and White so Revit interprets the DWG using project display units.
  2. Change the positioning method from Origin to Origin to Center to Center.
  3. Enable Current view only so the DWG inherits the active view's drawing scale.
  4. Specify Millimeters for Import Units instead of relying on automatic unit detection. (correct answer)
Explanation: When linking or importing a DWG into Revit, one of the most critical settings is Import Units, which tells Revit what unit system the source geometry was authored in. If this is set incorrectly — or left to "Auto-Detect" when the file's embedded unit metadata is unreliable — Revit will scale the geometry incorrectly, making a building appear the size of a postage stamp or a continent. In this scenario, the consultant confirmed the file was drawn in millimeters, yet automatic detection is producing a wrong scale. The fix is straightforward: manually specifying Millimeters for Import Units during the link operation overrides any faulty auto-detection and forces Revit to interpret the coordinate values at the correct scale. That makes D the most direct solution. A is wrong because the Black and White setting controls color display, not unit interpretation — it has no effect on geometry scale whatsoever. B is a red herring: changing the positioning method from Origin to Origin to Center to Center affects where the DWG is placed in the model, not how large it appears. The question even notes the insertion point is already in the expected area, confirming positioning isn't the issue. C is incorrect because "Current view only" restricts which views display the linked file — it does not inherit or adjust drawing scale, and it certainly doesn't resolve a unit mismatch. As a study tip: on Revit exam questions involving DWG links appearing at the wrong size, always think Import Units first. Scale problems are unit problems, not positioning or display problems.

Question 6

A linked DWG uses several bright layer colors that are useful to the consultant but are unsuitable for the Revit construction documents. The Revit team wants all CAD lines displayed monochromatically without editing the consultant's source file.

Which color option should be selected for the CAD link?

  1. Preserve, because Revit maps the source colors to monochrome line weights when views are printed.
  2. Invert, because Revit replaces every source layer color with black in all project views.
  3. Black and White, because Revit displays the linked CAD colors as monochrome graphics. (correct answer)
  4. Halftone, because Revit converts the DWG's colored layers to a black monochrome display.
Explanation: When working with linked CAD files in Revit, you have several color override options that control how the imported geometry appears in your project views. The key concept here is understanding what each override mode actually does to the source layer colors — and how that differs from options that only affect printing or apply unrelated visual effects. The Black and White option (C) is the correct choice because it directly overrides all layer colors from the linked DWG and displays every line as monochrome graphics within Revit's canvas itself. This means no editing of the consultant's file is required, and the change takes effect immediately in project views — exactly what the scenario demands. Choice A is tempting but incorrect. The Preserve option keeps the original source layer colors intact in Revit's display; any monochrome behavior you might associate with printing is controlled separately through print settings, not through this color override. It does not solve the display problem described. Choice B is a misconception about what Invert does. Invert reverses the hue of each color (turning red to cyan, blue to orange, etc.) rather than converting everything to black. It would actually produce an equally colorful — just differently colored — result, which is the opposite of monochromatic. Choice D confuses two separate concepts. Halftone reduces the visual weight of the link by making it appear faded or ghosted, simulating an underlay. It does not convert colors to monochrome. As a study tip, remember that in Revit's CAD link properties, Black and White is specifically the option for monochrome display — don't conflate it with print settings or halftone, which serve entirely different purposes.

Question 7

A detail DWG is needed as a tracing reference only in the active Level 1 floor plan. It must not appear in the Level 2 plan, elevations, sections, or 3D views.

Which setting should be enabled when the DWG is linked?

  1. Current view only, so the DWG is created as view-specific content in the active plan. (correct answer)
  2. Orient to View, so the DWG follows the orientation of every orthographic project view.
  3. Auto - Center to Center, so the DWG is limited to the view where it is positioned.
  4. Correct lines that are slightly off axis, so the DWG is excluded from other model views.
Explanation: When linking external files into Revit, one of the most important decisions you'll make is whether the content should appear across the entire project or only within a single view. This distinction is controlled at the moment of import through the "Current view only" checkbox in the Link CAD dialog. Enabling option A — Current view only — is the correct choice here. When this setting is active, Revit places the DWG as view-specific, meaning it lives exclusively in the active view (in this case, the Level 1 floor plan) and is invisible everywhere else: other floor plans, elevations, sections, and 3D views. This is exactly the behavior the scenario requires for a tracing reference. The distractors each target a different, real Revit setting — but none of them control view visibility. Option B, "Orient to View," adjusts the coordinate orientation of the linked file so it aligns with the project's view rotation; it has no effect on which views display the file. Option C, "Auto - Center to Center," is a positioning method that centers the DWG relative to the model's center point — it does not isolate the file to one view. Option D, "Correct lines slightly off axis," is a cleanup tool that snaps near-orthogonal lines to true horizontal or vertical; it has nothing to do with view visibility or placement scope. A useful rule of thumb: if a question asks about restricting a linked CAD file to a single view, think "Current view only." If it asks about where the file is placed in space, think about the positioning options like Center to Center or Origin to Origin.

Question 8

A DWG contains many layers. Only two layers are needed in the current coordination plan, but additional layers may be required in later views. The team wants to avoid relinking the DWG when those layers become necessary.

Which workflow provides the greatest future flexibility?

  1. Import all layers into the current plan, then convert required layers into model line categories.
  2. Link only the two required layers, then reveal the excluded layers later through Object Styles.
  3. Link only visible CAD layers, then use Manage Links to load omitted layers into selected views later.
  4. Link all layers, then control which layers are visible per view using Imported Categories in Visibility/Graphics. (correct answer)
Explanation: When working with linked CAD files in Revit, the key principle to understand is that linking (not importing) is always preferred for coordination workflows, and the goal is to maximize control without requiring file management workarounds later. Linking all layers and then managing their visibility through Visibility/Graphics Overrides → Imported Categories (answer D) is the correct approach because it keeps every layer available in the project from the start. You can suppress unwanted layers per view immediately, and when a future view needs additional layers, you simply adjust that view's Visibility/Graphics settings — no relinking, no file changes, no coordination disruption. The flexibility lives entirely in view-level controls. Answer A fails because importing (rather than linking) permanently embeds the CAD geometry into the Revit file and inflates file size. Converting layers to model line categories also loses the connection to the source DWG, making updates impossible. Answer B is based on a misconception: when you link a CAD file, you cannot "reveal excluded layers later through Object Styles." Object Styles controls Revit's native categories, not which CAD layers were included at link time — if a layer wasn't linked, it simply doesn't exist in the project. Answer C similarly misrepresents how Manage Links works; it handles file-level operations like reloading or unloading entire links, not selectively loading individual layers into specific views. A useful rule of thumb: link, don't import, and link everything when layer needs are uncertain. Let Visibility/Graphics do the filtering work per view — that's exactly the flexibility Revit is designed to provide.

Question 9

A linked survey DWG contains the layers C-ROAD, C-TREE, and C-TEXT. In one presentation plan, the road and tree graphics must remain visible, but C-TEXT must be hidden. Other views must continue showing all three layers.

What is the most appropriate action in the presentation plan?

  1. Open Visibility/Graphics, expand the DWG under Imported Categories, and turn off C-TEXT for that view only. (correct answer)
  2. Open Manage Links, select the DWG, and unload C-TEXT from the link for the current view.
  3. Select the linked DWG and use Hide in View by Elements to hide the C-TEXT layer within it.
  4. Open Object Styles, locate Imported Objects, and disable C-TEXT across the entire project.
Explanation: Whenever you see a Revit question about controlling visibility for a linked file in only one view, your focus should land immediately on Visibility/Graphics Overrides (VG) — specifically how Revit handles imported and linked CAD categories on a per-view basis. Revit stores linked DWG layers under Imported Categories within each view's Visibility/Graphics dialog. Because VG settings are view-specific by default, you can expand the linked file's entry, find C-TEXT, and uncheck its visibility — hiding it in that presentation plan alone while every other view remains untouched. That's exactly what A describes, making it the correct and most precise action. B is wrong because Manage Links controls whether the entire linked file is loaded or unloaded for the whole project — there is no per-layer, per-view toggle there. Unloading the link would remove all three layers everywhere, not just C-TEXT in one view. C is a tempting trap. "Hide in View > Elements" works for Revit model elements, but a linked DWG is treated as a single import instance, not as individual layer elements. You cannot isolate and hide just one layer (C-TEXT) using that command — you'd hide the entire DWG object. D is wrong because Object Styles changes affect the entire project globally. Disabling C-TEXT there would suppress it in every view simultaneously, violating the requirement that other views continue showing all three layers. Your study tip: remember that VG Overrides = per-view control, while Object Styles = project-wide defaults. Any time a question asks for view-only visibility changes to a linked CAD file, navigate straight to VG → Imported Categories.

Question 10

A linked civil DWG is reported as not found after the consultant reorganizes the project folders. The revised DWG contains updated geometry, but the Revit link must retain its existing placement and view overrides.

Which workflow should the Revit user apply?

  1. Use Reload so Revit searches the model's folder structure and automatically locates the moved DWG.
  2. Use Reload From to browse to the moved DWG and update the existing link's stored path. (correct answer)
  3. Remove the missing link and create a new link using the same positioning option as before.
  4. Import the moved DWG into the same view and transfer the old link's graphical overrides.
Explanation: When managing linked files in Revit, the critical distinction is between reloading a link (refreshing it from its stored path) and relocating a link (updating where Revit looks for the file). Questions about missing links after folder reorganization are really testing whether you understand how Revit stores and resolves file paths for linked content. Reload From is the correct tool here because it lets you manually browse to the file's new location and update the stored path Revit uses going forward. Crucially, it preserves everything already established for that link instance — its placement coordinates, pinning, and any view-specific visibility or graphic overrides. This is exactly what the scenario requires: updated geometry plus retained settings. Option A is tempting but wrong. Reload attempts to refresh the link using the currently stored path, which is the old, now-invalid location. Since the consultant moved the file, Revit cannot find it automatically — Reload will simply fail again without any path correction. Option C introduces unnecessary risk. Removing the link and re-linking destroys the existing instance, meaning you would have to manually re-establish placement and re-create all graphical overrides from scratch — the opposite of what the scenario asks. Option D confuses linking with importing. Importing embeds geometry permanently and loses the live-update relationship with the consultant's file. Graphical overrides from a link also cannot be transferred to an import this way; the two workflows are fundamentally different. A practical tip: whenever you see "missing link" paired with "retain existing settings," your answer is almost always Reload From — it updates the path without disrupting any established instance properties.