Autodesk Revit Quiz: View Range And Crop
10 questions · exam conditions
0:00
View Range And CropQuestion 1 of 10

A floor plan has its Top plane at +10 ft+10\,\mathrm{ft}, Cut Plane at +4 ft+4\,\mathrm{ft}, Bottom plane at 0 ft0\,\mathrm{ft}, and View Depth at −2 ft-2\,\mathrm{ft}, all relative to the associated level. A category-visible model element lies entirely between −1.5 ft-1.5\,\mathrm{ft} and −1.0 ft-1.0\,\mathrm{ft}.

Assuming no category-specific visibility exception applies, how will the element typically display in the plan?

It will not display because all of its geometry is below the Bottom plane.
It will display in projection using the category's normal projection line style.
It will display using the line style assigned to elements beyond the primary range.
It will display as cut geometry because the View Depth acts as another cut plane.
← Back to quizzes

Autodesk Revit Quiz

Autodesk Revit Quiz: View Range And Crop

Practice View Range And Crop 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 View Range And Crop, 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 floor plan has its Top plane at +10 ft+10\,\mathrm{ft}, Cut Plane at +4 ft+4\,\mathrm{ft}, Bottom plane at 0 ft0\,\mathrm{ft}, and View Depth at −2 ft-2\,\mathrm{ft}, all relative to the associated level. A category-visible model element lies entirely between −1.5 ft-1.5\,\mathrm{ft} and −1.0 ft-1.0\,\mathrm{ft}.

Assuming no category-specific visibility exception applies, how will the element typically display in the plan?

  1. It will not display because all of its geometry is below the Bottom plane.
  2. It will display in projection using the category's normal projection line style.
  3. It will display using the line style assigned to elements beyond the primary range. (correct answer)
  4. It will display as cut geometry because the View Depth acts as another cut plane.
Explanation: Whenever you see a Revit plan view question, think in terms of the three-layer sandwich: the Primary View Range (Top plane down to Bottom plane), and the View Depth region that extends below it. Here's how those layers work: elements whose geometry intersects the Cut Plane appear as cut geometry. Elements that fall within the Primary Range but below the Cut Plane appear in projection using the category's normal projection style. Elements that fall below the Bottom plane but at or above the View Depth plane occupy a special zone — they still display, but Revit renders them using the "Beyond" line style (a separate subcategory typically shown as a thin or dashed line). In this question, the element sits between −1.5 ft-1.5\,\mathrm{ft} and −1.0 ft-1.0\,\mathrm{ft}. The Bottom plane is at 0 ft0\,\mathrm{ft} and the View Depth is at −2 ft-2\,\mathrm{ft}. The element is entirely below the Bottom plane but above the View Depth limit, placing it squarely in the Beyond zone. That makes C correct — it displays using the Beyond line style. A is wrong because being below the Bottom plane doesn't automatically hide an element; the View Depth extends visibility further down to −2 ft-2\,\mathrm{ft}. B is wrong because the normal projection style only applies to elements within the Primary Range, not the Beyond zone. D is wrong because the View Depth is not a cut plane — it never slices geometry; it only controls how far below the Bottom plane elements remain visible. Remember: View Depth = visibility extension, not a cut operation. Elements there show in "Beyond" style, not as cut or normal projection.

Question 2

Most of a floor uses the plan view's current range correctly. A small sunken seating area must show walls and fixtures located below the view's Bottom plane, but the rest of the plan must not gain the same additional depth.

Which workflow provides the required localized visibility with the least effect on the rest of the view?

  1. Lower the view's Bottom and View Depth, and then tighten the model crop around the seating area.
  2. Create a plan region around the seating area and assign it a locally adjusted view range. (correct answer)
  3. Enable an underlay for the lower level and restrict it with the annotation crop boundary.
  4. Create a scope box around the seating area and assign the scope box to the plan view.
Explanation: Whenever Revit questions involve showing geometry at a different depth in only part of a view, you should immediately think about Plan Regions — Revit's tool for applying a localized view range override without touching the rest of the plan. A Plan Region lets you draw a closed boundary over a specific area and assign it its own View Range settings — including a lower Bottom and View Depth — completely independent of the host view's range. In this scenario, you'd draw a Plan Region around the sunken seating area, lower its Bottom and View Depth to capture the walls and fixtures below the main cut plane, and leave every other part of the plan completely unaffected. That's precisely the "localized visibility with least effect" the question describes, making B the correct workflow. Here's why the other choices fall short: A lowers the entire view's Bottom and View Depth, which would expose subfloor geometry everywhere in the plan — the opposite of localized control. Tightening the model crop doesn't restore selective depth; it just hides portions of the view entirely. C uses an underlay, which displays an entire additional level as a ghosted reference — you can't restrict it surgically to one seating area using the annotation crop, and underlays aren't meant for showing construction elements at varying depths within a single level. D confuses scope boxes with view range control; scope boxes govern which views a datum element (grid, level, reference plane) appears in — they have no ability to adjust cut plane depth locally. Remember: whenever a question asks for partial or localized view range changes within a single floor plan, Plan Region is almost always the answer.

Question 3

A plan view is assigned to a scope box. Its model crop follows the scope box, but the crop boundary must be adjusted in only this view without changing any other views that use the same scope box.

What should be done before editing this view's crop boundary?

  1. Set the view's Scope Box property to None, display the crop region, and edit its boundary. (correct answer)
  2. Edit the shared scope box boundary, and then restore the other affected views individually.
  3. Disable Annotation Crop, display the crop region, and drag the model crop boundary.
  4. Convert the view to a dependent view, and then edit the shared scope box boundary.
Explanation: Whenever you see a question about crop regions and scope boxes in Revit, think about the relationship between the two: a scope box is a shared control that drives crop boundaries across multiple views simultaneously. The moment you edit the scope box itself, every view assigned to it will be affected — which is exactly what this scenario is trying to avoid. The correct approach is A. By setting the view's Scope Box property to None, you detach that view from the shared scope box entirely. The crop region doesn't disappear — it stays in place at its current boundary — but it's now independent and view-specific. You can then display the crop region and freely adjust it without touching any other view. This is the standard Revit workflow for breaking a single view free from a scope box while leaving all other views unaffected. Option B is the wrong direction entirely: editing the shared scope box boundary propagates changes to all views using it, which is the problem you're trying to prevent, not solve. Option C is a red herring — disabling the Annotation Crop only hides annotation-specific crop handles; it has no effect on the model crop's relationship to a scope box, so dragging the boundary would still be constrained or would affect other views. Option D misunderstands dependent views; converting to a dependent view changes how a view relates to a primary view for reference purposes, not how it interacts with scope boxes. A useful rule of thumb: in Revit, if you need a view to behave independently from a shared control, you must remove the link before editing — don't try to edit around it.

Question 4

A plan's model crop must continue to show the entire floor plate. Several tag heads near the perimeter are inside that model crop, but the documentation manager wants to hide them by moving the annotation crop inward from the model crop on all sides.

Which statement describes the appropriate response?

  1. Inset the annotation crop, since it can always be made smaller than the model crop when both crops are active.
  2. Use Hide in View or an annotation filter, since the annotation crop boundary cannot be set inside the model crop boundary. (correct answer)
  3. Inset the model crop first, because the annotation crop automatically preserves all model geometry outside it.
  4. Assign a smaller scope box, since it constrains annotations independently without altering the model crop extents.
Explanation: Whenever you see a question about crop regions in Revit, it helps to remember that views actually have two separate crop boundaries: the model crop (which clips what geometry is visible) and the annotation crop (which clips tags, dimensions, and other annotations). The critical rule governing these two boundaries is that the annotation crop cannot be positioned inside the model crop — it must always match or extend beyond the model crop boundary. This is exactly why B is correct. Since the annotation crop boundary cannot be inset past the model crop, the only legitimate ways to hide those perimeter tag heads — while keeping the model crop unchanged — are to use Hide in View, Override Graphics, or an annotation filter to suppress specific tags selectively. A is the most tempting distractor because it sounds geometrically logical — of course a smaller region fits inside a larger one. But Revit enforces a hard constraint: the annotation crop cannot be smaller than the model crop. If you try, Revit will simply prevent it or snap the annotation crop back to the model crop boundary. C confuses the behavior entirely. Shrinking the model crop would cut off visible floor plate geometry, which the scenario explicitly forbids. The annotation crop does not "preserve geometry outside it" — that's not how either crop type functions. D misrepresents scope boxes. Scope boxes do control crop region extents across multiple views simultaneously, but they constrain both model and annotation crops together and do not offer independent annotation-only control. Your study tip: remember that in Revit, the annotation crop is always bounded by the model crop — it can be equal to or larger, never smaller.

Question 5

A large floor plan must be divided between two sheets. Both sheet views must retain coordinated scale, view range, visibility settings, and ongoing model updates, but each sheet must show a different portion of the floor with its own annotation extent.

Which workflow best satisfies these requirements?

  1. Duplicate the plan twice as independent views and manually maintain matching settings in both copies.
  2. Create two dependent views and edit the model and annotation crop regions separately in each dependent. (correct answer)
  3. Place the same primary plan on both sheets and apply different viewport crops on each sheet.
  4. Create two plan regions in the primary view and place each region separately as a viewport.
Explanation: When a large floor plan needs to be split across multiple sheets in Revit, the core concept being tested is dependent views — a specialized view relationship designed exactly for this scenario. Dependent views are child views derived from a single primary (parent) view. Because they share the same view properties — scale, view range, visibility/graphic overrides, and phase settings — any change made to the primary view automatically propagates to all dependents. However, each dependent has its own annotation crop region, which controls what annotations and tags appear on that sheet without affecting the others. This is precisely what the scenario demands: coordinated settings with independent annotation extents. Option B is correct because creating two dependent views lets you split the floor plan using separate crop regions per sheet while guaranteeing that model updates and view settings stay synchronized through the parent view. Option A fails because duplicating as independent views breaks that synchronization entirely. You would have to manually update scale, visibility settings, and view range in both copies every time something changes — a fragile, error-prone workflow at odds with BIM principles. Option C is not how Revit works: a viewport crop is tied to the view itself, not to the sheet placement. You cannot place the same view on two sheets with different crops independently; the crop region is a view property, not a sheet property. Option D misunderstands plan regions, which are used to locally override the view range within a single view — they are not separate placeable viewports. Study tip: Whenever a Revit question mentions splitting a large floor plan across sheets while keeping settings coordinated, immediately think dependent views — they are Revit's built-in solution for exactly this challenge.

Question 6

A plan view has a view template assigned. The View Range controls are unavailable, but this one view needs a different cut plane while all other settings governed by the template must remain enforced. Other views using the original template must remain unchanged.

Which action is the most controlled solution?

  1. Temporarily hide the crop region, modify the cut plane, and then show the crop region again.
  2. Remove the template from the view, modify the cut plane, and leave all view properties uncontrolled.
  3. Duplicate the template, change its View Range, and assign the duplicate to this view. (correct answer)
  4. Edit the original template's View Range and override the change in every other assigned view.
Explanation: Whenever you see a question about view templates in Revit, think about scope of change: who else is affected, and what control do you retain? View templates let you enforce consistent settings across multiple views, but they become a challenge when one view needs a unique exception. When a view template is assigned, properties like View Range become locked — you can't edit them directly in the view. The cleanest solution here is to duplicate the template, adjust only the View Range in the copy, and assign that duplicate to this single view. This preserves every other controlled setting (the problem requires all other template settings stay enforced), leaves the original template untouched for every other view using it, and gives you a dedicated, reusable template for this special case. That's exactly what C does, making it the most controlled and professional workflow. A is wrong because hiding the crop region has no effect on the View Range cut plane — these are completely separate concepts. The crop region defines the visible boundary of the view, not the elevation of the cut plane. B is wrong because removing the template entirely abandons all enforcement. The question explicitly states that all other settings governed by the template must remain enforced — leaving the view uncontrolled violates that requirement. D is wrong because editing the original template changes every view assigned to it. You'd then have to manually override settings in potentially dozens of other views — the opposite of a controlled solution and extremely error-prone. As a study rule: when one view needs an exception but the template's other settings must hold, duplicate and specialize rather than modify globally or abandon control entirely.

Question 7

In a plan view, the Top plane is +8 ft+8\,\mathrm{ft}, the Cut Plane is +4 ft+4\,\mathrm{ft}, the Bottom plane is +1 ft+1\,\mathrm{ft}, and the View Depth is +2 ft+2\,\mathrm{ft}, all relative to the same level. The Top, Cut Plane, and Bottom settings must remain unchanged.

Which change both creates a valid view range and extends visibility far enough to include geometry at −2 ft-2\,\mathrm{ft}?

  1. Change the View Depth offset to −2 ft-2\,\mathrm{ft}, keeping the current associated level and leaving all other planes unchanged. (correct answer)
  2. Change the View Depth offset to +4 ft+4\,\mathrm{ft}, keeping the current associated level and leaving all other planes unchanged.
  3. Change the Bottom offset to +3 ft+3\,\mathrm{ft}, keeping the current View Depth and leaving the other planes unchanged.
  4. Change the Cut Plane offset to +2 ft+2\,\mathrm{ft}, keeping the current Bottom plane and leaving the View Depth unchanged.
Explanation: Whenever you see a View Range question in Revit, think of it as a vertical sandwich with strict hierarchy rules: Top ≥ Cut Plane ≥ Bottom ≥ View Depth. The View Depth extends visibility below the Bottom plane to catch geometry that would otherwise be invisible. Your goal here is to include geometry at −2 ft-2\,\mathrm{ft}, which means the View Depth level must reach at least −2 ft-2\,\mathrm{ft}. Choice A sets the View Depth offset to −2 ft-2\,\mathrm{ft}. Since the associated level is at 0 ft0\,\mathrm{ft} (implied), the View Depth plane lands exactly at −2 ft-2\,\mathrm{ft}. This satisfies the hierarchy — View Depth (−2 ft-2\,\mathrm{ft}) ≤ Bottom (+1 ft+1\,\mathrm{ft}) — and reaches the target geometry. This is the correct answer. Choice B sets the View Depth to +4 ft+4\,\mathrm{ft}, which is above the Bottom plane (+1 ft+1\,\mathrm{ft}), violating the hierarchy rule. It also moves the View Depth upward, not downward, so it never reaches −2 ft-2\,\mathrm{ft}. Choice C raises the Bottom offset to +3 ft+3\,\mathrm{ft}. This actually shrinks the visible range and moves everything further from −2 ft-2\,\mathrm{ft}. It does not extend visibility downward at all. Choice D lowers the Cut Plane to +2 ft+2\,\mathrm{ft}, which only affects where objects are cut, not how far down the view reaches. Geometry at −2 ft-2\,\mathrm{ft} would remain outside the view range entirely. As a study tip, always sketch the four planes on a quick vertical diagram when solving View Range problems — visualizing the hierarchy instantly reveals which adjustments are valid.

Question 8

A text note crosses an active annotation crop boundary. Part of the note's bounding area remains inside the annotation crop, yet the complete text note continues to display.

Which explanation best accounts for this behavior?

  1. Text notes are governed by the model crop whenever their insertion points are inside the view.
  2. Annotation crop affects only tag leaders, so untagged text notes are never removed by it.
  3. An annotation intersecting the annotation crop can display completely rather than being geometrically trimmed. (correct answer)
  4. The annotation crop is inactive whenever its boundary is hidden in the current view.
Explanation: When working with Revit views, it helps to distinguish between two separate crop boundaries: the model crop (which clips 3D geometry) and the annotation crop (which controls the visibility of annotations like tags, text notes, and dimensions). Questions about unexpected annotation visibility almost always hinge on understanding how the annotation crop handles elements that straddle its boundary. The key behavior to know is that Revit treats annotations as whole objects — it does not geometrically trim or clip them the way it might clip a wall or line. When a text note's insertion point falls inside the annotation crop boundary, Revit considers that annotation "inside" the view, and it displays the entire note, even if part of its bounding box extends beyond the crop. This is exactly what answer C describes, making it correct. Answer A is misleading because text notes are annotation elements, not model elements — they are governed by the annotation crop, not the model crop. Conflating the two crops is a classic trap. Answer B is simply false; the annotation crop absolutely affects text notes, not just tag leaders. Tags, text notes, and dimensions are all subject to annotation crop visibility rules. Answer D introduces a misconception about boundary visibility — hiding the crop boundary line in a view does not deactivate the crop itself; the crop continues to function even when its graphical boundary is turned off. For your study strategy, remember this rule: annotation crops hide or show, they never trim. If an annotation's insertion point is inside the boundary, the whole annotation appears, regardless of overflow. This "all-or-nothing" behavior distinguishes annotations from model geometry in Revit's display logic.

Question 9

In a section view with active far clipping, a required object is horizontally and vertically inside the crop region but lies beyond the current viewing depth. The current crop boundary already has the desired sheet composition.

Which adjustment should be made to reveal the object without changing the composed crop area?

  1. Increase the Far Clip Offset while leaving the crop boundary at its current extents. (correct answer)
  2. Increase the plan Cut Plane offset while leaving the section crop at its current extents.
  3. Expand the annotation crop because it controls section depth behind the cut plane.
  4. Widen the model crop because its horizontal extent also establishes the section depth.
Explanation: When working with section views in Revit, it helps to understand that three independent controls govern what you see: the crop region (left/right/top/bottom boundaries), the annotation crop, and the far clip plane (viewing depth). These three controls are entirely separate, so adjusting one does not affect the others. When an object falls within the crop region's horizontal and vertical extents but is simply too far back in depth, the culprit is the far clip plane. Increasing the Far Clip Offset — option A — pushes that depth boundary further away from the cut plane, bringing the object into the visible range without touching the crop boundary edges. Your sheet composition stays exactly as designed. Option B is wrong because the Cut Plane controls the height at which Revit "slices" through a plan view, not the depth of a section. Adjusting it in a section context doesn't extend how far back Revit looks. Option C is wrong because the annotation crop only controls the visibility of annotation elements (tags, dimensions, text) that extend beyond the model crop. It has no influence over the 3D depth of the view — it cannot reveal geometry behind the far clip. Option D is wrong because the horizontal extent of the model crop controls left-right framing only. Widening it would alter your sheet composition and still wouldn't push the far clip deeper. A useful rule of thumb: in Revit section views, think of depth as its own axis. If geometry is "in frame" but invisible, always check the Far Clip Offset before touching any crop boundary.

Question 10

In a plan view, Crop View is enabled and Crop Region Visible is disabled. Geometry in an adjacent structural bay does not display. The bay must be included while the view remains cropped to a controlled boundary.

Which sequence is most appropriate?

  1. Enable Annotation Crop, enlarge it around the bay, and leave the model crop unchanged.
  2. Enable Crop Region Visible only, because showing the boundary also restores nearby model geometry.
  3. Disable Crop View permanently, because a hidden crop boundary cannot be resized or reactivated.
  4. Enable Crop Region Visible, edit the model crop to include the bay, and keep Crop View enabled. (correct answer)
Explanation: Whenever you see a Revit question about view cropping, keep three distinct controls in mind: Crop View (the on/off toggle that actually clips model geometry), Crop Region Visible (whether the crop boundary line is shown on screen), and the crop boundary shape itself (which you must edit manually to change what's included). These three settings are independent of each other, and confusing them is exactly what most wrong answers exploit. The correct approach, D, works because the root problem is that the crop boundary simply doesn't include the adjacent bay — not that cropping is broken or that the boundary is hidden. You enable Crop Region Visible so you can see and select the boundary, then drag or reshape it to encompass the bay, then keep Crop View enabled so the view remains deliberately bounded. This preserves your controlled boundary while expanding it to show the needed geometry. Choice A is tempting but misguided — the Annotation Crop controls visibility of tags and annotations beyond the model crop, not the model geometry itself. Enlarging it won't bring structural elements into view. Choice B reflects a common misconception: making the crop boundary visible doesn't change what geometry is included — it only reveals the existing boundary line. The geometry is still clipped at its original edge. Choice C is simply wrong; a hidden crop boundary can absolutely be resized and reactivated. Disabling Crop View permanently removes your controlled boundary entirely, which contradicts the requirement to stay cropped. Study tip: On Revit exam questions about cropping, always ask yourself whether the issue is what's cropped, whether cropping is on, or whether the boundary is visible — these are three separate problems requiring three separate fixes.