Blender Quiz: Enable Compositing And Use Basic Nodes Render Layers Composite Viewer
10 questions · exam conditions
0:00
Enable Compositing And Use Basic Nodes Render Layers Composite ViewerQuestion 1 of 10

An artist wants the same unmodified Render Layers image to appear in the compositor preview and become the final composite. The artist is considering duplicating the Render Layers node to provide one source for each output node.

Which setup achieves the goal with the least unnecessary duplication?

Use one Render Layers node connected to Composite, which automatically mirrors into Viewer
Use two Render Layers nodes because each output socket permits only one outgoing connection
Use one Render Layers node connected to Viewer, then connect Viewer onward to Composite
Use one Render Layers node and link its Image output separately to Viewer and Composite
← Back to quizzes

Blender Quiz

Blender Quiz: Enable Compositing And Use Basic Nodes Render Layers Composite Viewer

Practice Enable Compositing And Use Basic Nodes Render Layers Composite Viewer 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 Enable Compositing And Use Basic Nodes Render Layers Composite Viewer, 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 the same unmodified Render Layers image to appear in the compositor preview and become the final composite. The artist is considering duplicating the Render Layers node to provide one source for each output node.

Which setup achieves the goal with the least unnecessary duplication?

  1. Use one Render Layers node connected to Composite, which automatically mirrors into Viewer
  2. Use two Render Layers nodes because each output socket permits only one outgoing connection
  3. Use one Render Layers node connected to Viewer, then connect Viewer onward to Composite
  4. Use one Render Layers node and link its Image output separately to Viewer and Composite (correct answer)
Explanation: When working with Blender's compositor, it helps to understand a fundamental rule: a single node's output socket can feed multiple destination nodes simultaneously. This is different from input sockets, which typically accept only one connection. Keeping this distinction clear will help you avoid unnecessary node duplication. Because one output socket can branch to multiple nodes, you only need a single Render Layers node. You simply drag two separate links from its Image output — one going to the Viewer node and one going to the Composite node. Both receive the identical, unmodified image from the same source. That's exactly what D describes, and it's the cleanest solution. A is tempting but wrong. Connecting the Render Layers node to only the Composite node does not automatically mirror the result into the Viewer node. The Viewer must be explicitly connected to see a live preview in the Image Editor. B reflects a common misconception — that output sockets are limited to a single outgoing wire, the way input sockets are. In Blender's node editor, output sockets can fan out to as many destinations as you need. A second Render Layers node is entirely unnecessary here. C describes chaining the Viewer between Render Layers and Composite, as if the Viewer passes data forward. The Viewer is a terminal display node; it doesn't output data to other nodes. Connecting through it would break the pipeline entirely. A good rule of thumb: in Blender's node system, always ask yourself "can I just branch this output wire?" before reaching for a duplicate node — most of the time, you can.

Question 2

A Blender file contains two scenes. Scene A has Use Nodes enabled and a working Render Layers-to-Composite setup. Scene B has no compositor node tree enabled. The artist switches to Scene B and renders it, expecting Scene A's compositor setup to be applied.

What change is needed to make that expectation valid for Scene B?

  1. Connect Scene B's camera to Scene A's Composite node because cameras carry compositor settings
  2. Select Scene A in the Viewer node because Viewer determines which scene owns compositing
  3. Rename Scene B to Scene A because node trees are matched to scenes by their displayed names
  4. Enable and configure compositing for Scene B because compositor node trees are associated with scenes (correct answer)
Explanation: When working with Blender's compositor, the key concept to understand is that compositor node trees belong to individual scenes, not to the project as a whole. Each scene maintains its own independent node graph, and enabling "Use Nodes" in one scene has absolutely no effect on any other scene in the file. This is why D is the correct answer. Scene B needs its own compositor node tree configured with "Use Nodes" enabled. There is no mechanism in Blender that shares or inherits compositor setups across scenes — you must build (or recreate) the node tree within each scene where you want compositing to apply. The artist's expectation that Scene A's setup would carry over is a fundamental misunderstanding of how scene-level data works in Blender. Looking at the distractors: A is a trap that confuses camera objects with compositor data — cameras define a viewpoint, not post-processing behavior, and connecting cameras between scenes accomplishes nothing for compositing. B misrepresents the Viewer node entirely; the Viewer node is simply a preview display node within a compositor graph and has no authority over which scene "owns" compositing. C reflects a completely fictional behavior — Blender does not match node trees to scenes by name, and renaming Scene B would have zero effect on its compositor state. A useful rule of thumb: in Blender, scene-level settings stay in their scene. Whenever a question asks about sharing render, compositor, or world settings across scenes, your first instinct should be to check whether each scene has been independently configured. This applies to compositing, world lighting, and render properties alike.

Question 3

The compositor contains a correctly connected Render Layers-to-Composite chain. The artist enables Backdrop, but no image appears behind the nodes even though the render completed successfully.

Which modification most directly supplies an image for the compositor backdrop?

  1. Connect Render Layers to a Viewer node while keeping Backdrop enabled (correct answer)
  2. Reconnect Render Layers to Composite and disable the Backdrop option
  3. Connect the Composite node to a Viewer node through their Image sockets
  4. Select the Render Layers node and enable its scene camera preview
Explanation: When working with Blender's compositor, it helps to understand that the Backdrop and the Composite node serve entirely different purposes. The Composite node defines the final render output — it writes pixels to the render result. The Backdrop, however, pulls its image from a Viewer node, which is a completely separate node designed specifically to display a live preview behind your node tree. This distinction is the heart of the question. Even though the Render Layers → Composite chain is valid and the render completed, no Viewer node exists in the setup, so the Backdrop has nothing to display. The fix is exactly what A describes: connect the Render Layers node (or any node whose output you want to preview) to a Viewer node while keeping Backdrop enabled. The Backdrop then reads from that Viewer node and displays the image behind your network. B is wrong because disabling Backdrop simply hides the preview feature entirely — it doesn't fix the missing image problem and removes the functionality you're trying to use. C describes an impossible connection; the Composite node has no "Image" output socket, and piping it into a Viewer node through such a socket isn't a real Blender workflow. D is a fabricated option — Render Layers nodes don't have a "scene camera preview" toggle, so this reflects a misunderstanding of how that node works. A good study tip: remember the phrase "Composite outputs, Viewer displays." Any time you want to see a live image in the Backdrop, your workflow must include a Viewer node — the Composite node alone will never feed the Backdrop.

Question 4

A render has already finished. Without changing the scene, camera, view layer, or render settings, an artist adds a Viewer node and connects the existing Render Layers Image output to it.

What is generally the most efficient next step for inspecting the image?

  1. Evaluate the compositor using the existing render data; repeating the 3D render is generally unnecessary (correct answer)
  2. Start a new 3D render, because Render Layers nodes discard all data once the render window closes
  3. Save and reopen the file, because Viewer nodes can only display images that have been written to disk
  4. Replace Render Layers with an Image node pointed at the saved render, since only Image nodes retain completed results
Explanation: When working with Blender's Compositor, it helps to understand the difference between rendering and compositing. Rendering is the expensive 3D computation that produces raw image data; compositing is the cheaper 2D processing that happens afterward in the node graph. These are two separate stages, and Blender keeps them that way intentionally. After a render completes, Blender caches the render result in memory. The Render Layers node acts as a direct pipeline into that cached data — it doesn't discard the result when the render window closes. This means you can freely modify your compositor node tree and re-evaluate it against the existing render without starting a new 3D render. Adding a Viewer node and pressing Compose (or simply enabling auto-render in the compositor) reads from that cached result immediately. Answer A correctly describes this workflow: re-running the compositor against existing data is all you need. Answer B is wrong because it describes a behavior that doesn't exist — Render Layers nodes do not discard data when the render window closes, as long as the file remains open and the render result is still in memory. Answer C is wrong because Viewer nodes display live compositor output directly in the Image Editor; they have no requirement that an image be saved to disk first. Answer D is wrong because it solves a problem that doesn't exist — Render Layers nodes can already access the cached render, so replacing them with an Image node is unnecessary extra work. A good rule of thumb: in Blender, always ask yourself whether your change is a scene/render change or a compositor change. If it's purely compositional, you can almost always avoid a costly re-render.

Question 5

A render was made with transparency, and the artist wants to pass it through the compositor unchanged. Render Layers provides both an Image output and a separate Alpha output.

Which connection preserves the rendered color and its existing transparency in the normal pass-through setup?

  1. Connect only the Alpha output to Composite's Image input because Composite reconstructs the original colors
  2. Connect the Image output to Composite's Image input because that image already includes alpha information (correct answer)
  3. Connect Image to Viewer and Alpha to Composite so Blender combines the two output nodes automatically
  4. Connect both Image and Alpha directly to Composite because it has separate color and alpha inputs
Explanation: When working with Blender's compositor, it helps to understand how alpha information travels through the node system. The Image output from a Render Layers node carries an RGBA signal — that's red, green, blue, and alpha combined into a single data stream. The Alpha output is simply a separate, isolated grayscale channel extracted from that same image for cases where you need to manipulate transparency independently. Because the Image output already contains embedded alpha, connecting it directly to the Composite node's Image input is all you need to preserve both color and transparency intact. That's exactly what B describes, and it's the correct approach for a straightforward pass-through setup. A is backwards — the Composite node does not reconstruct color from an alpha signal alone. Sending only alpha to the Image input would produce a grayscale render at best, discarding all color data entirely. C misunderstands how output nodes work; the Viewer and Composite nodes are independent destinations, not components that Blender merges automatically. Routing Image to one and Alpha to the other simply sends partial data to two separate places. D is a common trap — the Composite node has a single Image input, not separate color and alpha inputs. Trying to connect both Image and Alpha simultaneously to the same socket would just override one connection with the other. The study tip here: remember that in Blender's compositor, RGBA travels together through the Image socket. Reach for the separate Alpha output only when you specifically need to isolate or modify transparency — not during a simple pass-through.

Question 6

A new scene has never used compositing. After completing a render, an artist opens the Compositor and clicks Use Nodes without manually adding or removing any nodes.

Which node arrangement should the artist expect Blender to create initially?

  1. A Render Layers node connected from its Image output to the Composite node's Image input (correct answer)
  2. A Render Layers node connected from its Alpha output to the Viewer node's Image input
  3. A Viewer node connected from its Image output to the Composite node's Image input
  4. A Composite node connected from its Image output to the Render Layers node's Image input
Explanation: When you enable compositing in Blender for the first time by clicking Use Nodes, Blender doesn't give you a blank slate — it automatically generates a default node setup designed to get you compositing immediately without extra configuration. Understanding what that default looks like is what this question tests. Blender's default compositor arrangement connects a Render Layers node to a Composite node, specifically wiring the Render Layers node's Image output into the Composite node's Image input. This makes practical sense: the Composite node is the final output destination (what gets saved or displayed as the rendered result), and the Render Layers node is the source feeding rendered image data into the pipeline. Choice A correctly describes this connection. Choice B is wrong because the Alpha output is not what gets routed by default — the Image output is — and the Viewer node is a preview tool, not part of the default auto-generated setup. Choice C inverts the logic entirely: a Viewer node has no Image output that feeds a Composite node; data flows into the Viewer node, not out of it. Choice D reverses the direction of the connection altogether — the Composite node receives data, it doesn't send it back upstream to the Render Layers node, which would be a meaningless loop. A helpful pattern to remember: in Blender's Compositor, data always flows left to right — sources (like Render Layers) on the left feed into destinations (like Composite) on the right. Any answer suggesting reversed data flow or a non-default node like Viewer in the auto-setup should be an immediate red flag.

Question 7

An artist intends to send an unmodified render to the final compositor output but is unsure which sockets establish the valid data flow.

Which socket-level connection correctly implements the intended pass-through?

  1. Composite Image output to Render Layers Image input, with the output node placed first in the chain
  2. Render Layers Alpha output to Composite Image input, producing the complete RGBA render result
  3. Render Layers Image output to Composite Image input, following source-to-destination data flow (correct answer)
  4. Composite Image input to Render Layers Image output, reversing the standard source-to-destination direction
Explanation: When working in Blender's Compositor, you need to think about data flow direction: information travels from a source node's output socket to a destination node's input socket — always left to right, output to input. The simplest pass-through setup connects the Render Layers node (which supplies rendered image data) directly to the Composite node (which sends data to the final output). The Render Layers node exposes an Image output socket carrying the full RGBA render result, and the Composite node exposes an Image input socket expecting exactly that data. Connecting Render Layers' Image output → Composite's Image input is the correct, minimal pass-through — which makes C the right answer. A is wrong on two counts: you cannot connect a Composite output to a Render Layers input (that reverses data flow), and the Composite node doesn't logically feed back into the source. The "placed first in the chain" detail further confuses node order with data direction. B fails because the Alpha socket carries only the transparency channel — a single grayscale value — not the complete RGBA image. Plugging Alpha into the Composite's Image input would produce an incomplete, monochrome result rather than the full render. D explicitly reverses source-to-destination direction by describing a connection from Composite's input to Render Layers' output, which is physically impossible in Blender's node editor — data cannot flow backward through sockets. Study tip: Always trace data flow by asking "where does the data come from (output socket) and where does it go (input socket)?" Output → Input is the universal rule in Blender's node systems.

Question 8

A scene renders two view layers named Characters and Environment. The Composite output currently shows Environment, but the artist wants the unmodified Characters layer instead. Both view layers are configured to be included in the render.

Which change is the most direct solution using the existing basic nodes?

  1. Change the Render Layers node's layer selection to Characters and keep its Image output connected (correct answer)
  2. Change the Composite node's layer selection to Characters and reconnect its Image input
  3. Rename Environment to Characters so the Composite node resolves the desired layer automatically
  4. Connect the Render Layers Alpha output because it encodes which view layer should be displayed
Explanation: When working with Blender's Compositor, it helps to understand the role of each node type. The Render Layers node is the source — it reads a specific view layer and exposes its data as outputs (Image, Alpha, Depth, etc.). The Composite node is the destination — it receives whatever is connected to it and sends that to the final output. Changing what the source reads is how you switch which layer appears in the result. In this scenario, the Render Layers node is currently set to Environment, so its Image output carries Environment's pixel data. Simply switching that node's layer selection to Characters means the same Image output now carries Characters data — no rewiring needed. That's exactly what A does, making it the most direct solution. B is wrong because the Composite node has no "layer selection" property at all — it's purely a destination node with an input socket, not a source. This option describes a feature that doesn't exist, making it a classic distractor that sounds plausible if you conflate the two node types. C is wrong because renaming the Environment view layer to Characters doesn't change what the Render Layers node is currently reading, nor does it give you the actual Characters layer data — it just relabels the wrong layer. You'd lose Environment content without gaining anything. D is wrong because the Alpha output encodes transparency information for that layer's pixels, not metadata about which view layer is "active." It carries no routing logic whatsoever. The key habit to build: always trace data from source to destination in a node graph. When output is wrong, fix the source first.

Question 9

A scene has Use Nodes enabled and a valid Render Layers-to-Composite connection. However, the Compositing option in the render post-processing settings is disabled before the artist starts a new render.

What should the artist expect from that render?

  1. The compositor evaluates normally, but only the Viewer output is omitted from the interface
  2. The compositor evaluates once, but its result is discarded only when the image is saved
  3. The render bypasses compositor processing even though the scene's compositor nodes still exist (correct answer)
  4. The render fails because enabling Use Nodes requires the Compositing option to remain enabled
Explanation: When working with Blender's compositor, it helps to understand that two separate switches control node-based compositing: Use Nodes (in the Compositor editor) and the Compositing toggle found under Post Processing in the render properties. These are independent settings, and confusing them is exactly what this question tests. The Compositing post-processing toggle acts as a master on/off switch that tells the render pipeline whether to pass the rendered image through the compositor at all. When you disable it, Blender skips compositor evaluation entirely during rendering — even if your node tree is fully built, connected, and valid. The raw render result goes directly to output, untouched. That's why C is correct: the compositor nodes still exist in the scene, but the render bypasses them completely. A misrepresents the behavior by suggesting the compositor still evaluates — it doesn't. Disabling the post-processing toggle prevents evaluation altogether; it's not a display-only change that merely hides the Viewer node output. B is wrong because it implies the compositor runs but its result is discarded at save time. In reality, the compositor never runs at all — there's nothing to discard. D describes a failure state that simply doesn't happen. Blender won't throw an error or crash because these two settings are independent. Having Use Nodes enabled while Compositing is disabled is a perfectly valid (and common) workflow state. A good rule of thumb: Use Nodes governs whether the node tree is active in the editor, while the Compositing post-processing option governs whether it runs during render. Know both toggles and what each one actually controls.

Question 10

An artist connects the Render Layers Image output to a Viewer node and sees the expected image in the compositor preview. The same image must also become the result used when the completed render is saved.

What additional change is necessary?

  1. Connect the Viewer node to the Composite node so the preview is forwarded to the render result
  2. Connect the Render Layers Image output to the Composite Image input as a second link (correct answer)
  3. Replace the Viewer node with a second Render Layers node assigned to the same view layer
  4. Connect the Render Layers Alpha output to Composite while leaving Image connected only to Viewer
Explanation: Whenever you work in Blender's Compositor, it helps to understand that two nodes serve fundamentally different purposes: the Viewer node displays a preview inside the compositor workspace, while the Composite node defines what actually gets written to the final render result — the image Blender saves when you press F12 or use Image > Save. These two nodes are completely independent pipelines. Plugging your Render Layers Image output into a Viewer node gives you a live preview, but that data never reaches the final output unless you explicitly route it to the Composite node as well. That's why option B is correct: you need a second connection from the Render Layers Image output directly into the Composite node's Image input. Blender allows a single output socket to feed multiple destination nodes simultaneously, so both connections can coexist without conflict. Option A is wrong because there is no way to connect a Viewer node to the Composite node — the Viewer node has no output sockets. It's a terminal node that only receives data. Option C is wrong because duplicating the Render Layers node is unnecessary and redundant; you already have the data available from the original node's output socket. Option D is wrong because splitting Image and Alpha across different destination nodes would send an incomplete signal to the Composite node — you'd lose the color data in the final render — and the Alpha channel alone doesn't constitute a proper render result. A helpful rule of thumb: always ask yourself, "Is this connected to the Composite node?" If not, it won't appear in your final saved render, no matter what the preview shows.