매달, 우리는 1000명 이상의 사람들이 시험 준비를 잘하고 시험을 잘 통과할 수 있도록 도와줍니다.
NVIDIA-Certified Professional: OpenUSD Development (NCP-OUSD) 온라인 연습
최종 업데이트 시간: 2026년06월04일
당신은 온라인 연습 문제를 통해 NVIDIA NCP-OUSD 시험지식에 대해 자신이 어떻게 알고 있는지 파악한 후 시험 참가 신청 여부를 결정할 수 있다.
시험을 100% 합격하고 시험 준비 시간을 35% 절약하기를 바라며 NCP-OUSD 덤프 (최신 실제 시험 문제)를 사용 선택하여 현재 최신 236개의 시험 문제와 답을 포함하십시오.
정답:
Explanation:
A payload is most appropriate when the scene contains heavy assets that should not be fully composed and loaded until needed. NVIDIA’s Learn OpenUSD payload lesson describes payloads as similar to references, but with the added ability to load and unload them on demand. It gives the example of opening a large city scene with all payloads unloaded so the stage loads quickly, then selectively loading only the city block or asset of interest. When loaded, the payloaded layers and their composed dependencies are brought into the scene.
Option B is correct because payloads are designed for deferred loading, scalable working sets, reduced initial load time, and lower memory cost.
Option A describes versioning or asset-resolution policy, not the primary distinction between payloads and references.
Option C does not justify a payload; small inexpensive assets are often fine as references.
Option D describes the opposite of payload behavior, because references are composed immediately, while payload traversal can be deferred. This aligns with Composition → Reference and Payloads, Load/Unload Behavior, Composition Arcs, Scalability, and LIVERPS Strength Ordering.
정답:
Explanation:
The correct method is to use primvars to drive shading variation while preserving instancing. NVIDIA’s Learn OpenUSD scenegraph instance refinement guidance states that prototypes are runtime data and are not editable, instance proxies are not editable, and local opinions on instance proxies are discarded. It then identifies hierarchical refinement as the appropriate strategy for non-destructive instance variation, including inherited primvars. Primvars can drive material properties such as color, inherit down the prim hierarchy, and be authored on the instanceable prim or an ancestor so materials inside the instance subgraph can read the inherited value.
Option B is correct because it changes the effective appearance without directly editing the instance proxy mesh and without disabling instancing.
Option A is incorrect because directly modifying an instance proxy’s geometry properties is not allowed.
Option C is incorrect because a relationship targeting a color attribute is not the standard mechanism for material color variation.
Option D is incorrect because replacing the mesh defeats the purpose of preserving the instanced asset structure. This aligns with Content Aggregation → Asset Modularity and Instancing → Refining Scenegraph Instances, Hierarchical Refinement, Primvars, and Instance Editability.
정답:
Explanation:
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.
정답:
Explanation:
ETL is useful for USD data exchange because it separates the problem into disciplined phases instead of forcing extraction, interpretation, optimization, and client-specific restructuring into one converter step. NVIDIA’s Learn OpenUSD data exchange guidance describes a two-phase approach, extract and transform, inspired by ETL. The extract phase should translate source data to OpenUSD as directly as possible, mapping source concepts to USD concepts to preserve the integrity and structure of the original data. The transform phase then applies optional changes such as user export options, content-structure changes, and optimizations for workflow or client performance.
Option B is correct because this separation of concerns makes converters easier to maintain, test, and adapt.
Option D is correct because the pattern preserves source fidelity first, then permits controlled tailoring for specific downstream needs.
Option A is incorrect because NVIDIA explicitly notes that data exchange is typically lossy and not every data model maps directly.
Option C is
incorrect because the guide states there is no single content structure suitable for every organization or workflow. This aligns with Data Exchange → Two-Phase Data Exchange, Data Extraction, Data Transformation, Export Options, and Pipeline Adaptability.
정답:
Explanation:
The sphere is not visible because the prim wall_a_inst is marked instanceable = true and also has a variant set, which is a composition arc. NVIDIA’s Learn OpenUSD instancing module states that “Instancing is driven by your composition arcs,” and explains that instanceable prims generate implicit prototypes from composed scenegraph content provided through those arcs. It also states that variant sets participate in composition and that variant selections are evaluated when OpenUSD determines which implicit prototypes to create.
In this layer, the Sphere is authored as a local child of the instanceable prim, but it is outside the selected "Emissive" variant. Since the selected variants "Default" and "Daytime" contain no sphere definition, the composed prototype for the instance contains no visible sphere. This is an instancing/composition issue, not a visibility-purpose issue and not a material-binding issue. Option
A is incorrect because the USDA does not mark the sphere as guide geometry.
Option B is incorrect because missing materials would not remove the sphere from the scenegraph.
Option C correctly identifies that local child opinions outside the relevant composition arc are not contributing to the instanced scenegraph. This aligns with Content Aggregation → Asset Modularity and Instancing → Scenegraph Instancing, Variant Set Refinement, and Composition Arcs.
정답:
Explanation:
The valid model kind hierarchies are A, B, and E. NVIDIA’s Learn OpenUSD material defines group, assembly, and component as model kinds, while subcomponent is explicitly outside the model hierarchy. The hierarchy rule is that all ancestors of a component must be group or a subkind of group, such as assembly, and a component acts as a leaf or pruning point in the model hierarchy; therefore, it cannot contain descendant model kinds such as another component, group, or assembly. (NVIDIA Docs)
A is valid because CarA is a component and every descendant has unset kind, so no nested model violates the component boundary.
B is valid because CarA is an assembly, organizational containers use group, and the leaf model assets are component prims. E is valid because CarA is a component, and internal important parts are marked as subcomponent, which is permitted inside a component and does not count as a model kind.
C is invalid because a component contains descendant component prims.
D is invalid because Wheels (group) appears under a component, placing a model kind below a component boundary. This aligns with Content Aggregation → Asset Structure → Model Hierarchy → Model Kinds.
정답:
Explanation:
The key distinction is that an IsA schema, also called a typed schema, defines the fundamental type of a prim through its typeName metadata. NVIDIA’s Learn OpenUSD glossary states that IsA schemas define a prim’s fundamental type through typeName, and that each prim has only one IsA schema determining its core nature, such as Mesh, Camera, or Light. NVIDIA’s schemas lesson also states that, unlike IsA schemas, API schemas do not assign a typeName; instead, they are list-edited in the apiSchemas metadata and queried using HasAPI. (NVIDIA Docs)
Option A is correct because it directly identifies the defining capability of an IsA schema: imparting a prim type. API schemas instead augment already-typed prims with additional properties or behavior.
Option B is incorrect because both IsA and API schemas may define attributes and relationships.
Option C is incorrect because IsA schemas are not always concrete; for example, OpenUSD includes abstract typed schemas such as imageable base classes, while concrete typed schemas are instantiable prim types. This aligns with Customizing USD → Schemas, IsA Schemas, API Schemas, Schema Registry, typeName, and apiSchemas Metadata.
정답:
Explanation:
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.
정답:
Explanation:
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.
정답:
Explanation:
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.
정답:
Explanation:
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.
정답:
Explanation:
UsdGeomSubset is used to identify subsets of a geometric primitive, most commonly groups of mesh faces, so that those groups can receive independent material bindings or other subset-level organization. The OpenUSD API states that materials are bound to GeomSubsets using the same UsdShade material-binding mechanisms used for regular geometry. It also states that a GeomSubset must be a direct child of the geometric prim it applies to, making discovery efficient and clearly scoped to that geometry.
Option A is correct because a single mesh can be partitioned into face groups, and each subset can be assigned a different material.
Option B is incorrect because UsdGeomSubset is not a UsdGeomImageable; therefore, imageable properties such as visibility or purpose cannot be authored on it.
Option C is incorrect because subsets classify elements; they do not force tessellation or modify mesh topology.
Option D is incorrect because subsets are authored below the relevant geometric primitive, not at the root stage level. This aligns with Data Modeling → Geometry Organization, Mesh Face Subsets, UsdGeomSubset, and UsdShade Material Binding.
정답:
Explanation:
An edit target determines where authored opinions are written while working through the composed view of a stage. NVIDIA’s Learn OpenUSD stage material emphasizes that a stage is not simply a file; it is a unified scenegraph populated from multiple data sources called layers. (docs.nvidia.com) In that layered environment, a developer often edits a composed prim while needing the resulting opinion to land in a specific contributing layer, variant, or composition context.
OpenUSD defines this role through UsdEditTarget: edit targets allow work on the composed stage and its UsdPrim objects while specifying which contributing site in the composition network should receive the authored opinions. (openusd.org)
Option C is correct because the edit target is the authoring destination, not a composition override mechanism.
Option A is incorrect because USD does not automatically merge edits into all layers.
Option B is incorrect because edits are not forced to the root layer; developers can target other valid layers or edit contexts.
Option D is incorrect because setting an edit target does not disable sublayers or composition arcs. This aligns with Pipeline Development → Layer Authoring, Edit Targets, Non-Destructive Editing, Stage Workflows, and Collaborative Layer Stacks.
정답:
Explanation:
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.
정답:
Explanation:
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.