AutoCAD Quiz: Overkill
10 questions · exam conditions
0:00
OverkillQuestion 1 of 10

A drawing contains three coincident lines of equal length. Two are on layer WALL, and one is on layer DEMO. All other object properties match. The drafter selects all three and runs OVERKILL with Layer not selected in the Ignore Object Property list.

What is the expected result?

All three lines remain because OVERKILL cannot process objects on multiple layers.
One line remains because coincident geometry is merged regardless of layer.
Two lines remain: one on WALL and one on DEMO.
Two lines remain, both assigned automatically to layer WALL.
← Back to quizzes

AutoCAD Quiz

AutoCAD Quiz: Overkill

Practice Overkill in AutoCAD 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 Overkill, giving you a quick way to practice the rules, question types, and explanations that matter most for AutoCAD.

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

A drawing contains three coincident lines of equal length. Two are on layer WALL, and one is on layer DEMO. All other object properties match. The drafter selects all three and runs OVERKILL with Layer not selected in the Ignore Object Property list.

What is the expected result?

  1. All three lines remain because OVERKILL cannot process objects on multiple layers.
  2. One line remains because coincident geometry is merged regardless of layer.
  3. Two lines remain: one on WALL and one on DEMO. (correct answer)
  4. Two lines remain, both assigned automatically to layer WALL.
Explanation: When working with OVERKILL in AutoCAD, the critical concept to understand is how the Ignore Object Property list controls what OVERKILL considers when deciding whether two objects are "duplicate." If a property is not in the Ignore list, OVERKILL treats it as a meaningful difference — meaning objects that differ in that property will not be merged. In this scenario, Layer is left unchecked in the Ignore list, so OVERKILL actively distinguishes objects by their layer. The two lines on layer WALL are identical to each other in every property, so OVERKILL merges them into one, leaving a single line on WALL. The line on layer DEMO differs from the WALL lines only by layer — and since layer is being respected, it is treated as a unique object and preserved. The result is exactly two lines remaining: one on WALL, one on DEMO, making C the correct answer. A is wrong because OVERKILL absolutely can process objects across multiple layers — it compares properties across all selected objects regardless of which layers they live on. B reflects the opposite misconfiguration: if Layer were added to the Ignore list, OVERKILL would treat layer as irrelevant and could reduce all three lines to one. That's not the case here. D introduces a fabricated behavior — OVERKILL never reassigns layer properties automatically; it preserves the surviving object as-is. A reliable study tip: always ask yourself, "Is the property in the Ignore list?" If it's ignored, differences in that property don't matter. If it's not ignored, those differences protect objects from deletion.

Question 2

Two lines have identical endpoints, layer, linetype, and lineweight. One line has an explicit red color, while the other has an explicit blue color. The cleanup requirement is to retain only one geometric line, regardless of its color assignment.

Which OVERKILL configuration best meets the requirement?

  1. Ignore Color during comparison, while leaving the other relevant properties included. (correct answer)
  2. Ignore Layer during comparison, while leaving Color included as a comparison property.
  3. Increase the geometric tolerance, while leaving all object properties included.
  4. Enable end-to-end combination, while leaving Color included as a comparison property.
Explanation: When using OVERKILL to eliminate duplicate geometry, you need to understand how its comparison engine works: AutoCAD compares selected objects property by property, and only objects that match on every included property get flagged as duplicates. If even one property differs, OVERKILL treats the objects as unique and leaves both intact. Here, the two lines are geometrically identical and share the same layer, linetype, and lineweight — the only difference is their explicit color (red vs. blue). Because color is included in the comparison by default, OVERKILL sees them as distinct objects and won't remove either. The fix is to tell OVERKILL to ignore color during comparison. Once color is excluded, the lines match on all remaining checked properties, OVERKILL recognizes them as duplicates, and retains just one — exactly what the requirement asks for. That makes A the correct choice. B is wrong because ignoring Layer while keeping Color included still leaves the color mismatch in play, so the two lines will still be treated as unique and neither gets removed. C is a misconception about what geometric tolerance does — it only adjusts how close endpoints must be to be considered coincident; it has no effect on property-based differences like color, so both lines survive. D confuses end-to-end combination, which merges collinear overlapping segments into one longer line, with duplicate removal; since these lines are already identical in length and position, combination isn't the relevant tool, and keeping Color included still blocks detection anyway. A helpful rule of thumb: whenever two objects are geometrically the same but differ in a display property, your OVERKILL strategy should be to ignore that differing property in the comparison settings.

Question 3

Three collinear lines with matching properties form a continuous run. Their extents are 00 to 44, 44 to 99, and 99 to 1414 drawing units. They touch only at endpoints and do not overlap.

Which setting is necessary for OVERKILL to replace the three lines with one continuous line?

  1. Enable combination of collinear objects that partially overlap.
  2. Increase tolerance until the three lines are considered coincident.
  3. Ignore Linetype so the lines can be converted into one polyline.
  4. Enable combination of collinear objects aligned end to end. (correct answer)
Explanation: When working with OVERKILL in AutoCAD, it helps to understand that the command has two distinct modes for handling collinear lines: one for lines that overlap and one for lines that simply touch end to end. Recognizing which geometric relationship your objects have is the key to choosing the right setting. In this scenario, the three lines share endpoints but have no overlapping segments — they meet cleanly at 44 and 99 drawing units. To merge them into a single line, you need OVERKILL's option to combine collinear objects that are aligned end to end, which is exactly what answer D describes. When this setting is enabled, OVERKILL recognizes the continuous chain and replaces it with one line spanning 00 to 1414. Answer A is a trap because it targets a different geometric condition — partial overlap, where segments share a region rather than just a point. Your lines don't overlap at all, so enabling this option would have no effect on them. Answer B is wrong because tolerance adjustments address near-coincident geometry (objects that are almost touching due to floating-point imprecision), not objects that are already perfectly connected end to end — raising the tolerance here solves the wrong problem. Answer C is a misconception: the Linetype setting in OVERKILL controls whether differences in linetype prevent combination, but it doesn't convert lines into polylines, and the question asks about replacing three lines with one line, not a polyline. As a study tip, remember that OVERKILL handles two collinear scenarios separately — overlapping and end-to-end — so always ask yourself how the lines are related geometrically before choosing a setting.

Question 4

A selected polyline contains redundant vertices and repeated or overlapping linear segments within the same polyline object. Other standalone objects in the selection do not duplicate it.

Which OVERKILL option most directly controls whether the internal polyline redundancy is examined?

  1. Ignore Layer in the object comparison settings to widen the match criteria.
  2. Optimize segments within selected polylines to inspect internal redundancy. (correct answer)
  3. Combine collinear objects aligned end to end to consolidate adjacent segments.
  4. Maintain associative objects to protect relationships during the cleanup operation.
Explanation: When working with the OVERKILL command, it's important to understand that it operates at two levels: comparing separate objects against each other, and examining redundancy within a single object. Questions like this test whether you can distinguish between those two scopes. The scenario describes a single polyline with internal problems — redundant vertices and overlapping segments contained within itself. This isn't about two polylines duplicating each other; it's about cleaning up the internals of one existing polyline. That distinction points directly to B, the "Optimize segments within selected polylines" option. This setting specifically instructs OVERKILL to look inside a polyline object and remove duplicate or superfluous vertices and collinear segments it finds there — exactly the problem described. A is a comparison setting that affects how OVERKILL decides whether two separate objects match each other by ignoring layer differences. It widens the criteria for object-to-object duplication but does nothing to address internal polyline structure. C refers to combining collinear objects that are end to end — meaning two separate line or polyline objects that could be merged into one. The passage explicitly states other standalone objects don't duplicate the polyline, so there's nothing to consolidate across object boundaries here. D deals with preserving associative objects (like those tied to dimensions or blocks) from being deleted during cleanup. It's a protective filter, not a redundancy-detection tool. A useful study tip: whenever OVERKILL appears on the exam, ask yourself whether the problem is between objects or within an object — that distinction separates options B and C every time.

Question 5

During cleanup, a drafter selects ordinary linework together with geometry participating in associative relationships. Duplicate ordinary lines should be removed, but associative objects must not be deleted or modified by OVERKILL.

Which workflow best satisfies both requirements?

  1. Enable Maintain associative objects, then run OVERKILL on the full selection. (correct answer)
  2. Ignore all object properties, then run OVERKILL with zero tolerance.
  3. Enable polyline optimization, then increase the comparison tolerance.
  4. Disable overlap combination, then ignore Layer and Color properties.
Explanation: When using OVERKILL to clean up a drawing, you need to understand two distinct goals it can serve: removing redundant geometry (duplicate lines, overlapping segments) and preserving special object relationships. Associative objects — such as dimensions, hatches, or arrays linked to geometry — can break or behave unexpectedly if OVERKILL modifies or deletes them. That tension between cleanup and preservation is exactly what this question tests. Option A is correct because the Maintain associative objects checkbox in the OVERKILL dialog is specifically designed for this scenario. When enabled, OVERKILL identifies any geometry participating in associative relationships and excludes it from deletion or modification, while still processing ordinary linework normally. You get the cleanup you need without damaging dependent relationships — both requirements satisfied simultaneously. Option B fails because ignoring all object properties makes OVERKILL more aggressive, not more careful. It would treat associative and non-associative objects identically, increasing the risk of deleting geometry that drives associative links. Zero tolerance doesn't add protection either. Option C conflates two unrelated settings. Polyline optimization controls how OVERKILL handles collinear polyline segments, and raising comparison tolerance widens what counts as "duplicate" — neither setting has anything to do with protecting associative relationships. Option D targets overlap combination and property matching (Layer, Color), which affect how segments are compared and merged. Disabling these changes the comparison logic but provides no mechanism to detect or protect associative objects. Your study tip: whenever an AutoCAD question involves preserving a specific object type during a batch operation, look for the dedicated toggle in that command's dialog — AutoCAD almost always provides one rather than requiring a workaround.

Question 6

Every insertion of a reusable block displays the same unwanted duplicate line. Inspection shows that the two coincident lines are separate entities stored inside the block definition; the block references themselves are not duplicated.

What is the most efficient way to use OVERKILL to correct all insertions?

  1. Select all block references and run OVERKILL in model space without editing the block.
  2. Explode every block reference, run OVERKILL, and recreate each block separately.
  3. Open the block definition for editing, run OVERKILL on its linework, and save it. (correct answer)
  4. Ignore Layer in OVERKILL so nested entities are processed through each reference.
Explanation: When you see a question about fixing duplicate geometry inside a block, the key concept is understanding the difference between a block definition and a block reference. A block definition is the master template stored once in the drawing database; every insertion (reference) simply points to that template. If the problem lives inside the definition, fixing it there automatically fixes every reference simultaneously — that's the power of blocks. This is exactly why C is correct. By using BEDIT (or double-clicking the block) to open the block definition, running OVERKILL on the internal linework to eliminate the coincident duplicate line, and then saving and closing the editor, every single insertion in the drawing is corrected in one operation. You're fixing the source, not the symptoms. A is tempting but fundamentally wrong — OVERKILL operates on individual entities in model space, and block references are treated as single atomic objects, not their internal geometry. Running OVERKILL on the references themselves won't touch the lines inside the definition. B is technically capable of removing duplicates but is catastrophically inefficient. Exploding every reference destroys the block structure, and rebuilding each block separately multiplies the workload. This approach defeats the entire purpose of using blocks for reusable geometry. D describes a misunderstanding of OVERKILL's "Ignore Layer" option. That setting affects how OVERKILL compares overlapping entities by layer, not whether it can process geometry nested inside block references — it cannot. A good rule of thumb: if geometry is wrong in every insertion, the bug is in the definition — always edit the source.

Question 7

Two coincident lines have identical properties. Before starting OVERKILL, the drafter selects only one of the two lines; the other line is not included in the command's selection set.

What is the expected result of that OVERKILL operation?

  1. The selected line is deleted because an unselected duplicate exists at the same location.
  2. The unselected line is deleted because selected objects always take precedence.
  3. Both lines are replaced by a new line using the current object properties.
  4. Neither line is removed because the command compares only objects in its selection set. (correct answer)
Explanation: When working with the OVERKILL command, the most important concept to keep in mind is that OVERKILL only analyzes and acts upon objects within its own selection set — it has no awareness of anything outside that set. OVERKILL works by comparing selected objects against each other, identifying duplicates, overlaps, or redundant segments within that group. If only one of two coincident lines is selected, OVERKILL has nothing to compare it against — from the command's perspective, that single line has no duplicate. As a result, neither line is modified or deleted, making D the correct answer. Choice A describes a behavior that doesn't exist in AutoCAD — OVERKILL never deletes a selected object simply because an unselected duplicate happens to occupy the same space. The command is entirely blind to unselected geometry. Choice B introduces a fictional "precedence" rule; OVERKILL doesn't rank objects by selection status or give priority to selected items over unselected ones. Choice C would only be a concern if both lines were selected and had differing properties — even then, OVERKILL merges or removes redundant objects rather than replacing them with a brand-new object using current layer or style settings. A good study tip for OVERKILL questions: always ask yourself, "What is actually inside the selection set?" The command is self-contained — it compares only what you give it. If you want OVERKILL to catch all duplicates in a drawing, you should select all relevant objects (or use Select All) before running the command. This is a common trap on AutoCAD exams that tests whether you understand the command's scope, not just its purpose.

Question 8

A horizontal line and a vertical line cross at their midpoints. They have matching layer, color, linetype, and elevation. The drafter selects both and runs OVERKILL with the standard overlap options enabled.

What should the drafter expect?

  1. One line is deleted because both objects contain the same intersection point.
  2. The lines are trimmed automatically so neither includes the intersection point.
  3. Both lines remain because crossing at one point is not duplicate or collinear overlap. (correct answer)
  4. The lines are joined into one polyline because their properties match.
Explanation: When working with OVERKILL, the key concept to internalize is what the command actually targets: duplicate or collinear overlapping geometry. OVERKILL removes redundant objects — lines that occupy the same path or segments that stack directly on top of one another. It is not a general-purpose cleanup tool for any lines that happen to share a point. In this scenario, a horizontal and vertical line cross at their midpoints — a clean perpendicular intersection. Even though the properties match perfectly (layer, color, linetype, elevation), these two lines travel in completely different directions. They share exactly one point, but neither line lies on top of the other, overlaps along any shared path, or duplicates the other's geometry. OVERKILL has nothing to act on, so both lines survive unchanged — making C correct. Choice A describes a behavior OVERKILL simply doesn't perform. Sharing an intersection point is not a condition for deletion; collinear overlap is. Choice B similarly misrepresents the command — OVERKILL doesn't trim geometry or remove intersection points; that's what TRIM does with defined cutting edges. Choice D confuses OVERKILL with JOIN or PEDIT. Matching properties are a prerequisite for OVERKILL to act on overlapping geometry, but matching properties alone never trigger a join or merge. A useful rule of thumb: OVERKILL only acts when lines are collinear and their segments overlap in space. Matching properties are necessary but not sufficient — the geometry itself must physically coincide. When you see a question where lines simply cross, OVERKILL is essentially a no-op.

Question 9

Two collinear lines with matching properties lie along the same axis. The first extends from 00 to 88 drawing units, and the second extends from 55 to 1212 drawing units. The option to combine collinear objects that partially overlap is enabled.

What geometry should remain after OVERKILL?

  1. One continuous line extending from 00 to 1212 drawing units. (correct answer)
  2. Two shortened lines extending from 00 to 55 and from 88 to 1212.
  3. One line containing only the shared interval from 55 to 88 drawing units.
  4. Two unchanged lines because neither object is a complete geometric duplicate.
Explanation: When you see a question about OVERKILL, focus on what each of its settings actually does to geometry rather than just whether objects are duplicates. OVERKILL's "combine collinear objects that partially overlap" option is specifically designed to merge overlapping segments into a single unified line — not simply delete exact duplicates. Here, you have a line from 00 to 88 and another from 55 to 1212 sharing the overlapping segment 55 to 88. With the combine-overlap option enabled, AutoCAD recognizes that these two lines are collinear, share matching properties, and partially overlap. It merges them into one continuous line spanning the full combined range — from 00 to 1212. That's why A is correct. B is wrong because it describes a trim or subtract operation, removing the shared region and leaving only the non-overlapping tails. OVERKILL does the opposite — it unifies, not subtracts. C describes keeping only the intersection, which would be an intersect Boolean operation, not a cleanup command. D is the most tempting trap: it assumes OVERKILL only removes perfect duplicates. While that's true for the basic duplicate-deletion function, the "combine partially overlapping collinear objects" option explicitly extends its behavior beyond exact matches — so two partially overlapping lines can be reduced to one. A useful rule of thumb: OVERKILL is a consolidation tool. When overlap-combining is enabled, think of it as asking, "Can these objects be expressed as one simpler object?" If yes, AutoCAD merges them. Watch for answer choices that confuse OVERKILL with trim, intersect, or subtract operations — that's a common trap on this exam.

Question 10

Two equal-length lines with matching object properties are nearly coincident. Their corresponding endpoints differ by 0.00040.0004 drawing unit. OVERKILL is run with a comparison tolerance of 0.0010.001 drawing unit.

Assuming no other geometry is selected, what is the most likely outcome?

  1. Both lines remain because OVERKILL recognizes only exactly coincident endpoint coordinates.
  2. One line is removed because the geometric difference falls within the specified tolerance. (correct answer)
  3. Both lines move to their average position and are replaced by a centered line.
  4. Both lines join end to end because the tolerance closes the endpoint difference.
Explanation: When you see a question involving OVERKILL, focus on what the tolerance setting actually controls: it defines how close two objects must be geometrically before OVERKILL treats them as duplicates and removes one. The tolerance is not a snap distance or averaging threshold — it is simply a comparison threshold. Here, the endpoints differ by 0.00040.0004 drawing units, and the comparison tolerance is set to 0.0010.001 drawing units. Since 0.0004<0.0010.0004 < 0.001, the geometric difference falls within the tolerance, meaning OVERKILL considers the two lines effectively identical and eliminates one. Answer B describes this outcome exactly — one line is removed because the difference is smaller than the specified tolerance. Answer A is wrong because it describes the behavior of OVERKILL when tolerance is set to 0.00000.0000 (or functionally zero). At that setting, only perfectly coincident geometry is flagged. That is not the case here — the tolerance has been deliberately set higher to catch near-duplicates like these. Answer C is wrong because OVERKILL does not average positions or reposition geometry. It deletes redundant objects entirely; it is a cleanup tool, not a geometry-merging tool. Answer D is wrong because OVERKILL does not join lines end to end. That behavior belongs to commands like JOIN. OVERKILL's job is to remove duplicates, not to connect separate segments. A useful rule of thumb: think of OVERKILL's tolerance as a "close enough" window. If the geometric difference between two overlapping objects fits inside that window, one gets deleted. Nothing is moved, averaged, or connected.