Blender Quiz: Use Depth Of Field And Focus Controls Intro
10 questions · exam conditions
0:00
Use Depth Of Field And Focus Controls IntroQuestion 1 of 10

An artist wants a rack-focus shot that begins on a foreground actor and ends on a background sign. The camera currently has a stationary Focus Object assigned, and keyframing Focus Distance alone produces no visible focus transition.

Which workflow will correctly create the rack focus while leaving the camera stationary?

Keep the stationary Focus Object and keyframe only the camera's clipping end value.
Clear the Focus Object and keyframe Focus Distance between the two subject depths.
Keep the stationary Focus Object and keyframe only the camera's F-Stop rotation.
Clear the Focus Object and keyframe the camera's sensor fit between the subjects.
← Back to quizzes

Blender Quiz

Blender Quiz: Use Depth Of Field And Focus Controls Intro

Practice Use Depth Of Field And Focus Controls Intro 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 Depth Of Field And Focus Controls Intro, 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

An artist wants a rack-focus shot that begins on a foreground actor and ends on a background sign. The camera currently has a stationary Focus Object assigned, and keyframing Focus Distance alone produces no visible focus transition.

Which workflow will correctly create the rack focus while leaving the camera stationary?

  1. Keep the stationary Focus Object and keyframe only the camera's clipping end value.
  2. Clear the Focus Object and keyframe Focus Distance between the two subject depths. (correct answer)
  3. Keep the stationary Focus Object and keyframe only the camera's F-Stop rotation.
  4. Clear the Focus Object and keyframe the camera's sensor fit between the subjects.
Explanation: When working with depth of field in Blender, it helps to understand that the camera's focus system has two mutually exclusive modes: a Focus Object (which dynamically locks focus to a tracked object) and a manually keyframed Focus Distance value. The key insight is that these two modes conflict — when a Focus Object is assigned, it overrides the Focus Distance field entirely, which is exactly why keyframing Focus Distance alone produces no visible result in the scenario described. To create a rack focus, you need the Focus Distance to be in control. That means first clearing the Focus Object, which hands control back to the numeric Focus Distance parameter. Once cleared, you can set a keyframe at the foreground actor's depth, then advance the timeline and set another keyframe at the background sign's depth. Blender will interpolate between them, producing a smooth, realistic focus pull — all while the camera itself stays stationary. That's why B is correct. A is wrong because clipping end controls how far the camera renders geometry, not where it focuses. Changing it has no effect on depth of field blur. C is wrong because F-Stop controls the intensity of the bokeh blur (aperture size), not where the focal plane sits — and the Focus Object would still override Focus Distance anyway. D is wrong because sensor fit adjusts how the camera maps its sensor dimensions to the render resolution, which affects framing and field of view, not focus depth. A useful rule of thumb: if Focus Distance keyframes seem to do nothing, your first instinct should be to check whether a Focus Object is overriding it.

Question 2

Three small objects are positioned at different horizontal locations in the frame. Their origins all lie on the same plane perpendicular to the camera's viewing direction. The center object's origin is used as the Focus Object.

Assuming the objects are otherwise identical, which result is most consistent with the camera's depth-of-field model?

  1. Only the center object is sharp because focus forms a sphere around the camera.
  2. All three can be sharp because their origins share the camera's focal plane. (correct answer)
  3. The side objects are clipped because they are farther from the image center.
  4. Only the side objects are sharp because depth of field excludes the optical axis.
Explanation: When working with depth of field in Blender, the key concept to understand is how the focal plane is defined. Blender's camera uses a planar depth-of-field model: everything at the same distance from the camera along its optical axis lies on the same focal plane, and objects whose origins fall on that plane will appear sharp. In the scenario described, all three objects have their origins on the same plane perpendicular to the camera's viewing direction — meaning they share the exact same depth value. Because the center object's origin defines the Focus Object, that depth becomes the focal plane. Since the side objects' origins sit at that same depth, their origins also fall on the focal plane, making all three objects equally sharp. This is why B is correct: sharing the focal plane is sufficient for sharpness, regardless of horizontal position in the frame. A is wrong because Blender's depth of field does not operate as a sphere centered on the camera. Focus is determined by distance along the camera's Z-axis, not radial distance from the camera's position — that would be a physically incorrect model. C confuses depth of field with a concept called lens vignetting or image clipping, neither of which is what depth of field controls. Horizontal position in the frame doesn't cause objects to fall out of focus or become clipped by the DoF system. D inverts the logic entirely. Depth of field doesn't exclude the optical axis — the center of the frame has no special penalty, and the Focus Object itself sits there. Remember: in Blender, depth drives focus, not screen position. If origins share the same camera-axis distance, they share the focal plane.

Question 3

In Cycles, lowering the camera's F-Stop creates the desired shallow depth of field, but the defocused background becomes noticeably noisy. The focus location and blur amount must remain unchanged.

Which adjustment is the most appropriate first response?

  1. Disable depth of field entirely and reduce the Focus Distance until the noisy region is hidden.
  2. Raise the F-Stop substantially and move the clipping end closer to the background plane.
  3. Increase render samples or enable denoising while keeping the existing depth-of-field settings. (correct answer)
  4. Move the Focus Object behind the background and reduce render resolution to hide the noise.
Explanation: Whenever you see a question about noisy renders in Cycles, your first instinct should be to identify the source of the noise before changing anything that affects the visual result. Noise in Cycles is fundamentally a sampling problem — the renderer hasn't collected enough light data to produce a clean image. Shallow depth of field, created by a low F-Stop, forces Cycles to trace many more ray paths through the lens aperture to simulate blur. This dramatically increases variance in defocused regions, which appears as grain. The correct first response is C: increase render samples so Cycles gathers more data per pixel, or enable denoising (such as the built-in OpenImageDenoise) to intelligently smooth the result — all without touching the depth-of-field settings the question explicitly protects. A is a trap because disabling depth of field entirely defeats the purpose of the shot. Reducing Focus Distance doesn't address noise at all — it just shifts what's in focus, which you're told must remain unchanged. B sounds technical but is wrong on both counts. Raising the F-Stop reduces the aperture, which lessens the depth-of-field blur — again violating the constraint. Moving the clipping end affects what geometry the camera renders, not noise quality. D is a red herring. Moving the Focus Object behind the background is conceptually backwards, and reducing render resolution hides detail rather than solving noise, producing a lower-quality image overall. A reliable study tip: in Cycles, noise and depth of field are separate concerns. Noise is a sampling issue; fix it with samples or denoising. Depth of field is a lens issue; fix it with F-Stop or Focus Distance.

Question 4

An artist enables the camera's viewport Limits display and sees additional camera guides. Expecting stronger blur, the artist renders again without changing F-Stop, Focus Distance, or the Focus Object. The rendered depth of field is unchanged.

What is the best explanation?

  1. Viewport Limits alter blur only after the camera's focal length is keyframed.
  2. Viewport Limits affect depth of field only when the camera has no clipping range.
  3. Viewport Limits are display guides and do not modify the rendered depth-of-field calculation. (correct answer)
  4. Viewport Limits modify depth of field only for objects hidden in the viewport.
Explanation: When working with Blender's camera settings, it helps to distinguish between display/visualization tools and render-calculation parameters. Viewport Limits is exactly this kind of question — it tests whether you understand which settings actually affect the rendered output versus which simply help you see information in the 3D viewport. Viewport Limits, found in the camera's Object Data Properties, draws visual guides in the viewport showing the camera's near and far clipping distances. These lines are purely informational overlays — they help you understand your scene spatially, but they pass no data into Blender's depth-of-field engine. The rendered blur is controlled exclusively by F-Stop (aperture width), Focus Distance (or a Focus Object), and the lens focal length. Since the artist changed none of those, the render is unchanged. C is correct. A is wrong because depth of field has no dependency on whether the camera has keyframes. Keyframing is an animation tool; it doesn't gate or unlock how render parameters behave. B is wrong because camera clipping range governs how far geometry is drawn/rendered in the scene — it has nothing to do with enabling or disabling depth-of-field calculations, regardless of Viewport Limits. D is wrong because depth of field applies to visible, rendered objects based on their distance from the camera. Objects hidden in the viewport (via the eye icon) aren't rendered at all, so they're irrelevant here. As a study tip: whenever a Blender question mentions a display or overlay setting, ask yourself, "Does this actually write data to the render engine, or does it only change what I see in the viewport?" That single question will resolve many similar traps.

Question 5

A shot already has the desired amount of background blur. The artist wants the circular bokeh to become oval and then rotate the oval's long axis, without moving the focal plane.

Which combination of controls should the artist use?

  1. Change the camera type to Orthographic, then adjust sensor fit for orientation.
  2. Change Focus Distance away from the subject, then adjust F-Stop for orientation.
  3. Change Aperture Blades to 00, then adjust clipping start for orientation.
  4. Change Aperture Ratio away from 1.01.0, then adjust Aperture Rotation for orientation. (correct answer)
Explanation: When working with Blender's depth-of-field settings, it helps to separate two concerns: bokeh shape and bokeh orientation. The question asks you to distort circular bokeh into an oval and then rotate that oval — all without touching the focal plane. The Aperture Ratio (found in the camera's Depth of Field settings) controls the aspect ratio of the bokeh shape. At 1.01.0, bokeh is perfectly circular; moving it away from 1.01.0 stretches it into an oval. Aperture Rotation then spins that oval around its center, letting you point the long axis wherever you like. Together, these two controls do exactly what the prompt describes — making D the correct answer. Choice A is a trap because switching to Orthographic projection eliminates perspective entirely, which actually removes depth-of-field blur rather than reshaping it. Sensor fit affects image cropping, not bokeh geometry. Choice B confuses bokeh shape with bokeh amount. Changing Focus Distance shifts which plane is sharp (moving the focal plane, which the question explicitly forbids), and F-Stop controls blur intensity — neither reshapes the bokeh into an oval. Choice C is doubly wrong. Setting Aperture Blades to 00 produces circular bokeh (the default round aperture), so it cannot create an oval. Clipping Start determines how close to the camera geometry is rendered, and has no effect on bokeh shape or rotation whatsoever. A good study habit here: memorize that Aperture Ratio → shape, Aperture Rotation → orientation, and F-Stop → amount. Blender exam questions often mix these three to test whether you can distinguish them.

Question 6

A product render has the correct brightness and focus point, but the labels slightly in front of and behind the focus point remain too sharp. The camera's F-Stop is 8.08.0.

Which change most directly produces a shallower depth of field without requiring an exposure correction in Blender?

  1. Increase the F-Stop above 8.08.0 while leaving the focus point unchanged.
  2. Decrease the F-Stop below 8.08.0 while leaving the focus point unchanged. (correct answer)
  3. Decrease the shutter time while leaving the camera aperture unchanged.
  4. Increase the clipping start while leaving the camera aperture unchanged.
Explanation: Whenever you see a question about depth of field in Blender, think about the relationship between F-Stop and aperture size. The F-Stop value is inversely related to the aperture opening: a lower F-Stop means a wider aperture, which lets in more light and produces a shallower depth of field (more background/foreground blur). A higher F-Stop means a narrower aperture and a deeper depth of field (more of the scene stays sharp). The scenario describes labels near the focus point appearing too sharp — meaning the depth of field is too deep. To fix this, you need to widen the aperture, which means decreasing the F-Stop below 8.08.0. In Blender's camera settings, lowering the F-Stop directly controls the virtual aperture blade size, producing more bokeh and a narrower in-focus zone. Crucially, the question asks for no exposure correction needed — but note that in Blender's Cycles or EEVEE with physical camera settings enabled, changing the F-Stop does affect exposure. However, among the given options, B is the only choice that directly addresses depth of field through aperture, making it the most correct answer in this context. Choice A is wrong because increasing the F-Stop narrows the aperture, which would make the depth of field even deeper — the opposite of what you need. Choice C is wrong because shutter time affects motion blur and exposure, not depth of field. Choice D is wrong because clipping start controls where Blender begins rendering geometry in the viewport — it has no effect on depth of field or aperture. Remember the core rule: lower F-Stop = wider aperture = shallower depth of field. This inverse relationship is one of the most commonly tested camera concepts in Blender certification questions.

Question 7

A camera uses a manually entered Focus Distance and is initially aimed directly at a statue. The camera is then rotated toward a nearby doorway without changing its location or Focus Distance. The artist expected the statue to remain the focus target.

Which statement best explains the resulting focus behavior?

  1. The focal plane moves to the clipping end, so both the doorway and statue become equally sharp.
  2. The focal plane remains fixed in world space, so camera rotation cannot affect the statue's focus.
  3. The focal plane follows the nearest visible object, so the doorway automatically becomes the focus target.
  4. The focal plane rotates with the camera, so the unchanged distance no longer guarantees focus on the statue. (correct answer)
Explanation: Whenever you see a question about camera focus in Blender, the key concept to understand is how Focus Distance is defined: it's measured as a fixed distance along the camera's local Z-axis (the direction the camera is pointing), not as a distance to a specific object in world space. This means the focal plane is always a flat surface sitting at the specified distance directly in front of wherever the camera is aimed. When you rotate the camera toward the doorway, that focal plane rotates with it — it pivots around the camera's location and now sits at your set distance in front of the doorway, not the statue. The statue, which is now off to the side, no longer falls on that plane. D is correct because the rotation changed what the unchanged distance points at, breaking the artist's assumption that the statue would stay in focus. A is wrong because focal planes don't snap to clipping boundaries — the clipping range and focal plane are separate concepts, and there's no mechanism that makes everything equally sharp here. B describes how focus would work if it were pinned to a world-space coordinate, but Blender's Focus Distance is camera-relative, not world-relative; rotating the camera absolutely does change what's in focus. C describes autofocus behavior based on proximity detection, which doesn't exist in Blender's manual Focus Distance mode — the camera doesn't detect or track objects automatically. The key study tip: always remember that Focus Distance is camera-local. Think of the focal plane as a physical panel attached to the front of the camera — it goes wherever the camera points.

Question 8

An Empty is visibly placed on the front surface of a large glass sphere and assigned as the camera's Focus Object. After the Empty is scaled and its displayed shape becomes much larger, the sphere's intended surface remains in focus at the same location.

Why did scaling the Empty not shift the camera's focus?

  1. The focus calculation uses the Empty's origin position, not the size of its viewport display. (correct answer)
  2. The focus calculation uses the Empty's nearest visible edge, which remained attached to the sphere.
  3. The focus calculation ignores all Empty transforms after the object is first assigned.
  4. The focus calculation uses the sphere's origin because the Empty touches its surface.
Explanation: When working with Blender's depth-of-field system, it helps to understand what the camera actually tracks when you assign a Focus Object: it locks onto that object's origin point — the small orange dot that marks the object's local center — not its visual representation in the viewport. Empties are display-only objects with no real geometry. Their "size" slider and shape (axes, circle, cube, etc.) only affect how they look in the viewport as a visual aid. Scaling an Empty or changing its display size never moves its origin. Since the camera measures focus distance from its own origin to the Focus Object's origin, and neither origin moved, the focal plane stays exactly on the sphere's surface. That's why A is correct. B is wrong because Blender doesn't trace edges or mesh boundaries for focus calculations — Empties have no geometry edges at all, so this logic doesn't apply to any object type. C is incorrect because the camera does continuously update focus as the Focus Object moves through the scene; transforms like location and rotation absolutely affect focus. What doesn't matter is display size. D is a tempting trap — it implies proximity to another object somehow transfers ownership of the focus target — but the camera always reads the assigned Focus Object's own origin, regardless of what that object is touching or overlapping. A useful rule of thumb: in Blender, origins drive behavior, display drives appearance. Whenever a question involves parenting, constraints, or focus objects, ask yourself whether the origin moved — because that's almost always what the engine actually cares about.

Question 9

A camera has a Focus Object assigned to an Empty located on a character's eyes. The camera's Focus Distance is also set to a different distance. The artist changes only the Focus Distance, but the rendered focal plane does not move.

Which action will make the manually entered Focus Distance control the focal plane?

  1. Clear the Focus Object assignment, then adjust the camera's Focus Distance. (correct answer)
  2. Keep the Focus Object assigned, then reduce the camera's F-Stop value.
  3. Move the camera clipping start behind the manually entered focus distance.
  4. Disable the Empty's viewport visibility, then adjust the Focus Distance.
Explanation: When working with Blender's camera depth of field system, it's important to understand that Focus Object always overrides Focus Distance. These two settings don't blend or average together — the Focus Object takes complete priority. If a Focus Object is assigned, Blender calculates the focal plane based on that object's distance from the camera at render time, and your manually typed Focus Distance value is simply ignored. This is why A is correct. Clearing the Focus Object assignment removes the override, allowing the camera to use the Focus Distance value you've entered directly. Once the Focus Object field is empty, adjusting Focus Distance will immediately control where the focal plane sits in your scene. B is wrong because F-Stop controls the depth of field blur intensity — how wide or narrow the in-focus band appears — not which distance is used as the focal plane. Reducing F-Stop makes more of the scene blurry but doesn't resolve the override conflict. C is a trap that conflates clipping with focus. Clipping Start determines what geometry the camera renders at all — it has no relationship to depth of field calculations or focal plane position. D is a common misconception: viewport visibility (the eye icon) affects whether you see an object in the viewport, not whether it functions as a focus target. The camera's data block still references the Empty as a Focus Object regardless of its visibility setting, so the override remains active. As a study rule: whenever a camera setting "isn't working," check whether a linked object (Focus Object, Constraints, Tracking) is silently overriding your manual input.

Question 10

Out-of-focus point lights should appear as clearly defined hexagons. The camera already has a low F-Stop, but the highlights remain circular.

Which camera adjustment most directly creates the requested highlight shape?

  1. Set Aperture Blades to 66 and use Aperture Rotation to orient the hexagons. (correct answer)
  2. Set Aperture Blades to 33 and use Focus Distance to add three more sides.
  3. Leave Aperture Blades at 00 and use Aperture Ratio to form regular hexagons.
  4. Set Aperture Blades to 66 and use the clipping range to sharpen the hexagons.
Explanation: When working with Blender's camera settings for cinematic bokeh effects, the key concept is aperture blade simulation. In real cameras, the aperture diaphragm is made of overlapping blades that form a polygon — and that polygon shape is exactly what out-of-focus point lights (bokeh highlights) reveal. Blender's camera properties replicate this physically. To produce hexagonal bokeh, you need exactly 66 aperture blades, since each blade contributes one side to the polygon. Once the blade count is correct, Aperture Rotation lets you orient the resulting hexagons to any angle — useful when art direction requires a specific tilt. A low F-Stop (already set in the scenario) ensures the bokeh is visible and defocused, but without the correct blade count, the shape stays circular. Option A correctly pairs both controls: blade count for shape, rotation for orientation. Option B is wrong on two counts — 33 blades produce triangles, not hexagons, and "Focus Distance" controls where the focal plane sits, not how many sides a bokeh shape has. You cannot add sides by adjusting focus. Option C fails because setting Aperture Blades to 00 tells Blender to use a perfectly circular aperture — the very problem described in the passage. "Aperture Ratio" adjusts the elliptical stretch of the aperture, not the number of sides. Option D correctly sets the blade count but then incorrectly invokes the clipping range, which determines how near and far objects are rendered in the scene — it has no influence on bokeh shape. The study takeaway: when a Blender question involves bokeh shape, always think Aperture Blades = number of sides, and pair it with Aperture Rotation for orientation control.