A practical mixed-format strategy is to use human-readable USDA for lighter, structural, or non-geometric layers, while using binary USDC for heavier geometry and animation data. NVIDIA's Learn OpenUSD layer guidance identifies .usd, .usda, and .usdc as USD layer formats, where each layer is a modular source of scene description that can participate in composition. ( docs.nvidia.com ) This means a scene can compose different layers with different encodings through sublayers, references, payloads, and other arcs.
Option B is correct because it reflects the common pipeline division: USDA is convenient for inspection, debugging, review, and hand-authored structural opinions, while USDC is better suited for dense numeric data such as meshes, point caches, and time-sampled animation because it is compact and efficient for machine consumption. The official OpenUSD toolset also supports conversion between formats using tools such as usdcat, allowing pipelines to choose the representation that best fits each layer's purpose. ( openusd.
org )
Option A is too rigid; shading data does not require USDC. Option C reverses the usual debugging distinction because USDA is the readable format commonly preferred when inspecting scene text. This aligns with Data Exchange # USD File Formats, Layer Composition, USDA, USDC, and Pipeline File Strategy .

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 .

For an "export as overrides" workflow, the exporter should generate sparse authored opinions that represent only the modified or added contributions of the current workstream. NVIDIA's Learn OpenUSD Data Transformation guidance explicitly describes this pattern: third-party developers can use the stage from raw extraction to export data as sparse overrides for multi-workstream workflows. It also explains that if an export represents one workstream within a larger asset structure, it may define new prims, apply overrides on existing prims, or both, and should distill the data down to the workstream's unique contributions.
Option A is correct because over specs and sparse property opinions preserve USD's non-destructive composition model. They allow a stronger layer to modify the composed result without duplicating unchanged source data. Option B is incorrect because splitting each prim into separate layers is not required for sparsity and would add unnecessary composition complexity. Option C is incorrect because re-exporting the entire imported asset as full definitions would duplicate unchanged data and obscure the actual edits. This aligns with Data Exchange # Data Transformation, Export Options, Sparse Overrides, Round-Trip Exchange, and Multi-Workstream Workflows .

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 UsdShade prim type is NodeGraph. NVIDIA's Learn OpenUSD material introduces UsdShade as the schema family used for creating and binding materials, where materials store renderer-facing shading definitions. The OpenUSD UsdShade specification defines UsdShadeNodeGraph as the mechanism for packaging shading networks into reusable units. A node graph can contain shader nodes and nested node graphs, expose public inputs as an interface, provide outputs, and be referenced into larger networks as a reusable building block.
Option C is correct because NodeGraph is explicitly designed for reusable and parameterized shading- network structure. It allows a pipeline to encapsulate repeated shading logic while exposing only selected parameters to consuming materials or larger graphs. Option A is incorrect because SubNetwork is not the correct UsdShade prim type in OpenUSD. Option B is incorrect because a custom schema could theoretically define new data models, but it is not the standard UsdShade construct for reusable shader-network packaging.
This aligns with Visualization # UsdShade, Materials, Shading Networks, NodeGraph Interfaces, Parameterization, and Reusable Material Components .