Primitive Meshes & Topology - Blender

1. Which statement correctly identifies the resulting boundary topology?
   Answer: The four former top-rim edges each belong to one face and form an open boundary When working with mesh topology in Blender, the key concept to understand is the boundary edge: an edge that belongs to exactly one face. A closed, manifold mesh has every edge shared by exactly two faces. Deleting a face doesn't remove its surrounding edges — it simply leaves those edges with one fewer face attached. Starting with a default cube, the top face is bounded by four edges forming its rim. Before deletion, each of those rim edges belongs to two faces: the top face and one adjacent side face. Once you delete only the top face, those four rim edges each retain their connection to a single side face — dropping from two-face membership to one. That's the definition of a boundary edge, and together those four edges form an open loop — a hole in the mesh. This confirms answer A as correct. Answer B is wrong because the vertical edges (the cube's corner pillars) are unaffected by the deletion — each still connects to two faces (two side faces), so they remain interior edges and contribute no boundary. Answer C is incorrect because the deletion does leave edges with only one face, breaking the closed-manifold condition. The mesh is no longer watertight. Answer D confuses boundary edges with loose geometry. Loose edges have zero face connections. The former top-rim edges still belong to one face each — they're boundaries, not floating geometry. As a study tip, always ask yourself: how many faces does each edge touch after an operation? Zero = loose, one = boundary, two = interior. This mental checklist will clarify most Blender topology questions.
2. After returning to Object Mode, which result correctly describes the mesh?
   Answer: One object containing two disconnected components with $16$ vertices, $24$ edges, and $12$ faces When you add geometry while already inside Edit Mode, Blender adds it directly into the current object's mesh data — not as a separate object. This is the core concept being tested here. A default cube has $8$ vertices, $12$ edges, and $6$ faces. When you add a second default cube in Edit Mode, its geometry is appended to the same mesh. Since the two cubes don't touch or share any vertices, the result is one object with two disconnected mesh islands — also called components. Adding the counts together: $8 + 8 = 16$ vertices, $12 + 12 = 24$ edges, and $6 + 6 = 12$ faces. That's exactly what A describes, making it correct. B is wrong because it describes two separate objects, which is what would happen if you added the second cube in Object Mode instead of Edit Mode — a common point of confusion. C is wrong because the cubes are genuinely disconnected; there are no hidden edges bridging them. Blender doesn't fabricate connections between islands. D is wrong because its vertex and edge counts ($12$ vertices, $20$ edges) don't correspond to any standard combination of two default cubes — those numbers might seem plausible at a glance, but they don't follow from the actual geometry. A useful rule to remember: the mode you're in when you add geometry determines ownership. Edit Mode → same object. Object Mode → new object. This distinction appears frequently in Blender workflow questions, so internalize it as a reflex.
3. What are the mesh's new topology counts?
   Answer: $26$ vertices, $43$ edges, and $18$ faces When triangulating faces in Blender, you need to track what each diagonal actually adds to the mesh. A diagonal is a new edge that splits one quadrilateral into two triangles — it connects two existing vertices, so it creates no new vertices and no new faces beyond the split itself. Here's the math for triangulating three quads: each diagonal adds $1$ edge and converts $1$ face into $2$ faces (a net gain of $1$ face). Applying this three times gives you $+3$ edges and $+3$ faces. Starting from $26$ vertices, $40$ edges, and $15$ faces: $26 \text{ vertices},\quad 40 + 3 = 43 \text{ edges},\quad 15 + 3 = 18 \text{ faces}$ That matches answer C. Looking at the wrong choices: A gives $46$ edges instead of $43$ — this comes from mistakenly adding $2$ edges per triangulation instead of $1$, perhaps confusing a diagonal with two new edges. B gives $29$ vertices — a classic trap where you incorrectly assume that adding a diagonal requires inserting new midpoint vertices, which it doesn't; a diagonal connects existing corner vertices of the quad. D keeps the face count at $15$, ignoring that each diagonal genuinely splits one face into two, so the face count must increase. A good rule of thumb: triangulating by diagonal = 0 new vertices, +1 edge, +1 face per quad. Memorize this triplet (0, +1, +1) and you can solve any variant of this question instantly without second-guessing yourself.
4. Compared with the N-gon cylinder, how does the Triangle Fan cylinder's topology change?
   Answer: It has $2$ more vertices, $24$ more edges, and $22$ more faces When comparing cap fill types in Blender, you need to count the mesh elements each method generates — vertices, edges, and faces — then find the difference between the two configurations. Start by counting both cylinders. With $12$ side vertices, an N-gon cylinder uses those same $12$ perimeter vertices per cap, connected by a single polygon (the N-gon itself). No center vertex is needed. Each cap contributes $1$ face and $0$ interior edges — the perimeter edges are shared with the sides. So across both caps: $+0$ extra vertices, $+0$ extra interior edges, $+2$ faces total for the caps. A Triangle Fan cap instead places $1$ center vertex per cap, then connects it to each of the $12$ perimeter vertices with $12$ new edges, creating $12$ triangular faces per cap. Across both caps, that's $+2$ center vertices, $+24$ new edges ($12 \times 2$), and $+24$ triangular faces instead of $2$ N-gon faces — a net gain of $+22$ faces ($24 - 2$). So the Triangle Fan cylinder has $2$ more vertices, $24$ more edges, and $22$ more faces than the N-gon cylinder — confirming answer A. B is tempting but miscounts the faces, suggesting $24$ more rather than accounting for the $2$ N-gon faces being replaced. C incorrectly claims no extra vertices, forgetting the two center points. D wildly overstates the vertex count — only $2$ center vertices are added, not $24$. When solving topology comparison questions, always build a complete element table for each configuration before subtracting — it prevents the partial-count mistakes that make B, C, and D plausible traps.
5. Which set of topology counts is correct?
   Answer: $20$ vertices, $31$ edges, and $12$ faces When working with grid topology in Blender, you need to apply Euler's formula relationships for planar meshes. For a grid with $X$ vertices along one axis and $Y$ along the other, three formulas govern the topology: vertices $= X \times Y$, faces $= (X-1)(Y-1)$, and edges $= X(Y-1) + Y(X-1)$. With $5$ vertices in one direction and $4$ in the other, plug in directly. Vertices: $5 \times 4 = 20$. Faces: $(5-1)(4-1) = 4 \times 3 = 12$. Edges along the horizontal runs: $5 \times (4-1) = 5 \times 3 = 15$. Edges along the vertical runs: $4 \times (5-1) = 4 \times 4 = 16$. Total edges: $15 + 16 = 31$. That gives you $20$ vertices, $31$ edges, and $12$ faces — confirming answer A is correct. Answer B claims $40$ edges and $20$ faces, which would require a full $5 \times 4$ grid of faces — but that would need $6 \times 5$ vertices, not $5 \times 4$. Answer C gets the vertex and face counts right but undercounts edges at $28$, likely from forgetting one full row or column of edge segments. Answer D drops the vertex count to $16$, confusing a $4 \times 4$ grid with a $5 \times 4$ one, which is a classic off-by-one error. A useful memory trick: the face count always uses $(\text{vertices} - 1)$ per direction, because faces live in the gaps between vertices, not on the vertices themselves. Keep this "subtract one per axis" rule in mind whenever grid topology appears on the exam.
6. What is the expected topological result?
   Answer: The shared edge is removed and the two faces become one larger polygon When working with Blender's mesh editing tools, it helps to think about what "dissolving" actually means topologically: unlike deletion, dissolving merges surrounding geometry rather than creating holes. This distinction is central to the question. When you select the shared interior edge between two quad faces and run Dissolve Edges, Blender removes that edge while keeping all surrounding geometry intact. Because both faces were bounded by that edge, eliminating it allows them to merge seamlessly into a single, larger polygon — in this case, an eight-sided ngon (assuming no shared vertices beyond the edge endpoints). That's exactly what C describes, making it the correct answer. A is wrong because it describes the behavior of Delete Edges, not Dissolve. Deleting an edge removes it and can leave the mesh with open boundary loops or orphaned faces, depending on context. Dissolve is specifically designed to avoid creating holes. B confuses edge dissolving with vertex dissolving — removing the endpoint vertices while keeping the edge is not a valid operation here and doesn't reflect how Dissolve Edges works. The edge is what gets dissolved, not its vertices. D describes a duplication or separation operation, which has nothing to do with dissolving; this would be closer to what Rip or manual edge creation might do, and it contradicts the fundamental purpose of dissolving geometry. A useful rule of thumb: Delete punches holes, Dissolve cleans topology. Whenever you want to reduce edge/vertex count without opening up your mesh, reach for Dissolve. This distinction appears frequently in Blender topology questions, so keep it sharp.
7. What topology results immediately after the extrusion?
   Answer: $8$ vertices, $12$ edges, and $6$ faces, forming a closed box-like mesh When working with extrusion in Blender, you need to track exactly what geometry gets created versus what gets preserved. Extrude Region duplicates the selected geometry, connects it with new edges, and leaves the original geometry intact — nothing is deleted or merged automatically. Starting with your single square face: it has $4$ vertices, $4$ boundary edges, and $1$ face. When you extrude it as a region and move it perpendicular to its plane, Blender duplicates all four vertices (giving you $4 + 4 = 8$ vertices total) and creates four new side faces connecting the original ring of vertices to the new ring. The original bottom face remains, and the new top face is created at the extruded position. That yields $1$ bottom $+ 4$ sides $+ 1$ top $= 6$ faces. The edges include the original $4$ bottom edges, $4$ new top edges, and $4$ new vertical connecting edges, totaling $12$ edges. This makes B correct: $8$ vertices, $12$ edges, and $6$ faces — a closed, box-like shell. Choice A is wrong because it assumes the original bottom face is removed, which doesn't happen automatically. Choice D makes the same mistake — claiming the original face disappears — and also miscounts the faces as $5$. Choice C is fundamentally wrong in claiming extrusion reuses the original vertices; extrusion always duplicates them, which is precisely why new geometry gets created rather than just repositioned. A reliable tip: memorize that Extrude Region = duplicate + connect + keep original. Whenever you see topology-counting questions, trace each element (vertices, edges, faces) step by step rather than estimating.
8. Which statement correctly describes both the new counts and the Euler characteristic $V-E+F$?
   Answer: The mesh has $8$ vertices, $18$ edges, $12$ faces, and Euler characteristic $2$ When you triangulate a mesh, you need to carefully track how each element count changes — vertices, edges, and faces all shift in specific ways, and the Euler characteristic $V - E + F$ gives you a powerful check on your work. Start with the default cube: $8$ vertices, $12$ edges, $6$ faces. Triangulating means splitting each quadrilateral face with one diagonal. Since no vertices are added or merged, $V$ stays at $8$. Each diagonal is a brand-new edge added inside a face, so you gain $6$ new edges: $12 + 6 = 18$ edges total. Each diagonal also splits one quad into two triangles, doubling the face count: $6 \times 2 = 12$ faces. Now apply the Euler characteristic: $V - E + F = 8 - 18 + 12 = 2$. For any convex polyhedron (topologically equivalent to a sphere), this should always equal $2$ — a great built-in sanity check. So D is correct. A gets the edge count ($18$) and vertex count ($8$) right but leaves the face count at $6$, as if no triangulation actually happened. It then calculates $8 - 18 + 6 = -4$, which is wrong on both counts. B invents $24$ edges — perhaps by mistakenly adding $12$ diagonals instead of $6$, or double-counting — and arrives at the same incorrect Euler value of $-4$. C introduces $14$ vertices, which contradicts the problem's explicit statement that no vertices are added. All remaining numbers cascade incorrectly from that false premise. A quick study tip: whenever a topology question gives you a Euler characteristic, use $V - E + F = 2$ as your verification tool — if your counts don't produce $2$ for a closed mesh, something went wrong.
9. Which topology counts should the torus have?
   Answer: $96$ vertices, $192$ edges, and $96$ faces When analyzing torus topology, you need to understand how a torus wraps a grid of vertices around two axes simultaneously. Think of it as a rectangular grid that closes on itself in both directions — the "major" ring (the big circle) and the "minor" ring (the tube cross-section). For a torus with $M$ major segments and $m$ minor segments, the formulas are: $\text{Vertices} = M \times m$ $\text{Faces} = M \times m$ $\text{Edges} = 2 \times M \times m$ This works because every vertex is shared by exactly four faces in a fully wrapped quad mesh — no boundary edges, no caps, no seam duplication. With $12$ major and $8$ minor segments: vertices $= 12 \times 8 = 96$, faces $= 12 \times 8 = 96$, and edges $= 2 \times 12 \times 8 = 192$. That confirms D as correct. A gets the edges and faces swapped relative to vertices — it inflates vertices to $104$ and faces to $192$, which would require extra geometry that isn't present in a standard torus. B uses values like $180$ and $84$ that don't correspond to any clean formula using these segment counts — these numbers suggest a possible off-by-one miscalculation, perhaps treating segment rings as open rather than closed. C catastrophically reverses the edge and face counts while also dropping vertices to $20$, which has no geometric basis here. A quick study tip: for any closed, seam-free quad primitive in Blender, remember that faces always equal vertices, and edges always equal twice the faces. This Euler-consistent pattern is your fastest check on torus topology questions.
10. Which description is correct before any vertices are merged?
    Answer: The mesh has $8$ vertices, $8$ edges, and $2$ faces, with two coincident but separate boundary edges When working with mesh topology in Blender's Edit Mode, it's crucial to understand that spatial overlap does not equal topological connection. Blender never automatically merges, welds, or combines geometry — every vertex, edge, and face remains independent until you explicitly merge it. Here's the math: each plane starts with $4$ vertices, $4$ edges, and $1$ face. Two planes together give you $4 + 4 = 8$ vertices, $4 + 4 = 8$ edges, and $1 + 1 = 2$ faces. Even though one edge from each plane sits at the exact same position in 3D space, they are still two distinct edges belonging to two distinct loops. The coincident edges are simply overlapping boundary edges — unconnected neighbors, not shared topology. This makes B correct: $8$ vertices, $8$ edges, $2$ faces. A is wrong because it assumes Blender auto-connects coincident elements, reducing vertices to $6$ and edges to $7$. That only happens after you run Merge by Distance (or manual merging). C makes a similar error — claiming the overlapping edges collapse into one shared edge, dropping the count to $7$ edges. Again, no merge means no collapse. D compounds two misconceptions at once: that coplanar faces auto-combine into one face and that vertices auto-merge, which Blender never does passively. A reliable rule of thumb: in Blender, proximity is never connectivity. Always ask yourself whether a merge operation was explicitly performed. If the passage says "no merge," trust the raw element counts from both objects independently.

Start this quiz