Move/Copy - Autodesk Fusion 360

  1. What is the best way to implement the revision?
    Answer: Edit the existing Move feature and change its translation from 18 mm18\text{ mm} to 23 mm23\text{ mm}. When working with Fusion 360's parametric timeline, the key principle is editing intent — your timeline should clearly communicate the designed value, not accumulate a chain of incremental corrections. Whenever a recorded feature needs revision, ask yourself: should I reflect the true design value, or just patch over it? The cleanest solution here is D: double-click the existing Move/Copy feature in the timeline and update the translation directly from 18 mm18\text{ mm} to 23 mm23\text{ mm}. This preserves a single, readable feature whose value matches your design intent exactly. Fusion 360 will recompute all downstream features accordingly — that's the power of a parametric, history-based workflow. A is a destructive approach. Deleting the body eliminates all history associated with it and breaks any downstream dependencies, which is far too drastic for a simple value change. B adds a second Move feature of 23 mm23\text{ mm}, which would result in a cumulative translation of 18+23=41 mm18 + 23 = 41\text{ mm} — not the intended 23 mm23\text{ mm}. This is a classic arithmetic trap: the new feature stacks on top of the old one rather than replacing it. C is mathematically aware (18+5=23 mm18 + 5 = 23\text{ mm}), but it clutters the timeline with two features where one suffices. A future reviewer — or future you — must mentally add the values to understand the actual offset, which defeats the purpose of a clean parametric history. Study tip: On Fusion 360 questions, always prefer editing an existing parametric feature over adding compensating features. A clean timeline with self-evident values is both best practice and the most commonly tested correct behavior.
  2. Which Move/Copy settings create the required result in one operation?
    Answer: Select the spacer body, enable Create Copy, and apply the 40 mm40\text{ mm} translation. Whenever you see a Move/Copy question in Fusion 360, ask yourself two things: what object am I acting on, and do I need the original to stay put? Those two factors together determine the correct settings. The Move/Copy command behaves very differently depending on whether Create Copy is enabled. Without it, the selected geometry simply relocates — the original disappears from its starting position. With it, Fusion 360 duplicates the geometry and moves the copy, leaving the original untouched. For this scenario, you need two spacer bodies: the original at its current position and a new one translated 40 mm40\text{ mm} along the X axis. That means you must select the body, enable Create Copy, and apply the translation — exactly what C describes. One operation produces both bodies simultaneously. A is wrong for two reasons: you should select a body, not a component (components carry additional structure), and suppressing the original afterward is an unnecessary extra step that contradicts the "one operation" requirement. B selects the correct object type (the body) but disables Create Copy, so the operation simply moves the original 40 mm40\text{ mm} — you end up with one body in the new position and nothing at the original location. D selects only a single face rather than the entire body; moving a face pushes that face's geometry, distorting the solid rather than copying it. A useful rule of thumb: body = the geometry you want to duplicate; Create Copy = preserve the original. If a question mentions keeping the original and adding a new instance, both conditions must be satisfied simultaneously.
  3. Which Move/Copy setup best accomplishes the relocation?
    Answer: Set Move Object to Components, select the mounting unit, and translate the component. When working with Fusion 360's Move/Copy dialog, the key question to ask yourself is: what level of the hierarchy do I need to move? Fusion organizes designs into components, bodies, sketches, and construction geometry — and moving at the wrong level can leave parts of your design behind. Here, the mounting unit is a component containing multiple elements: two solid bodies, a construction axis, and a sketch. The only way to relocate all of these together — preserving their relative positions — is to move the component itself. When you set Move Object to Components and select the mounting unit, Fusion treats the entire container as one entity and translates everything inside it uniformly. That's why B is correct. A is tempting but flawed: moving bodies individually (or even together) only relocates the solid geometry. The construction axis and sketch remain at their original positions, breaking the spatial relationships within the unit. C makes the problem worse — translating faces via the Faces option performs a push/pull-style deformation on the solid bodies rather than relocating them. You'd distort the geometry, not move it. D targets only the sketch geometry. Even if you translated the sketch correctly, the two solid bodies and the construction axis would stay put, leaving the component's contents misaligned. A useful rule of thumb: if everything inside a container must move together, move the container — not its contents. On Fusion 360 questions involving assemblies, always look for the option that operates at the highest appropriate level of the design hierarchy.
  4. Where will the reference point be relative to the rotation axis after the move?
    Answer: (0,30,0) mm(0,30,0)\text{ mm}, because positive rotation carries positive X toward positive Y. When a question involves rotating a point about an axis, think in terms of the right-hand rule and standard rotation conventions. In a right-handed coordinate system, a positive rotation about the Z axis sweeps the positive X axis toward the positive Y axis — this is the foundational rule that unlocks this entire problem. Starting at (30,0,0) mm(30, 0, 0)\text{ mm}, the point sits on the positive X axis at radius r=30 mmr = 30\text{ mm}. Applying the 2D rotation formula for θ=90°\theta = 90°: x′=rcos⁡(90°)=30⋅0=0x' = r\cos(90°) = 30 \cdot 0 = 0 y′=rsin⁡(90°)=30⋅1=30y' = r\sin(90°) = 30 \cdot 1 = 30 The new position is (0,30,0) mm(0, 30, 0)\text{ mm}, confirming that A is correct. Positive rotation carries positive X toward positive Y — exactly what the right-hand rule predicts. B describes a clockwise (negative) rotation, which would give (0,−30,0)(0, -30, 0). This is the most common trap: confusing positive and negative rotation direction. C is physically nonsensical — rotation keeps the point at a fixed radius from the axis; it never adds the radius to a coordinate. If you see an answer that changes the distance from the axis during a pure rotation, eliminate it immediately. D is a fundamental misunderstanding: rotating a rigid body absolutely repositions its points in space — only the relative distances between points within the body stay fixed. As a study tip, always sketch the XY plane and mark positive X. Ask yourself: "Which way does positive Z rotation sweep?" That quick mental sketch will save you from the B trap every time.
  5. What should the designer do before applying the translation?
    Answer: Unground the component, and then use Move/Copy to translate the component occurrence. Whenever you see a question about moving components in Fusion 360, the key distinction to keep in mind is the difference between a grounded component and a free one. A grounded component is pinned to the assembly origin — it has zero degrees of freedom, so any translation you attempt will be blocked or ignored because the ground constraint overrides the move. To actually reposition a component occurrence and have it stay in its new location, you must first remove that ground constraint. That's exactly what answer A describes: unground the component first, then use Move/Copy to apply the 25 mm25\text{ mm} translation. Without the ground, the occurrence is free to move, and its new position becomes its assembly position — no copy needed, no workaround required. Answer B is wrong because activating a component and moving only its solid body changes the body's position within the component's local space, not the component's placement in the assembly. This creates an internal offset, not an assembly-level translation. Answer C is wrong because enabling Create Copy duplicates the component into a new occurrence at the translated position — the original grounded occurrence stays where it is. The designer wants to move the existing occurrence, not create a second one. Answer D is wrong because converting a component to a body destroys the component structure (hierarchy, joints, and references), which is a destructive and unnecessary step just to perform a simple translation. As a study tip: on Fusion 360 questions, always ask yourself whether a constraint (like ground) would prevent the intended action — resolving the constraint is usually step one.
  6. Which Move/Copy workflow is the most appropriate?
    Answer: Choose Rotate, select the hole's cylindrical axis or a coincident construction axis, and enter the angle. When working with Move/Copy in Fusion 360, the critical question to ask yourself is: what is my pivot point, and am I rotating or translating? This question tests whether you understand how to define a custom rotation axis so that a body spins in place around a specific geometric feature. Because the lever must rotate around the cylindrical hole's centerline without any translation, you need precise control over both the type of motion and the pivot location. Option A is correct because selecting Rotate lets you explicitly define the axis of rotation — in this case, the hole's cylindrical face axis or a construction axis coincident with it — and then enter an exact angle. The body rotates purely around that centerline with zero translation, which is exactly what the scenario demands. Option B fails because Free Move keeps the default manipulator pivot, which is not on the hole centerline. Dragging a translation arrow also introduces linear movement, violating the "must not translate" constraint. Option C is a trap — Point to Point is a translation mode that moves a body so one point aligns with another; it does not perform angular rotation around an axis, and selecting "opposite points on the hole" would simply shift the body, not spin it. Option D reveals a common misconception: Translate moves a body linearly along a direction vector. Entering an angular value into a translation field is nonsensical — Translate has no angular input. Study tip: On Move/Copy questions, always match the motion type (rotate vs. translate) to the goal first, then verify whether the pivot/axis can be explicitly set to the required geometric feature.
  7. Where is the reference point after both features are evaluated in timeline order?
    Answer: (−15,0,0) mm(-15,0,0)\text{ mm}, because the translated location is then rotated about the origin. Whenever you see a question involving sequential Move/Copy features in Fusion 360's timeline, think about order of operations: each feature is applied to the result of all previous features, not to the original position. Here's the math. The reference point starts at (5,0,0)(5,0,0) mm. The first Move/Copy translates it +10+10 mm in X, placing it at (15,0,0)(15,0,0) mm. The second Move/Copy then rotates that point 180∘180^\circ about the global Z axis through the origin. A 180∘180^\circ Z-axis rotation negates both X and Y coordinates: (x,y)→(−x,−y)(x,y) \rightarrow (-x,-y). Applying that to (15,0,0)(15,0,0) gives (−15,0,0)(-15,0,0) mm — confirming D is correct. A is wrong because it applies the rotation only to the original coordinate (5,0,0)(5,0,0), ignoring that the translation already moved the point to (15,0,0)(15,0,0) before the rotation occurs. The timeline is sequential, not parallel. B confuses rotation's effect on orientation with its effect on position. A 180∘180^\circ rotation absolutely changes the position of any point not sitting exactly at the center of rotation. Since the point is at (15,0,0)(15,0,0), not at the origin, it moves dramatically. C reverses the timeline order — it imagines the rotation happens first and the translation second. In Fusion 360, features are evaluated top-to-bottom in the timeline, so the translation always precedes the later rotation. Study tip: When tackling timeline-order questions, literally trace the point through each feature in sequence. Never jump ahead or apply operations simultaneously — Fusion 360's parametric timeline is strictly sequential.
  8. Which Move/Copy method most directly produces the required result?
    Answer: Use Point to Point, selecting the body vertex first and the destination vertex second. When working with Move/Copy in Fusion 360, the key distinction to keep in mind is what geometric constraint the task requires. Here, you need a pure translation — no rotation, just a positional shift that snaps one vertex precisely onto another. That's exactly what the Point to Point method is designed for. Point to Point (answer A) lets you select a source point on the body and a destination point on another body, and Fusion calculates the exact translation vector needed to bring them together. The body moves without any rotation, which perfectly satisfies both conditions in the problem: correct orientation preserved, vertex aligned exactly. Answer B, Rotate, is wrong by definition — the problem explicitly states the body must not rotate. Selecting two vertices as rotation-axis endpoints would also create an arbitrary spin rather than a positional correction. Answer C, Free Move, relies on manually dragging the body using on-screen handles and rotation rings. Even if you could visually approximate coincidence, this method is imprecise and depends on snapping behavior rather than exact geometric selection. It also risks accidental rotation while dragging, violating the "no rotation" constraint. Answer D, Translate, sounds plausible because translation is the right motion type. However, it requires you to manually enter XYZ distance values — meaning you'd first have to calculate the coordinate difference between the two vertices. That's an indirect, error-prone workflow. Point to Point does this automatically by letting Fusion measure the delta for you. Study tip: On Fusion 360 questions, whenever a task involves snapping one geometric feature precisely to another without rotation, Point to Point is almost always the most direct tool — it eliminates manual calculation entirely.
  9. What are the body's final global coordinates?
    Answer: (−8,6,5) mm(-8,6,5)\text{ mm}, because the signed translations affect X and Y independently. When working with Move/Copy operations in Fusion 360, you need to think of translations as signed offsets added to existing coordinates — each axis updates independently, and untouched axes remain unchanged. Starting at (12,−8,5) mm(12, -8, 5)\text{ mm}, the first operation moves the body 20 mm20\text{ mm} in the negative X direction, so you subtract 20 from the X coordinate: 12+(−20)=−812 + (-20) = -8. The second operation moves 14 mm14\text{ mm} in the positive Y direction, adding 14 to Y: −8+14=6-8 + 14 = 6. The Z coordinate is never touched, so it stays at 55. That gives a final position of (−8,6,5) mm(-8, 6, 5)\text{ mm}, confirming that C is correct. A is wrong because it assumes both translations become negative offsets — the Y translation is explicitly positive, so you add 14, not subtract it. This reflects a misreading of direction signs. B makes the opposite error with X, treating "negative X direction" as though it means adding 20 instead of subtracting, which would give 3232 for X — the wrong sign entirely. D represents a fundamental misconception: translation values are offsets, not replacements. If the values replaced the coordinates, the whole concept of a starting position would be irrelevant, which is never how Fusion 360 (or vector math) works. A useful rule of thumb: in any CAD translation question, always frame your work as new coordinate=old coordinate+signed offset\text{new coordinate} = \text{old coordinate} + \text{signed offset}, axis by axis. If an axis isn't mentioned in the operation, its value doesn't change.
  10. What should the designer do after verifying the new location?
    Answer: Choose Capture Position so the current component location is stored in the design history. When working with assemblies in Fusion 360, you need to understand how the software tracks component positions relative to design history. Fusion 360 uses a parametric timeline, meaning positional changes must be explicitly committed to be preserved — simply moving a component doesn't automatically record that change. When you move an ungrounded component, Fusion 360 flags it with a pending positional change, essentially saying "something has moved, but it hasn't been saved to the timeline yet." To commit that new location into the design history, you use Capture Position — which is exactly what option B describes. This command tells Fusion 360 to record the component's current location as a timeline event, making it part of the parametric design and reproducible if you roll back and replay history. Option A is backwards — Revert Position does the opposite of what you want. It discards the pending move and returns the component to its previously recorded location, throwing away your change rather than keeping it. Option C is a misconception about grounding: grounding locks a component in place relative to the assembly origin, but it does not convert a pending move into a recorded feature or save positional data to the timeline the way Capture Position does. Option D confuses assembly context with component origin — activating a component lets you edit it internally, but it has no effect on committing an assembly-level positional change. A useful tip: whenever Fusion 360 shows a pending change indicator on a component, think of it as an "unsaved draft." Capture Position is your save button for assembly locations in the parametric timeline.

Start this quiz