NVIDIA OpenUSD Development NCP-OUSD Exam Questions

Answer : A

The most appropriate combination is VariantSets, Purposes, and AssetResolvers because each feature addresses one of the stated production problems at the correct abstraction level. Variant sets provide artist-facing switches for alternative representations of the same asset, including material variations, geometric variations, and LOD-style alternatives. NVIDIA's Learn OpenUSD guide states that variant sets define alternative representations that can be switched at runtime, and that variants may override properties, define descendant prims, or author composition arcs.

Purposes help separate representation classes such as proxy, render, and guide. NVIDIA's glossary describes purpose as a UsdGeomImageable attribute used to classify geometry into selective visibility categories, allowing clients to include or exclude categories during rendering, bounding, or interactive traversal.

Asset resolvers address asset versioning and storage indirection. NVIDIA's asset-structure guidance specifically recommends keeping instances within a specific version and leveraging storage and asset-resolver capabilities to keep assets atomic.

Option B is more renderer/Hydra-infrastructure focused and does not directly solve artist-facing variation and versioning. Option C contains useful composition and shading tools, but it is not the best combined solution for LODs, material options, and asset versions. This aligns with Pipeline Development Artist Workflows, Variant Sets, Purpose, Asset Resolution, and Asset Versioning.

Answer : A, B

API schemas and typed schemas serve different modeling roles in OpenUSD. NVIDIA's Learn OpenUSD schema guidance states that IsA, 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.

Answer : A

The correct exporter behavior is to generate sparse overrides that represent only the authored contribution of the current workstream. In OpenUSD data exchange workflows, an exporter should not blindly rewrite the full imported asset when the intent is to preserve collaborative, non-destructive editing. Instead, the exporter should author only the changes required to express the current application's contribution: modified prims, newly added prims, changed attributes, relationships, metadata, or other authored opinions.

Option A is correct because an over is specifically used to contribute opinions to an existing prim without redefining the entire prim structure. This allows the exported layer to sit above the source asset in a layer stack and override only the relevant data. Option B incorrectly equates sparsity with splitting each prim into separate referenced layers; USD sparsity is achieved by authoring minimal opinions, not by unnecessary layer fragmentation. Option C is incorrect because exporting full definitions for every prim and property would duplicate unchanged data, reduce clarity, and undermine USD's composition-based collaboration model. This maps to the NVIDIA OpenUSD Development Study Guide topics Data Exchange, especially exporter design, data transformation, sparse authoring, and collaborative layer-based workflows.

Answer : A

The correct troubleshooting path is to verify the prim's kind and whether UsdGeomModelAPI behavior is properly applied. OpenUSD's UsdGeomModelAPI documentation states that draw modes provide alternate imaging behavior for USD subtrees with kind model. The attributes model:drawMode and model:applyDrawMode are resolved to decide whether traversal should stop at a model boundary and replace the subtree with proxy geometry. For bounds, the replacement is the model-space bounding box of the replaced prim. (openusd.org)

Option A is correct because drawMode = 'bounds' is not a generic visibility toggle for arbitrary prims. It is a model-level imaging mechanism. The prim must participate correctly in the model hierarchy, and the relevant UsdGeomModelAPI attributes must be authored or inherited in a way that causes draw mode application. The documentation also notes that component models are automatically treated as if model:applyDrawMode were true unless explicitly disabled. (openusd.org)

Options B, C, and D are unrelated to model draw-mode activation. Physics collision APIs, volume schemas, and material binding APIs can affect simulation, volume representation, or shading, but they do not control whether model draw modes are applied. This aligns with Visualization Model Draw Modes, UsdGeomModelAPI, Kinds, Bounds, and Imaging Substitution.

Answer : A

The correct method is my_prim.GetAttribute('size') because the question asks for a specific attribute, not a relationship or generic property. NVIDIA's Learn OpenUSD material defines properties as the data-bearing namespace objects on prims and distinguishes two property categories: attributes and relationships. Attributes hold typed values, while relationships point to other objects in the scene description. NVIDIA's Omniverse developer reference also states that Usd.Prim.GetAttribute() returns a Usd.Attribute, after which Usd.Attribute.Get() is used to resolve the actual authored or composed value.

Option A is therefore the precise API call. Option B is incorrect because GetRelationship() retrieves relationship properties, not value-bearing attributes. Option C is less specific: GetProperty('size') can retrieve either an attribute or relationship as a generic UsdProperty, requiring additional type handling. Option D is incorrect because primvars are accessed through schema-specific APIs such as UsdGeom.PrimvarsAPI, not directly as a general Usd.Prim method. This aligns with Pipeline Development USD Python API, Property Access, Attributes, Relationships, and Scenegraph Authoring.

Answer : B

A specialize composition arc broadcasts fallback opinions from a source prim to one or more specializing destination prims. NVIDIA's Learn OpenUSD glossary defines specializes as a composition arc that broadcasts fallback values from a source prim and applies only when the specializing prim does not already have its own authored opinion. It further explains that specializes is similar to inherits in its broadcast behavior, but differs because specializes contributes fallback values rather than stronger reusable opinions. (docs.nvidia.com)

Option B is correct because it captures the essential behavior: source specs are supplied as fallback data. Option A is incorrect because specializes is the weakest composition arc in LIVERPS ordering; it does not always win. NVIDIA's strength-ordering guide states that specializes acts as a new fallback value, winning only when stronger composition choices provide no value. (docs.nvidia.com) Option C describes the conceptual naming idea of specialization but not the primary functional mechanism. Option D is incorrect because ''stronger specs'' describes a different strength behavior. This aligns with Composition Inherits and Specializes, Fallback Opinions, LIVERPS Strength Ordering.

Answer : A

Codeless schemas are preferred when the pipeline goal is portability, easy distribution, and reduced application coupling. NVIDIA's Learn OpenUSD schema guidance states that schemas define data models and optional APIs for encoding and interchanging 3D and non-3D concepts, and notes a trend toward codeless schemas for easier distribution, with schemas becoming more focused on data modeling rather than behavior implementation.

Option A is correct because a codeless schema can be distributed as schema data and plugin metadata without requiring every consuming application to compile, link, or ship custom generated C++/Python schema classes. OpenUSD's schema-generation documentation identifies codeless schemas as schemas produced without corresponding C++ classes, where only generatedSchema.usda and plugInfo.json are essential for runtime registration.

Option B is incorrect because strongly typed convenience APIs are the advantage of codeful generated schemas. Option C is incorrect because fallback values are authored in schema definitions. Option D is incorrect because codeful and codeless schemas can both participate in schema registration and value interpretation. This aligns with Customizing USD Schemas, API Schemas, Codeless Schemas, Schema Registry, Data Modeling for Interchange.