NVIDIA OpenUSD Development NCP-OUSD Exam Questions

Answer : C

Option C correctly describes the relationship between interpolation and element counts for mesh normals and normal-like primvars. In UsdGeomMesh, vertex interpolation provides one value per mesh point, while faceVarying interpolation provides one value for each face-vertex, meaning each corner of each face can carry its own value. This distinction is essential for representing smooth normals, hard edges, UV seams, and other discontinuities across faces. OpenUSD's UsdGeomMesh documentation defines vertex interpolation as one element per point and faceVarying interpolation as one element for each face-vertex that defines the mesh topology.

Option A is incorrect because authored normals do not always have to match the number of points; the required count depends on the normals interpolation. Face-varying normals, for example, require one value per face corner rather than one per point. Option B is incorrect because normals should generally not be authored on subdivision meshes; subdivision algorithms define their own normals. OpenUSD notes that authored normals should only be used for polygonal meshes where subdivisionScheme = 'none'.

This aligns with Data Modeling UsdGeomMesh, Normals, Primvar Interpolation, Vertex Data, Face-Varying Data, and Polygonal Mesh Representation.

Answer : A

Variant sets enhance flexibility by allowing a prim to expose named alternatives, where a selected variant contributes its authored opinions into the composed scene. NVIDIA's Learn OpenUSD guide states that variant sets define alternative representations for a prim and allow switching between them without duplicating data. Typical uses include model shapes, looks, materials, and levels of detail. It further explains that a prim can have one or more named variant sets, each containing variant choices, and that the selected variant composes the opinions authored for that variant at the prim where the variant set is defined.

Option A is correct because applications, stronger layers, or session layers can select among alternatives non-destructively. Option B is misleading because variants are not permanently embedded as a single active configuration; only the selected variant participates in composition. Option C is incorrect because conflict resolution is governed by USD composition and value-resolution rules, not by variant sets alone. Option D is incorrect because USD does not merge every possible variant into one representation. This aligns with Composition Variant Sets, Variant Selections, Composition Arcs, and LIVERPS Strength Ordering.

Answer : A

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.

Answer : A, C, E

The visibility opinions that must be updated are on World, Scope, and Cube. In OpenUSD, visibility is hierarchical and pruning. UsdGeomImageable defines the visibility attribute with allowed values inherited and invisible; effective visibility is computed from the most ancestral authored invisible opinion. The OpenUSD API further states that MakeVisible() may need to override ancestor visibility and hide sibling branches to preserve the intended result. (openusd.org)

In the given scene, /World is explicitly invisible, so the entire subtree is invisible regardless of descendants. /World must therefore be changed to visible behavior, typically visibility = 'inherited'. /World/Xform/Scope is also explicitly invisible, so Scope must also be changed to inherited to allow its children to be evaluated as visible. Once those ancestor invisibility opinions are removed, both Sphere and Cube would become visible by inheritance. To make only the sphere visible, the Cube must receive an explicit visibility = 'invisible' opinion. The sphere does not require an authored visibility opinion because it becomes visible through inheritance. This aligns with Visualization UsdGeomImageable, Visibility, Hierarchical Pruning, and Effective Visibility Computation.

Answer : A, C, E

The valid imageable purpose values among the options are guide, render, and proxy. NVIDIA's Learn OpenUSD glossary describes purpose as a UsdGeomImageable attribute used to classify geometry into visibility categories that can gate traversals such as rendering or bounding-box computation. It lists purpose values including default, render, proxy, and guide. (docs.nvidia.com)

Option A is correct because guide is used for guide or helper geometry that should generally appear only when an interactive application has been asked to display guides. Option C is correct because render identifies final-quality render geometry. Option E is correct because proxy identifies lightweight preview or proxy representation. OpenUSD's UsdGeomImageable documentation confirms the allowed values as default, render, proxy, and guide. (openusd.org)

Option B is incorrect because lights are represented through lighting schemas, not as an imageable purpose token. Option D is incorrect because materials and shading assignments are represented through UsdShade schemas and relationships, not through imageable purpose. This maps to Visualization Imageable Purpose, Render/Proxy/Guide Geometry, Hydra Traversal, and Display Filtering.

Answer : B

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.

Answer : D

The key distinction is addressability and representation. Native, or scenegraph, instancing preserves each instance as a prim in the composed scene hierarchy. Each instance root can have its own path, transform, metadata, and root-level refinements while sharing an implicit prototype generated from matching instanceable composition. OpenUSD's scenegraph instancing documentation explains that prims bringing in common scene description through composition arcs can share those composed subgraphs rather than duplicating them per prim.

Point instancing, by contrast, is a vectorized representation. NVIDIA's instancing guide states that point instancing represents repeated instances through array attributes such as positions, orientations, scales, prototype indices, and prototype relationships. It is more compact because it does not require a prim for each instance, but this comes with reduced flexibility and addressability.

Option D is correct because native instances remain individually addressable scenegraph prims, while point instances are addressed through array elements and IDs rather than unique prim paths. A reverses prototype behavior: native instancing uses implicit prototypes, while point instancing uses explicit prototype relationships. B and C impose restrictions that do not exist. This aligns with Content Aggregation Scenegraph Instancing, PointInstancer, Prototypes, Addressability, and Scalable Repetition.