Autodesk Revit Quiz: Creating Views
10 questions · exam conditions
0:00
Creating ViewsQuestion 1 of 10

A Level 2 floor plan contains carefully placed dimensions, tags, and text notes. A second Level 2 plan is required for a different documentation purpose. It must begin with the same annotations, but subsequent annotation and visibility changes must remain independent of the original view.

Which workflow best satisfies these requirements?

Duplicate the Level 2 plan using Duplicate and recreate the required annotations manually.
Duplicate the Level 2 plan using Duplicate with Detailing, then modify the new view independently.
Duplicate the Level 2 plan using Duplicate as Dependent, then assign it a different view template.
Create another floor plan for Level 2 and transfer the original annotations through a scope box.
← Back to quizzes

Autodesk Revit Quiz

Autodesk Revit Quiz: Creating Views

Practice Creating Views 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 Creating Views, 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 Level 2 floor plan contains carefully placed dimensions, tags, and text notes. A second Level 2 plan is required for a different documentation purpose. It must begin with the same annotations, but subsequent annotation and visibility changes must remain independent of the original view.

Which workflow best satisfies these requirements?

  1. Duplicate the Level 2 plan using Duplicate and recreate the required annotations manually.
  2. Duplicate the Level 2 plan using Duplicate with Detailing, then modify the new view independently. (correct answer)
  3. Duplicate the Level 2 plan using Duplicate as Dependent, then assign it a different view template.
  4. Create another floor plan for Level 2 and transfer the original annotations through a scope box.
Explanation: When working with Revit views, the key distinction to understand is how each duplication method handles view-specific elements like annotations, dimensions, and tags — and whether the duplicated view stays linked to the original or becomes independent. Duplicate with Detailing (option B) copies both the model geometry display and all view-specific elements (dimensions, tags, text notes) into a new, fully independent view. From that point forward, changes in the new view — added annotations, visibility overrides, view template assignments — have zero effect on the original Level 2 plan. This is exactly what the scenario requires. Option A uses plain Duplicate, which copies the view's display settings but leaves all annotations behind entirely. You'd be starting from scratch with detailing, which directly contradicts the goal of beginning with the same annotations. Option C, Duplicate as Dependent, creates a child view that shares view-specific elements with the parent. Annotations added to either view appear in both, and visibility changes propagate — the exact opposite of "independent." Assigning a different view template doesn't break this dependency for detailing elements. Option D is a fabricated workflow. Revit has no mechanism to transfer annotations between views through a scope box. Scope boxes control visibility extents for grids and levels, not annotation migration. A useful rule of thumb: think of the three duplication methods as a spectrum — Duplicate gives you no detailing, Duplicate as Dependent shares detailing, and Duplicate with Detailing gives you a fresh independent copy of everything. Match the method to how much independence you need.

Question 2

A large floor plan must be divided between two sheets. Both sheet views must display coordinated dimensions and tags from one primary plan, but each must show a different geographic portion of the building.

Which approach provides the required coordination with the least duplicated annotation work?

  1. Create two independent floor plans for the level and apply the same view template to both.
  2. Duplicate the primary plan twice with detailing and adjust each duplicate's annotation crop.
  3. Create two dependent views from the primary plan and assign different crop regions to them. (correct answer)
  4. Place the primary plan in two viewports and crop each viewport directly on its sheet.
Explanation: When a large floor plan must span multiple sheets in Revit, the key concept being tested is the difference between independent views and dependent views, and how each handles annotation coordination. Dependent views are child views linked to a single parent plan. Any annotation — dimensions, tags, text — placed in the parent automatically appears in all dependent views. Each dependent view can have its own crop region, letting you isolate a different portion of the building per sheet. This is exactly what the scenario requires: coordinated annotations across two sheet views showing different geographic areas with minimal duplicated effort. That makes C the correct approach. Option A creates two entirely independent floor plans. Annotations placed in one do not appear in the other, so you would have to recreate every dimension and tag manually — the opposite of efficient coordination. Option B, duplicating with detailing, also produces independent copies of the view. "With Detailing" preserves existing annotations in the duplicate, but any new annotation added afterward must be added separately to each view, breaking coordination going forward. Option D is a common misconception: you cannot place the same view in two viewports simultaneously in Revit. Each view instance can only live on one sheet at a time, so this approach isn't technically possible. A useful pattern to remember: whenever a Revit question mentions coordinated annotations across multiple sheets from one plan, think dependent views. They are purpose-built for this workflow — one source of truth for annotation, multiple crop regions for different sheet layouts. If you see "independent plan" or "duplicate," that's a signal the coordination will break down.

Question 3

An interior elevation marker in a room already creates elevation views in three directions. A fourth elevation is now required from the same marker, and the remaining directional control has not yet been used.

What should be done to create the fourth elevation while retaining the existing marker location?

  1. Select the marker and activate its unused directional control to generate the additional elevation view. (correct answer)
  2. Duplicate one existing elevation and rotate its crop region toward the remaining wall.
  3. Convert one existing elevation to a reference elevation and redirect its elevation head.
  4. Place a second elevation marker at the same location and hide its other directional controls.
Explanation: When working with interior elevation markers in Revit, it helps to understand that a single elevation marker can generate up to four elevation views — one for each cardinal direction it controls. Each direction is represented by a segmented arc around the marker, and each segment can be independently activated or deactivated. This question tests whether you understand how to use an existing marker's built-in directional controls before resorting to workarounds. The correct approach is A: select the existing marker and enable its unused directional segment. When you click the marker, you'll see checkboxes or toggleable arrowheads for each direction. Clicking the inactive one instantly creates a new elevation view associated with that same marker, keeping everything organized under a single reference point. This is exactly the tool Revit provides for this scenario — no duplication or workarounds needed. Option B is tempting but misguided. Duplicating an existing elevation and rotating its crop region doesn't create a properly associated view from the marker; it produces a disconnected copy that won't update the marker's directional indicators and clutters your view organization. Option C is incorrect because converting an elevation to a reference elevation changes its purpose — reference elevations point to views defined elsewhere and aren't meant to capture new geometry of their own. Option D is unnecessarily complex. Placing a second marker at the same location introduces redundancy and visual clutter on the plan. Hiding controls doesn't add functionality — it just obscures what's already there. As a study tip, remember that in Revit, the built-in object properties almost always provide the cleanest solution. If a tool already supports the task natively, using it beats any manual workaround.

Question 4

A building section has the correct horizontal and vertical crop extents. However, rooms farther behind the section line are omitted because the section's viewing depth is too shallow. Expanding the visible crop boundary does not reveal them.

Which adjustment should be made?

  1. Increase the section view's Far Clip Offset or move its far clip plane farther from the section line. (correct answer)
  2. Increase the section view's annotation crop so model elements behind the cut become visible.
  3. Extend the section line beyond the building so its perpendicular viewing depth is increased.
  4. Increase the plan view's view depth so the associated section inherits a deeper range.
Explanation: When working with section views in Revit, it helps to distinguish between the crop region (which controls what's visible left/right and up/down) and the far clip plane (which controls how deep into the model the view looks, perpendicular to the section line). The passage describes rooms that are hidden because the view isn't looking far enough behind the cut — that's a depth problem, not a boundary problem. The correct adjustment is A: increasing the Far Clip Offset moves the far clip plane away from the section line, extending the viewing depth and revealing elements that were previously outside the section's range. You can adjust this in the section view's Properties panel under "Far Clip Offset," or by dragging the dashed far clip line in the plan view. B is wrong because the annotation crop controls the visibility of tags and annotations, not model geometry. Expanding it won't bring hidden rooms into view. C confuses the length of the section line (its horizontal extent across the building) with its depth. Extending the section line sideways changes which portion of the building is cut, not how deep behind the cut the view reaches. D is a trap — plan view depth and section view depth are independent settings. A section view does not inherit its far clip range from the plan view that hosts it. A good rule of thumb: if elements are missing side to side, adjust the crop region; if they're missing front to back (depth), adjust the Far Clip Offset. Keeping these two axes mentally separate will save you on exam day.

Question 5

Plans on six levels must use matching model crop boundaries around one building wing. The project team also wants later boundary adjustments to be made once and reflected in all six plans.

Which workflow most directly provides this coordinated control?

  1. Assign the same scope box to all six plan views and edit the scope box whenever extents change. (correct answer)
  2. Apply the same view template to all six plans and update the crop boundary in the template when needed.
  3. Duplicate the first plan as dependent views and reassociate each dependent view with a different level.
  4. Place all six plans on one sheet and align their viewports using a shared guide grid.
Explanation: When a question asks about coordinating identical crop boundaries across multiple plan views — especially with the requirement that one edit updates all of them — you should immediately think about scope boxes, Revit's dedicated tool for controlling view extents across multiple views simultaneously. A scope box is a 3D annotation element that you draw in a plan view and then assign to multiple views via each view's properties. Once assigned, all six plans share the same crop boundary defined by the scope box. When you resize the scope box, every assigned view updates automatically — exactly the "edit once, update everywhere" behavior the question describes. This makes A the correct answer. B is tempting but flawed. View templates control many view properties, but the crop region boundary is typically not among the parameters transferred by a view template. Even if it were, templates don't provide the live, dynamic link that a scope box does — you'd have to manually re-apply the template each time. C describes dependent views, which are useful for dividing one large plan into multiple sheets (like a large floor plate split into quadrants). Dependent views share the same level, so reassociating them with different levels isn't how Revit works — each plan view is tied to its own level independently. D places views on a sheet and aligns viewports visually using a guide grid, which is a drafting/presentation tool. It does nothing to synchronize the actual model crop boundaries in the view definitions themselves. Remember: whenever you see "edit once, apply across multiple views," scope boxes are almost always the answer on Revit exam questions.

Question 6

In a floor plan, the global view range correctly displays most of the story. A small raised platform is above the plan's cut plane and is therefore missing. Changing the entire view range would cause unwanted overhead elements to appear elsewhere.

How should the platform be displayed without changing the view range for the rest of the plan?

  1. Create a detail callout around the platform and overlay its view on the original floor plan.
  2. Draw a Plan Region around the platform and assign an appropriate local view range. (correct answer)
  3. Add the platform level as an underlay and restrict the underlay to the platform boundary.
  4. Create a scope box around the platform and assign a different cut plane to that scope box.
Explanation: When a floor plan's view range works well overall but fails to capture an element at a non-standard height, Revit gives you a targeted tool rather than forcing you to compromise the entire view: the Plan Region. A Plan Region lets you draw a boundary around a specific area and assign it its own local view range settings — cut plane, top, bottom, and view depth — completely independent of the parent view's settings. This is exactly the right tool when a raised platform sits above the main cut plane but you don't want to pull the global cut plane higher and accidentally expose unwanted overhead elements elsewhere. B is correct because drawing a Plan Region around the platform and raising its local cut plane captures the platform geometry without affecting anything outside that boundary. A is wrong because a detail callout creates a separate, independent view — it doesn't overlay seamlessly onto the floor plan in a way that solves the display problem within the original view. Callouts are for documentation and detail, not for patching view range gaps. C is incorrect because underlays show an adjacent level's geometry projected below your current view, and they can't be masked or clipped to an arbitrary boundary like a platform footprint. Underlays also wouldn't place the cut at the right height for the platform. D is a common trap: scope boxes control which views a level/grid appears in and which views share crop region boundaries — they do not have their own cut plane settings and cannot override view range locally. Remember: whenever a question describes a localized height problem within a single floor plan view, Plan Region is almost always the answer.

Question 7

A floor plan requires an enlarged restroom plan whose crop is defined by a new callout boundary. The enlarged plan must be a newly created model view, not a pointer to an existing detail or drafting view.

How should the callout be created?

  1. Select the Callout tool, enable Reference Other View, and choose the parent floor plan.
  2. Duplicate the parent floor plan, then place a reference callout linked to that duplicate's full extents.
  3. Select an appropriate plan callout type, leave Reference Other View cleared, and draw the boundary. (correct answer)
  4. Create a drafting view first, then use a reference callout to define its model crop boundary.
Explanation: When working with callouts in Revit, the critical distinction is between a standard callout (which generates a brand-new model view) and a reference callout (which points to an existing view). Questions about enlarged plans will often hinge on this difference. Drawing a callout with Reference Other View cleared — option C — is exactly how you create a fresh, independent floor plan view scoped to the callout boundary. Revit automatically generates the new plan view, adds it to the Project Browser, and ties its crop region to the boundary you drew. This satisfies the requirement for a newly created model view of the restroom. Option A is the classic trap: enabling Reference Other View turns the callout into a pointer. It annotates the parent sheet with a callout bubble, but no new model view is created — it simply redirects viewers to an already-existing view. This is the opposite of what the question asks for. Option B compounds the problem by starting with a duplicate view (which is a model view, but already fully exists) and then placing a reference callout, adding unnecessary steps and still not producing the correct workflow. Option D is doubly wrong: drafting views are non-model, 2D-only environments with no crop boundary tied to model geometry, so a reference callout cannot define a model crop for them. A useful rule of thumb: "Reference Other View" = no new view created. Whenever an exam question specifies that a new model view must be generated, immediately rule out any workflow involving reference callouts or drafting views.

Question 8

A designer needs a static eye-level 3D view from a specified point in a lobby, aimed at the reception desk. The resulting view must exhibit perspective convergence rather than the parallel projection of an axonometric view.

Which method should the designer use?

  1. Open the default 3D view and use Orient to View to align it with the lobby floor plan.
  2. Use the Camera tool, place the camera position, and then define the target direction. (correct answer)
  3. Create an elevation at the camera position and enable perspective in the elevation properties.
  4. Create a walkthrough path with one key frame and convert the frame into an axonometric view.
Explanation: When working with Revit views, you need to distinguish between projection types: axonometric (orthographic) views preserve parallel lines and have no vanishing points, while perspective (camera) views simulate how the human eye actually sees space — with convergence toward vanishing points. Any question describing a "static eye-level view from a specific point with perspective convergence" is asking about Revit's Camera tool. The Camera tool (found on the View tab) is precisely designed for this scenario. You place the camera origin (the viewer's eye position) and then click to define the target point — in this case, the reception desk. Revit immediately generates a perspective 3D view with realistic convergence, and you can fine-tune the eye elevation and crop region afterward. This is the only native Revit tool that produces a static, positioned perspective view from a defined standpoint. That makes B the correct answer. A is wrong because the default 3D view is axonometric by default, and "Orient to View" simply reorients the camera angle to match a plan or elevation — it does not create a new positioned perspective view or enable perspective projection on its own. C is wrong because elevation views are orthographic by definition; there is no "enable perspective" property in elevation settings. Revit elevations cannot be converted to perspective projections. D is wrong on two counts: a walkthrough produces an animated path view, and converting a keyframe produces a perspective view — but the passage specifies the final view must be perspective, not axonometric, so "convert to axonometric" directly contradicts the requirement. Study tip: On Revit exam questions, the word "perspective" is your signal to think Camera tool — it's the only view type in Revit that inherently produces perspective projection from a defined eye point.

Question 9

A floor plan already exists for Level 4. The ceiling layout must now be documented in a separate view that looks upward and uses reflected ceiling plan behavior. No reflected ceiling plan currently exists for that level.

What is the appropriate way to create the required view?

  1. Duplicate the Level 4 floor plan and change its Discipline property to Coordination.
  2. Create a ceiling element on Level 4 and allow Revit to generate its documentation view.
  3. Create a new floor plan for Level 4 and reverse the view direction in its properties.
  4. Use Plan Views > Reflected Ceiling Plan and select Level 4 in the plan dialog. (correct answer)
Explanation: Whenever you see a question about creating a specific view type in Revit, focus on the distinction between view types — floor plans, ceiling plans, sections, elevations — because each one has a dedicated creation workflow and displays content differently, even when referencing the same level. A Reflected Ceiling Plan (RCP) is a purpose-built view type in Revit that simulates looking upward at the ceiling, displaying ceiling-hosted elements like light fixtures, diffusers, and ceiling grids. The correct way to create one is through the View tab → Plan Views → Reflected Ceiling Plan, then selecting Level 4 from the dialog. This generates a view with the correct cut plane orientation, visibility settings, and view template defaults specific to ceiling documentation. Option D describes this workflow exactly. Option A is wrong because duplicating a floor plan and changing its Discipline to "Coordination" only affects how categories are filtered — it does not flip the view direction or apply ceiling-plan behavior. You would still have a floor plan looking downward. Option B confuses modeling elements with documentation views; placing a ceiling object on a level does not automatically generate or configure any view. Revit does not create views from element placement. Option C is a plausible-sounding trap — there is no "reverse view direction" property in a floor plan's instance properties. Floor plans and RCPs are fundamentally different view families, and you cannot convert one into the other by editing properties. For the exam, remember: view type = view behavior. If the scenario requires a specific kind of plan view, always look for the dedicated creation command under View → Plan Views rather than trying to repurpose an existing view.

Question 10

An orthographic 3D view shows the entire building and is already placed on a coordination sheet. A second 3D view is needed to show only a vertical slice through a congested service zone. The original overall-building view must remain unchanged.

Which sequence best creates the required second view?

  1. Create a camera view inside the service zone and reduce its far clip offset to the slice thickness.
  2. Edit the original view's crop region, save its orientation, and place another viewport on the sheet.
  3. Duplicate the 3D view, hide all unrelated categories, and apply those settings through a view template.
  4. Duplicate the 3D view, enable Section Box in the duplicate, and adjust the box around the service zone. (correct answer)
Explanation: When working with 3D views in Revit, the key challenge is isolating a specific portion of a model without disturbing existing views already placed on sheets. The tool designed exactly for this purpose is the Section Box, a resizable 3D clipping boundary that trims the visible geometry to whatever extents you define. The correct approach, D, works because duplicating a 3D view creates an independent copy that shares no live connection to the original's settings. Once duplicated, enabling the Section Box in that copy and dragging its faces to frame only the service zone gives you a precise vertical slice — exactly what the coordination workflow requires. The original view on the sheet is completely untouched. A is tempting but wrong because a camera view produces a perspective projection, not an orthographic one. More importantly, a camera's far clip controls depth from the camera point — it cannot produce a clean vertical slice through a zone the way a Section Box can. B describes modifying the original view's crop region, which directly violates the requirement to leave the overall-building view unchanged. Editing then "saving orientation" doesn't create a separate independent view; it risks altering what's already on the sheet. C hiding categories addresses visibility, not geometry extents. Hiding categories removes object types entirely rather than spatially isolating a zone, so you'd still see fragments of unrelated geometry wherever those categories appear inside the service zone. View templates also control appearance, not spatial clipping. A useful rule of thumb: whenever a question asks you to isolate geometry spatially in a 3D view, think Section Box first. It's Revit's dedicated tool for exactly that task.