NCP-OUSD Exam Preparation Material | NVIDIA-Certified Professional: OpenUSD Development (NCP-OUSD)

Explanation:
The missing chassis is caused by an unresolved reference target. In parkingLot.usda, the reference is authored as @cars.usda@ without a target prim path. When a reference omits the target prim path, USD uses the referenced layer’s defaultPrim as the entry point. NVIDIA’s Learn OpenUSD guide states that if no defaultPrim is set, bringing that layer in as a reference or payload resolves as an empty layer and emits a warning. It also identifies defaultPrim as layer metadata and a best practice for stages intended to be referenced or payloaded.
Option A fixes the issue by setting, for example, defaultPrim = "redCar" in cars.usda, allowing @cars.usda@ to resolve to /redCar and bring in its chassis.
Option C also fixes it by making the reference explicit, for example references = @cars.usda@</redCar>. NVIDIA’s data-transformation guidance similarly notes that without defaultPrim, a stage cannot be referenced without specifying a target prim.
Option B does not solve reference resolution; assigning a type to car01 would not identify which car to compose.
Option D changes model-kind semantics only and does not affect the reference target. This aligns with Composition → Reference, Default Prim, Target Prim Paths, and Asset Entry Points.

Explanation:
Variant sets enhance flexibility by allowing a prim to expose named alternatives, where one variant selection contributes its authored opinions to the composed result. NVIDIA’s Learn OpenUSD material describes variant sets as a way to define “alternative representations for a prim and switch between them without duplicating data.” It also explains that a prim may have one or more named variant sets, each containing variant choices, and that the selected variant composes the opinions authored for that choice.
Option A is correct because variant sets support selectable alternatives such as different model shapes, material looks, levels of detail, configurations, or composition arcs. This gives downstream tools or stronger layers the ability to choose a representation non-destructively without rewriting the asset.
Option B is inaccurate because variants are not permanently merged into the prim; only the selected variant participates in the composed scene.
Option C is incorrect because conflict resolution is handled by USD’s composition and value-resolution rules, not automatically by variant sets themselves.
Option D is also incorrect because USD does not statically combine every variant into a single representation. This aligns with the NVIDIA OpenUSD Development Study Guide topics Composition → Variant Sets, Composition Arcs, and LIVERPS strength ordering.

Explanation:
The issue is caused by an invalid scenegraph structure: a Cube gprim is nested below a Sphere gprim. OpenUSD considers nesting gprims under other gprims invalid, and usdchecker warns on this construct because important USD features such as activation and visibility are hierarchical and pruning. The OpenUSD glossary states that when an ancestor gprim is deactivated or made invisible, there should be no way for a descendant gprim to remain active or visible. (openusd.org)
Option B is correct because the authored hierarchy violates the expected gprim organization. The correct structure is to place geometry prims under transform or organizational prims, such as Xform or Scope, rather than directly under other gprims.
Option A is incorrect because USD visibility is not purely explicit per prim. NVIDIA’s Omniverse visibility guide states that setting a prim’s visibility to invisible makes the prim and all children invisible. (docs.omniverse.nvidia.com)
Option C is also incorrect because setting the Sphere invisible should hierarchically affect descendants in a valid hierarchy. This aligns with Visualization → Visibility, Imageable Prims, Gprim Structure, and Valid Scenegraph Organization.

Explanation:
Custom attributes in OpenUSD are user-defined properties authored on prims to store additional typed data beyond predefined schema attributes. NVIDIA’s Learn OpenUSD material states that custom attributes can hold “numeric values, strings, or arrays,” and that custom attributes are created with UsdPrim::CreateAttribute(), where Sdf.ValueTypeNames represents the attribute type. NVIDIA’s OpenUSD data type reference lists Asset with the USDA value type token asset, and StringArray with the USDA token string[], making asset paths and string arrays valid attribute value types.
Option B is correct because asset path values are represented through the asset value type and are commonly used for resource references such as textures or external asset identifiers.
Option C is correct because string[] is a valid array value type.
Option A is incorrect because USD does not have a native struct attribute type; NVIDIA recommends namespace-prefixed attributes for mapping grouped or compound fields.
Option D is incorrect in this context because dictionaries are associated with metadata/customData patterns, not ordinary typed custom attributes. This aligns with Customizing USD → Custom Properties, Sdf.ValueTypeNames, Namespaced Attributes.

Explanation:
API schemas and typed schemas serve different modeling roles in OpenUSD. NVIDIA’s Learn OpenUSD schema guidance states that Is A, or typed, schemas define what a prim fundamentally is by assigning a typeName, while API schemas define what capabilities a prim has by adding optional properties or behaviors to an already-typed prim. API schemas do not assign a typeName; instead, they are list-edited through the apiSchemas metadata and queried with HasAPI. (docs.nvidia.com)
Option A is correct because API schemas can be applied across different prim types, while a typed schema defines a specific prim type such as Mesh, Camera, or Xform.
Option B is also correct because one prim has a single typed schema identity, but multiple API schemas can be applied to enrich that prim with additional behaviors. NVIDIA further notes that API schemas may be single-apply or multiple-apply, where multiple-apply schemas can be applied more than once to the same prim using different instance names. (docs.nvidia.com)
Option C is incorrect because API schemas can define attributes and relationships.
Option D is incorrect because Python binding policy is not the distinguishing factor between API and typed schemas. This aligns with Customizing USD → Schemas, IsA Schemas, API Schemas, typeName, apiSchemas Metadata.