AutoCAD Quiz: Revision Clouds
10 questions · exam conditions
0:00
Revision CloudsQuestion 1 of 10

A temporary closed polyline already follows the exact boundary of an irregular drawing revision. Its combination of straight and curved segments should become the cloud boundary without being manually retraced.

Which REVCLOUD workflow most directly produces the required markup?

Choose Object, select the closed polyline, and confirm the cloud direction.
Choose Polygonal, snap to several locations, and manually approximate the boundary.
Choose Freehand, trace over the polyline, and close the cloud near its start.
Choose Rectangular, create a bounding box, and stretch its corners to the polyline.
← Back to quizzes

AutoCAD Quiz

AutoCAD Quiz: Revision Clouds

Practice Revision Clouds 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 Revision Clouds, 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 temporary closed polyline already follows the exact boundary of an irregular drawing revision. Its combination of straight and curved segments should become the cloud boundary without being manually retraced.

Which REVCLOUD workflow most directly produces the required markup?

  1. Choose Object, select the closed polyline, and confirm the cloud direction. (correct answer)
  2. Choose Polygonal, snap to several locations, and manually approximate the boundary.
  3. Choose Freehand, trace over the polyline, and close the cloud near its start.
  4. Choose Rectangular, create a bounding box, and stretch its corners to the polyline.
Explanation: When REVCLOUD questions describe an existing object that already defines the boundary you need, your first instinct should be to ask: "Can I convert this object rather than redraw it?" AutoCAD's REVCLOUD command includes an Object option specifically for this purpose — it converts a closed shape (polyline, circle, ellipse, spline, or rectangle) directly into a revision cloud, preserving every segment of the original geometry without any manual retracing. That's exactly why A is correct. The closed polyline already matches the irregular boundary, including its mix of straight and curved segments. Choosing Object, selecting that polyline, and confirming the arc direction instantly produces a cloud that follows the precise boundary — no approximation, no extra effort. B is wrong because Polygonal requires you to click each vertex manually. Even if you snap carefully, you're recreating the boundary point by point, which is redundant when the polyline already exists and risks introducing geometric drift on curved segments. C is wrong because Freehand is a cursor-traced mode — you physically drag to draw the cloud. Tracing over an existing polyline freehand is imprecise and defeats the purpose of having an accurate reference object already in place. D is wrong because Rectangular produces only a four-sided, axis-aligned cloud. It cannot conform to an irregular boundary regardless of how you stretch it afterward, and it would require significant rework to approximate a complex shape. A useful rule of thumb: whenever the question mentions a closed existing object that matches the needed boundary, the answer almost always involves the Object conversion option — it's REVCLOUD's most efficient and accurate workflow.

Question 2

A CAD standard requires all newly created revision-cloud arcs to have uniform chord lengths. The specified arc length is correct, but newly generated clouds still contain deliberate arc-to-arc variation.

Which change addresses the variation without changing the required nominal arc size?

  1. Set REVCLOUDARCVARIANCE to its uniform chord-length setting. (correct answer)
  2. Set REVCLOUDCREATEMODE to its rectangular cloud creation setting.
  3. Set PLINETYPE to its lightweight polyline storage setting.
  4. Set PEDITACCEPT to suppress the polyline conversion prompt.
Explanation: When you see a question about revision clouds behaving inconsistently despite correct arc-size settings, focus on the system variables that control how revision cloud geometry is generated — specifically whether arcs are drawn uniformly or with intentional randomness. AutoCAD includes a built-in variance feature for revision clouds that deliberately introduces arc-to-arc variation to give clouds a more hand-drawn, organic appearance. The system variable REVCLOUDARCVARIANCE controls this behavior. When set to 0 (Off), all arcs in a newly created revision cloud use a consistent, uniform chord length matching your specified value. When set to 1 (On), AutoCAD applies random variation around that nominal size. If your CAD standard demands uniform chord lengths, toggling this variable to its uniform setting — answer A — is exactly the right fix, and it does so without touching the arc size itself. Answer B is a distractor about cloud shape (rectangular vs. freehand/polygonal), which has nothing to do with arc-length consistency. Answer C references PLINETYPE, which determines how polylines are stored internally (heavyweight vs. lightweight) — completely unrelated to revision cloud arc behavior. Answer D involves PEDITACCEPT, which suppresses the prompt asking whether to convert an object to a polyline during PEDIT; it has no influence on how revision cloud arcs are sized or varied. As a study tip: AutoCAD questions about "why does my geometry look slightly different each time?" often point to a variance or jitter variable. Recognizing that REVCLOUDARCVARIANCE is the dedicated toggle for revision cloud uniformity will help you quickly eliminate unrelated system variables as distractors.

Question 3

In an AutoCAD version that exposes separate minimum and maximum revision-cloud arc lengths, a drafter sets the minimum to 8080 drawing units and the maximum to 300300 drawing units. AutoCAD rejects the maximum because it exceeds the permitted relationship between the two values.

If the minimum must remain 8080 units, what is the largest valid maximum arc length?

  1. 160160 drawing units
  2. 240240 drawing units (correct answer)
  3. 300300 drawing units
  4. 320320 drawing units
Explanation: Whenever AutoCAD exposes separate minimum and maximum arc-length controls for revision clouds, it enforces a strict proportional rule: the maximum arc length cannot exceed three times the minimum arc length. This constraint exists to prevent arcs from becoming so irregular that the cloud loses its recognizable appearance. With a minimum of 8080 units, you calculate the upper bound by multiplying: 80×3=24080 \times 3 = 240 units. That makes B) 240 drawing units the largest valid maximum — any value beyond this violates AutoCAD's built-in validation and gets rejected outright. Looking at the distractors: A) 160 units corresponds to 80×280 \times 2, which is a valid maximum but not the largest one permitted — you'd be leaving usable range on the table. C) 300 units is exactly what the passage describes the drafter attempting, and the key point is that AutoCAD rejects it precisely because 300>240300 > 240. Choosing C means ignoring the rejection described in the scenario. D) 320 units equals 80×480 \times 4, which exceeds the multiplier even further — this is the most clearly invalid option, likely included to trap students who guess a "double of 160" pattern without knowing the actual rule. For your study sessions, remember the revision cloud constraint as the "3× rule": Max≤3×Min\text{Max} \leq 3 \times \text{Min}. Exam questions on this topic almost always give you the minimum and ask you to find the boundary, so practice applying this multiplier quickly rather than relying on memorized numbers.

Question 4

A review markup must resemble a broad-nib pen stroke, with a more stylized thick-and-thin appearance. The cloud's boundary and arc size are already correct, and changing the entire layer's lineweight would also affect other annotations.

Which revision-cloud modification best satisfies the requirement?

  1. Change the cloud's style from Normal to Calligraphy. (correct answer)
  2. Increase the cloud's maximum arc length while retaining Normal style.
  3. Reverse the cloud direction while retaining the current lineweight.
  4. Increase the revision layer's lineweight and reduce its transparency.
Explanation: When working with revision clouds in AutoCAD, it helps to remember that the REVCLOUD command offers more than just arc-size control — it also includes a Style property that changes the fundamental appearance of the cloud's strokes. This question is testing whether you know that style setting and what it visually produces. The passage specifies a "broad-nib pen" look with thick-and-thin variation — that's the hallmark of calligraphic line work. AutoCAD's revision cloud has exactly two style options: Normal (uniform arc strokes) and Calligraphy (strokes that vary in width, mimicking a broad-nib pen). Switching the style from Normal to Calligraphy, as choice A does, directly produces that thick-and-thin aesthetic without touching arc length, layer lineweight, or any other annotation on the layer. That's the precise, targeted fix the scenario demands. Choice B is wrong because increasing maximum arc length changes the size of the arcs, not their visual weight or stroke character — you'd still have uniform-width lines. Choice C reverses the cloud's direction (flipping which side the arcs bulge toward), which affects orientation, not stroke appearance — a common trap if you confuse "direction" with "style." Choice D is explicitly ruled out by the passage itself: raising the layer's lineweight would alter every annotation on that layer, not just the revision cloud. A good study tip: whenever an AutoCAD question involves a revision cloud's appearance rather than its size, think Style (Normal vs. Calligraphy) first — it's the only property that controls stroke-width variation independently of lineweight settings.

Question 5

A revision cloud was created around a group of relocated equipment. Later, the equipment geometry was moved again, but the cloud remained at its previous location even though both objects are on appropriately managed layers.

Which explanation and corrective action are most appropriate?

  1. The cloud is nonassociative; move, edit, or recreate it to match the revised geometry. (correct answer)
  2. The cloud lost annotative scaling; add the equipment's layer scale to the cloud.
  3. The cloud is externally referenced; reload the host drawing to update its position.
  4. The cloud has uniform arcs enabled; restore variable arcs to activate geometry tracking.
Explanation: Whenever you see a question about revision clouds in AutoCAD, the key concept to recall is associativity — or more precisely, the lack of it. Unlike dimensions or hatches (which can be associative and update when referenced geometry changes), revision clouds have no built-in link to other objects. They are purely independent drawing entities placed by the user to mark an area of change. This is exactly why A is correct. The cloud stayed behind when the equipment moved because it was never "attached" to that geometry in the first place. Revision clouds don't track, follow, or update alongside other objects — they simply exist where you drew them. The only fix is to manually move, stretch, or recreate the cloud around the new geometry location. B is a distractor built around the annotative scaling feature, which controls how objects display at different viewport scales. Annotative scaling has nothing to do with a cloud's position relative to geometry — confusing display scaling with spatial tracking is a common misconception. C incorrectly invokes external references; while xrefs do require reloading to reflect updates, the scenario describes a single drawing with no mention of xrefs. D fabricates a feature entirely — "uniform arcs" is not an AutoCAD property that enables or disables geometry tracking of any kind. As a study tip, remember this rule: revision clouds are always nonassociative. On the AutoCAD exam, if a question describes a cloud that didn't update after geometry changed, the answer will always involve manually correcting the cloud — not adjusting a setting or reloading a file.

Question 6

Most of an existing revision cloud is correct, but one side must be rerouted around an expanded revision area. The rest of the cloud should remain unchanged, and the final result should remain a continuous cloud.

Which workflow is most efficient?

  1. Reverse the cloud direction, stretch the revised side, and reverse the direction again.
  2. Explode the cloud, erase several arcs, and join newly drawn circles to the remaining segments.
  3. Scale the entire cloud from a point near the changed side, then trim the excess arcs.
  4. Use REVCLOUD Modify, draw the replacement path, and identify the obsolete portion to remove. (correct answer)
Explanation: When editing revision clouds in AutoCAD, the key question to ask yourself is: does a built-in tool exist that handles this specific task? Reaching for workarounds when a dedicated command is available is always less efficient — and this question tests whether you know REVCLOUD's Modify option. The REVCLOUD Modify option is purpose-built for exactly this scenario. You invoke REVCLOUD, select Modify, then trace a new path around the expanded revision area. AutoCAD automatically removes the obsolete portion of the original cloud and closes the result into a seamless, continuous cloud. No manual cleanup, no gap-closing, and the untouched sides remain perfectly intact. That makes D the most efficient workflow. The distractors each represent a common trap. A is a creative but clunky approach — reversing cloud direction doesn't give you surgical control over a single side, and stretching arcs distorts the characteristic arc size that gives revision clouds their meaning. B is the "brute force" trap: exploding a cloud destroys its object integrity and forces you to reconstruct geometry manually, which is time-consuming and error-prone. Joining circles to arc segments also doesn't regenerate proper cloud arcs. C misapplies the SCALE command — scaling the whole cloud changes every side proportionally, which violates the requirement that the rest of the cloud remain unchanged, and trimming leftover arcs still leaves an incomplete boundary. As a study tip, remember that AutoCAD often embeds editing sub-options within the original creation command (REVCLOUD, PLINE, SPLINE, HATCH). When a question involves modifying a specific object type, always check whether that command has a Modify or Edit option before assuming you need a workaround.

Question 7

An existing revision cloud encloses the correct area, but its scallops are too small and numerous at the intended plot scale. The enclosed footprint must not be enlarged.

What is the best modification in an AutoCAD version that treats the cloud as a revision-cloud object?

  1. Offset the cloud outward and erase the original cloud after plotting.
  2. Apply SCALE to the cloud using its geometric center as the base point.
  3. Increase the cloud's global width through its object properties.
  4. Increase the cloud's arc chord length through its object properties. (correct answer)
Explanation: When working with revision cloud objects in modern AutoCAD (as opposed to older polyline-based clouds), you should think about the object's editable properties rather than workarounds that alter its geometry or position. The key constraint here is that the enclosed footprint must stay the same — so any solution that moves or rescales the boundary is off the table. The revision cloud object stores an arc chord length property, which controls how large each individual scallop arc is. Increasing this value makes each arc span a longer chord, producing fewer, larger scallops — exactly what you need when scallops appear too small and cluttered at plot scale. The boundary defined by the cloud does not change; only the arc density does. That makes D the correct answer. A is wrong because offsetting the cloud outward directly violates the requirement that the enclosed footprint must not be enlarged. Erasing the original afterward doesn't fix the fact that you've changed the coverage area. B is wrong because applying SCALE enlarges the entire cloud object — both its scallops and its enclosed area — which again violates the footprint constraint. Choosing the geometric center as a base point is a reasonable-sounding detail, but it doesn't rescue a fundamentally incorrect operation. C is a tempting trap: "global width" sounds like it might affect scallop appearance, but global width is a polyline property, not a native property of the revision cloud object. Applying it here conflates two different object types and wouldn't produce the intended result. Remember: whenever a question specifies a revision cloud object (not a polyline), look for arc-related properties — chord length controls scallop size without touching the boundary.

Question 8

A drafter repeatedly creates revision clouds by specifying a series of vertices around angled mechanical components. The drafter wants that creation method to become the default for future REVCLOUD operations, without changing existing clouds.

Which setting should the drafter modify?

  1. REVCLOUDARCVARIANCE, selecting the setting for polygonal chord distribution
  2. REVCLOUDCREATEMODE, selecting the polygonal cloud creation method (correct answer)
  3. PLINEGEN, selecting continuous linetype generation around cloud vertices
  4. DELOBJ, selecting retention of source objects after cloud conversion
Explanation: When working with REVCLOUD in AutoCAD, questions about default behavior should direct your thinking toward system variables that store creation preferences — not variables that affect appearance or object handling. The drafter's workflow involves clicking a series of vertices to define the cloud's boundary, which is the polygonal creation method. The variable REVCLOUDCREATEMODE controls exactly this: it sets the default input method AutoCAD uses when you start the REVCLOUD command. Setting it to the polygonal option means every future REVCLOUD operation will default to vertex-by-vertex input, matching the drafter's habit — without touching any existing clouds. That makes B the correct answer. Now, let's clear up the distractors. A, REVCLOUDARCVARIANCE, controls how uniformly or randomly the arc sizes are distributed along the cloud's perimeter — it's a visual/aesthetic setting, not an input-method setting. C, PLINEGEN, determines whether linetypes are generated continuously across polyline vertices rather than restarting at each one; it has nothing to do with how revision clouds are created. D, DELOBJ, controls whether source geometry (like a rectangle or polyline used to convert into a cloud) is deleted or retained after conversion — it governs object cleanup, not the creation mode itself. The key trap here is confusing how a cloud looks (arc variance, linetype) or what happens to source objects (DELOBJ) with how a cloud is created (REVCLOUDCREATEMODE). On AutoCAD exams, always ask: does the variable control the workflow method or the result appearance? That distinction will help you eliminate distractors quickly.

Question 9

While converting a closed circular boundary with REVCLOUD's Object option, the proposed scallops bulge toward the center. Drafting standards require the scallops to bulge away from the enclosed revision.

What should the drafter change to correct the cloud without altering its boundary size?

  1. Increase the minimum arc length until each scallop extends beyond the circle.
  2. Select Calligraphy style so the wider side of each arc faces outward.
  3. Use Reverse direction so the scallops are generated on the opposite side. (correct answer)
  4. Apply a negative global width to reverse the converted polyline's curvature.
Explanation: When working with REVCLOUD's Object option, AutoCAD converts an existing closed shape (like a circle) into a revision cloud by generating arcs along its boundary. The critical concept here is that the direction the arcs curve — inward or outward — is determined by which direction AutoCAD traces the boundary. If the scallops are bulging the wrong way, the fix is purely about reversing that tracing direction, not about resizing or restyling anything. The Reverse direction prompt (choice C) flips how AutoCAD traverses the converted object's perimeter, which causes each arc to bulge toward the opposite side. Since the boundary itself doesn't change — only the direction of traversal does — the cloud's overall size and shape remain identical, satisfying the requirement to keep the boundary intact. Choice A is wrong because increasing the arc length changes the size and count of scallops, not which side they bulge toward. You'd distort the cloud's appearance without solving the direction problem. Choice B is a trap — the Calligraphy style varies line width to simulate a pen stroke effect, giving arcs a tapered look. It has no effect on which side the arcs curve toward. Choice D describes something that doesn't exist in AutoCAD; you cannot apply a negative global width to a polyline, and even if you could, polyline width has no bearing on arc curvature direction. A handy rule of thumb: whenever a REVCLOUD question mentions scallops facing the wrong direction, your first thought should be Reverse direction — it's AutoCAD's built-in fix for exactly this scenario, with zero impact on boundary geometry.

Question 10

A building plan is drawn in millimeters and will be plotted at a scale of 1:501:50. Office standards require revision-cloud arcs to appear approximately 55 mm to 88 mm long on the plotted sheet.

Which model-space arc-length range should be used when creating the revision cloud?

  1. 55 mm to 88 mm
  2. 5050 mm to 8080 mm
  3. 250250 mm to 400400 mm (correct answer)
  4. 500500 mm to 800800 mm
Explanation: Whenever you see a question about annotation sizes in AutoCAD, the key concept to apply is model-space scaling: anything that must appear a certain size on the plotted sheet must be drawn larger in model space by the plot scale factor. Here, the drawing uses a 1:501:50 scale, meaning every 1 mm on the paper represents 50 mm in the model. To find the correct model-space size, multiply the desired paper size by the scale factor: 5 mm×50=250 mm,8 mm×50=400 mm5 \text{ mm} \times 50 = 250 \text{ mm}, \quad 8 \text{ mm} \times 50 = 400 \text{ mm} So the revision-cloud arcs must be drawn between 250 mm and 400 mm in model space — confirming that C is correct. A (5 mm to 8 mm) is the trap for students who forget to scale up at all. If you draw arcs at paper size in model space, they will print nearly invisible at 1:501:50. B (50 mm to 80 mm) reflects multiplying by only 1010 instead of 5050 — perhaps confusing the scale factor or misreading 1:501:50 as 1:101:10. The arcs would still appear far too small on the plotted sheet. D (500 mm to 800 mm) overshoots by a factor of 10 — the result of multiplying by 100100 instead of 5050, or simply misjudging the scale direction entirely. These arcs would plot ten times too large. As a quick rule: paper size × scale denominator = model-space size. Tattoo this formula in your memory for any annotation, hatch, or cloud question involving a plot scale.