- How should the Align tool be used to establish this behavior?
Answer: Select the grid first, select the wall centerline second, and close the displayed lock.
When working with Revit's Align tool, order and locking are everything — especially when you need elements to maintain a parametric relationship after the alignment is made.
The Align tool works by snapping a selected element to a reference. In Revit, the first click defines the reference (where things align to), and the second click defines the element to move. To lock the alignment so that the wall centerline follows the grid if the grid moves, you must click the padlock icon that appears and close it. This creates a permanent constraint between the two elements. Answer B is correct: select the grid first as the reference, then select the wall centerline as the element being aligned, and lock the constraint — this binds the partition to the grid.
Answer A reverses the selection order and leaves the lock open, which is doubly wrong. Leaving the lock open means no persistent constraint is created, so the wall won't follow the grid. Answer C uses the wall face instead of the centerline — but the passage specifically requires the centerline to coincide with the grid — and pinning only prevents the wall from moving accidentally; it does not create a relationship between the wall and the grid. Answer D selects in the correct order (grid first, then wall) but targets the face rather than the centerline, and critically leaves the lock open, so no parametric constraint is established.
A useful pattern to remember: in Revit, first click = reference, second click = element to move. And any time a question asks about elements moving together, look for the locked alignment constraint — an open lock is just a one-time nudge.
- Which workflow best meets the requirement?
Answer: Use Move with Disjoin selected so the wall separates before it is relocated.
When moving a wall in Revit that is joined to other walls, you need to understand how wall joins behave during the Move command. By default, joined walls stretch or compress to maintain their connections when you relocate one of them — which is exactly what you don't want here, since the perpendicular walls must remain unchanged.
The Disjoin option in the Move command's Options Bar is designed precisely for this scenario. When you check Disjoin before moving, Revit breaks all join relationships on the selected wall before relocating it, so the perpendicular walls stay exactly as they are and the moved wall travels to its new position as a completely independent element. This satisfies both requirements: the wall moves parallel to its original position, and the perpendicular walls are untouched. Answer B is the correct workflow.
Answer A is a trap. The Constrain option restricts movement to horizontal or vertical directions only — it has nothing to do with managing wall joins. The perpendicular walls would still stretch to follow the moved wall, violating the requirement.
Answer C would technically produce the right end result, but it's unnecessarily destructive and inefficient. Copying creates a new, unjoined wall, then you must manually clean up the original joined wall and any leftover geometry — far more steps than needed.
Answer D misuses the Align tool. Align is for snapping one element's face to another reference plane or surface. It doesn't move a wall to a new parallel position in the way the scenario requires, and leaving a lock unlocked simply means no constraint is applied.
The study tip: whenever a Revit question involves moving joined elements while keeping neighbors intact, immediately think Disjoin in the Options Bar — it's a targeted option that often goes unnoticed but solves this exact problem cleanly.
- Which option is most important to enable when the array is created?
Answer: Enable Group and Associate so the members retain an editable array relationship that supports later quantity changes.
When working with arrays in Revit, the key question to ask yourself is: does this array need to remain editable as a group, or will each element live independently? The answer depends entirely on whether the designer needs to revisit the count later — which is exactly what this scenario describes.
Group and Associate is the setting that keeps array members linked together under a single, manageable relationship. When enabled, Revit treats the arrayed elements as a group, and you can simply click the array and type a new count value to add or remove members instantly. This is why C is correct — it directly addresses the requirement to adjust quantity without demolishing and rebuilding the layout.
A is wrong because disabling Group and Associate does the opposite of what's needed. Once ungrouped, the columns scatter into independent elements with no shared array logic, so changing the count means manual deletion or placement — exactly the inefficiency the designer wants to avoid.
B is wrong because Constrain controls the direction of movement during array creation (locking it perpendicular or parallel), not the ongoing editability of element count. It's a placement aid, not a quantity-management tool.
D is wrong because Move To: Last defines how spacing is calculated — whether the offset applies to the next element or the final element. It affects geometry setup, but it has no bearing on whether the array count remains editable afterward.
A useful rule of thumb: whenever a question mentions future quantity changes, think Group and Associate. That toggle is Revit's mechanism for keeping array intelligence alive after creation.
- Which Copy configuration provides the intended workflow?
Answer: Select Multiple, define the base point once on the original chair, and click each of the three destination points in succession.
When working with the Copy tool in Revit, the key distinction to understand is the difference between the Multiple and Constrain options, and how they control workflow efficiency. Questions like this test whether you know how to minimize repetitive steps when placing several copies from a single reference point.
The Multiple option is specifically designed for exactly this scenario: you define your base point once on the original element, then click as many destination points as needed — all within the same active command. This lets you place all three additional chairs in succession without restarting Copy or redefining your reference point. That makes D the correct answer, and the most efficient workflow for the task described.
Looking at the wrong answers: A falls apart because Repeat Last Command restarts the Copy command entirely each time, forcing you to redefine the base point for every new chair — the opposite of what the scenario requires. B is tricky because it sounds logical, but clearing Multiple actually disables the multi-placement behavior, meaning the command ends after just one copy is placed. You'd have to restart the command for each remaining chair. C misuses Constrain, which limits movement to horizontal or vertical axes — it doesn't help with multi-placement at all, and defining three separate base points contradicts the requirement to use the same reference point on the original chair.
A useful pattern to remember: whenever a Revit question mentions placing several copies "without restarting the command," that's your signal to look for Multiple mode in the Copy options bar. It's Revit's built-in solution for batch placement from a single base point.
- Which Rotate workflow satisfies both requirements?
Answer: Start Rotate, relocate the center of rotation to the column center, select Copy, and specify 35∘.
When you see a Revit workflow question involving duplication and rotation around a specific point, focus on two independent requirements: where the rotation pivots and whether the original is preserved.
Revit's Rotate tool places the center of rotation at the selected element's centroid by default, but you can relocate it anywhere — including to a column center — by dragging or clicking a new pivot point during the command. Critically, the Copy option within Rotate tells Revit to leave the original in place and create a rotated duplicate. Choosing A — starting Rotate, relocating the pivot to the column center, enabling Copy, then entering 35∘ — satisfies both requirements perfectly: the furniture is rotated 35∘ around the column, and the original instance remains unchanged.
Option B fails because it retains the default center (the element's own centroid, not the column center) and clears Copy, meaning the original furniture moves rather than being duplicated — two errors in one choice. Option C describes the Move tool, which translates elements along a straight-line displacement; it has no concept of angular rotation around an external pivot, so entering 35∘ is meaningless in that context. Option D uses Mirror, which reflects geometry across an axis — a fundamentally different transformation. Mirroring cannot produce a 35∘ rotation; the angle between original and mirrored result depends on the axis orientation, not a direct degree input.
A useful pattern to remember: whenever a Revit question requires rotating around an external point, look for the pivot-relocation step inside the Rotate command combined with the Copy toggle — that combination is the only tool that handles both constraints simultaneously. - What should the designer expect?
Answer: The countertop remains where aligned because no persistent constraint was created when the lock was left open.
When working with the Align tool in Revit, it's essential to understand the difference between a temporary alignment and a locked constraint. The Align tool positions one element relative to another, but that positioning only becomes a persistent, parametric relationship when you click the padlock icon that appears after the alignment. This distinction is the core concept being tested here.
When the designer skips the lock, no constraint is written into the model. The countertop simply sits at its new position — it has no "memory" of the reference plane. So when the reference plane moves later, the countertop stays put. This is exactly what B describes, making it the correct answer.
A is wrong because it assumes Align automatically creates a permanent constraint — it does not. The lock icon exists precisely because the constraint is optional, not automatic. Leaving the lock open means no constraint is ever established.
C introduces a false rule about operand order. The sequence in which you pick references during an Align operation determines which element moves to match the other, but it has no bearing on whether a constraint is created afterward. That is always controlled by the lock.
D is incorrect because the Align tool has no pinning functionality. Pinning is a separate command that prevents an element from being moved, and it does not get triggered by alignment operations.
Your study tip: treat the padlock in Align as the "commit" button for the relationship. If you see a question about elements not following reference planes or other hosts, immediately ask yourself — was the lock clicked? That single step separates a live constraint from a one-time positional nudge.
- Which modification workflow is most appropriate?
Answer: Use Mirror–Pick Axis, select the grid as the axis, and keep Copy selected.
When working with symmetry tools in Revit, the key distinction to keep in mind is the difference between mirroring (which flips geometry across an axis) and copying (which preserves the original). You also need to know whether your axis already exists in the model or must be drawn.
Revit offers two Mirror commands: Mirror–Pick Axis lets you click an existing model element — like a grid line — as the reflection axis, while Mirror–Draw Axis requires you to sketch a temporary axis manually. When you run either command, a Copy checkbox appears in the Options Bar. Leaving it checked mirrors the selection and retains the originals; unchecking it moves the selection to the mirrored position, deleting the originals.
In this scenario, the axis is an existing grid line and the original layout must stay in place. That means you need Mirror–Pick Axis with Copy enabled — which is exactly what A describes. You simply select the elements, invoke Mirror–Pick Axis, click the grid, and confirm with Copy checked. Both sides now exist symmetrically.
B is wrong because clearing Copy would move the original layout to the mirrored position, eliminating the source side — the opposite of what the passage requires. C uses Mirror–Draw Axis, which is unnecessary here since the grid line already exists as a valid axis; additionally, clearing Copy again destroys the originals. D uses Rotate with Copy at 180°, which would spin elements around a pivot point — not produce a true mirror reflection. Rotated geometry is not the same as mirrored geometry.
As a study tip: whenever a Revit question mentions preserving originals during a mirror operation, that's your cue that Copy must remain checked. - Which radial Array settings should be used?
Answer: Set Number to 5, select Move To: Last, and enter an angle of 120∘.
When working with Revit's radial Array tool, two settings control the geometry: Number (total elements including the original) and Move To, which determines how the angle you type is interpreted.
The Move To: Last option means your entered angle spans from the first element all the way to the last — the full arc. Move To: 2nd means the angle only represents the gap between the first and second elements, so Revit multiplies that gap across all items.
For this scenario: you need 5 fixtures total (the original plus four copies), and you want the entered angle to represent the complete 120° span from first to last. Setting Number to 5 and Move To: Last with 120° tells Revit to place all five fixtures evenly across exactly 120°, with the first and fifth fixtures sitting at each end. That makes D correct.
A is wrong because entering 30° with Move To: Last would produce a 30° total arc, not 120°. B uses Move To: 2nd with 120°, which means each gap between adjacent fixtures is 120° — Revit would spread the array over 480° total, far beyond the intended span. C sets Number to 4 instead of 5, which only creates four total fixtures (the original plus three copies), leaving you one fixture short.
A reliable memory trick: Move To: Last = the angle you type IS the full arc. If you want the total span to match your input exactly, always choose Last — and make sure your Number includes the original element. - Which workflow most reliably produces the required modification?
Answer: Use Move with Constrain selected, indicate the perpendicular direction, and type 900 mm to lock the displacement.
When moving geometry in Revit, the critical challenge with oblique (non-orthogonal) walls is controlling the direction of movement, not just the distance. Without directional control, typing a distance value means nothing if Revit doesn't know which way to move the element.
The Move tool with Constrain active is precisely designed for this scenario. When you enable Constrain, Revit locks movement to the axis most closely aligned with your cursor direction. By nudging your cursor perpendicular to the wall's face before typing 900 mm, you guarantee the displacement is exactly perpendicular — no rotation, no copying, no deviation. This is why C is the correct workflow.
A is wrong because Rotate changes the wall's angular orientation around a pivot point — it doesn't translate (shift) the wall linearly. Entering 900 mm as a rotation value is geometrically meaningless for linear displacement; rotation values are angles, not distances.
B is the most tempting trap. Move without Constrain does accept a typed distance, but Revit will move the wall in whatever freehand direction you indicated with your cursor. On an oblique wall, eyeballing "perpendicular" introduces angular error — the displacement will almost certainly drift off-axis.
D misrepresents the Align tool. Align snaps geometry to a selected reference line or face; it does not accept a numeric offset distance. You would need the Offset tool for distance-based repositioning, and even then, workflow precision matters.
Your study tip: on Revit exam questions involving precise directional moves, always ask yourself, "Which tool controls both direction AND distance?" — that's your Move + Constrain combination. - Which linear Array settings produce the required result directly?
Answer: Set Number to 6, select Move To: Last, and enter 7,500 mm.
When working with Revit's linear Array tool, you need to understand two key settings: Number (total elements including the original) and Move To (which controls what your drag distance represents). "Move To: Last" means the distance you enter spans from the first element to the last. "Move To: 2nd" means the distance represents the spacing between consecutive elements.
The problem asks for 6 total cabinets with the first and last centers 7,500 mm apart. Option A sets Number to 6 and uses Move To: Last with 7,500 mm — this tells Revit to place 6 cabinets total, with the final cabinet's center exactly 7,500 mm from the original. Revit automatically divides that span into 5 equal gaps of 7,500÷5=1,500 mm each. This matches the requirement perfectly, making A the correct answer.
Option B sets Number to 5, which only produces 5 cabinets — one short of the required 6. Option C uses Number 6 correctly but selects Move To: 2nd with 7,500 mm, which would treat 7,500 mm as the spacing between each pair, producing a total span of 5×7,500=37,500 mm — far too large. Option D gets the spacing value right (1,500 mm per gap) but sets Number to 5, again yielding only 5 cabinets instead of 6.
A helpful memory rule: Number = total count (original included), Move To: Last = total span, Move To: 2nd = individual spacing. Mixing these two settings is the most common trap on Array questions.
