NCP-OUSD Exam Questions & Answers

When a process changes the topology or point count of a mesh, it must also update dependent geometric data whose interpolation depends on the mesh's element counts. OpenUSD primvars are not arbitrary side data; their array sizes and ordering are tied to interpolation mode. For mesh vertex interpolation, the primvar array provides one element for each point, in the same order as the mesh points array. For faceVarying interpolation, the primvar array follows the flattened faceVertexIndices order.

Option B is correct because subdividing or replacing points changes the data contract for non-constant primvars such as display color, UVs, normals, or other interpolated values. The process authoring the stronger points opinion must ensure that related primvars remain valid for the resulting geometry. Option A is incorrect because points is an attribute and can be overridden by stronger opinions; render-time subdivision through subdivisionScheme is a separate mechanism. Option C is incorrect because USD composition does not automatically resize or reinterpret primvar arrays to match newly authored points. This aligns with Data Modeling Meshes, Points, Primvars, Interpolation, Topology, and Geometry Validity.

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.

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.

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.

OpenUSD's plugin architecture is a major customization mechanism. Option A is correct because NVIDIA's Learn OpenUSD Data Exchange material states that file format plugins allow OpenUSD to compose with additional file formats and non-file-based sources, translating the source format on the fly as a USD layer. It also notes that file format plugins may be bidirectional, supporting both reading and writing. (docs.nvidia.com)

Option B is also correct because custom plugins can extend OpenUSD beyond built-in behavior. NVIDIA's OpenUSD plugin samples include schemas, both codeful and codeless, file format plugins, dynamic payloads, and Hydra scene indices, demonstrating plugin-based extension of data models and runtime behavior. (github.com)

Option C is not the best general statement for OpenUSD development certification in this context. Some tooling-level plugin systems can use Python, but core extensibility such as schema libraries and file format plugins commonly depends on plugin metadata and compiled libraries or generated schema artifacts. Option D is false because plugins are discovered through plugin registration metadata, such as plugInfo.json, and do not require recompiling USD itself. This aligns with Customizing USD Plugins, Schemas, File Format Plugins, plugInfo.json, and Extensibility.