Autodesk Revit Quiz: Resolving Constraint Conflicts

10 questions · exam conditions

0:00

Resolving Constraint ConflictsQuestion 1 of 10

A permanent dimension between two reference planes is locked and is therefore maintaining their spacing. The dimension annotation should not appear in a presentation view, but the spacing must remain constrained.

Which workflow best meets both requirements?

Hide the dimension element in that view while leaving its locked constraint in place.

Delete the dimension and accept the warning that its associated constraint will be removed.

Unlock the dimension, delete it, and pin both reference planes in their current locations.

Convert the permanent dimension to a temporary dimension and lock it to retain the spacing.

← Back to quizzes

Autodesk Revit Quiz

Autodesk Revit Quiz: Resolving Constraint Conflicts

Practice Resolving Constraint Conflicts 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 Resolving Constraint Conflicts, 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

Which workflow best meets both requirements?

Hide the dimension element in that view while leaving its locked constraint in place. (correct answer)
Delete the dimension and accept the warning that its associated constraint will be removed.
Unlock the dimension, delete it, and pin both reference planes in their current locations.
Convert the permanent dimension to a temporary dimension and lock it to retain the spacing.

Explanation: When working with locked dimensions in Revit, you need to keep two concerns separate: the visual appearance of an annotation and the constraint it enforces. These are independent properties, and the exam frequently tests whether you understand that distinction. In Revit, hiding an element in a specific view does not delete or modify the element itself — it simply suppresses its visibility in that view. This means a locked dimension can be hidden using View-specific visibility controls (right-click → Hide in View, or Visibility/Graphics overrides) while its constraint remains fully active. The reference planes will continue to maintain their spacing even though the dimension annotation is invisible in the presentation view. This is exactly what option A describes, making it the correct workflow. Option B is a trap for students who conflate deleting a dimension with simply hiding it. Deleting a locked dimension removes the constraint entirely — Revit even warns you this will happen — which violates the requirement that spacing must remain constrained. Option C attempts a workaround by pinning the reference planes, but pinning prevents elements from being accidentally moved; it does not enforce a relationship between two planes the way a locked dimension does. The relative spacing constraint is lost. Option D is a common misconception: temporary dimensions in Revit cannot be locked or saved as persistent constraints. They exist only during an active editing session, so this option doesn't preserve anything. The key study takeaway: in Revit, visibility ≠ existence. Hiding an element in a view never removes its parametric behavior. When a question asks you to suppress annotation without losing logic, think "hide, don't delete."

Question 2

In the Family Editor, the left and right reference planes are controlled by a dimension labeled with the Width parameter. Both reference planes were also locked to fixed reference lines during early development. The family works at its original size but produces a constraint error when Width is changed.

Which modification most appropriately restores parametric behavior?

Remove the Width label while retaining both locks to the fixed reference lines.
Remove the locks to the fixed reference lines while retaining the dimension labeled Width. (correct answer)
Change Width from an instance parameter to a type parameter while retaining all locks.
Pin both reference planes and replace the Width parameter with an equality constraint.

Explanation: When building parametric families in Revit, every reference plane should have exactly one "driver" controlling its position. A constraint error signals a conflict — two competing rules are trying to locate the same plane simultaneously, which Revit cannot resolve. Here, the Width dimension parameter and the locks to fixed reference lines are both attempting to control the left and right reference planes. At the original size these constraints happen to agree, so no conflict appears. The moment you change Width, the dimension tries to move the planes while the locks insist they stay put — an overconstrained system that throws an error. The fix is to remove one driver. Since Width is the intended parametric control, removing the locks to the fixed reference lines (answer B) frees the planes to follow the dimension correctly, restoring full parametric behavior without sacrificing the parameter. Answer A does the opposite — it removes the label (the parametric driver you actually want) while keeping the conflicting locks, which means Width no longer controls anything and the family becomes rigid rather than flexible. Answer C changes the parameter scope from instance to type, but the underlying geometric conflict between the dimension and the locks still exists; scope has nothing to do with overconstrained geometry. Answer D introduces pinning and equality constraints, which would eliminate Width entirely and create a different kind of rigidity — planes equidistant from center with no width control at all. A useful rule of thumb for the exam: when a Revit family works at one size but breaks when a parameter changes, immediately suspect overconstrained geometry. Your first question should be "what two things are fighting to control the same element?"

Question 3

Three adjacent structural bays are controlled by an equality constraint, so all three bay widths must remain equal. The overall dimension across the bays is locked at $10{,}000\,\text{mm}$ . One bay also has a separate locked dimension of $3000\,\text{mm}$ .

If equal bays and the locked overall width are the design priorities, which action resolves the over-constraint?

Pin the two exterior grid lines and retain all three existing dimensional constraints without modification.
Remove the equality constraint and retain the overall and $3000\,\text{mm}$ constraints.
Remove the overall lock and retain the equality and $3000\,\text{mm}$ constraints.
Remove the $3000\,\text{mm}$ bay lock and retain both the equality and overall constraints. (correct answer)

Explanation: Whenever you see a question about over-constrained geometry in Revit, ask yourself: how many independent constraints does the system have, and how many degrees of freedom remain? Three equal bays with an overall width of

10{,}000\,\text{mm}

already fully determines every grid position — each bay is automatically

\frac{10{,}000}{3} \approx 3{,}333\,\text{mm}

. Adding a separate locked dimension of

3{,}000\,\text{mm}

to one bay creates a contradiction, because that bay cannot simultaneously be

3{,}333\,\text{mm}

and

3{,}000\,\text{mm}

. The system is over-constrained by exactly one redundant lock. Since the design priorities are equal bays and locked overall width, the fix is to remove only the conflicting

3{,}000\,\text{mm}

bay lock. With just the equality constraint and the

10{,}000\,\text{mm}

overall lock in place, Revit can calculate the bay widths freely and consistently. That makes D the correct action. A is wrong because pinning the exterior grids does nothing to resolve the mathematical contradiction between the three constraints — all three still conflict simultaneously. B eliminates the equality constraint, which directly violates the stated design priority of equal bays; the remaining two constraints (overall and

3{,}000\,\text{mm}

) would only define one bay, leaving the layout underdetermined and unequal. C removes the overall lock, which violates the other stated priority; the equality plus the

3{,}000\,\text{mm}

lock would set each bay to

3{,}000\,\text{mm}

, giving a total of

9{,}000\,\text{mm}

— wrong overall. A useful rule of thumb: always count your constraints against your unknowns before deciding which one to remove, and always protect the constraints that match the stated design intent.

Question 4

A wall endpoint is joined to another wall, and the wall face is aligned and locked to a reference plane. A user selects the wall and activates Move with the Disjoin option, expecting this to allow the wall to move away from the reference plane.

Why can the movement still fail, and what is the appropriate correction?

Disjoin affects only hosted elements, so the wall must instead be changed to another type.
Disjoin releases the alignment lock, but the wall-end join must also be manually deleted.
Disjoin releases the wall-end join, but the alignment lock must also be unlocked or removed. (correct answer)
Disjoin temporarily pins the wall, so the wall must be unpinned after completing the move.

Explanation: Whenever you see a Revit question about moving walls that seem "stuck," think in terms of constraint layers — Revit can hold a wall in place through multiple independent mechanisms simultaneously, and releasing one does not automatically release the others. The Disjoin option in the Move command specifically breaks wall-end joins — the geometric connections between wall endpoints and neighboring walls or elements. This frees the wall's endpoint from being dragged along with the joined element. However, Disjoin has no effect on alignment locks, which are separate constraints created when you use the Align tool and click the padlock icon. If the wall face is locked to a reference plane, that lock remains fully active regardless of Disjoin, preventing the wall from moving perpendicular to that plane. To successfully move the wall, you must both use Disjoin (to release the end join) and manually unlock or remove the alignment lock before or during the move. This is exactly what C describes, making it the correct answer. A is wrong because Disjoin applies to wall-end joins, not just hosted elements like doors or windows — it's unrelated to element type or family category. B reverses the logic: Disjoin handles the wall-end join automatically during the move command; what you still need to address manually is the alignment lock, not the join. D is a fabricated behavior — Disjoin does not pin the wall, and no such "temporary pin" mechanism exists in Revit. A helpful rule of thumb: in Revit, always ask yourself how many constraints are holding an element. Locked alignments and joined ends are independent — check for both before troubleshooting a failed move.

Question 5

A pinned wall is also controlled by a locked dimension to a grid. The grid will remain fixed, but the wall must be moved to a new offset and then constrained at that new distance.

What sequence is required to make the revision without leaving an unresolved constraint?

Unpin the wall, release or edit the locked offset, move the wall, and establish the new locked value. (correct answer)
Unpin the wall, move it with Disjoin enabled, and leave the original locked offset unchanged.
Unlock the offset, move the wall, and leave the wall pinned throughout the operation.
Delete the grid, move the pinned wall, and recreate the grid at the original location.

Explanation: Whenever you see a Revit question involving constraints and pinning together, recognize that these are two separate but overlapping restrictions — and both must be resolved before a valid move can occur. Failing to address either one will leave the model in a conflicted or broken state. The correct approach, answer A, follows a logical sequence that clears every obstacle before and after the move. First, unpinning the wall removes the positional lock that prevents any movement at all. Then, releasing or editing the locked dimension (the offset to the grid) removes the second constraint — because even an unpinned wall cannot freely move if a locked dimension is still enforcing its current position. Once both restrictions are cleared, you move the wall to its new location and establish a new locked dimension value to re-constrain it properly. No conflict remains. Answer B fails because using "Disjoin" during a move only breaks the wall's connection to joined geometry — it does not resolve the locked offset dimension. That constraint stays active and will cause an error or snap the wall back. Answer C is flawed because a pinned wall cannot be moved, period. Unlocking the dimension alone does not override the pin, so the wall still cannot be repositioned. The pin must always be addressed first. Answer D is a destructive workaround. Deleting the grid disrupts all other elements constrained to it, and recreating it introduces unnecessary risk of misalignment — this is never the correct workflow for a simple wall relocation. A useful rule of thumb: resolve constraints in the order they would block you — pin first, then locked dimensions — and always re-constrain after moving.

Question 6

A door centerline is locked to Grid 2. A second locked dimension controls the distance from the same door centerline to the end of its host wall. The wall end must be extended, Grid 2 will not move, and the door must remain centered on Grid 2.

Which constraint should be released before extending the wall?

Release the door's hosted relationship and retain both locked dimensions.
Release the door-to-grid alignment and retain the door-to-wall-end dimension.
Release the door-to-wall-end dimension and retain the door-to-grid alignment. (correct answer)
Release the wall's base constraint and retain both door-location constraints.

Explanation: Whenever Revit constraints conflict during a geometry change, you need to identify which constraint blocks the intended move and release only that one — preserving every constraint that supports your design intent. Here, your goal is threefold: extend the wall end, keep Grid 2 fixed, and keep the door centered on Grid 2. The door-to-grid alignment lock is what enforces that centerline position — it's the constraint you want to keep. The door-to-wall-end dimension, however, creates a rigid relationship between the door and the wall terminus. When you try to extend the wall, Revit sees a conflict: the wall end is moving, the door is pinned to the grid, and the locked distance between them can no longer be satisfied. Releasing the door-to-wall-end dimension (answer C) removes that conflict while keeping the door anchored to Grid 2, exactly as required. Answer A fails because retaining both locked dimensions still creates the same geometric conflict — the door can't simultaneously honor a fixed distance to a moving wall end and stay on Grid 2. Answer B is the opposite of what you need: releasing the door-to-grid alignment removes the very constraint that keeps the door centered on the grid, which violates the design requirement. Answer D targets the wall's base constraint, which controls its vertical position, not its plan length — editing that wouldn't resolve the horizontal dimension conflict at all. A useful strategy: always trace the chain of constraints involved in your edit. Release only the constraint that directly conflicts with the change, and verify that what remains still satisfies every design requirement.

Question 7

Three parallel walls, A, B, and C, are controlled by locked dimensions. The distance from A to B is $2500\,\text{mm}$ , the distance from B to C is $3500\,\text{mm}$ , and the overall distance from A to C is $6000\,\text{mm}$ . A design revision requires the overall distance to become $6200\,\text{mm}$ while the A-to-B distance remains unchanged.

Which action most directly resolves the constraint conflict while preserving the stated design intent?

Unlock the B-to-C dimension, then change the overall dimension to $6200\,\text{mm}$ . (correct answer)
Unlock the A-to-B dimension, then change the overall dimension to $6200\,\text{mm}$ .
Unpin wall C, then change the overall dimension to $6200\,\text{mm}$ .
Delete the overall dimension, then move wall B by $200\,\text{mm}$ .

Explanation: Whenever Revit's locked dimensions create a constraint conflict, your first instinct should be to identify which constraint is blocking the change and which one design intent requires you to preserve. Think of locked dimensions as a system of equations — if every value is locked, the model is over-constrained and Revit cannot resolve a change until you free exactly one degree of freedom. Here, you have three locked values: A-to-B =

2500\,\text{mm}

, B-to-C =

3500\,\text{mm}

, and overall A-to-C =

6000\,\text{mm}

. The design intent is explicit: A-to-B must stay at

2500\,\text{mm}

, and the overall must become

6200\,\text{mm}

. That means only B-to-C needs to absorb the

200\,\text{mm}

change, growing to

3700\,\text{mm}

. Option A — unlocking the B-to-C dimension first, then editing the overall — does exactly this. It frees the one constraint that should change, lets Revit recompute, and preserves the A-to-B relationship. Option B is the critical trap: unlocking A-to-B violates the stated design intent by making that gap eligible to move — the opposite of what the problem asks. Option C addresses wall C's position rather than the dimensional constraint; unpinning a wall doesn't resolve a locked-dimension conflict in the parametric sense and could produce unpredictable behavior. Option D avoids the constraint system entirely by deleting the overall dimension and manually moving wall B, which would shift the A-to-B distance away from

2500\,\text{mm}

and break that requirement. The strategy to remember: before changing any constrained dimension, ask "which lock opposes my edit, and does removing it violate any stated requirement?" Unlock only the dimension that should change — never the one you're protecting.

Question 8

A floor boundary sketch line is locked to an exterior wall so that the floor follows the wall. The same sketch line is also controlled by a locked dimension to a stationary reference plane. The wall must move, and the floor edge is intended to remain aligned with it.

How should the conflict be resolved?

Change the floor's height offset and retain both horizontal boundary constraints.
Edit the floor sketch, release the wall alignment lock, and retain the reference-plane dimension.
Detach the wall from its top constraint and retain both floor-boundary constraints.
Edit the floor sketch, release the dimension to the reference plane, and retain the wall alignment lock. (correct answer)

Explanation: When a floor sketch line carries two competing constraints — a lock to a moving wall and a lock to a stationary reference plane — Revit cannot satisfy both simultaneously. The key question to ask yourself is: which constraint reflects the design intent going forward? Since the goal is for the floor edge to follow the wall as it moves, the wall alignment lock is the one worth keeping. That reasoning points directly to D. By editing the floor sketch and releasing the dimension to the reference plane, you eliminate the conflicting constraint while preserving the wall alignment lock. Now when the wall moves, the floor boundary moves with it — exactly the intended behavior, with no constraint conflict. Option A fails because changing the height offset addresses vertical positioning, not the horizontal boundary conflict between two competing sketch constraints. The contradiction remains entirely unresolved. Option B has the logic backwards: releasing the wall alignment lock and keeping the reference-plane dimension means the floor edge will stay fixed while the wall moves, which is the opposite of the stated intent. Option C is a distractor that targets the wall's top constraint, which governs the wall's vertical attachment to a ceiling or roof — completely unrelated to horizontal floor boundary behavior. A useful pattern to remember: whenever you encounter a constraint conflict in Revit, first identify which constraint serves the current design intent, then release the one that opposes it. Don't change geometry (like offset values) to mask a constraint problem — resolve it at the constraint level. On the exam, watch for distractors that sound structural but address the wrong parameter entirely, as C and A demonstrate here.

Question 9

When a designer moves a wall, Revit reports that the constraints are not satisfied. The wall has several nearby dimensions and alignments, but the designer does not know which of them are controlling the wall.

What should the designer do first to diagnose the conflict without unnecessarily removing valid constraints?

Use Reveal Constraints or the warning's Show control to inspect the relationships affecting the wall. (correct answer)
Select all nearby dimensions and toggle every displayed lock to the unlocked state.
Use Reset Temporary Hide/Isolate so that Revit can recalculate the wall relationships.
Unjoin the wall at both ends before attempting the same movement again.

Explanation: When Revit reports unsatisfied constraints after moving a wall, your instinct should be to diagnose before you act. Constraint conflicts in Revit stem from locked dimensions, pinned elements, or alignment relationships — and the challenge is identifying which relationships are actually causing the problem without destroying valid ones in the process. The right first step is A: using Reveal Constraints (found on the View tab) or clicking the Show button within the warning dialog. Both tools visually highlight every constraint affecting the selected element — locked dimensions, alignment locks, and pins — letting you see exactly what's holding the wall in place. This gives you precise, targeted information so you can make an informed decision about which constraint to modify or remove. B is a destructive shortcut. Unlocking every nearby dimension indiscriminately could remove intentional design constraints that should be preserved — exactly what the question warns you to avoid. You'd be solving the symptom by potentially breaking the design. C is a red herring. Reset Temporary Hide/Isolate controls visibility only; it has no effect on constraint calculations or conflict resolution. Revit's constraint engine doesn't depend on what's hidden or isolated. D addresses wall joins, which control geometry cleanup between intersecting walls — not dimensional or alignment constraints. Unjoining the wall won't resolve a locking conflict and may introduce new geometry issues. Study tip: On Revit exam questions about constraint errors, always look for the non-destructive diagnostic option first. Reveal Constraints and warning dialog Show buttons are Revit's built-in tools for exactly this workflow — learn them as a pair.

Question 10

A wall was aligned and locked to Grid A. A separate permanent dimension from the wall to Grid B was also locked. Grid B remains fixed, but Grid A must move as part of a grid-layout revision. The wall is intended to follow Grid A.

Which change should be made before moving Grid A?

Remove the locked alignment to Grid A and retain the locked dimension to Grid B.
Remove the locked dimension to Grid B and retain the locked alignment to Grid A. (correct answer)
Unpin Grid A and retain both wall constraints during the grid movement.
Disallow the wall join at each endpoint and retain both wall constraints.

Explanation: When working with walls and constraints in Revit, you need to think about constraint conflicts. A wall can obey multiple locked relationships simultaneously — but only if those relationships are compatible. When they aren't, Revit will throw an error or produce unexpected geometry when you try to move something. Here, the wall has two locked constraints: an alignment lock to Grid A, and a dimension lock to Grid B. If you move Grid A while both locks are active, the wall is being told two contradictory things at once — "follow Grid A" and "stay a fixed distance from Grid B." Since Grid B isn't moving, these instructions cannot both be satisfied, and Revit will either warn you or fail the move entirely. The solution is B: remove the locked dimension to Grid B before moving Grid A. This frees the wall from its obligation to Grid B, allowing the alignment lock to Grid A to do its job cleanly — the wall follows Grid A as intended. A is backwards. Removing the alignment lock to Grid A means the wall has no reason to follow the grid when it moves, defeating the entire purpose of the operation. C is a misconception — unpinning Grid A addresses a different constraint (pinning prevents elements from being moved accidentally) and doesn't resolve the conflicting wall constraints at all. D is a distractor involving wall joins, which govern geometry at wall endpoints. Disallowing joins has no effect on the locked alignment or dimension constraints driving this conflict. A good rule of thumb: before moving any reference (grid, level, reference plane), audit every constraint on elements attached to it and ask "can all remaining locks still be satisfied after this move?" If not, release the conflicting one first.