Nail the NVIDIA NCP-OUSD: OpenUSD Development Strategy (2026)

Usd.Property.GetPropertyStack() is the most appropriate choice because the debugging goal is to determine where a composed property value is coming from. In USD, a final property value can be affected by multiple authored opinions across sublayers, references, payloads, variants, inherits, specializes, and local overrides. NVIDIA’s Learn OpenUSD glossary defines a property stack as the ordered list of property specs that contribute values or metadata for a composed property, and notes that UsdProperty::GetPropertyStack() is specifically useful for debugging, not as the primary value-resolution mechanism. It also explains that USD resolves values by traversing composition information in strength order.

Option C is therefore correct because it exposes the contributing property specs and their layer origins, helping identify why a stronger opinion produced an unexpected result. Option A only traverses prims on the composed stage and does not explain value provenance. Option B reports aggregate stage statistics, not composition-source details. Option D exports the stage or layer contents but does not provide targeted diagnostic ordering for a property. This aligns with Debugging and Troubleshooting → Value Resolution, Property Stack, Composition Debugging, and Layer Opinion Inspection .

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 .

Strictly evaluated against the OpenUSD API contract, C is the only fully correct statement as written. SdfChangeBlock groups multiple low-level Sdf edits so that change processing can be delayed and handled efficiently as one batch. The official API documentation states that opening a change block causes Sdf to delay notifications until the outermost block exits; notifications are queued, not permanently muted. Therefore, A is incorrect. The same documentation gives a strong warning that it is not safe to use Usd or other downstream APIs while a change block is open, because those representations may be stale or may hold expired handles to Sdf objects. Therefore, querying mutating prims during the block is unsafe, making C correct.

Option B is incorrect because it explicitly says to use USD APIs inside the block, which the official guidance warns against. Option D is also incorrect because the intended safe authoring pattern is to gather required edits first, then apply them directly through the Sdf API inside the change block. This aligns with Pipeline Development → Efficient Authoring, Sdf Layers, SdfChangeBlock, Change Notification, and Bulk Scene Description Mutation .

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 .

A scalable asset structure should be designed around the needs of clients and collaborators and around structural principles such as modularity and performance . NVIDIA’s Learn OpenUSD asset-structure guidance states that a well-designed scalable asset structure should always be tailored to the needs of clients and collaborators. It also emphasizes that collaboration is core to OpenUSD and that scalable structures should support parallel workstreams across multiple dimensions.

Option C is correct because asset structure is not created in isolation; it must serve the downstream consumers, artists, tools, departments, and delivery requirements that will interact with the asset. Option D is correct because NVIDIA identifies the four principles of scalable asset structure as Legibility, Modularity, Performance, and Navigability . Modularity enables reuse and flexible composition, while performance ensures efficient reads, writes, loading, and interaction at production scale.

Option A is too vague and not one of the named primary design aspects. Option B can matter tactically, but file formats and compression are implementation choices, not the primary asset-structure design drivers. This aligns with Content Aggregation → Asset Structure Principles → Clients, Collaborators, Modularity, Performance, and Scalability .

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 .

Namespace-prefixed attributes are the correct approach for representing grouped or compound source data in OpenUSD. NVIDIA’s Learn OpenUSD data extraction guidance states that when source formats contain compound or grouped data types, such as structs, records, or grouped fields, namespace-prefixed attributes provide the convention for grouping related properties together in USD. It also states that USD does not have a native struct type, so namespace-prefixed attributes serve as the standard approach for representing this kind of grouped data.

Option B is correct because attributes such as acme:sensor:temperature, acme:sensor:humidity, and acme:sensor:pressure can express ownership and logical grouping while remaining ordinary USD attributes with valid scalar or array value types. NVIDIA’s custom properties lesson reinforces this pattern, explaining that namespace prefixes logically group related properties on a single prim and are especially useful when mapping structured data types from other formats into USD.

Option A is incomplete because arrays represent repeated values, not named compound fields. Option C is incorrect because USD does not provide a native struct attribute type. This aligns with Data Exchange → Data Extraction, Conceptual Data Mapping, Custom Properties, Namespace-Prefixed Attributes .

OpenUSD file format plugins belong under the Data Exchange topic because they expand how USD participates in interchange workflows. Their purpose is to allow OpenUSD to read, interpret, and in some cases write data using formats beyond the native USD file types such as .usd, .usda, .usdc, and .usdz. Through these plugins, external file formats can be exposed to USD as layers and can participate in composition arcs such as references, payloads, and sublayers. This allows pipelines to integrate heterogeneous asset sources while still using USD’s scene description model, composition engine, and layer-based workflows.

Option A is correct because it directly identifies the function of file format plugins: extending OpenUSD functionality for reading and writing various file formats. Option B is incorrect because visualization is only one possible downstream use of exchanged data, not the purpose of the plugin system. Option C is incorrect because translation between formats does not inherently guarantee lossless preservation of every schema, opinion, or semantic construct. Option D is incorrect because compression is not the primary role of file format plugins. This aligns with the NVIDIA OpenUSD Development Study Guide topic Data Exchange , especially file formats, connectors, and plugin-based interoperability.

A PointInstancer instance position is not computed from the per-instance positions array alone. NVIDIA’s Learn OpenUSD point-instancing lesson explains that authored positions are in the local coordinate space of the PointInstancer. For the final world-space transform, USD combines multiple transforms: first the prototype root transform , then the instance-specific transform components such as scales[i], orientations[i] , and positions[i], and finally the transform authored on the PointInstancer prim itself.

Option B is correct because it includes both additional transform sources that affect the resulting placement: the prototype root’s transform and the PointInstancer prim’s transform. This matters in production asset aggregation because prototypes may carry their own local placement or orientation, while the instancer prim may be moved, rotated, or scaled as a whole. Option A is incomplete because it incorrectly discards the prototype root transform. Option C is incorrect because it treats instance positions as isolated data and ignores the composed transform stack. This aligns with Content Aggregation → Asset Modularity and Instancing → PointInstancer, Prototype Roots, Instance Transforms, and Transform Composition .

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 .