Blender Quiz: Use Edit Mode Selection Tools And Transform Operations
10 questions · exam conditions
0:00
Use Edit Mode Selection Tools And Transform OperationsQuestion 1 of 10

Two disconnected square faces are selected in Edit Mode. The transform pivot is set to Individual Origins. The user scales along the X axis by a factor of 0.50.5.

Which outcome should occur?

Each face narrows around its own center, while the two face centers remain in place.
Both faces narrow around their shared median point, moving their centers closer together.
Each face narrows around the object origin, moving both centers toward that origin.
Both faces rotate toward the X axis because individual origins use separate orientations.
← Back to quizzes

Blender Quiz

Blender Quiz: Use Edit Mode Selection Tools And Transform Operations

Practice Use Edit Mode Selection Tools And Transform Operations in Blender 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 Use Edit Mode Selection Tools And Transform Operations, giving you a quick way to practice the rules, question types, and explanations that matter most for Blender.

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

Two disconnected square faces are selected in Edit Mode. The transform pivot is set to Individual Origins. The user scales along the X axis by a factor of 0.50.5.

Which outcome should occur?

  1. Each face narrows around its own center, while the two face centers remain in place. (correct answer)
  2. Both faces narrow around their shared median point, moving their centers closer together.
  3. Each face narrows around the object origin, moving both centers toward that origin.
  4. Both faces rotate toward the X axis because individual origins use separate orientations.
Explanation: When working with transform pivots in Blender, the key question to ask is: what point does each selected element rotate or scale around? The pivot setting answers this directly — it defines the center of transformation for every operation you perform. With Individual Origins selected as the pivot, Blender assigns each disconnected piece its own local center for the transformation. So when you scale two separate square faces by 0.50.5 along X, each face shrinks toward its own geometric center independently. The centers themselves don't move — only the vertices pull inward around those fixed points. This confirms that A is correct. B describes what would happen with the Median Point pivot instead. That mode calculates a single shared center between all selected elements, so both faces would scale toward one common point, drawing their centers closer together — not the behavior here. C describes scaling relative to the Object Origin, a completely different pivot option. Using the object origin as the reference point would pull all vertices toward that single fixed location in object space, causing face centers to shift toward it. D is a fabricated distractor mixing up scaling with rotation and incorrectly attributing orientation behavior to Individual Origins. Scaling along X simply narrows geometry along that axis — it has nothing to do with rotating toward an axis. A useful study habit: memorize Blender's five pivot options (Individual Origins, Median Point, Active Element, 3D Cursor, Object Origin) and practice predicting how the same transform produces different spatial results depending on which pivot is active. Exam questions frequently swap pivot types to test exactly this distinction.

Question 2

A cube is in Mesh Edit Mode and Vertex Select mode. The viewport is in solid shading, X-Ray is disabled, and the cube is viewed directly from the front. The user drags a box that surrounds the cube's entire projected outline.

Under the default selection behavior, which vertices become selected?

  1. Only the visible front vertices enclosed by the box become selected. (correct answer)
  2. All front and rear vertices enclosed by the box become selected.
  3. Only the rear vertices occluded by the front faces become selected.
  4. No vertices become selected because solid shading blocks box selection.
Explanation: When working with box selection in Blender's Edit Mode, the critical variable to understand is X-Ray mode. X-Ray controls whether selection tools "see through" geometry or only interact with what's visible on the surface facing you. With X-Ray disabled (as stated in this scenario), box selection behaves like a spotlight — it only selects geometry that is actually visible from your current viewpoint. Since you're in solid shading viewing the cube from the front, the front four vertices are visible, but the rear four vertices are hidden behind the cube's front faces. Box selection respects this occlusion and selects only what you can see. Answer A is correct: only the visible front vertices are selected, even though the box surrounds the cube's entire outline. Answer B describes the behavior you'd get if X-Ray were enabled. With X-Ray on, box selection pierces through the mesh and captures all geometry — front and back — within the dragged region. This is a common point of confusion because many users toggle X-Ray without realizing how dramatically it changes selection behavior. Answer C inverts the logic entirely — occluded vertices are the ones excluded, not the ones selected. There's no scenario in standard Blender behavior where only hidden vertices get selected. Answer D is a fabricated rule. Solid shading affects display, not the availability of selection tools. Box selection works perfectly in solid shading — it just respects visibility when X-Ray is off. The exam tip here: whenever a question mentions shading mode and X-Ray status together, that's your signal that occlusion and selection depth are being tested. Always ask yourself, "Is X-Ray on or off?"

Question 3

A mesh object has an unapplied object rotation of 90∘90^\circ around the world Z axis. In Edit Mode, one vertex is selected and the transform orientation is set to Global. The user executes G, X and enters a distance.

Along which direction is the vertex constrained?

  1. Along the object's local X direction, which is rotated with the object.
  2. Along the world X direction, regardless of the unapplied object rotation. (correct answer)
  3. Along the world Y direction because Edit Mode automatically uses local axes.
  4. Along the vertex normal because unapplied rotation overrides Global orientation.
Explanation: When working with transform orientations in Blender, the key question to ask is: what does the selected orientation actually control? Transform orientation determines which coordinate system defines the constrained axis — and it operates independently of whether object transforms have been applied. When you set the transform orientation to Global and press G, X, you are explicitly telling Blender to use the world coordinate system. The X axis constrained is therefore the world X axis — a fixed direction in 3D space that never moves regardless of how any object is positioned, rotated, or scaled. This makes B correct: the vertex moves strictly along the global X direction. A is wrong because it confuses transform orientation with the object's local space. The Local orientation would align axes with the object's own rotation — meaning, after a 90°90° Z rotation, the object's local X points along the world Y. Choosing Global explicitly overrides this; the unapplied rotation is irrelevant to the constrained direction. C is wrong for a related reason. It incorrectly claims Edit Mode automatically switches to local axes. Edit Mode does not change which orientation you've selected — if you set Global, it stays Global. The 90°90° rotation would cause the local X to align with world Y, so this answer blends a real fact (local X ≈ world Y after that rotation) with a false premise about automatic behavior. D is wrong because vertex normals are a separate orientation mode entirely, and unapplied rotations do not override your manually selected orientation. Study tip: Always track which orientation mode is active in the header. "Global" always means world axes — no object transform can redirect it.

Question 4

In Edge Select mode, a user Alt-clicks an edge in a regular quad strip. Farther along the strip, the topology reaches a pole where the vertex does not have the regular four-edge quad-grid connectivity.

How does edge-loop selection normally respond to this topology?

  1. It continues through the pole by selecting whichever outgoing edge appears geometrically straightest to Blender.
  2. It selects every edge connected to the pole and then resumes selection on all resulting branches simultaneously.
  3. It stops at the pole because the regular opposite-edge continuation is ambiguous there. (correct answer)
  4. It converts to face-loop selection mode as soon as the irregular vertex is encountered.
Explanation: When working with edge loops in Blender, understanding how the selection algorithm propagates is essential. Edge-loop selection works by a simple rule: starting from a selected edge, Blender traverses a quad strip by always picking the opposite edge across each quad face. This "opposite edge" logic works cleanly as long as every vertex has exactly four edges meeting in a regular quad-grid pattern. A pole breaks this rule. A pole is a vertex where the number of connected edges differs from four (commonly three or five). When edge-loop selection reaches a pole, there is no single, unambiguous "opposite edge" — the algorithm cannot determine which outgoing edge correctly continues the loop. As a result, Blender simply stops the selection there. This makes C the correct answer. Option A is tempting but wrong — Blender does not evaluate geometric straightness or angles to guess which edge to continue through. The selection is purely topological, not geometric. Option B describes a kind of "branching flood fill," which is not how edge-loop selection works at all; selecting every connected edge at a pole would defeat the purpose of a loop selection. Option D is entirely fabricated — Blender does not silently switch between selection modes mid-operation based on topology. A useful study tip: whenever a Blender question involves loop selection behavior, ask yourself "is the topology regular quads all the way through?" If anything breaks the four-edge pattern — poles, triangles, or ngons — expect the loop to terminate, not improvise. This principle also applies to face-loop selection, which has the same sensitivity to irregular topology.

Question 5

In Vertex Select mode, vertex A is active. Two edge-connected routes lead from A to vertex B. One route contains three very long edges; the other contains four very short edges. The user invokes Select Shortest Path on B with the Topology Distance option enabled.

Which route is selected between A and B?

  1. The three-edge route, because Topology Distance compares the number of topological steps. (correct answer)
  2. The four-edge route, because its summed geometric edge length is smaller.
  3. Both routes, because shortest-path selection fills every enclosed region by default.
  4. Neither route, because shortest-path selection cannot cross edges of unequal lengths.
Explanation: When you see a question about Select Shortest Path in Blender, the key is recognizing that the word "shortest" changes meaning depending on which distance mode is active. This question tests whether you understand the difference between geometric distance and topological distance. With Topology Distance enabled, Blender ignores the actual 3D lengths of edges entirely. Instead, it counts the number of edge steps required to walk from the active vertex to the target vertex — like counting hops on a graph. The three-edge route requires 3 steps; the four-edge route requires 4 steps. Because 3 < 4, Blender selects the three-edge route, making A the correct answer. B is wrong because it describes behavior that would occur without Topology Distance — when Blender uses real geometric edge lengths to compute the shortest path. In that default mode, the four short edges might indeed win. But once you enable Topology Distance, physical length is completely irrelevant. C is wrong on two counts: shortest-path selection does not fill enclosed regions by default, and the behavior described doesn't relate to any actual Blender feature. This is a fabricated distractor designed to confuse you with vague spatial reasoning. D is wrong because shortest-path selection works perfectly well across edges of unequal lengths — that limitation simply doesn't exist in Blender's toolset. Study tip: Whenever you see "Topology Distance" in a Blender question, immediately think edge count, not edge length. It's a common trap to assume "shortest" always means geometric distance — in topology mode, only the number of connections matters.

Question 6

A single face in the middle of a large, uneven quad mesh is selected in Face Select mode. Some neighboring faces are physically narrow, while others are physically wide. The user invokes Select More once.

Which description best matches the resulting selection?

  1. Faces within a fixed world-space radius are added, so narrow faces are favored.
  2. All faces in the same connected mesh island are added in one operation.
  3. One topological layer of neighboring faces is added, independent of face dimensions. (correct answer)
  4. Only faces with normals matching the active face are added to the selection.
Explanation: When working with mesh selection in Blender, it helps to distinguish between topological operations and geometric ones. Topological operations care about how faces are connected, not how big or small they are in 3D space. Select More (Ctrl+NumPad Plus) is a purely topological tool — it expands the current selection by exactly one layer of adjacent faces, meaning any face that shares an edge with an already-selected face gets added. This is why C is correct. Starting from your single selected face, Select More reaches outward one "ring" of connectivity. Whether a neighboring face is a sliver 1mm wide or a giant quad spanning meters makes absolutely no difference — if it shares an edge, it joins the selection. A describes a hypothetical distance-based selection tool, like a radial falloff. Blender does have proximity-based tools, but Select More is not one of them. Narrow faces being "favored" by geometry makes no sense for a topology-driven operation. B describes what Select All or picking a linked mesh island (L key) would do — Select More deliberately stops at one topological layer, not the entire island. D confuses Select More with a completely different tool: Select Linked Flat Faces, which does filter by normal angle. Select More ignores normals entirely. A useful study tip: whenever you see "Select More / Select Less" in Blender questions, think topology, not geometry. The operation is equivalent to graph traversal — one step outward through shared edges, every time, regardless of world-space size, shape, or orientation.

Question 7

An interior edge in a quad strip is selected. The user starts Edge Slide with G, G, types 1.51.5, and confirms. Clamping remains enabled, and no merge option is enabled.

What is the most likely result?

  1. The edge passes beyond the neighboring boundary because typing a value always overrides the clamp setting.
  2. The edge stops at the clamped end of the slide range and does not automatically merge with adjacent vertices. (correct answer)
  3. The edge scales to one and one-half times its original length, pivoting around its own midpoint.
  4. The edge translates freely in global space by exactly one and one-half Blender units along its length.
Explanation: When you use Edge Slide in Blender (G, G), you're sliding an edge along its neighboring topology — not translating it in global space or scaling it. The slide range runs from −1-1 to 11, where 1.01.0 means the edge reaches the adjacent boundary edge on one side and −1.0-1.0 reaches the other. Clamping restricts the edge from going outside this range, preventing it from "popping through" neighboring geometry. When you type 1.51.5, you're requesting a value beyond the valid clamped range. With clamping enabled, Blender simply stops the edge at 1.01.0 — the boundary of the slide range — rather than allowing it to overshoot. Since the merge option is not enabled, the edge stops there but does not automatically collapse or merge with the adjacent boundary vertices. That makes B the correct result. A is wrong because typing a numeric value does not override the clamp setting. Clamping is a separate toggle (Alt during the operation) and remains active regardless of what value you type. C is a common misconception — Edge Slide has nothing to do with scaling along a midpoint; that describes the S key (Scale). D is also wrong because Edge Slide moves along the local topology, not in global Blender units; the values are normalized ratios within the slide corridor, not distances. A helpful rule to remember: in Blender, numeric input during a modal operation respects any active constraints or limits — it doesn't bypass them. Always check whether clamping or snapping is active before assuming a typed value will be applied literally.

Question 8

A quad face is selected in Face Select mode. The user switches to Vertex Select mode, where the face's four corner vertices appear selected. The user deselects one of those vertices and then switches back to Face Select mode.

What happens to the original face selection?

  1. The face remains selected because three selected corners are sufficient to reconstruct it.
  2. The face is deleted because switching modes with a partial boundary makes it invalid.
  3. The face remains selected because selection-mode changes preserve face history exactly.
  4. The face becomes unselected because not all of its defining vertices remain selected. (correct answer)
Explanation: When switching between selection modes in Blender, it helps to understand the underlying rule: face selection is derived from vertex selection, not stored independently. Blender doesn't maintain a separate "face memory" — a face is considered selected only when all of its defining vertices are selected simultaneously. This is exactly why D is correct. When you deselect one vertex of that quad in Vertex Select mode, only three of the four corner vertices remain selected. When you return to Face Select mode, Blender checks each face's vertices to determine selection state. Since the quad no longer has all four corners selected, it fails that check and appears unselected. The distractors each represent a specific misconception worth addressing. A tempts you with the intuition that "most of the face" should count — but Blender uses an all-or-nothing rule for vertex-to-face selection conversion; three out of four is not enough. B introduces the idea of deletion, which is completely fabricated — switching selection modes is a display/filter operation and never destroys geometry. Nothing is removed from your mesh by toggling modes. C suggests that face selection is stored as independent history that survives mode changes intact, but as explained above, Blender recalculates face selection from vertex states on every mode switch; there is no preserved "face history." A useful rule of thumb to remember: in Blender, faces are selected when all their vertices are selected — no exceptions. When a question describes partial vertex deselection followed by a mode switch, always ask yourself whether every vertex of that face is still selected before deciding its fate.

Question 9

Several vertices are selected in Edit Mode. The user presses Shift+D to duplicate them, moves the mouse, and then right-clicks to cancel the interactive movement.

What remains after the movement is canceled?

  1. The duplicate operation is fully undone, leaving only the original vertices selected.
  2. The duplicate remains selected at the original location, overlapping the source geometry. (correct answer)
  3. The duplicate remains at the last mouse position, but the originals become selected.
  4. The source vertices are deleted, and the duplicate replaces them at the original location.
Explanation: When working with duplication in Blender's Edit Mode, it helps to understand that Shift+D is actually a two-phase operation: first it creates the duplicate, then it immediately enters an interactive grab (G) state so you can reposition it. These two phases are independent — canceling the second does not undo the first. Right-clicking during the movement phase cancels only the transform, snapping the duplicate back to its origin point. The duplicate itself was already created the moment you pressed Shift+D, and that creation isn't reversed by the right-click. This is why B is correct — the duplicate remains, fully overlapping the source vertices at the same location, and it stays selected (shown in orange) while the originals return to an unselected state. A is the most tempting wrong answer because right-clicking often feels like a full "cancel," but it only cancels the grab transform, not the duplication itself. If you want to fully undo, you need Ctrl+Z. C gets the selection logic backwards — after canceling movement, the duplicate remains selected, not the originals. D describes something closer to Alt+D (linked duplicate) behavior in some workflows, but even then, no source deletion occurs; it's simply a fabricated scenario with no basis in Blender's actual behavior. A useful rule of thumb: in Blender, right-click cancels the active transform, not the operation that triggered it. Whenever you see a question about interactive operations like this, ask yourself what the tool actually created before the mouse movement began.

Question 10

One mesh object contains two disconnected islands positioned close together. A vertex on the first island is selected. Proportional Editing is enabled with Connected Only, and the influence radius is enlarged enough to overlap both islands on screen. The selected vertex is then moved.

What is the expected result?

  1. Both islands deform because every vertex inside the displayed radius receives proportional influence.
  2. Only the selected vertex moves because disconnected geometry disables all proportional falloff.
  3. The first island deforms with falloff, while the disconnected second island remains unchanged. (correct answer)
  4. The first island moves rigidly, while the second island deforms according to screen distance.
Explanation: When you see a question about Proportional Editing in Blender, the key concept to focus on is how the falloff influence is calculated — specifically, whether it travels along mesh topology or simply across screen space. Proportional Editing normally uses screen-space distance to determine which vertices fall within the influence radius. However, enabling Connected Only changes this behavior fundamentally: influence is now restricted to vertices that are topologically connected to the selected vertex — meaning they share an unbroken chain of edges. Once topology becomes the gating condition, the visual overlap of the radius on screen becomes irrelevant for determining what gets affected. This is exactly why C is correct. The selected vertex belongs to the first island, so falloff propagates through that island's connected edges with the usual smooth falloff. The second island, being a separate disconnected mesh, has no topological path linking it to the selected vertex, so none of its vertices receive any influence — regardless of how large the radius appears on screen. A is wrong because it describes standard Proportional Editing without Connected Only. Enlarging the radius does affect screen-space reach normally, but Connected Only overrides that logic entirely. B overcorrects in the opposite direction — Connected Only doesn't eliminate falloff altogether; it still applies a smooth falloff, just only through connected geometry. D inverts the actual behavior: the first island deforms with falloff (not rigidly), and the second island is completely unaffected (not partially deformed). As a study tip, remember that Connected Only = topology gate: if there's no edge path to a vertex, the radius simply can't reach it, no matter how big it looks.