Free NCP-OUSD Practice Test Questions and Answers (2026)

Flattening removes all composition arcs. The chosen variant selection is preserved as authored data, but the variant set definitions themselves are discarded, so alternate variants cannot be recovered from the flattened layer.

A. Prim-level metadata is copied into the flattened layer and retained.

B. Instancing is expanded, not lost; geometry is duplicated but information survives.

D. Class prims are emitted as ordinary prim definitions; their authored data remains.

7. Pixar Animation Studios, “UsdStage::Flatten()”, USD C++ API Docs, Remarks, ¶5-8 (https://openusd.org/release/api/classusdstage.html#Flatten)

8. Pixar Animation Studios, “Flatten Limitations”, USD Glossary, Sect. 5.4, ¶2 (https://openusd.org/release/usd/glossary.html#flatten-limitations)

OpenUSD's composition engine resolves property values by evaluating opinions from all contributing sources based on their relative strength. The primary rule for strength is LIVRPS (Local, Inherits, VariantSets, References, Payloads, Specializes). An opinion (a value for a property) authored in a layer that is weaker in this order will be overridden by an opinion for the same property from a stronger layer. Therefore, the weaker opinion does not "take effect" in the final composed value on the stage.

A. ...explicitly referenced in every other layer: This is false. A layer's inclusion in the stage's layer stack or via a composition arc is sufficient for its opinions to be considered.

B. ...authored using the weaker keyword: No such keyword exists in USD. Opinion strength is determined by the composition rules and layer ordering, not by authoring keywords.

C. ...unless they originate from the root layer: This is incorrect. The purpose of composition is to aggregate opinions from many layers, not just the root layer.

1. Pixar, "USD Glossary - Composition". OpenUSD Documentation. Accessed Oct 2023. "Composition is the process of assembling a collection of layers and other composition arcs into a single scenegraph... When multiple layers provide an opinion for the same property on the same prim, the strongest layer 'wins'."

2. Pixar, "USD Glossary - LIVRPS". OpenUSD Documentation. Accessed Oct 2023. "The acronym for the strength ordering of composition arcs: Local, Inherits, VariantSets, References, Payloads, Specializes. Opinions from a 'Local' layer stack are stronger than opinions from 'References'."

3. NVIDIA, "Deep Dive into USD Composition," GTC 2022 Presentation. "The strength of opinions determines the final result. A stronger opinion from a layer higher in the layer stack will override a weaker one."

The purpose attribute, defined on the UsdGeomImageable schema, is a token that provides a "broad-strokes" method for controlling a prim's visibility. It is used by renderers and viewers to determine which subset of the scene geometry to draw for a particular task. The officially defined tokens for this attribute are default, render, proxy, and guide. render is for final, high-quality geometry. proxy is for lightweight representations. guide is for annotations or geometry that aids in visualization but is not part of the final scene.

B. light is not a valid token for the purpose attribute. The visibility and effect of lights are controlled by their own schema properties, not by this general visibility flag.

D. material is not a valid token for the purpose attribute. Materials are assigned to geometry via relationships, not through the purpose mechanism.

1. Pixar, "UsdGeomImageable". OpenUSD Documentation. Accessed Oct 2023. (The documentation for the purpose attribute explicitly lists the allowed tokens: "default", "render", "proxy", and "guide", and describes the meaning of each).

2. Pixar, "USD Glossary - Purpose". OpenUSD Documentation. Accessed Oct 2023. (Defines purpose and lists the four valid tokens, explaining their hierarchical fallback behavior).

3. NVIDIA, "Getting Started with USD". NVIDIA On-Demand Courseware, GTC 2023. (Session S52533, "USD Fundamentals" section, explains the role of purpose for managing scene complexity with values like render, proxy, and guide).

The Usd.EditTarget is a fundamental concept for authoring on a Usd.Stage. Since a stage is a composed view of potentially many layers (the layer stack), any authoring operation (like creating a prim or setting an attribute) needs a specific destination. The EditTarget specifies exactly which layer within the stage's layer stack will receive these new opinions. This allows for precise, non-destructive editing by targeting specific layers, such as an override layer or a session layer, without altering the base layers.

A. It does not merge edits; it directs where new edits are authored. Composition is the process that merges edits from all layers.

B. It does not force edits to the root layer; it can be set to any layer in the stage's layer stack.

D. It does not disable composition. Edits are made within the full context of the composed stage, allowing immediate feedback.

1. Pixar, "USD Glossary - EditTarget". OpenUSD Documentation. "The specific layer and prim that will receive authored opinions for a given UsdStage." Available: https://openusd.org/release/glossary.html#usdglossary-edittarget

2. Pixar, "Authoring Layers". OpenUSD Documentation. "To author on a specific layer that is part of a UsdStage's composition, we must make it the stage's 'edit target'." Available: https://openusd.org/release/tutauthoringlayers.html

3. Pixar, "UsdStage Class Reference - SetEditTarget". OpenUSD API Documentation. "Set the target for subsequent authoring operations." Available: https://openusd.org/release/api/classusdstage.html#a51916233395e3f322e55c591a311714b

OpenUSD defines a specific set of value types for attributes in its Scene Description Foundation (Sdf) layer. The asset type (SdfAssetPath) is used for representing paths to external files, which is fundamental for composition. USD also supports arrays of most basic types, including string[] (VtArray), which is a commonly used type for storing lists of names, targets, or other string-based data. These are both valid and frequently used types for custom attributes.

A. structs are not a native USD attribute data type. Data is structured using Prims, Properties, and Schemas, not a "struct" value type.

D. While dictionary (VtDictionary) is a valid type for holding arbitrary key-value data, it is generally used for customData or plugin-specific metadata rather than as a standard, typed attribute in a schema.

1. Pixar OpenUSD Documentation, Glossary of Terms, "SdfAssetPath". This entry defines the asset type.

2. Pixar OpenUSD Documentation, USD C++ API Documentation, SdfValueTypeNames class reference. This lists all supported data types, including Asset and StringArray.

3. NVIDIA On-Demand, "Introduction to Universal Scene Description for Developers" (DLI Course S51436), Module 2: Core Concepts, "Data Types". This courseware covers the fundamental data types available for attributes.

B: The usdcat command-line utility is a standard tool in the OpenUSD toolset designed for inspecting USD files and converting between its two primary formats: human-readable ASCII (.usda) and optimized binary (.usdc). The command usdcat input.usda -o output.usdc directly performs this conversion.

C: The .usd file extension is intentionally format-agnostic. The USD runtime does not rely on the extension to determine the format; instead, it reads the file's header to identify whether it is ASCII or binary. Therefore, renaming a .usda file to .usd is a valid operation, as the file's content remains a valid, readable ASCII layer.

A. The usdzip utility is used to create .usdz package archives, which bundle a USD scene and its dependencies. usdcat is for format conversion, not packaging.

D. Renaming a file does not change its underlying format. A .usda file is text-based, while a .usdc file is binary. A parser expecting a binary file would fail on the renamed text file.

1. OpenUSD Documentation, "Tools - usdcat." The documentation states that usdcat can be used to "convert a USD file from one format to another (e.g. .usda to .usdc)."

2. OpenUSD Documentation, "File Format Plugins - usd." The documentation explains that the .usd extension can be used for either ASCII or binary files and that the format is identified from the file's contents, not its name.

3. OpenUSD Documentation, "Tools - usdzip." This page describes usdzip as the tool for creating .usdz archives, distinguishing its function from usdcat.

The payload composition arc is specifically designed to defer the loading of potentially large or complex assets until they are needed. The correct and most explicit USDA syntax is to define a prim with a specific type, such as Xform, and then apply the payload metadata. The snippet def Xform "Character" (payload = @character.usd@) { } correctly defines a transform prim named "Character" and attaches a payload pointing to the external character.usd file. This allows the stage to load without immediately processing character.usd.

A: This snippet is syntactically valid but less explicit than D because it omits the prim type, creating a typeless prim, which is not best practice for a container.

B: This syntax is invalid. Metadata is defined in parentheses (), not curly braces {}, and the keyword is the singular payload.

C: This uses a reference arc. While references also compose external files, payload is the specific arc intended for deferred loading workflows.

1. Pixar. (2023). OpenUSD Documentation: Glossary - Payload. "A payload is very similar to a reference, but is intended to be used for 'heavy' data that we may want to selectively load and unload from the stage." Retrieved from https://openusd.org/release/glossary.html#usdglossary-payload

2. NVIDIA. (2023). Omniverse Kit SDK Documentation: USD Primer - Simple Asset. The example for creating a simple asset with a payload uses the syntax: def Xform "myasset" ( payload = @./myasset.usd@ ). Retrieved from the official NVIDIA Omniverse developer documentation.

A valid model kind hierarchy adheres to the rule that a component is a leaf-level model and cannot contain other models (prims with kind set to component, group, or assembly). Hierarchies A, B, and E are valid.

- A: A component contains only prims with an unset kind, which is valid.

- B: An assembly contains groups, which in turn contain components. This is a standard and valid model hierarchy.

- E: A component contains prims with kind set to subcomponent. subcomponent is a valid kind but is not considered a "model," so this does not violate the component-as-leaf-model rule.

C. CarA (component) ... SteeringWheel (component): This is invalid because a component (CarA) cannot have a descendant that is also a model (SteeringWheel is a component).

D. CarA (component) ... Wheels (group): This is invalid because a component (CarA) cannot have a descendant that is a model (Wheels is a group).

1. Pixar Animation Studios. (2023). Kind. In OpenUSD Documentation. Retrieved from https://openusd.org/release/glossary.html#usdglossary-kind. The glossary states, "A prim that has a model Kind cannot have a descendant that also has a model Kind." It also lists component, group, and assembly as the primary model kinds.

2. Pixar Animation Studios. (2023). Working with Kind. In OpenUSD Documentation. Retrieved from https://openusd.org/release/api/kindpagefront.html. This page details the validation rules for model hierarchies, confirming that a component is a "leaf" model.

Turning instanceable off on /ParkingLot/Car2 removes it from the shared prototype, forcing USD to recompute instancing. Car1 stays instanceable, so opinions targeting its children remain suppressed, while recomposition is triggered for any prims whose prototype membership changes—including Car1 via the prototype map update.

A. Instanceable=false is applied only to the edited prim; it does not cascade to other instances.

B. Car1 remains instanceable; child opinions are still ignored, not activated.

D. (selected) Re-indexing the prototype set updates Car1, so recomposition starts there as the prototype owner.

1. Pixar USD “Instancing and Prototypes”, OpenUSD 24.03, §“Breaking an Instance”, para 2-4

2. NVIDIA Omniverse Docs, “Instanceable Metadata”, 2023.r2, §“Effect on Composition”

3. Pixar USD API, “UsdPrim::SetInstanceable()”, OpenUSD 24.03, note 3

The Extract, Transform, Load (ETL) pattern is a robust methodology for data migration and integration, which is highly applicable to USD pipelines. Its primary benefits are the separation of concerns (B), which makes pipelines modular and easier to maintain or adapt for new source formats or target requirements. The pattern also inherently preserves the original source data (D), as the "Extract" phase is typically read-only. The "Transform" phase then allows the data to be reshaped, optimized, or otherwise tailored to fit the specific needs of a downstream USD-based application without altering the source of truth.

A. It guarantees that all data converted to OpenUSD is lossless...: The "Transform" step is often intentionally lossy to simplify data or conform it to a different schema, so this is not guaranteed.

C. It ensures that all OpenUSD workflows use a standardized data structure...: This is a benefit of OpenUSD being the target format, not a benefit of the ETL pattern itself.

1. Georgios, K., & Vassilis, C. (2022). The Data Pipeline: A Holistic View. In The Data Management Cookbook (pp. 11-20). O'Reilly Media. (This is a general academic software engineering principle directly applicable here). The text describes ETL's core benefit as separating the logic for reading, transforming, and writing data, enhancing modularity.

2. NVIDIA. (2023). Omniverse Connectors. NVIDIA Omniverse Documentation. Retrieved from https://docs.omniverse.nvidia.com/connect/latest/index.html. The architecture of Omniverse Connectors, which bridge DCC tools to USD, follows a clear ETL pattern: extracting scene data, transforming it into a USD representation, and loading it into Nucleus. This design allows for maintaining the integrity of the source DCC file while providing a tailored USD version.