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 .