Autodesk Revit Quiz: Interference Checks
10 questions · exam conditions
0:00
Interference ChecksQuestion 1 of 10

A structural beam physically overlaps a concrete column at its supported end. The elements were intentionally combined with Join Geometry, and the joint is valid. A separate unjoined beam passes through a duct.

When the appropriate categories are checked, which result is most likely?

Both intersections are reported because every overlap of solid geometry is treated as an interference.
Only the joined beam-column condition is reported because joined geometry receives additional checking.
Neither condition is reported because structural framing is excluded whenever a join exists elsewhere.
The unjoined beam-duct intersection is reported, while the valid joined beam-column condition is generally omitted.
← Back to quizzes

Autodesk Revit Quiz

Autodesk Revit Quiz: Interference Checks

Practice Interference Checks 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 Interference Checks, 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 beam physically overlaps a concrete column at its supported end. The elements were intentionally combined with Join Geometry, and the joint is valid. A separate unjoined beam passes through a duct.

When the appropriate categories are checked, which result is most likely?

  1. Both intersections are reported because every overlap of solid geometry is treated as an interference.
  2. Only the joined beam-column condition is reported because joined geometry receives additional checking.
  3. Neither condition is reported because structural framing is excluded whenever a join exists elsewhere.
  4. The unjoined beam-duct intersection is reported, while the valid joined beam-column condition is generally omitted. (correct answer)
Explanation: Whenever you see a question about Revit's Interference Check tool, focus on one core principle: the tool is designed to flag unintentional clashes, not every instance of overlapping geometry. When you run Interference Check in Revit, the tool intelligently recognizes geometry that has been deliberately joined using the Join Geometry command. A joined beam-column condition represents an intentional, valid connection — Revit understands that the overlap was purposeful, so it generally omits this pair from interference results. The unjoined beam passing through a duct, however, has no such designation. Revit sees that overlap as a potential problem and flags it. This makes D the correct answer: the unjoined clash is reported, while the valid joined condition is typically excluded. Answer A is wrong because it describes a naive "flag everything" approach that would make Interference Check nearly useless in real structural models where joins are routine. Answer B gets the logic completely backwards — joined geometry is excluded from reporting, not given "additional checking." The join is precisely what tells Revit the overlap is intentional. Answer C invents a rule that doesn't exist; the presence of a join elsewhere in the model has no blanket effect on unrelated categories or elements. Exclusions are element-specific, not model-wide. For your study strategy, remember that Interference Check respects Join Geometry as a signal of design intent. A good way to internalize this: joining resolves the clash in Revit's logic, so it won't appear in the report. On the exam, if a scenario mentions a valid join, that intersection is almost certainly the one being omitted, not flagged.

Question 2

A coordinator exports an interference report to HTML and sends it to consultants. The next day, several elements are moved in the Revit model, but no new report is exported.

Which statement best describes the HTML report the consultants already received?

  1. It is a snapshot of the results at export time and does not update when the Revit model changes. (correct answer)
  2. It recalculates the conflicts whenever a recipient opens the file while connected to the project network.
  3. It updates element locations automatically but retains the original conflict count until Revit is reopened.
  4. It remains synchronized only if the recipients have the same linked-model paths as the coordinator.
Explanation: When you see a question about Revit's interference checking tools, think about the fundamental nature of exported reports: are they live documents or static snapshots? This distinction is central to understanding how coordination workflows operate. Revit's interference check generates results based on the model's state at the exact moment you run it. When you export that report to HTML, you're capturing a static snapshot — a frozen record of which elements were conflicting at that specific point in time. The HTML file has no connection to the Revit model whatsoever; it's a standalone document sitting on someone's hard drive or server. So when elements moved the next day, the HTML report the consultants received remained completely unchanged, still reflecting the original conflict data. That makes A correct. B is wrong because HTML files have no mechanism to communicate with Revit or recalculate anything. They're plain web documents — no live data connection exists, regardless of network access. C describes a behavior that simply doesn't exist in Revit; the software has no feature that selectively updates element locations within an exported HTML while preserving other values. This is a fabricated hybrid that sounds plausible but has no basis in how the tool works. D confuses interference reporting with linked-model path dependencies — linked model paths matter when opening a Revit project, not when reading a previously exported HTML report. A useful rule of thumb: any time Revit "exports" to a non-Revit format (HTML, PDF, IFC, etc.), treat the result as permanently disconnected from the source model. If the model changes, a new export is always required.

Question 3

Several sleeve families visibly intersect concrete walls. Although they are named "Pipe Sleeves," the families were created in the Generic Models category. A coordinator runs an interference check between Pipes and Walls, but the sleeves do not appear in the results.

Which change most directly tests the sleeve-wall intersections without first editing the families?

  1. Check Generic Models against Walls because interference selection follows assigned categories rather than family names. (correct answer)
  2. Check Pipes against Walls again after renaming each sleeve type to include the word "Pipe."
  3. Check Pipe Accessories against Walls because any family containing pipe-related geometry is included automatically.
  4. Check Walls against Walls because hosted Generic Models are evaluated as part of their wall hosts.
Explanation: Whenever you see a question about Revit's interference check, the key concept to keep in mind is that the tool filters elements strictly by Revit category, not by family name, nested geometry, or any visual appearance on screen. In this scenario, the sleeves were built as Generic Models families — that is their assigned category regardless of what they're named. When the coordinator ran the check between Pipes and Walls, Revit searched for elements belonging to the Pipe category. The sleeve families, being Generic Models, were invisible to that filter. Running the check between Generic Models and Walls directly targets those elements by their actual category, which is exactly why A is correct — no family editing required. B is wrong because renaming a family type changes only its label; it has zero effect on the category assignment that interference check uses. You could name a Generic Model "Pipe Supreme Deluxe" and it would still be filtered as a Generic Model. C is a trap that assumes Revit interprets geometry or intent — it does not. There is no automatic inclusion based on pipe-related content; only the assigned category matters. D misunderstands how hosted elements work. Even if a Generic Model is wall-hosted, Revit evaluates it as its own category (Generic Models) during interference checks, not as part of the wall's category. The study tip here: always ask "what category is this family assigned to?" before setting up an interference check. Family names and hosting relationships are irrelevant — category assignment is the only thing Revit sees.

Question 4

Two identical ducts cross a wall. At the first duct, the wall contains a modeled opening large enough to clear the duct. At the second duct, a drafting detail shows an opening, but no opening was modeled in the wall geometry.

What should a wall-versus-duct interference check report?

  1. It should report only the second duct because its apparent opening does not remove wall geometry. (correct answer)
  2. It should report both ducts because wall openings are ignored during interference calculations.
  3. It should report only the first duct because modeled openings are treated as separate interfering elements.
  4. It should report neither duct because both openings are represented somewhere in the project documentation.
Explanation: When working with interference checks in Revit, it's essential to distinguish between modeled geometry and drafted representations. Interference checks analyze actual 3D elements in the model — they cannot read 2D drafting details or infer intent from annotated drawings. Here's the key principle: a modeled wall opening (created with the Opening tool or a void cut) physically removes geometry from the wall element. When Revit runs an interference check between walls and ducts, it tests whether the duct's solid geometry overlaps with the wall's remaining solid geometry. If a real opening exists, there's no solid material where the duct passes — so no clash is reported. The first duct, therefore, clears the check correctly. The second duct is different. A drafting detail is purely a 2D annotation layer — it adds lines to a view but does nothing to the wall's 3D geometry. The wall is still fully solid where that duct passes through it. Revit sees solid wall intersecting solid duct and correctly flags it as an interference. Answer A captures this precisely and is correct. Answer B is wrong because wall openings are not ignored — properly modeled openings genuinely eliminate the geometry that would cause a clash. Answer C inverts the logic; modeled openings remove wall material rather than creating a new interfering element. Answer D reflects a dangerous misconception: documentation intent and model geometry are not the same thing, and Revit's interference engine only knows what's actually built in the model. Study tip: Whenever a Revit question contrasts "drafted" versus "modeled," assume only modeled elements affect geometry-based calculations like interference checks, quantity takeoffs, or schedules.

Question 5

A pipe intentionally passes through a wall at an approved penetration location. The geometry remains intersecting because the final opening will be coordinated later. The team has confirmed that this specific result should not continue distracting reviewers.

What is the most appropriate action in the interference-results workflow?

  1. Delete the result entry so the intersecting elements are also removed from their source models.
  2. Ignore the selected interference so the accepted element pair is suppressed from the report workflow. (correct answer)
  3. Hide the wall in the active view so the conflict is treated as resolved in future checks.
  4. Export the selected interference so the clash is automatically marked as approved in the model.
Explanation: When you encounter a question about managing interference check results in Revit, the key concept being tested is the difference between resolving a clash geometrically versus acknowledging it administratively within the report workflow. These are two very different things, and the exam loves to test whether you know which tools serve which purpose. The Ignore function in Revit's Interference Check dialog is specifically designed for exactly this scenario — when a clash is intentional or accepted, and your team simply wants to suppress it from appearing as an active concern in subsequent reports. Choosing B correctly applies the Ignore tool, which hides the selected result from the report without altering either element in any linked or source model. The pipe and wall remain exactly where they are, but reviewers are no longer distracted by the flagged pair. A is a critical trap: deleting the result entry does not delete the elements themselves, but more importantly, this confuses report management with model editing. You never remove physical geometry by manipulating clash results. C is wrong because hiding a wall in the active view is purely a visual display adjustment — it has no effect on interference check data, and the clash will reappear the next time the check is run. D misrepresents what the Export function does; exporting the interference report generates a spreadsheet for external documentation purposes, not an in-model approval mechanism. The study tip here: on Revit workflow questions, always distinguish between view-level changes (hiding, overriding), model-level changes (deleting, moving), and report-level changes (ignoring, exporting). The Ignore tool operates exclusively at the report level.

Question 6

An interference report lists five wall-pipe conflicts. A user edits the model and resolves two of them while leaving the report dialog open. The report still displays all five entries.

What should the user do to verify the remaining conflicts using the same check criteria?

  1. Click Show for each entry, because displaying a conflict recalculates the full report automatically.
  2. Export the report again, because exporting removes entries whose geometry no longer intersects.
  3. Refresh the interference results so Revit reevaluates all entries against the updated model geometry. (correct answer)
  4. Close and reopen the project, because interference results only update when the file is reopened.
Explanation: Whenever you see a question about Revit's Interference Check tool, remember that its results are static snapshots — the report captures a moment in time and does not automatically update as you edit the model. Understanding this behavior is the key to answering workflow questions like this one. When you edit geometry while the Interference Check dialog remains open, Revit does not silently recalculate in the background. The five entries stay listed regardless of what you've fixed. To see which conflicts genuinely remain, you need to click the Refresh button within the dialog. This triggers Revit to reevaluate all previously checked categories against the current model geometry, removing resolved conflicts and confirming which ones persist — all without closing and restarting the check. That makes C the correct action. A is wrong because clicking Show simply zooms the view to the conflicting elements so you can inspect them visually. It does not trigger any recalculation of the report data — the entry will still appear even if the geometry no longer intersects. B is a misconception about the Export function. Exporting writes the current (stale) report to an HTML file for documentation purposes. It reads from the existing results, not from a fresh geometry check, so resolved conflicts would still appear in the exported file. D is a common trap that exaggerates the limitation. While reopening the project does clear session data, it is a drastic and unnecessary step. Refresh accomplishes the same verification goal instantly without closing the file. Study tip: On Revit workflow questions, watch for options that confuse viewing tools (Show, Export) with recalculation tools (Refresh, rerun the check). They test this distinction frequently.

Question 7

An architectural model contains walls, and a loaded mechanical Revit link contains ducts. The mechanical link is visible and correctly positioned. The team wants to identify only ducts that physically intersect architectural walls.

Which interference-check configuration most directly produces the required results?

  1. Choose Current Project on both sides, then select Walls on one side and Ducts on the other.
  2. Choose Current Project for Walls and the mechanical link for Ducts, then run the check. (correct answer)
  3. Choose the mechanical link on both sides, then select Walls on one side and Ducts on the other.
  4. Choose Current Project for Ducts and the mechanical link for Walls, then run the check.
Explanation: When running an Interference Check in Revit, the tool lets you compare elements from two different sources — either the Current Project or any loaded Revit link. The key insight is that each element category must be drawn from the model where it actually lives. Walls exist in the architectural (current) project; ducts exist in the mechanical Revit link. Your interference check configuration must reflect that separation. B is correct because it correctly maps each element to its host: Current Project supplies the Walls, and the mechanical link supplies the Ducts. Revit can then cross-reference geometry between the two sources and flag only the cases where a duct physically intersects a wall — exactly what the team needs. A is wrong because selecting Current Project on both sides limits the check to elements within the architectural model only. Since the ducts live in the linked file, not the current project, they won't appear in that category list and the check produces no meaningful results. C fails for the opposite reason: choosing the mechanical link on both sides restricts the check to elements within that link. Walls are in the current project, not the link, so they're unavailable — you'd essentially be checking the mechanical model against itself. D inverts the correct mapping — it looks for Ducts in the Current Project and Walls in the mechanical link. Neither of those elements exists in the wrong model, so no intersections would be found. A reliable study tip: before configuring an Interference Check, mentally ask "Which model does each element live in?" Match the source to the element, and you'll always set up the dialog correctly.

Question 8

A structural Revit link was initially placed correctly, then moved 600 mm east in the host project to correct its coordination position. A duct in the host now intersects a linked beam at the beam's displayed location.

How will a host-duct versus linked-framing interference check evaluate the beam?

  1. It uses the beam's original link coordinates and ignores any positioning transformation applied in the host project.
  2. It compares element origins numerically and reports a clash only when both models share identical internal origins.
  3. It uses the linked model's current transformed placement in the host when testing the physical intersection. (correct answer)
  4. It cannot evaluate the beam until the link is bound and its elements are converted into native host-project geometry.
Explanation: When working with Revit interference checks involving linked models, the key concept to understand is how Revit handles link transformations. Every linked model can be repositioned, rotated, or mirrored within the host project, and Revit tracks this as a placement transformation matrix — separate from the link's internal coordinates. The Interference Check tool in Revit is transformation-aware. When you run a check between host elements and linked-model elements, Revit applies the link's current positioning transformation before testing physical intersections. So if your structural link was moved 600 mm east, Revit evaluates the beam exactly where it visually appears on screen — at its transformed location. This is why C is correct: the interference check uses the linked model's current, transformed placement in the host, and your duct will correctly register as clashing with the beam. A describes a behavior that doesn't exist in Revit — the tool never ignores the positioning transformation and falls back to original internal coordinates. That would make coordination workflows completely unreliable. B introduces a fictional requirement about shared internal origins; Revit's interference engine works on real-world geometry positions after transformation, not raw numerical origin comparisons. D is a common misconception worth watching out for: binding a link converts it to native geometry, but this step is absolutely not required for interference detection. Linked elements participate in clash detection in their linked state. As a study tip, remember that in Revit, what you see is what gets checked — the interference engine always respects the visual, transformed position of any linked model.

Question 9

In the active architectural plan, the Structural Framing category is hidden, and a loaded structural link is also hidden by the view template. Both remain loaded in the project. A user runs an interference check between current-project ducts and structural framing in the link.

How do the active view's visibility settings affect this interference check?

  1. Only framing visible before the view template was applied is included in the interference check.
  2. The check cannot run until the linked model and both categories are visible in the active view.
  3. The selected model sources and categories are checked even though they are hidden in the active view. (correct answer)
  4. The ducts are checked, but hidden framing is omitted because linked visibility controls govern clash detection.
Explanation: Whenever you see a question about Revit's Interference Check tool, remember this core principle: interference checking is a model-data operation, not a view-display operation. The tool queries geometry that exists in the project's database, independent of what any particular view happens to be showing. When you run an interference check, you select categories and model sources (current project, specific links) from the dialog. Revit then searches all loaded geometry matching those selections — regardless of whether those elements are hidden by view templates, visibility/graphics overrides, or category toggles in the active view. This is why C is correct: the duct-to-structural-framing clash detection runs against all relevant geometry in memory, and hidden elements are still fully present in memory. A is wrong because it introduces a false condition — "visible before the view template was applied" has no meaning in Revit's interference check logic. The tool never references view history or pre-template states. B is wrong because it confuses view visibility with tool prerequisites; you do not need elements visible in the active view to run a check. This is a common trap on this exam. D is wrong because it invents a rule that "linked visibility controls govern clash detection." Visibility settings in linked files affect display only — they carry no authority over interference check results. The study tip here: whenever a Revit question pairs a visibility/display concept with an analysis or documentation tool (interference check, schedules, tags), ask yourself whether the tool reads display state or model data. Most analytical tools read model data, making view visibility irrelevant to their output.

Question 10

A team uses Copy/Monitor for structural grids and levels. A mechanical duct later intersects a structural beam, but no monitored grid or level has changed.

Which workflow should be used to identify the new physical conflict?

  1. Run Coordination Review because it evaluates all geometric intersections involving monitored elements.
  2. Run an interference check between the duct and structural-framing categories in the relevant models. (correct answer)
  3. Reload the structural link because Copy/Monitor detects clashes only during a link reload operation.
  4. Add the duct to Copy/Monitor because only monitored model elements can participate in clash detection.
Explanation: When working with linked models in Revit, it's essential to distinguish between two separate collaboration tools: Copy/Monitor and Interference Check. Copy/Monitor tracks positional changes to specific elements (grids, levels, columns, etc.) and alerts you when a monitored element moves or is modified. It is not a clash detection tool — it never was. Physical geometric conflicts between building components require a completely different workflow. In this scenario, no monitored element has changed, so Copy/Monitor has nothing to report. The conflict is a new geometric intersection between a mechanical duct and a structural beam — a classic clash detection problem. The correct approach, answer B, is to run an Interference Check (found under the Collaborate tab) between the duct category in the mechanical model and the structural framing category in the linked structural model. This tool evaluates actual geometric overlaps between any selected element categories across models, which is exactly what you need here. Answer A is wrong because Coordination Review only surfaces alerts generated by Copy/Monitor — it reports on monitored element changes, not general geometric intersections. Answer C is a misconception: reloading a linked file updates geometry and can trigger Copy/Monitor alerts for changed monitored elements, but it does not run any clash detection. Answer D is incorrect because Copy/Monitor is designed for positional tracking of key reference elements, not for enrolling arbitrary building components into clash detection. The key study tip: remember that Copy/Monitor = tracking changes to reference elements, while Interference Check = detecting geometric clashes. Questions that describe a physical overlap between components are always pointing you toward Interference Check, regardless of what Copy/Monitor is doing.