Autodesk Revit Quiz: Grids

10 questions · exam conditions

0:00

GridsQuestion 1 of 10

Four parallel grids, A through D, are constrained by one continuous aligned dimension whose equality control is enabled. The initial spacing between adjacent grids is $6\,\text{m}$ . Grid A is pinned, and grid D is moved $3\,\text{m}$ farther away from grid A.

Assuming the equality constraint remains active, what is the resulting spacing between adjacent grids?

Each bay remains

6\,\text{m}

, and grid A moves to absorb the difference.

The first two bays remain

6\,\text{m}

, and the last bay becomes

9\,\text{m}

All three bays become

7\,\text{m}

because the grids redistribute equally.

All three bays become

9\,\text{m}

because grid D moved outward.

← Back to quizzes

Autodesk Revit Quiz

Autodesk Revit Quiz: Grids

Practice Grids 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 Grids, 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

Assuming the equality constraint remains active, what is the resulting spacing between adjacent grids?

Each bay remains $6\,\text{m}$ , and grid A moves to absorb the difference.
The first two bays remain $6\,\text{m}$ , and the last bay becomes $9\,\text{m}$ .
All three bays become $7\,\text{m}$ because the grids redistribute equally. (correct answer)
All three bays become $9\,\text{m}$ because grid D moved outward.

Explanation: Whenever you see a question involving Revit's equality constraint on a dimension string, your first move should be to identify the total length being distributed and how many equal segments must share it. Here, four grids (A through D) create three bays. With grid A pinned and the equality control active, any change to the overall span is redistributed evenly across all three bays — Revit recalculates each segment automatically to maintain equal spacing. Initially, each bay is

6\,\text{m}

, giving a total span of

3 \times 6 = 18\,\text{m}

. When grid D moves

3\,\text{m}

farther from grid A, the new total span becomes

18 + 3 = 21\,\text{m}

. With equality active, that span divides evenly:

21 \div 3 = 7\,\text{m}

per bay. That confirms C is correct — all three bays redistribute to

7\,\text{m}

. A is wrong because grid A is explicitly pinned; it cannot move. The pinned constraint locks grid A in place, so it can never "absorb" the difference. B describes a scenario where no equality constraint exists — only the last bay stretches to accommodate the change. This would happen if equality were off, not on. D assumes only grid D's bay changes, misunderstanding what the equality constraint does. Moving grid D doesn't isolate the change to one bay; it triggers a full redistribution. As a study tip: always track how many segments fall under the equality dimension and remember that pinned elements are immovable anchors — the remaining grids shift to satisfy both the pin and the equal spacing.

Question 2

In the Level 1 plan, several grids have carefully adjusted 2D endpoints and selected end bubbles displayed. The Level 2 and Level 3 plans are parallel to Level 1 and should use the same datum presentation, but the grid model extents must not be changed.

Which workflow most directly applies the Level 1 presentation to the other plans?

Select the grids in Level 1, use Propagate Extents, and select Level 2 and Level 3. (correct answer)
Select the grids in Level 1, switch both endpoints to 3D, and reopen the other plans.
Copy the grids from Level 1 and use Paste Aligned to Selected Levels.
Create a view template from Level 1 and apply it to Level 2 and Level 3.

Explanation: When working with grids and levels in Revit, it's critical to understand the difference between 3D extents (the model's true geometry, shared across all views) and 2D extents (view-specific overrides that control how a grid appears in a single plan). Questions like this test whether you know how to synchronize that 2D presentation without disturbing the underlying model. Propagate Extents is the purpose-built tool for exactly this scenario. When you select grids in Level 1 and run Propagate Extents, Revit copies all 2D endpoint adjustments and bubble visibility settings to whichever parallel views you choose — Level 2 and Level 3 here — while leaving the 3D model extents completely untouched. That's why A is correct: it transfers only the view-specific presentation data, which is precisely what the question asks for. B is a trap. Switching endpoints from 2D to 3D doesn't propagate anything; it reverts Level 1's carefully crafted appearance back to the global model extents, potentially undoing all your work there. C is wrong because Copy/Paste Aligned to Selected Levels creates entirely new grid elements, duplicating the model geometry rather than sharing the existing grids. You'd end up with doubled grids and a corrupted model. D is partially tempting — view templates can control some visual properties — but they do not transfer 2D datum extents or bubble overrides. Template settings simply don't include that type of annotation-level datum customization. Your study tip: whenever a question mentions datum presentation (grids, levels, reference planes) needing to match across views without changing model geometry, think Propagate Extents immediately.

Question 3

A wall's location line is set to Wall Centerline. The wall must become coincident with an existing grid and remain constrained to it, while the grid must stay in its current position during the alignment operation.

Which procedure accomplishes this requirement?

Start Align, select the wall centerline first, select the grid second, and lock the alignment.
Start Align, select the grid first, select the wall centerline second, and lock the alignment. (correct answer)
Move the wall until a temporary dimension reads zero, then pin the wall in place.
Dimension from the grid to a wall face, enable equality, and pin the dimension.

Explanation: Whenever you see a question about the Align tool in Revit, focus on one critical rule: the first element you select is the reference (it stays fixed); the second element moves to meet it. This is the opposite of what many students intuitively assume. Because the grid must remain stationary, it must be selected first — making it the immovable reference. Then you select the wall centerline second, which causes the wall to shift and become coincident with the grid. After alignment, locking the constraint (the padlock icon) ensures the wall remains pinned to that grid going forward. This is exactly what B describes, making it the correct procedure. A reverses the selection order — selecting the wall first would make the wall the reference, meaning Revit would attempt to move the grid to match the wall. Since grids are typically locked or at minimum should stay fixed in this scenario, this defeats the requirement entirely. C is a manual workaround using temporary dimensions and pinning. While pinning can lock an element, this approach doesn't create a parametric constraint between the wall and the grid — it simply freezes the wall in place without tying its position to the grid's future movement. D describes using a dimension with equality, which is a legitimate constraint technique in other contexts, but equality constraints work between multiple equivalent distances — not for snapping a single wall to align with a grid line. It also doesn't satisfy the "coincident" requirement cleanly. Memory tip: In Align, think "reference first, mover second" — and always lock immediately to make the constraint permanent.

Question 4

A building wing changes direction twice. The project requires one grid datum with one name to follow the resulting connected bent path so that references identify it as a single grid.

Which method should be used to create the grid?

Create three separate grids, join their endpoints, and assign all three the same name.
Create one straight grid and use endpoint elbows to form the complete model path.
Draw connected detail lines and assign a grid-head annotation to the final segment.
Use Multi-Segment Grid, sketch a continuous path, and finish the sketch. (correct answer)

Explanation: When Revit questions describe a single datum that must follow a bent or angled path while maintaining one consistent name and bubble, you should immediately think about grid types — specifically, whether a standard grid can accomplish this at all. A standard Revit grid is a single straight line. It has no native ability to change direction mid-run. The Multi-Segment Grid tool (found in the Architecture tab under Datum) breaks this limitation by letting you sketch a continuous, connected path made of multiple segments — straight or arc — that Revit treats as one unified grid object with one name and one grid head. That makes D the correct approach: you sketch the connected bent path and finish the sketch to produce a single, properly identified grid datum. Option A is a common workaround assumption, but Revit does not allow you to merge separate grids into one object simply by giving them the same name. You'd end up with three independent grids that share a label visually but remain three distinct elements — references would not treat them as one. Option B is a misconception about endpoint elbows. Elbows on a grid only offset the grid bubble graphically for annotation clarity; they do not bend the actual grid line or create a multi-directional path. Option C confuses drafting elements with model data. Detail lines are view-specific 2D graphics and carry no datum intelligence — attaching a grid head annotation doesn't transform them into a functional grid. As a study tip, remember that Revit's Multi-Segment Grid is the only native tool for a bent datum that functions as one object — if an exam scenario describes a grid that changes direction, that tool is almost certainly the answer.

Question 5

In a cropped plan, a grid line is visible but its enabled end bubble lies outside the annotation crop and is therefore clipped. The model crop must remain unchanged, and no other view should be affected.

What is the most appropriate correction?

Enlarge the model crop until it contains the grid endpoint and its bubble.
Set that endpoint to 2D and drag it inside the annotation crop in the current view. (correct answer)
Shorten the grid's 3D extent until the bubble lies inside every plan crop.
Toggle the endpoint bubble off and back on while the annotation crop is active.

Explanation: Whenever you see a question about grid visibility in Revit, think in terms of 3D vs. 2D extents. Grid lines have two sets of extents: 3D extents, which are shared across all views, and 2D extents, which are view-specific overrides. This distinction is the key to solving clipping problems without unintended side effects. When a grid bubble is clipped by the annotation crop, the cleanest fix is to switch that endpoint to a 2D override and drag it inside the annotation crop boundary — exactly what option B describes. This adjustment exists only in the current view, leaving every other view untouched and honoring the constraint that the model crop must stay the same. Option A fails because enlarging the model crop violates the stated constraint — the model crop must remain unchanged. It also potentially exposes unwanted model elements. Option C is tempting but dangerous: shortening the 3D extent affects the grid's position in all views simultaneously, which breaks the "no other view should be affected" requirement. Option D is a red herring — toggling the bubble off and back on does nothing to move it inside the annotation crop; the bubble will simply reappear clipped in the same position. The practical study tip here is to memorize this rule: 3D extents = global, 2D extents = view-local. Whenever an exam question adds the constraint that other views must be unaffected, that's your signal to look for the 2D-extent or view-specific override solution. Option B is correct because it is the only choice that is both view-isolated and non-destructive to the model crop.

Question 6

A structural column is slightly offset from the intersection of two perpendicular grids. It must move to the intersection now and continue following the intersection if either grid is repositioned later.

Which workflow creates the required behavior?

Move the column to the intersection using snaps, and then pin the column at that location.
Align the column center to one grid, lock it, and pin the second grid.
Align and lock the column's center reference to each grid in the corresponding direction. (correct answer)
Dimension the column to both grids, enter zero for each value, and delete the dimensions.

Explanation: When working with column placement in Revit, the key concept being tested is parametric constraints — specifically, how the Align + Lock workflow creates a persistent, bidirectional relationship between an element and a reference, rather than just a one-time positional fix. The Align tool lets you align an element's reference plane (such as its center) to another reference, like a grid line. Critically, when you click the lock icon that appears after aligning, Revit creates a permanent constraint: the column's center stays bound to that grid. Doing this in both X and Y directions — once per grid — means the column is fully constrained to the intersection. If either grid moves later, the column moves with it. That's exactly what option C describes, making it the correct workflow. Option A is tempting but wrong. Snapping moves the column to the correct position, but pinning only prevents the column from being accidentally moved manually — it does not create a relationship with the grids. If a grid repositions, a pinned column stays put. Option B partially applies the right tool (Align + Lock to one grid), but "pinning the second grid" is not a valid or effective way to create a constraint to the column. Pinning a grid locks the grid itself in place, not the column-to-grid relationship. Option D using dimensions to zero out the offset and then deleting them removes the constraint entirely once the dimensions are gone. No persistent relationship remains afterward. Your takeaway: in Revit, Align + Lock = parametric constraint; snapping and pinning only control position at one moment in time.

Question 7

A grid has bubbles displayed at both ends in several plan views. In one plan only, the bubble at the left endpoint must be hidden while the grid line and right bubble remain visible. Other views must not change.

Which action best satisfies the requirement?

Select the grid in that plan and toggle the left endpoint's bubble visibility control. (correct answer)
Edit the grid type and assign a blank symbol to the left endpoint.
Hide the Grids annotation category in that plan's Visibility/Graphics settings.
Switch the left endpoint from 3D to 2D and shorten the grid line slightly.

Explanation: When working with grids in Revit, it's essential to understand the difference between view-specific (2D) overrides and model-level (3D) changes. Grid bubble visibility can be controlled independently per view without affecting the underlying grid element globally. Revit grids have small grip controls at each endpoint that let you toggle bubble visibility on or off for that specific view. Selecting the grid in the target plan view and clicking the bubble toggle at the left endpoint hides only that bubble, in only that view — exactly what the question requires. This is answer A, and it's the correct choice because it operates at the view-specific level, leaving all other views untouched. Answer B is a trap for students who confuse type-level settings with view-level overrides. Editing the grid type changes the symbol for every instance of that grid type across the entire project — the opposite of what's needed here. Answer C would hide all grid lines and bubbles in that view by suppressing the entire Grids annotation category, which is far too broad and would affect every grid, not just one bubble on one grid. Answer D combines two separate actions — switching to 2D and shortening the line — and while switching to 2D does allow view-specific endpoint manipulation, simply shortening the line doesn't hide a bubble; it just moves the endpoint. This approach is indirect, imprecise, and not the standard workflow. Study tip: On Revit exam questions, phrases like "in one view only" are your signal to look for view-specific overrides rather than type edits or category-level controls. Always match the scope of the tool to the scope of the requirement.

Question 8

A set of grids is assigned to a scope box. A user tries to drag a grid's 3D endpoint so that it extends beyond the scope box, but the datum continues to follow the scope-box boundary.

What should the user do to manually redefine that grid's model extents?

Unpin the grid, leave the scope box assigned, and drag the endpoint beyond the boundary.
Convert the endpoint to 2D, drag it outward, and propagate the change to every plan.
Disable the view crop, drag the endpoint outward, and then restore the crop.
Set the grid's Scope Box parameter to None, then edit its 3D extents. (correct answer)

Explanation: Whenever you see a question about datum extents in Revit, think about the relationship between scope boxes and 3D vs. 2D controls. Scope boxes govern a datum's 3D extents — the model-level boundary that propagates across all views. When a grid is assigned to a scope box, Revit locks that grid's 3D endpoints to the scope box boundary, which is exactly why dragging the endpoint fails in this scenario. To manually redefine the 3D extents, you must first sever that control relationship by setting the grid's Scope Box parameter to None. Once the scope box is no longer governing the datum, the 3D endpoints become freely editable, and you can drag them to any position you need. That's why D is correct — it's the only option that removes the actual constraint preventing the edit. A is a trap because unpinning a grid frees it from being accidentally moved, but pinning has nothing to do with scope box control. The scope box will still govern the 3D extents even after unpinning. B describes converting to a 2D endpoint, which only affects the datum's appearance in a single view — it doesn't change the model-level 3D extents at all, and "propagating" a 2D override to every plan isn't how Revit works. C is a distractor that confuses view crop regions with datum extents; the crop region controls what's visible in a view, not where a grid's 3D endpoint is anchored. As a study tip: always distinguish between 3D extents (model-wide, controlled by scope boxes) and 2D extents (view-specific overrides). Exam questions will often blur this line to test whether you know which setting affects which behavior.

Question 9

A grid displays correctly in the Level 1 and Level 2 plan views. In Level 1, a user changes the grid's right endpoint from 3D extents to 2D extents and drags that endpoint inward.

What should the user expect in Level 2?

The right endpoint moves inward because all datum endpoint edits affect parallel views.
The grid remains unchanged because a 2D extent adjustment is view-specific. (correct answer)
The entire grid becomes hidden because one endpoint no longer uses 3D extents.
Only the grid bubble moves inward, while the grid line retains its original extent.

Explanation: Whenever you see a Revit question about datum elements (grids, levels, reference planes) and endpoint adjustments, the key concept to focus on is the difference between 3D extents and 2D extents — because these two modes behave in completely opposite ways across views. In Revit, a grid's 3D extents are shared across all parallel views at the same scale. If you drag a 3D endpoint, every parallel plan view reflects that change. However, when you switch an endpoint to 2D extents, you are explicitly telling Revit to treat that endpoint as local to the current view only. The adjustment you make stays in that view and does not propagate anywhere else. This is exactly what happens in the scenario: the user switches the right endpoint to 2D and drags it inward in Level 1. Level 2 sees no change whatsoever — confirming that B is correct. A misrepresents how 3D extents work. It's true that 3D endpoint edits affect parallel views, but the moment you convert an endpoint to 2D, it loses that cross-view behavior entirely. The user did the opposite of what A describes. C is incorrect because switching one endpoint to 2D doesn't hide the grid or affect its visibility. Visibility is controlled through Visibility/Graphics overrides, not extent type. D confuses the grid bubble with the grid line endpoint. In Revit, the bubble position is tied to the endpoint — they are not independently movable in the way D implies. A useful rule of thumb: 2D = view-specific, 3D = shared. When you see "2D extents" in a question, immediately think "this change stays local to that one view."

Question 10

Two existing grids are named 2 and 3. Their physical locations are correct, but their names must be exchanged. Grid names must remain unique throughout the operation.

Which renaming sequence will successfully exchange the two names?

Rename grid 2 to 3, and then rename the original grid 3 to 2.
Rename grid 3 to 2, and then rename the original grid 2 to 3.
Rename grid 2 to TEMP, rename grid 3 to 2, and rename TEMP to 3. (correct answer)
Select both grids, edit one bubble to 3, and allow Revit to swap the names.

Explanation: Whenever Revit requires unique grid names at all times — not just at the end of an operation — you cannot directly swap two names in a single step or even two steps if either intermediate state would create a duplicate. Think about what happens if you try to rename grid 2 directly to 3: Revit already has a grid named 3, so it will reject the rename because it would create a duplicate. This is the trap that answers A and B both fall into. Choice A tries to rename grid 2 to 3 first, but grid 3 already exists — Revit blocks this immediately. Choice B tries the same swap from the other direction, renaming grid 3 to 2 first, but grid 2 already exists, so Revit blocks that as well. Neither two-step direct swap works because uniqueness is enforced at every individual step, not just the final state. Choice D is a fictional feature — Revit has no automatic "swap names" behavior when you edit multiple bubbles simultaneously. Selecting both grids and editing one does not trigger any intelligent name-exchange logic. The correct approach, choice C, uses a temporary placeholder name. By renaming grid 2 to TEMP first, you free up the name "2" without creating any conflict. Now you can safely rename grid 3 to 2, and finally rename TEMP to 3. At every step, all names remain unique, so Revit accepts each change without complaint. As a study tip, whenever an exam question involves swapping unique identifiers in Revit — grids, levels, or view names — think "temporary variable" first, just like a classic variable-swap algorithm in programming.