- Which capability would be lost by making that replacement?
Answer: Each valve would lose its own component occurrence, local origin context, and independent assembly placement.
When working with Fusion 360's data model, you need to distinguish between components and bodies — they serve fundamentally different structural roles. A component is a self-contained design unit with its own origin, timeline, local coordinate system, and the ability to exist as a discrete occurrence in an assembly. A body is simply geometry that lives within a component; it has no independent placement identity.
The scenario describes two valves that need separate local construction axes and independent positioning in an assembly. These are exactly the capabilities that components provide. When you place a component into an assembly, each instance — called an occurrence — gets its own transform, local origin context, and can be independently moved, constrained, and grounded. Replacing those two components with two bodies under the root strips away that entire occurrence system, which is why C is correct: each valve loses its component occurrence, local origin context, and independent assembly placement.
A is wrong because bodies can be created and modified by timeline features — features in Fusion 360 operate on geometry regardless of whether it belongs to a sub-component or the root. B is incorrect because material assignments in Fusion 360 apply to bodies, not exclusively to components, so bodies under the root can still receive separate materials. D is a tempting distractor, but visibility in Fusion 360 can be toggled per body individually, even under the root component — there is no single shared toggle that forces all root bodies to one visibility state.
As a study tip: whenever a question involves assembly structure, ask yourself what occurrence-level properties are at stake — placement, local axes, and independent instancing are all component-exclusive features in Fusion 360.
- Why is the current structure insufficient, and what is the appropriate correction?
Answer: The solids share one component identity; place the pin and lever in separate components before adding the joint.
Whenever you see a question about joints in Fusion 360, the fundamental concept to understand is that joints connect components, not bodies. This distinction is the heart of what this question is testing.
In Fusion 360's component hierarchy, a component is the fundamental unit of motion and assembly logic. When two bodies exist inside the same component, Fusion 360 treats them as a single rigid object — they share one component identity. You cannot apply a joint between two bodies that belong to the same component because the software has no mechanism to drive relative motion between them at that level. The correct fix, as described in A, is to place the pin and lever into separate components first, then apply a revolute joint between those components. This is exactly right.
B is wrong because extending the pin through the lever is a modeling action that changes geometry, not component structure. Contact between bodies doesn't enable joints — component separation does. C is wrong because grounding is used to fix a component in space relative to the origin, which prevents motion rather than enabling it; grounding a body also isn't the same as fixing the structural problem of shared component identity. D is wrong because combining bodies would make the situation worse by merging the two solids into one, and motion links are used to synchronize existing joints — they don't replace a revolute joint that can't yet be created.
Your study tip: always ask yourself "are these components or just bodies?" before adding any joint. If the objects live in the same component, split them first — joints need separate components to work.
- Which model organization is most appropriate?
Answer: Place the three bodies inside one enclosure component, then joint that single component to the frame.
When organizing geometry in Fusion 360, the central question is always: what moves together as a unit? Components define the assembly's motion structure — each component is the thing you joint, animate, or constrain. Bodies within a component are simply geometry that travels together as one rigid mass.
Here, the enclosure's three bodies (shell, insert, label) are permanently bonded — they never move relative to each other. The enclosure as a whole, however, needs to connect to a frame. That combination points directly to D: group all three bodies inside a single enclosure component, then apply one joint between that component and the frame. This mirrors real-world assembly logic and keeps your joint tree clean and intentional.
Answer A is factually wrong — Fusion 360 components can absolutely contain multiple bodies. Believing this would lead you to destructively merge distinct geometry, losing the ability to manage or reference individual bodies later. Answer B creates three separate components unnecessarily, forcing you to manage three rigid joints where one suffices. This bloats the assembly, invites misalignment errors, and misrepresents the physical object — the enclosure is one purchased item, not three. Answer C is a common trap: bodies living under the root component lack a proper component identity, so jointing directly to a body (rather than a component) is unreliable and considered poor practice in Fusion 360's assembly workflow.
Study tip: On Fusion 360 questions, map "things that move or assemble as one unit" to components, and "distinct geometry within that unit" to bodies inside that component. This single rule resolves most model organization scenarios.
- Which statement best describes the significance of activating the subassembly during sketch creation?
Answer: It places the sketch in the subassembly's modeling context, while referenced assembly geometry may create contextual dependencies.
When working with assemblies in Fusion 360, the concept of modeling context is critical. Whichever component is active when you create a sketch or feature becomes the owner of that element. Simultaneously, if your sketch references geometry from other components, Fusion 360 establishes contextual dependencies — live links that tie your sketch to external geometry within the assembly environment.
This is exactly what answer C captures. Activating the subassembly makes it the owner of the newly created sketch, placing it firmly within that subassembly's modeling context. However, because the sketch references assembly-level geometry (from outside the subassembly), Fusion 360 records those references as contextual links. This means if that external geometry changes later — even from an unrelated root-level edit — the sketch may update or break depending on how those references resolve.
Answer A is incorrect because activating a component never "grounds" it or freezes external geometry. Grounding is a separate joint concept that constrains positional freedom, not sketch references. Answer B is wrong because activating a subassembly does not convert bodies into separate occurrences, nor does it reassign sketch ownership to the root component — the active component always owns new sketches. Answer D is incorrect because activating a subassembly does not absorb or claim all assembly geometry; geometry from other components remains external, which is precisely why contextual dependencies form.
As a study tip, remember this rule: the active component owns the sketch, but referenced external geometry creates contextual dependencies. Fusion 360 questions about assembly modeling frequently test whether you understand this ownership-versus-reference distinction.
- What is the most likely organizational result, and how should the workflow be corrected?
Answer: The new features belong to the root context; activate the housing before creating housing-owned features.
Whenever you see a question about feature ownership in Fusion 360 assemblies, think about the active component rule: whatever component is active at the time you create a feature is the component that owns it.
In Fusion 360, features — sketches, bodies, extrusions — belong to whichever component is currently active, not to the component whose geometry you happen to be referencing or clicking on. When the root component is active, any sketch you draw and any body you create gets placed under the root, even if you're sketching on a face that visually belongs to the housing. This means the housing's geometry is being used as a reference, but the new features are organizationally owned by the root component. The correct fix is to double-click the housing in the browser to activate it first, then create your sketch and extrude — ensuring those features live inside the housing's component context. That makes answer A correct.
Answer B is wrong because Fusion 360 does not infer ownership from which component's face you select — the active component always determines ownership, regardless of context. Answer C describes a split ownership scenario (sketch in one component, body in another) that simply doesn't happen; both are created under the same active component. Answer D is a fabricated rule — adjacency has no bearing on feature ownership, and "isolating" a component doesn't reassign ownership the way activating it does.
Study tip: In Fusion 360 assembly questions, always ask "which component is active?" before anything else — that single factor controls where every new feature ends up in the browser hierarchy.
- Which workflow most directly prepares the model for the required assembly behavior?
Answer: Create components from the two bodies, then define the sliding relationship between those components.
When working with assembly joints in Fusion 360, the core principle to remember is that joints connect components, not bodies. Fusion 360's joint system is built around components as the fundamental unit of assembly — bodies are geometry, while components carry positional identity and degrees of freedom.
This means the essential first step whenever you need assembly behavior is converting bodies into components. Once you use Create > Create Components from Bodies, each body becomes its own independent component with its own origin and transform. From there, you can apply a Slider joint between the jaw component and the base component, which constrains motion to a single translational axis — exactly the sliding behavior the question describes. That's why A is correct: it follows the proper Fusion 360 workflow in the right order.
B fails because placing both bodies inside a single component doesn't enable joint behavior between them. Joints operate between components, not between bodies sharing the same component container.
C is tempting because grounding sounds like a reasonable first step, but you cannot apply joints directly to bodies under the root component. Grounding is meaningless here without first creating components.
D is the most dangerous distractor: using the Join operation merges the two bodies into one, permanently destroying the separate geometry you need for independent motion. A combined body cannot slide relative to itself.
A useful rule of thumb: if a question involves motion or positional constraints in Fusion 360, your first instinct should always be to ask, "Do I have components yet?" If not, create them before touching any joint tools.
- Which sequence creates the intended hierarchy most reliably?
Answer: Create a new component under the gearbox, activate it, and create the cover sketch and body in that context.
When working with Fusion 360's component hierarchy, the key distinction to understand is the difference between a body and a component. Bodies are raw geometry — they have no independent identity, no sketch ownership, and no joint behavior. Components are containers that hold their own sketches, bodies, construction geometry, and eventually joints. Whenever you need a part that behaves as its own discrete entity within an assembly, you need a component, not just a body.
Option B is correct because it follows Fusion 360's intended workflow precisely. By creating a new component under the gearbox (making it a child of the gearbox component), you establish the correct nested hierarchy. Activating that new component before sketching and extruding ensures that all geometry — sketches, origin, and resulting body — belongs to the service cover component, giving it its own part identity and enabling future joint and contact behavior scoped correctly within the assembly.
Option A fails because renaming a body doesn't transform it into a component. Bodies cannot own sketches, cannot be jointed independently, and dragging them between folders doesn't change their fundamental nature. Option C makes the same mistake — adding another body inside the gearbox context creates shared geometry without a separate part identity, and assigning a joint between two bodies inside the same component is not the same as a proper assembly joint. Option D is a trap: Fusion 360 doesn't support converting a sketch into a component, and creating geometry under the root before the intended parent component exists produces incorrect parentage that is cumbersome to fix.
As a study tip, remember: component first, then activate, then create geometry. That activation step is what Fusion 360 uses to determine ownership of everything you build.
- Which action best restructures the design with the least remodeling?
Answer: Use Create Components from Bodies so each selected body becomes organized in a separate component.
When you encounter a question about restructuring an existing Fusion 360 design into components, ask yourself: what's the most direct path from bodies to components without losing geometry or position?
In Fusion 360, solid bodies and components serve different roles. Bodies are raw geometry; components are organizational units that can carry metadata like part numbers, participate in joints, and appear independently in the BOM. The Create Components from Bodies command (found under Assemble) was built precisely for this legacy-conversion scenario — it wraps each selected body in its own component in a single operation, preserving geometry and position exactly. No remodeling, no repositioning, no sketching required. Answer A is the correct choice because it matches the scenario's requirements directly and efficiently.
Answer B is wrong because dragging all three bodies into one component defeats the purpose — the parts would share a single component identity, making independent part numbering and jointing impossible. They'd still be distinguishable as bodies, but not as separate components.
Answer C is a trap for students who confuse the Combine tool with restructuring. Combining merges geometry into a single body, which would destroy the distinct shapes you need to preserve — the opposite of the goal.
Answer D describes full remodeling from scratch: projecting geometry into sketches and re-extruding. This is the most labor-intensive option and introduces unnecessary risk of dimensional error. The question specifically asks for least remodeling, so this fails immediately on that criterion.
A useful rule of thumb: whenever a question mentions "legacy bodies" that need to become components, Create Components from Bodies is almost always the answer — it's the dedicated tool for exactly that workflow.
- Which duplication strategy best satisfies both requirements?
Answer: Copy the roller component and use Paste to create additional occurrences of the same component definition.
Whenever you see a question about managing repeated parts in Fusion 360, focus on two distinct needs: linked definitions (edits propagate everywhere) and independent positioning (each instance lives where you put it). These are not in conflict — Fusion 360 handles both through the concept of component occurrences.
A component in Fusion 360 has one definition but can appear multiple times in an assembly as separate occurrences. Each occurrence has its own position, joint, and transform, yet they all share the same underlying geometry. This means editing the component once — changing the bore, for example — updates every occurrence automatically. Copying a component and using Paste (not Paste New) creates exactly this: additional occurrences of the same component definition. That's why D is correct.
A is wrong because placing multiple bodies inside a single component doesn't give you independent assembly-level positioning control; bodies within a component move together as one unit and aren't treated as separate assembly instances. B is the opposite trap — Paste New deliberately breaks the link between definitions, creating completely independent components that no longer update together when you edit one. This satisfies independent positioning but destroys the shared-definition requirement. C copies raw geometry (a body) into the root component, which loses all component structure entirely; bodies can't be jointed the way components can, and they don't share a definition.
Study tip: On Fusion 360 questions, watch for the Paste vs. Paste New distinction — it's a classic trap. Paste = shared definition (linked), Paste New = independent definition (unlinked). Know which one you need before you click.
- Why will this organization not provide the intended motion?
Answer: Both bodies belong to the grounded component, so they share one assembly occurrence and cannot move independently.
Whenever you see a question about motion and dragging in Fusion 360, the key distinction to understand is the difference between bodies and components. Bodies are geometry that lives inside a component; components are the assembly-level objects that Fusion 360 tracks for position, joints, and motion.
When you ground a component, you freeze that entire component's occurrence in the assembly — every body inside it becomes immovable as a unit. Since both the base plate and the locating block are bodies within the same single component, they share one assembly occurrence. There is no separate occurrence for the locating block that the assembly engine can track or translate independently. Dragging in the assembly workspace operates on component occurrences, not on individual bodies, so neither body can be moved relative to the other regardless of grounding.
Choice A is wrong because grounding applies to the whole component, not selectively to one body inside it. Rigid groups are used to lock multiple components together — they're irrelevant here since the problem is that there's only one component to begin with. Choice C incorrectly invokes "capture position," which records the current state of component positions but has no bearing on whether bodies within a single component can move independently — they cannot, ever. Choice D is a fabricated constraint; a body's lack of a separate sketch origin has no effect on whether it can be repositioned.
The correct answer is B: both bodies share one grounded component occurrence, so independent motion is architecturally impossible in this setup.
Study tip: Always ask yourself whether your design elements are separate components or just bodies inside one component — this distinction controls everything about assembly motion in Fusion 360.
