- Which recovery method is most likely to preserve the downstream sketch relationships?
Answer: Repair the broken projection reference by reassociating it with the intended replacement edge using Fusion 360's broken-reference repair tools.
Whenever you encounter broken reference errors in Fusion 360, the core principle to keep in mind is parametric continuity — your goal is to maintain the associative chain between upstream geometry and downstream features, not rebuild from scratch. This question tests whether you understand how to surgically repair a broken link rather than destroying the work built around it.
The right move here is C. Fusion 360 provides broken-reference repair tools that let you reassociate a failed projection with a new, valid edge. Because the replacement edge already occupies the correct location, rerouting the reference preserves every dimension and constraint that depended on the original projected entity. The downstream sketch stays intact; only the broken link is replaced. This is exactly the purpose these tools exist for.
Option A is a destructive overreaction. Deleting the downstream sketch throws away all the constraints and dimensions you've carefully built — you'd be starting over unnecessarily, and you'd face the same potential instability if the model changes again. Option B is similarly destructive to relationships: drawing an unconstrained line over the edge creates a "floating" element with no parametric tie to the upstream geometry, meaning future upstream changes won't propagate correctly. You've lost the intelligence of the model. Option D sidesteps the problem entirely without solving it — suppressing the split feature might restore the original projection temporarily, but it defeats the purpose of the split and leaves the model in an incomplete, unresolved state.
Study tip: On Fusion 360 exam questions, whenever a downstream feature breaks due to upstream changes, the preferred answer almost always involves repairing the reference, not deleting or bypassing it. Preservation of parametric relationships is the guiding philosophy of the software.
- Which modification most directly prevents the unintended movement while preserving the intended parametric behavior?
Answer: Dimension the rectangle to the sketch origin and verify that the sketch is fully constrained.
Whenever you see a question about unexpected movement in Fusion 360 assemblies, think about sketch constraint completeness and how geometry is anchored relative to the origin. The root cause of geometry shifting is almost always an underconstrained sketch — one where dimensions exist but the sketch's position in space is not locked down.
In this scenario, the rectangle has width and height dimensions, but nothing ties it positionally to the sketch origin. When you edit the width, Fusion recalculates geometry from an ambiguous reference point, causing the whole sketch to drift. The fix in B — dimensioning the rectangle to the sketch origin and confirming full constraint — directly solves this. Once the rectangle's edges or corners are explicitly located relative to the origin, editing width or height regenerates predictably because the anchor point never changes. A fully constrained sketch (no blue lines remaining) guarantees this stability while keeping all parametric dimensions intact.
A is a trap: fixing every line freezes geometry absolutely, which destroys parametric flexibility. You can no longer edit width or height at all, which violates the requirement to preserve parametric behavior.
C addresses assembly-level grounding, which prevents the component from moving freely in the assembly space, but it does nothing to fix the internal sketch ambiguity — the hole still drifts relative to the rectangle when the sketch regenerates.
D — projecting finished body edges back into the base sketch — creates circular references and downstream rebuild errors. It's a workflow anti-pattern, not a constraint solution.
For the exam, remember: fully constrained sketch + origin-referenced dimensions = predictable parametric behavior. If geometry moves unexpectedly, always audit sketch constraints before looking at assembly-level fixes.
- Which workflow best prevents future source revisions from changing the receiving sketch?
Answer: Break the projection link, then constrain and dimension the resulting sketch geometry as required.
When working with projected geometry in Fusion 360, the key distinction to understand is associativity — whether a sketch element automatically updates when its source changes. Questions like this ask you to recognize when breaking that link is the right engineering decision.
The scenario explicitly states that future revisions to the source component must not affect the receiving sketch. The cleanest solution is B: breaking the projection link. In Fusion 360, you can right-click projected (purple) geometry and select "Break Link," which converts it into independent sketch geometry. Once unlinked, the geometry is yours to constrain and dimension freely — it becomes a stable, editable foundation completely immune to upstream changes.
A is tempting but fundamentally flawed. Fix/UnFix locks geometry in place spatially, but it does not sever the associative projection link. If the source component changes in a way that conflicts with the fixed constraint, Fusion 360 can throw errors or produce unexpected results — the link still exists.
C misunderstands what disabling design history (timeline) actually does. It affects parametric history capture, not projection associativity. The linked geometry remains live, so source changes can still propagate to the receiving sketch.
D is also incorrect. Grounding a component fixes its position in space but has no effect on whether projection links remain active. The sketch would still update if the source geometry itself were modified.
Your study tip: whenever a question mentions "one-time snapshot" or "must not update," that's a signal to break the link rather than constrain or lock the associative geometry — those are different operations solving different problems.
- Which assembly strategy would best reduce this risk for future vendor revisions?
Answer: Create joint origins from stable interface datums and define the assembly joints between those joint origins.
When working with vendor components in Fusion 360 assemblies, the core challenge is reference stability — your joints need to survive model swaps where internal geometry identities can change unpredictably. The best strategy is to insulate your assembly logic from the vendor model's internal topology.
This is exactly what A accomplishes. By creating joint origins on stable, intentionally defined interface datums (like a construction point or axis at the mounting interface), you anchor your joints to geometry you control — not geometry buried inside the vendor file. When the vendor model is replaced, your joint origins remain intact, and the assembly relationships survive because they reference your datums, not the vendor's internal edges.
B is a trap — applying a rigid group freezes relative positions between components, but it doesn't help when a replacement breaks joint references. A rigid group has no power to restore lost geometry references.
C is a workaround, not a strategy. Grounding and suppressing joints before each replacement creates manual overhead every revision cycle and still doesn't solve the root problem of fragile references — it just sidesteps them temporarily.
D misunderstands how joint reference resolution works. Adding more edges doesn't guarantee one will survive; if the internal topology changes, all selected edges could lose their identity simultaneously. More references to unstable geometry just creates more points of failure.
The key study tip here: whenever you see questions about assembly robustness across design changes, ask yourself "who owns the reference geometry?" If the answer is a vendor or external file, abstract it away with your own datums. That's the stable-interface principle.
- Which modification most effectively prevents the slot from following the unstable housing edge?
Answer: Replace the projected centerline with a construction line constrained to the component origin or an origin plane.
Whenever you see a Fusion 360 sketch question involving projected geometry, ask yourself: where is this reference anchored? Projected edges and midpoints inherit their position from the parent body, so if that body changes unpredictably, anything referencing it will drift — even inside a "fully constrained" sketch.
In this scenario, the projected centerline is tied to a housing edge that moves asymmetrically. The slot sketch is fully constrained relative to that centerline, but the centerline itself is a moving target. The fix is to anchor the symmetry reference to something that never moves: the component origin or an origin plane. Answer A does exactly this — replacing the projected centerline with a construction line locked to the origin eliminates the dependency on the unstable edge entirely, giving the slot a fixed, reliable axis of symmetry regardless of housing changes.
B is tempting because Equal constraints on the two end arcs do enforce width symmetry, but they don't control the slot's position along the housing. The slot can still drift laterally when the housing shifts. C adds a redundant width dimension to a sketch that's already fully constrained for width — this doesn't address the position problem at all and would actually over-constrain the sketch. D is a workflow trap: manually fixing the profile after every change is not a parametric solution. It defeats the purpose of constraint-based modeling and introduces human error each time the housing updates.
Study tip: In Fusion 360, "fully constrained" only means constrained relative to its references — if the references themselves are unstable, the geometry is still effectively floating. Always trace your sketch references back to stable geometry like origin planes.
- Which change would most likely make the pattern less sensitive to these topology changes?
Answer: Use a feature pattern that references the pocket-producing timeline feature rather than its resulting faces.
When building patterns in Fusion 360, the key distinction to understand is face patterns vs. feature patterns. A face pattern copies the geometry results of a feature — the actual faces produced at that moment in the timeline. A feature pattern copies the operation itself, replaying it parametrically for each instance. This question is testing whether you understand why that difference matters when the model evolves.
When you add draft and fillets to the original pocket, the underlying faces change — some split, some disappear, some are newly created. A face pattern has no awareness of the feature logic; it only holds references to specific face IDs, which are now broken. A feature pattern, by contrast, references the pocket-producing timeline entry (the extrude cut, for example), so when the model rebuilds, each instance replays that feature's logic, including the new draft and fillets. This is exactly why D is correct — it eliminates the fragile face-reference dependency entirely.
A is a red herring; Fix/UnFix controls sketch constraints and has no effect on how pattern references resolve after topology changes. B might temporarily work, but it doubles down on the fragile approach — you'd need to manually reselect faces every time geometry changes, making the model harder to maintain, not less sensitive. C sounds like a workaround but actually creates more rigidity; converting pockets to grounded bodies removes them from the parametric history entirely, breaking the associativity you want to preserve.
As a study tip: whenever a Fusion 360 question involves patterns failing after edits, ask yourself whether the pattern references geometry results or timeline operations. Feature patterns are almost always more robust for parametric workflows.
- Which statement most accurately evaluates the reviewer's conclusion?
Answer: The conclusion is incorrect because full constraint removes local degrees of freedom but linked references can still move.
When working with Fusion 360's parametric timeline, you need to distinguish between local constraints and external dependencies. A sketch's constraint status tells you only whether its own internal geometry has zero remaining degrees of freedom — it says nothing about what happens when the references that geometry is built on change.
This is exactly why C is correct. Associative projections pull live geometry from an upstream body into your sketch. When those upstream edges or faces move due to a design revision, the projected references update automatically — and your sketch geometry moves with them, even though the sketch itself remains "fully constrained." Full constraint eliminates local degrees of freedom (no free-floating points, no undefined angles), but it doesn't freeze the anchors those constraints are attached to. The sketch is constrained relative to its references, not relative to absolute space.
A is the trap most students fall into. "Fully constrained" sounds absolute, but it only means the sketch's internal geometry is locked relative to its own reference frame — which can itself shift when upstream geometry changes. This is a fundamental misconception about what constraint status actually measures.
B introduces a component-boundary condition that doesn't exist in Fusion 360's constraint logic. Whether the upstream body and downstream sketch share a component has no bearing on whether associative projections will update and carry the sketch geometry along.
D incorrectly narrows the problem to named user parameters. Parameters can drive change, but the vulnerability here comes from any upstream revision that alters projected geometry, not just parametric dimensions.
Remember: in Fusion 360, always ask "what are my constraints anchored to?" — a fully constrained sketch tied to moving references will move with them.
- Which change best aligns the feature reference with the stated requirement?
Answer: Change the extent to Distance and set the extrusion distance to 18 mm.
When a design requirement specifies a fixed dimension, your modeling strategy should directly encode that dimension — not rely on the position of another object that may change. This question tests whether you can distinguish between reference-based extents (which adapt to geometry) and explicit-distance extents (which guarantee a specific value).
Setting the extent to Distance and entering 18 mm directly satisfies the requirement. The boss will always be exactly 18 mm tall regardless of what happens to the cover — it's a hard-coded, geometry-independent value. That's precisely what "must always be exactly 18 mm" demands. B is correct.
A sounds clever — using an offset from the cover face seems like it could enforce 18 mm — but the flaw is that To Object still references the cover's position as the starting logic. If the cover face moves, the offset is measured from a new baseline, potentially changing the effective boss height depending on how the feature resolves. More importantly, the fundamental driver is still the cover, not an absolute distance.
C grounding the cover locks it in this assembly configuration, but grounding is an assembly constraint, not a modeling rule. If the cover is ever repositioned or the constraint is relaxed, the boss height breaks. It's a workaround, not a solution.
D introduces unnecessary complexity. Adding a construction plane doesn't change the extrusion extent type, and All would cut or extend through the entire body — it doesn't guarantee 18 mm.
Study tip: When a requirement uses the word "always" with a specific value, that's a signal to use an explicit Distance extent rather than any reference-based extent.
- Which timeline and reference change best reflects the design intent while avoiding the failure?
Answer: Reference stable pre-chamfer wall or datum geometry and place the chamfer after the dependent rib feature.
Whenever you encounter timeline dependency failures in Fusion 360, the core question to ask is: what geometry should this feature actually be anchored to, and is that anchor stable across all configurations? Parametric modeling problems like this one test whether you understand how upstream changes cascade downstream.
The correct approach, answer D, addresses both the root cause and the design intent simultaneously. If the rib is meant to align with the unchamfered wall, it should reference the wall's pre-chamfer edge or a datum plane derived from that wall — geometry that exists regardless of whether the chamfer is present. Placing the chamfer after the rib in the timeline then ensures the rib's reference never disappears when the chamfer is suppressed, eliminating the failure entirely. This is called resolving a fragile parent-child dependency by anchoring children to stable, upstream geometry.
Answer A is a workaround, not a fix — it forces the chamfer to always exist, which defeats the purpose of the manufacturing configuration and doesn't reflect the stated design intent. Answer B uses a fixed copy of the chamfer edge, which freezes the geometry at a snapshot in time; it breaks associativity and will silently drift out of sync if the wall geometry changes later. Answer C is geometrically impossible — you cannot reference the chamfer edge before the chamfer feature exists in the timeline, so moving the rib upstream while keeping that reference simply relocates the error.
As a study rule: stable references beat convenient references. Always ask whether your sketch reference survives feature suppression, deletion, or reordering — if it doesn't, redesign the dependency chain, not the suppression behavior.
- Which redesign is most likely to make the sweep path resilient to future fillet changes?
Answer: Project geometry from a dimensioned master sketch referenced to origin geometry, then use that projection as the path.
When working with parametric modeling in Fusion 360, the core concept being tested here is reference stability — specifically, how to build downstream features that survive upstream geometry changes. Whenever a sweep, loft, or cut depends on a projected solid edge, you're creating a direct dependency on that edge's identity. If the upstream operation (like a fillet) replaces or regenerates that edge, Fusion loses track of it, breaking the downstream feature.
The most resilient approach, as answer A describes, is to anchor your geometry to stable, origin-referenced sketch entities rather than transient solid edges. A master sketch tied to origin planes and explicit dimensions doesn't "disappear" when a fillet radius changes — it exists independently of the solid's edge topology. Projecting from that stable sketch into your sweep path sketch means the path survives any upstream solid modification.
Answer B is a workflow workaround, not a redesign. Gradually increasing the fillet radius may occasionally help Fusion track edge identity, but it's fragile and unreliable — it doesn't solve the underlying architectural problem.
Answer C is a contradiction. "Fixing" a projected edge while keeping its projection link active doesn't break the dependency on the solid edge; the reference can still be lost when topology changes.
Answer D is structurally impossible in the parametric timeline. A sweep that uses an extruded solid's geometry cannot logically precede that extrusion — moving it before the base feature would create a circular or unresolvable dependency.
Study tip: On Fusion 360 parametric design questions, always favor sketch-based geometry anchored to the origin over projected solid edges when resilience to future changes matters. Stable references live in sketches, not in solid topology.
