Autodesk Fusion 360 Quiz: Diagnosing Sketch Constraints
10 questions · exam conditions
0:00
Diagnosing Sketch ConstraintsQuestion 1 of 10

A rectangular sketch has horizontal and vertical constraints on its edges. Its width and height are dimensioned, and the dimensions can no longer change. However, the entire rectangle can still be dragged without changing its size or orientation.

Which action most directly resolves the remaining under-constrained condition while preserving the rectangle's existing design intent?

Apply a coincident constraint between one intended reference point of the rectangle and the sketch origin.
Add a second width dimension to the opposite horizontal edge of the rectangle.
Apply equal constraints between both pairs of opposite edges of the rectangle.
Convert one horizontal edge and one vertical edge into construction geometry.
← Back to quizzes

Autodesk Fusion 360 Quiz

Autodesk Fusion 360 Quiz: Diagnosing Sketch Constraints

Practice Diagnosing Sketch Constraints in Autodesk Fusion 360 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 Diagnosing Sketch Constraints, giving you a quick way to practice the rules, question types, and explanations that matter most for Autodesk Fusion 360.

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 rectangular sketch has horizontal and vertical constraints on its edges. Its width and height are dimensioned, and the dimensions can no longer change. However, the entire rectangle can still be dragged without changing its size or orientation.

Which action most directly resolves the remaining under-constrained condition while preserving the rectangle's existing design intent?

  1. Apply a coincident constraint between one intended reference point of the rectangle and the sketch origin. (correct answer)
  2. Add a second width dimension to the opposite horizontal edge of the rectangle.
  3. Apply equal constraints between both pairs of opposite edges of the rectangle.
  4. Convert one horizontal edge and one vertical edge into construction geometry.
Explanation: When working with sketches in Fusion 360, you need to think in terms of degrees of freedom (DOF). A 2D sketch entity can move in three ways: horizontally, vertically, and rotationally. Constraints and dimensions remove these freedoms one by one until the sketch is fully constrained (shown in black). The question describes a rectangle that is correctly sized and oriented — meaning its rotation and shape DOF are gone — but it can still translate freely in the XY plane. That means two DOF remain: horizontal and vertical position. A is correct because anchoring one point of the rectangle to the sketch origin simultaneously removes both remaining translational DOF in a single, clean operation. The origin is the natural reference point in Fusion 360, and tying geometry to it directly expresses design intent — "this feature starts here." B is wrong because adding a second width dimension to the opposite horizontal edge doesn't fix the positional freedom at all. The rectangle's width is already defined; you'd be redundantly constraining a dimension that's already resolved, which Fusion 360 would flag as an over-constrained conflict. C is wrong because equal constraints between opposite edges would only enforce that opposing sides are the same length — a condition already satisfied by the existing width and height dimensions. This adds nothing new and doesn't address position. D is wrong because converting edges to construction geometry changes the sketch's structure without adding any positional constraint. Construction lines are still geometrically free unless explicitly constrained. A useful rule of thumb: when a sketch can still be dragged as a whole, the missing constraint is always positional — anchor it to a fixed reference like the origin.

Question 2

A sketch line has each endpoint constrained coincident with an endpoint of an associatively projected model edge. The projected edge is 60 mm60\text{ mm} long. Adding a driving length dimension of 55 mm55\text{ mm} to the sketch line produces an over-constrained warning.

If the sketch line should continue following the projected model edge, which resolution best preserves that intent?

  1. Convert the projected edge to construction geometry, then retain the 55 mm55\text{ mm} driving dimension.
  2. Delete one endpoint coincidence and retain the 55 mm55\text{ mm} driving dimension on the sketch line.
  3. Change the line's length dimension to driven so it reports the projected edge's current length. (correct answer)
  4. Apply Fix/UnFix to the sketch line and suppress the warning without changing either dimension.
Explanation: Whenever you see a conflict between a sketch element and its associatively projected source, ask yourself: what is the source of truth for this geometry? In Fusion 360, an associative projection means the sketch element is meant to follow the model edge — the model drives the sketch, not the other way around. Here, the sketch line is coincident with both endpoints of a projected edge that is 60 mm60\text{ mm} long. Adding a driving dimension of 55 mm55\text{ mm} creates a contradiction: you're telling Fusion the line is 55 mm55\text{ mm}, but the associative projection insists it must be 60 mm60\text{ mm}. The over-constrained warning is Fusion telling you these two instructions conflict. The correct resolution — C — is to change the 55 mm55\text{ mm} dimension to driven (reference) mode. A driven dimension simply reports the current length without imposing it, so the projection continues to control the geometry. The line faithfully follows the model edge, and the dimension updates automatically if the edge ever changes. A is wrong because converting the projected edge to construction geometry severs the associative link entirely — you'd lose the "follow the model edge" behavior the question explicitly asks to preserve. B removes one coincidence constraint, which would free the line to drift away from the projected edge rather than follow it. D uses Fix/UnFix to pin the sketch line at its current position, which hard-codes the geometry and breaks the dynamic relationship with the model edge — the opposite of associative intent. Remember: driving dimensions control geometry; driven dimensions report it. When a projection should govern length, let the projection drive and demote your manual dimension to driven.

Question 3

A designer opens a sketch and Fusion reports that it is fully constrained. The designer expected a line to remain adjustable through dimensions, but the line cannot be dragged and no dimensional constraint explains its locked location. The line has a Fix/UnFix constraint.

What should the designer do first to restore intentional parametric control and then diagnose the remaining degrees of freedom?

  1. Delete the line, redraw it in the same location, and rely on inferred constraints to preserve its position.
  2. Remove the Fix/UnFix constraint, drag-test the line, and add only the required geometric or dimensional constraints. (correct answer)
  3. Convert the line to construction geometry, drag-test it, and convert it back after adding dimensions.
  4. Add dimensions matching the line's current coordinates while leaving the Fix/UnFix constraint applied.
Explanation: Whenever you encounter a sketch that's "fully constrained" but for unexpected reasons, your first instinct should be to identify what is doing the constraining — because not all constraints represent intentional parametric design. Fix/UnFix is a rigid, position-locking constraint that pins geometry absolutely in space, bypassing the dimensional-and-geometric constraint system you'd normally use to drive a model's behavior. The right approach, captured in B, is to remove the Fix/UnFix constraint first. This immediately restores the line's degrees of freedom, allowing you to drag-test it and observe exactly which directions it can still move. From there, you can deliberately add only the geometric constraints (horizontal, vertical, coincident, etc.) or dimensional constraints (length, angle, position) that reflect your actual design intent. This is the essence of parametric modeling: constraints should be meaningful and editable, not just positional locks. A is a destructive workaround. Deleting and redrawing doesn't solve the conceptual problem, and inferred constraints (auto-constraints during sketching) may silently reapply a Fix or other unintended constraint — leaving you in the same situation. C converts the line to construction geometry, which changes its role in the sketch entirely. Construction geometry doesn't form profiles for extrusion, so this approach risks breaking downstream features and doesn't diagnose the actual constraint issue. D layers dimensional constraints on top of an active Fix/UnFix, creating redundancy without resolving the root problem. The Fix still overrides parametric intent, so your dimensions become cosmetic rather than controlling. As a study habit, always treat Fix/UnFix as a temporary tool for alignment purposes — never a substitute for proper sketch constraints in a production model.

Question 4

A line appears horizontal and initially does not move during light drag testing. Its length is dimensioned, but Fusion still reports the sketch as under-constrained. When the line is dragged more deliberately, it rotates slightly around a constrained endpoint.

Which diagnosis and correction best match this behavior?

  1. The line's length dimension has failed; delete it and apply a fixed constraint to the entire line.
  2. The endpoint coincidence controls orientation; replace it with a parallel constraint to the sketch axis.
  3. The line still has rotational freedom; apply a horizontal constraint if horizontal orientation is intended. (correct answer)
  4. The sketch solver is temporarily stale; close the sketch and reopen it without adding constraints.
Explanation: When diagnosing under-constrained sketches in Fusion 360, think about degrees of freedom — every sketch entity can move in translation, rotation, or both. A line has three degrees of freedom: X position, Y position, and rotation angle. Dimensioning its length removes one, but that still leaves two others. The scenario describes a line that resists light dragging but rotates when pushed more deliberately. This is the classic signature of a missing angular or orientation constraint. The length dimension is working fine — the line simply hasn't been told which direction to point. Applying a Horizontal constraint eliminates that rotational freedom entirely, which is exactly what option C prescribes. If the line were meant to sit at a different angle, a specific angle dimension would serve the same purpose. Option A misidentifies the problem entirely. The length dimension hasn't failed — the sketch acknowledges it, which is why the line doesn't stretch. Deleting it and applying a Fix constraint would over-constrain and rigidly lock the line's position, which is generally bad practice for parametric design. Option B introduces a parallel constraint to replace endpoint coincidence. Endpoint coincidence controls location, not orientation, so removing it would likely break positional relationships rather than fix rotation. A parallel constraint can enforce direction, but coincidence should not be discarded to get there. Option D suggests the solver is stale and closing the sketch will resolve it. Fusion 360's solver updates in real time; reopening the sketch adds no new constraints and changes nothing. Study tip: When Fusion reports under-constrained even after dimensioning, always ask "have I locked orientation too?" — length and angle are separate degrees of freedom.

Question 5

A fully constrained mounting-hole sketch contains a line whose endpoints and length are controlled by dimensions and geometric relationships. A later inspection reveals that the same line also has a Fix/UnFix constraint. Editing the length dimension causes an over-constrained warning.

Which modification is most likely to restore dimensional editing while preserving the existing parametric relationships?

  1. Remove the endpoint relationships and retain Fix/UnFix together with the edited length dimension.
  2. Delete the length dimension and retain Fix/UnFix as the primary parametric control for the line.
  3. Convert the line to construction geometry and leave both Fix/UnFix and the length dimension applied.
  4. Remove the Fix/UnFix constraint and retain the dimensions and geometric relationships that define the line. (correct answer)
Explanation: Whenever you encounter over-constrained sketch warnings in Fusion 360, your first instinct should be to identify redundant constraints — cases where the same degree of freedom is locked down more than once. A line has three degrees of freedom: position of each endpoint and length. Dimensions and geometric relationships already fully address all three, so adding a Fix/UnFix constraint on top creates a conflict — two systems are fighting to control the same thing. Removing the Fix/UnFix constraint, as described in D, eliminates that redundancy without disturbing anything meaningful. Your parametric dimensions and geometric relationships remain intact, the sketch stays fully constrained, and editing the length dimension works exactly as intended. This is the clean, parametric-friendly solution. A is backwards — removing the endpoint relationships and keeping Fix/UnFix discards the parametric chain you want to preserve. Fix/UnFix pins geometry absolutely in space, which is far less flexible than dimension-driven control when design intent needs to change. B deletes the length dimension and relies on Fix/UnFix as primary control, which abandons the parametric relationship entirely. You can no longer drive the line's length through a value — defeating the whole purpose of a parametric sketch. C converting the line to construction geometry changes its role: construction geometry doesn't contribute to profiles or boundary definitions. You'd lose the line's functional role in the sketch while still leaving the constraint conflict unresolved. A good rule of thumb: Fix/UnFix is a last resort, typically used for imported or reference geometry — not for lines already governed by dimensions. When you see both coexisting, Fix/UnFix is almost always the redundant one to remove.

Question 6

A rectangular profile is symmetric about a vertical construction centerline. Its width and height are dimensioned. The centerline is constrained vertical and has one endpoint coincident with the sketch origin. The rectangle can still slide upward and downward while remaining symmetric and retaining its dimensions.

Which added relationship most directly removes the remaining freedom without redundantly controlling width or height?

  1. Constrain the rectangle's center point coincident with the sketch origin or another intended point on the centerline. (correct answer)
  2. Apply equal constraints to the rectangle's opposite edges while keeping the symmetry constraint active.
  3. Add a second height dimension to the opposite vertical edge and match the existing height value.
  4. Apply a second vertical constraint to the construction centerline, since the existing one does not yet fix the rectangle's vertical position.
Explanation: Whenever you see a question about sketch constraints in Fusion 360, think in terms of degrees of freedom (DOF). Every sketch element starts with freedom to move, and your job is to fully constrain it by eliminating all remaining DOF without over-constraining. Here, the rectangle is symmetric about a vertical centerline, and its width and height are dimensioned — so it cannot change size or tilt. The centerline is vertical and pinned at the origin. What remains? The rectangle can still translate vertically, meaning it can slide up and down along the centerline. That's exactly one remaining DOF. Answer A directly eliminates that vertical translation by anchoring the rectangle's center point to the origin (or another fixed point on the centerline). Since the symmetry constraint already keeps the rectangle centered horizontally about the centerline, fixing the center point vertically is the single, clean fix that fully constrains the sketch. Answer B applies equal constraints to opposite edges, but those edges are already indirectly controlled by the symmetric constraint and the width/height dimensions — this would be redundant and could cause over-constraint errors. Answer C adds a duplicate height dimension to the opposite vertical edge. This is explicitly redundant: height is already defined, and Fusion 360 will flag a driven or conflicting dimension. Answer D misunderstands the role of the vertical constraint on the centerline. That constraint controls the line's orientation, not the rectangle's position along it. Adding a second vertical constraint to the same line is meaningless — it's already vertical. Study tip: Always ask yourself, "How many directions can this geometry still move?" Then apply exactly one constraint per remaining direction.

Question 7

Two circles have an equal constraint, and the first circle has a diameter dimension of 20 mm20\text{ mm}. A designer then attempts to apply a driving diameter dimension of 25 mm25\text{ mm} to the second circle.

Why does the new dimension conflict, and which change preserves the equal-size design intent?

  1. The circles share a center constraint; remove that constraint and retain both driving diameter dimensions.
  2. The equal constraint already controls the second diameter; make the 25 mm25\text{ mm} dimension driven or omit it. (correct answer)
  3. The first diameter controls both circle locations; replace the equal constraint with a concentric constraint.
  4. The second circle lacks a radius constraint; add a radius dimension before applying its diameter dimension.
Explanation: Whenever you see a question about sketch constraints in Fusion 360, think about redundancy: a sketch becomes over-constrained when you try to define something that's already fully controlled by an existing constraint. Here's the core logic. An equal constraint between two circles forces both diameters to always match. Once the first circle has a driving dimension of 20 mm20\text{ mm}, the equal constraint automatically propagates that size to the second circle — its diameter is no longer a free variable. Attempting to add a driving dimension of 25 mm25\text{ mm} to the second circle creates a direct contradiction: the equal constraint says d2=20 mmd_2 = 20\text{ mm}, while the new dimension says d2=25 mmd_2 = 25\text{ mm}. Fusion 360 flags this as an over-constrained conflict. The fix is exactly what B describes — either make the 25 mm25\text{ mm} dimension driven (so it merely displays the current value without controlling it) or omit it entirely, preserving the equal-size design intent without conflict. A is wrong because the issue has nothing to do with a shared center constraint. Removing a center or concentric constraint wouldn't resolve a size conflict at all. C misidentifies the problem entirely — a diameter dimension doesn't control circle location, and swapping the equal constraint for a concentric one would lose the size relationship the designer wants to preserve. D is a fabricated distractor; Fusion 360 does not require a radius dimension before accepting a diameter dimension, and that has no bearing on over-constraining. As a study tip: whenever a conflict appears in Fusion 360, ask yourself "what is already controlling this parameter?" Tracing the constraint chain almost always reveals the redundancy.

Question 8

A circle's center is coincident with the sketch origin. The circle already has a radius dimension of 25 mm25\text{ mm}. A designer wants the sketch also to display a diameter of 50 mm50\text{ mm} for documentation, but adding it as a normal dimension causes a constraint conflict.

What is the best way to display the diameter without over-constraining the circle?

  1. Delete the radius dimension and apply a Fix/UnFix constraint to the circle before adding the diameter.
  2. Keep the radius dimension and add the diameter as a driven reference dimension. (correct answer)
  3. Remove the center's coincident constraint and add the diameter as a driving dimension.
  4. Keep both dimensions as driving dimensions because their numerical values are mathematically consistent.
Explanation: Whenever you see a sketch constraint question in Fusion 360, the key concept to focus on is the difference between driving dimensions and driven (reference) dimensions. A driving dimension actively controls geometry, while a driven dimension simply displays a value calculated from existing constraints — it cannot conflict because it doesn't add new information. Here, the circle is already fully defined: its center is pinned to the origin (coincident constraint), and its size is set by the 25 mm25\text{ mm} radius dimension. Since radius and diameter are mathematically linked by d=2rd = 2r, adding a second driving dimension for 50 mm50\text{ mm} would tell Fusion 360 to control the same geometric property twice — causing an over-constrained conflict. The solution in B is correct: keep the existing radius dimension and add the diameter as a driven reference dimension (shown in parentheses in Fusion 360). It displays 50 mm50\text{ mm} for documentation without asserting any new control over the geometry. A is wrong because deleting the radius dimension and using Fix/UnFix doesn't preserve the clean parametric relationship — Fix locks geometry absolutely, which is a blunt workaround that breaks flexibility. C is wrong because removing the coincident constraint actually removes a constraint to make room for a conflicting one, destabilizing your sketch intent rather than solving the documentation need. D is a common trap — mathematical consistency doesn't matter to Fusion 360's constraint solver; two driving dimensions on the same property will always over-constrain, regardless of whether the numbers agree. As a study tip: anytime you need to display redundant information in a sketch without breaking constraints, think driven/reference dimension first.

Question 9

After adding a dimension to a nearly complete sketch, Fusion reports an over-constrained condition. The sketch contains several dimensions, inferred horizontal and vertical constraints, and one equal constraint. The designer does not yet know which existing relationship conflicts with the new dimension.

Which troubleshooting workflow is most appropriate before deleting geometry?

  1. Undo the new dimension, inspect related constraints and dimensions, then remove or convert only the redundant control. (correct answer)
  2. Apply Fix/UnFix to all sketch entities, then recreate the new dimension using the same measured value.
  3. Delete all automatically inferred constraints, then rebuild every relationship with dimensional constraints only.
  4. Convert all existing dimensions to driven dimensions, then restore them one at a time without inspection.
Explanation: When Fusion 360 reports an over-constrained sketch, it means one relationship is redundant — but that doesn't mean you should start deleting things blindly. The skill being tested here is systematic diagnosis: identifying the specific conflict before making any destructive changes. The right move, as captured in A, is to undo the new dimension first, which immediately resolves the over-constrained state and returns you to a working sketch. From there, you can methodically inspect the constraints and dimensions near the affected geometry — looking for duplicates, conflicting equal constraints, or inferred relationships that lock the same degree of freedom your new dimension was trying to control. Once you've identified the redundant control, you remove or convert only that one. This preserves all intentional design intent. B is counterproductive because Fix/UnFix locks geometry to absolute coordinates in world space — it doesn't help you diagnose which relationship is conflicting, and applying it broadly introduces new problems. C is far too destructive. Deleting all inferred constraints (like horizontals and verticals) throws away valid, intentional relationships that would need to be painstakingly rebuilt. It treats a surgical problem with a sledgehammer. D converts everything to driven (reference) dimensions without understanding why the conflict exists. Restoring dimensions one at a time without first diagnosing the redundancy is guesswork, not troubleshooting. The study tip here: whenever Fusion flags an over-constraint, your first instinct should be undo, then investigate — not delete. Fusion's constraint display and the Sketch palette are your diagnostic tools; use them before touching any geometry.

Question 10

A line visually touches a circle and has a tangent constraint to the circle. When the line is dragged, it remains tangent but its apparent contact point can move, and one endpoint can separate from the circle. The sketch remains under-constrained.

Which additional constraint should be applied if that specific endpoint must remain at the tangency location on the circle?

  1. Apply an equal constraint between the line and the circle so their sizes remain associated.
  2. Apply a midpoint constraint between the line endpoint and the center point of the circle.
  3. Apply a perpendicular constraint between the line and the circle at the apparent contact location.
  4. Apply a coincident constraint between the line endpoint and the circle while retaining tangency. (correct answer)
Explanation: Whenever you see a sketch constraint question in Fusion 360, ask yourself two things: what geometric relationship needs to be enforced, and between which specific entities? This question tests the difference between a tangency relationship (how the line meets the circle) and a positional relationship (where a specific point sits on the circle). A tangent constraint alone tells Fusion 360 that the line and circle must touch without crossing — but it doesn't specify which point of the line does the touching. That's why the endpoint can drift away while the sketch still satisfies tangency. To lock that endpoint to the circle's edge, you need a coincident constraint between the endpoint and the circle itself. Combined with tangency, this forces that exact point to live on the circle at the tangency location, fully anchoring the geometry. D is correct. A is wrong because an equal constraint relates the sizes of two entities (like matching radii or lengths) — it has nothing to do with position or where a point sits on a curve. B is wrong because a midpoint constraint places a point at the center of a line segment, not on a circle. Connecting the endpoint to the circle's center point would pull the endpoint inward, off the circle entirely — not anchor it to the circumference. C is wrong because a perpendicular constraint governs angle between two lines or curves. Tangency to a circle already implies perpendicularity between the line and the radius at contact, so this adds no new positional control. Study tip: In Fusion 360, always pair a tangent constraint with a coincident constraint when you need a specific endpoint pinned to a curve — tangency alone only governs how they meet, not where.