- Which workflow restores that instance without changing the visibility of other furniture?
Answer: Enter Reveal Hidden Elements, select the hidden instance, and choose Unhide in View > Elements.
Revit has two distinct visibility systems that you must learn to distinguish: temporary overrides (Isolate/Hide in View tools that disappear when you end the session or reset) and permanent element-level overrides (Hide in View > Elements, which persist until explicitly reversed). This question tests whether you know how to undo a permanent, element-specific hide — not a category-level one.
Because the instance was hidden via Hide in View > Elements, only that specific element is affected. The Furniture category itself is still visible, so the override lives at the element level, not the category level. The only way to reverse it is to first see the hidden element, then unhide it at the same level it was hidden. Reveal Hidden Elements mode (the lightbulb icon at the bottom of the view) does exactly this — it temporarily tints hidden elements magenta so you can select them. Once selected, Unhide in View > Elements removes the override from that instance alone, leaving all other furniture untouched. That makes D the correct workflow.
A is wrong because isolating the Furniture category is a temporary override tool — it has no effect on permanently hidden elements, which won't even appear during temporary isolation. B is wrong because toggling the category off and on in Visibility/Graphics affects the entire Furniture category globally in that view, which changes visibility for all furniture, not just the missing instance. C is wrong because "Select All Instances > Visible in View" only finds elements currently visible — a permanently hidden instance is invisible and therefore unselectable by this command.
As a study tip: whenever a question mentions a single element being hidden versus an entire category, that's your signal that the answer lives in Reveal Hidden Elements, not Visibility/Graphics.
- Which action should the user take to make the filtered walls visible in that plan?
Answer: Modify or disable the applicable filter in Visibility/Graphics, or change the walls so they no longer meet its rule.
Whenever you see a question about hidden elements in Revit that can't be unhidden through the standard right-click menu, you should immediately think about the source of the hiding. Revit has distinct mechanisms for hiding elements, and each requires a different fix.
View filters work by evaluating element parameters against rules you define in Visibility/Graphics Overrides. When a filter hides an element, that element is not technically "hidden" in the traditional sense — it's being suppressed by a live rule that continuously applies. This is why Reveal Hidden Elements mode shows nothing to unhide: the filter isn't storing a hidden state on the element itself, it's simply refusing to display it based on logic. The correct fix, answer B, is to either modify or turn off the filter in Visibility/Graphics, or edit the walls so they no longer satisfy the filter's condition (e.g., assigning a Fire Rating value so the "blank" rule no longer matches).
Answer A is wrong because Temporary Hide/Isolate is a session-based tool unrelated to view filters, which are saved view properties — resetting it does nothing here. Answer C is wrong because the filter is hiding specific elements that match its rule, not the entire Walls category; category-level hiding is a separate toggle in Visibility/Graphics. Answer D is completely fabricated — pinning locks an element's position but has no connection to filter-based visibility or selection behavior.
The key study tip: always ask why an element is hidden before choosing how to unhide it. Revit's visibility system has layers — category, filter, and element-level — and each layer has its own solution.
- Which result should the user expect?
Answer: A 3D view is activated with a section box fitted around the selected elements; unrelated elements inside that box may remain visible.
When you encounter questions about the Selection Box tool in Revit, think carefully about what the tool actually controls: the view boundary, not element visibility. Selection Box creates a section box — a 3D clipping boundary — fitted tightly around whatever elements you had selected. It does not filter or isolate those elements from other geometry.
Here's what actually happens: Revit opens (or activates) the default 3D view and automatically sizes the section box to encompass your selected elements. Any other model elements that physically fall within that bounding region will also be visible. This makes A the correct answer — the section box is fitted to the selection, but nearby unrelated geometry inside that box remains fully visible.
B is wrong because Selection Box never duplicates a view or makes permanent changes to element visibility. "Permanently hidden" should be an immediate red flag — Selection Box is a temporary investigative tool, not a view management command. C describes something closer to an Isolate Element or Temporary Hide/Isolate workflow, not Selection Box; the tool has no awareness of which elements you "intended" to study versus bystanders caught inside the box. D describes a crop region adjustment in plan view, which is a completely different operation — Selection Box always targets the 3D view, never the current plan.
A useful memory anchor: think of the section box as a cookie cutter on a 3D view — it cuts away everything outside your selection's extents, but anything inside that shape is still visible. It controls the box boundary, not element-level visibility.
- What is the result after the user confirms the Filter dialog?
Answer: Only the currently selected walls and structural columns remain selected; model visibility is unchanged.
When working with selections in Revit, it's important to distinguish between tools that control what is selected versus tools that control what is visible. The Filter dialog falls firmly in the first category.
When you make a mixed selection and open the Filter dialog (accessible via the selection toolbar or right-click menu), Revit shows you a breakdown of every category represented in your current selection. Unchecking a category and confirming simply removes those elements from your active selection set — nothing more. In this scenario, clearing Floors and Room Tags leaves only the walls and structural columns selected, while the floors and room tags remain fully visible and unchanged in the model. That makes C the correct answer.
A is wrong because the Filter dialog has no effect on view visibility whatsoever. Hiding elements requires View > Visibility/Graphics, Hide in View, or Temporary Hide/Isolate — not the selection filter. B describes behavior similar to a "Selection Filter" preset or the selection filtering checkboxes in the bottom-right of the Revit interface (the small icons that toggle which categories are selectable), not the Filter dialog accessed during an active selection. Confusing these two features is a classic trap. D is wrong because the Filter dialog only narrows your existing selection — it never expands it to include additional elements from the view.
A useful memory aid: think of the Filter dialog as a strainer for your current selection. It only lets certain elements pass through; it doesn't add new ones or touch the view display.
- What is the most direct method for targeting the room-separation line without first hiding the wall or the link?
Answer: Press Tab to cycle through nearby selectable candidates, then click when the line prehighlights.
When working in a crowded Revit view where multiple elements overlap near your cursor, the challenge isn't just selecting — it's targeting the right element. Revit's Tab key cycling is the core tool designed exactly for this situation, and that's what this question is testing.
When you hover your cursor over a dense area, Revit prehighlights whichever element it detects first based on its internal priority. Pressing Tab shifts that prehighlight to the next selectable candidate in the stack — you can keep pressing Tab to cycle through all overlapping elements (walls, room-separation lines, linked elements, etc.) without clicking anything. Once the room-separation line prehighlights, a single click locks in that selection. This is the most direct, non-destructive method, making C the correct answer.
A is wrong because Shift+click adds to or removes from an existing selection — it doesn't cycle through overlapping candidates during prehighlighting. Using Shift here would alter your selection set, not help you target an element.
B is a misuse of the Filter dialog. Filter works after you've already made a selection to remove unwanted categories — it cannot preemptively restrict what gets prehighlighted or clicked in the canvas.
D contains a false premise. Pressing Esc doesn't toggle link selection on or off; it cancels active commands or deselects. Controlling link selectability is done through the Selection toggles in the status bar, not Esc.
Study tip: Whenever you see a Revit question about selecting overlapping elements, Tab cycling is almost always the answer. Think of Tab as a "next candidate" button — memorize it as your precision-selection shortcut.
- Which drag direction should the user choose if doors and windows that are only partially enclosed must be excluded before applying the selection filter?
Answer: Drag from left to right, and then retain only Doors and Windows in the selection filter.
Whenever you see a Revit selection question involving partial versus full enclosure, your first instinct should be to think about crossing selection vs. window selection — this is the core concept being tested here.
In Revit, dragging left to right creates a window selection, which captures only elements that are entirely within the selection boundary. Dragging right to left creates a crossing selection, which captures any element that the boundary touches or crosses, including partially enclosed elements. Since the question asks you to exclude partially enclosed doors and windows, you want only fully enclosed ones — making a left-to-right window selection the right starting move.
Once you've made that window selection, you apply the Filter tool to narrow down to Doors and Windows only, removing walls, furniture, and anything else caught inside the boundary. That's exactly what B describes, making it the correct answer.
A is wrong on two levels: right-to-left (crossing) would include partially enclosed elements — the opposite of what you want — and clearing only Walls still leaves other unwanted categories selected. C makes the same directional mistake as A; even with the correct filter strategy afterward, the crossing selection already brought in partially enclosed doors and windows you're trying to avoid. D uses the correct left-to-right direction but clears only Walls from the filter, which would leave every other non-door/window category (fixtures, furniture, etc.) still selected.
Study tip: Memorize the directional rule as "Right is tight" — drag right for tight/complete enclosure only. This single rule resolves most Revit selection direction questions quickly.
- What should the user do before resetting Temporary Hide/Isolate?
Answer: Choose Apply Hide/Isolate to View from the Temporary Hide/Isolate controls.
Whenever you see a question about view visibility in Revit, distinguish between temporary and permanent view-specific states — that distinction is exactly what's being tested here.
Temporary Hide/Isolate is a quick, session-based tool accessed from the View Control Bar (the sunglasses icon). It lets you hide or isolate elements on the fly without permanently affecting the view's visibility settings. The critical workflow detail is this: if you want that temporary state to "stick" as a permanent, view-specific override, you must select Apply Hide/Isolate to View from the same Temporary Hide/Isolate dropdown before resetting it. This converts the temporary condition into actual view-level hidden element overrides, making option C correct. Once applied, the isolated elements remain visible and everything else stays hidden, even after you reset the temporary mode.
Option A is incorrect because selection filters control which elements can be selected, not what is visible in a view — assigning one to a view template won't replicate a hide/isolate condition. Option B is backwards: Reveal Hidden Elements is used to find and restore hidden elements, not to preserve an isolation state. Working inside that mode to unhide elements would actually undo the coordination setup you want to keep. Option D is a trap — locking a view controls editing permissions, and saving the project while temporary isolation is active does not convert it to a permanent override; closing and reopening the file would simply reset it.
Remember: Apply Hide/Isolate to View is the bridge between temporary and permanent visibility — memorize it as the "commit" command for the Temporary Hide/Isolate workflow.
- Which change is required to make the linked model instance selectable while leaving it pinned?
Answer: Enable both Select Links and Select Pinned Elements, because the target is both linked and pinned.
Whenever you see a Revit selection question involving a linked file, think in terms of stacked filters — Revit applies multiple selection controls simultaneously, and every applicable filter must be enabled before an element becomes selectable.
In Revit, the Selection toolbar (bottom-right of the screen) contains independent toggles that act as gates. For a linked model instance, two separate conditions apply: the element is a link (requiring Select Links to be on) and the element is pinned (requiring Select Pinned Elements to be on). Because both conditions describe the element simultaneously, both toggles must be enabled at the same time. That's exactly what answer D states, making it correct.
Answer A fails because it assumes pinning only restricts movement, not selection. In Revit, pinning also blocks selection unless Select Pinned Elements is explicitly enabled — the pin acts as a full interaction lock, not just a position lock.
Answer B makes the opposite mistake: it assumes visibility guarantees selectability, and that links are always selectable. Visibility and selectability are independent in Revit. A visible element can still be blocked by a disabled selection filter.
Answer C introduces a red herring about "Select Elements by Face" and selecting links only at edges. Links can be selected anywhere on their bounding box or geometry when the correct toggles are active — this option conflates face-based selection (relevant for in-place families or floors) with link selection behavior.
Study tip: When a Revit element won't select, mentally run through the Selection toolbar toggles and ask how many apply to that element. If it's both linked and pinned, you need both switches — neither one alone is sufficient.
- Which command selects only the instances of that same window type that are currently visible in the active plan?
Answer: Select All Instances > Visible in View
When working with selections in Revit, it's important to distinguish between scope (where Revit looks) and visibility (what's currently shown). This question tests whether you understand how the "Select All Instances" tool respects view boundaries.
When you right-click a selected element in Revit, the Select All Instances submenu gives you two choices. Option A, Visible in View, restricts the selection to instances that are currently displayed within the active view's crop region — exactly what the scenario requires. Instances on other levels or outside the crop boundary are excluded automatically. This is the precise, targeted command for this situation.
Option B, In Entire Project, does the opposite — it selects every instance of that window type across all levels and views, including those hidden outside the crop region. That's too broad for what's being asked.
Option C, using Filter with only the Windows category retained, would work on whatever is already selected. It doesn't expand your selection to other instances of the same type, and it can't distinguish between different window types — it would keep all windows in the current selection, not just that one type.
Option D, Temporary Isolate > Element, doesn't select additional elements at all. It simply hides everything else in the view temporarily so you can focus on what's already selected. It changes visibility, not selection scope.
As a study tip, remember the Visible in View vs. In Entire Project distinction as a scope toggle. Exam questions will often include distractors that change visibility (like Isolate) to trick you into confusing display control with selection control.
- Which statement correctly describes the resulting visibility?
Answer: Only the two selected door instances are hidden in the active elevation; other instances remain unaffected.
Whenever you see a question about visibility in Revit, the key distinction to hold in mind is the scope of what you're hiding: a category, a type, or specific element instances — and where that change applies.
Hide in View > Elements is a view-specific, instance-specific command. When you select two door instances and apply it, Revit hides exactly those two elements in exactly the active view. Nothing else changes. Other door instances of the same type stay visible in that elevation, and those two hidden doors remain fully visible in every other view in the project. This makes B the correct answer — only the two selected instances are hidden, only in the active elevation.
Choice A is tempting but wrong: hiding elements does not act on the entire type. "Hide in View > Elements" targets the selected instances, not all instances sharing that type. If you wanted to hide all instances of a type in a view, you'd use Hide in View > By Element Type instead.
Choice C describes hiding an entire category — that would be done through Visibility/Graphics Overrides (VG) by unchecking the Doors category. Selecting two elements and using "Hide in View > Elements" never touches the category setting.
Choice D inverts how Revit works. View-specific overrides are, by definition, local to the view. There is no "Hide in View" command that propagates across all views; project-wide visibility would require a different workflow, such as modifying Filters or phase settings.
As a study tip, remember the phrase "in View" — any Revit command containing those words affects only the active view, never the whole project.
