NVIDIA NCP-OUSD Practice Exam Questions & Answers

UsdGeomSubset is used to identify subsets of a geometric primitive, most commonly groups of mesh faces, so that those groups can receive independent material bindings or other subset-level organization. The OpenUSD API states that materials are bound to GeomSubsets using the same UsdShade material-binding mechanisms used for regular geometry. It also states that a GeomSubset must be a direct child of the geometric prim it applies to, making discovery efficient and clearly scoped to that geometry.

Option A is correct because a single mesh can be partitioned into face groups, and each subset can be assigned a different material. Option B is incorrect because UsdGeomSubset is not a UsdGeomImageable; therefore, imageable properties such as visibility or purpose cannot be authored on it. Option C is incorrect because subsets classify elements; they do not force tessellation or modify mesh topology. Option D is incorrect because subsets are authored below the relevant geometric primitive, not at the root stage level. This aligns with Data Modeling Geometry Organization, Mesh Face Subsets, UsdGeomSubset, and UsdShade Material Binding.

The most essential composition arc for components in a model hierarchy is the payload. NVIDIA's Learn OpenUSD glossary describes payloads as composition arcs similar to references, but with deferred loading for scalability, and specifically notes that payloads are typically added to component asset root prims for efficient scalable composition. (docs.nvidia.com)

Option A is correct because component models act as the leaf or pruning boundary of the model hierarchy. NVIDIA's model-kind guidance explains that the model hierarchy is designed to prune traversal at the component boundary, and that component models cannot contain other component models as descendants. (docs.nvidia.com) Payloads reinforce that design by allowing large component contents to remain unloaded until needed, improving stage-opening performance and enabling scalable aggregation of large scenes.

Option B is incorrect because inherits are mainly for reusable class-style opinions. Option C is useful for alternatives such as LODs or looks, but it is not the essential component-loading mechanism. Option D is a weaker composition mechanism used for specialization and fallback-style refinement. This aligns with Content Aggregation Asset Structure, Model Hierarchy, Components, Payloads, and Scalable Scene Assembly.

The most plausible cause is that the two environments are resolving asset identifiers differently. NVIDIA's Learn OpenUSD glossary defines asset resolution as the process of translating an asset path into the actual location of a consumable resource, and identifies ArResolver as the plugin point that can be customized to resolve assets through site logic, databases, or version-control systems.

Option C is correct because the same authored USD layer can contain references, payloads, textures, or other asset-valued paths that are resolved at runtime. If one user's resolver context maps @character.usd@ to version 12 while another maps it to version 15, or if one environment cannot resolve a dependency at all, the composed stage can differ. This can manifest as missing geometry, stale geometry, missing materials, or unresolved payloads. Reference and payloads are composition arcs that bring external scene description into the stage, so resolution differences directly affect what data is available for composition.

Option A is incorrect because USD does not change composition semantics based on available memory. Option B is not the primary explanation here; instance prototypes are derived from composed instance data, but the root problem described is inconsistent asset resolution. This aligns with Debugging and Troubleshooting Asset Resolution, Reference, Payloads, Resolver Contexts, Missing Dependencies.

The correct UsdLux light type is DistantLight. NVIDIA's Learn OpenUSD lighting guide identifies UsdLux.DistantLight as a schema where light is emitted from a distant source along the negative Z axis, commonly known as a directional light. This makes it the most appropriate light type for representing sunlight in an outdoor scene.

Option C is correct because sunlight is effectively modeled as coming from an extremely distant source, so its rays are treated as broadly parallel across the scene. The OpenUSD DistantLight schema documentation explicitly describes it as typically used for distant, broad light sources like sunlight, where rays affect the entire scene and are roughly parallel. It also notes that the inputs:angle attribute controls angular diameter; the fallback value approximates the Sun's apparent angular size from Earth.

Option A, RectLight, is better suited for rectangular area emitters such as panels or windows. Option B, DomeLight, is commonly used for environment or HDRI lighting. Option D, SphereLight, represents local emission from a spherical source, such as a bulb. This aligns with Visualization UsdLux, Lighting Schemas, DistantLight, Directional Lighting, and Outdoor Illumination.

A conceptual data mapping document primarily records how concepts and data from a source format map into OpenUSD concepts, schemas, prims, properties, and authored scene description. NVIDIA's Learn OpenUSD Data Extraction lesson states that producing such a document is valuable because it serves as a data specification for extraction implementation, helps stakeholders set requirements and expectations, and helps developers understand which features are supported between two formats and what to expect from the extraction phase. (docs.nvidia.com)

Option D is correct because the document is specifically about translation between OpenUSD and another data representation, such as a DCC format, interchange format, or custom application model. Option A is broader than the purpose of the document; an end-to-end workflow specification may include tools, review, publishing, validation, and delivery, while conceptual mapping focuses on data correspondence. Option B is also too narrow because content structure is only one possible mapped concept. Option C is incorrect because storage requirements are not the core concern. This aligns with Data Exchange Data Extraction, Conceptual Data Mapping, Format Translation, and Converter Design.

An opinion may not appear in the final composed stage because USD resolves competing opinions according to composition strength. NVIDIA's Learn OpenUSD material explains that a layer stack is the ordered set of a layer and its recursively gathered sublayers, with the root layer considered strongest, followed by sublayers according to their composed order. It also states that strength ordering determines which opinion is composed into the final stage when multiple layer stacks or layers contribute data for the same prim or property. (docs.nvidia.com)

Option D is correct because a weaker layer can author a valid opinion, but that opinion can be hidden by a stronger authored opinion on the same target. Option A is incorrect because sublayers do not need to be referenced by every other layer to affect a stage. Option B is incorrect because there is no general ''weaker keyword'' that lowers priority. Option C is incorrect because opinions from sublayers, references, payloads, variants, inherits, and specializes can all contribute to composition. This aligns with Composition Sublayers, Layer Stacks, Opinion Strength, and LIVERPS Strength Ordering.

Flattening a stage resolves the composed result into a single merged layer, baking the effects of composition into authored scene description. The critical loss here is variant-set structure. OpenUSD's UsdStage::Flatten() documentation states that flattening removes most composition metadata and that ''all VariantSets are removed and only the currently selected variants will be present in the resulting layer.'' This means the flattened output preserves the currently selected representation, but the ability to switch among alternate variants is lost.

Option C is therefore correct. Option A is not the best answer because flattening authors resolved values and can preserve relevant composed metadata, although composition metadata is removed. Option B is incorrect because modern OpenUSD flattening preserves native scenegraph instancing by flattening prototypes and adding internal references from instances to their corresponding prototypes. Option D is incorrect because class prims still exist after flattening, although inherit arcs are removed and inherited data is copied onto consuming prims. This aligns with Composition Flattening, Variant Sets, Composition Metadata, Inherits, and Scenegraph Instancing.