NVIDIA-Certified Professional: OpenUSD Development (NCP-OUSD) (NCP-OUSD) Free Practice Test
Question 1
Consider the following prim hierarchies. Each prim hierarchy is represented by nested unordered lists and each list item represents a prim with the following format: PRIM_NAME (KIND). No text within the parentheses means that the kind is unset for that prim. Only evaluate model kind hierarchy correctness and the structural choices. Which prim hierarchies represent valid model kind hierarchies? Choose three.
Correct Answer: A,C,D
Explanation: Only visible for TestSimulate members. You can sign-up / login (it's free).
Question 2
A key responsibility of the pipeline is to assemble content that may have divergent stage metadata across layer stacks. Which of these metadata is automatically handled by composition when they diverge across layer stacks?
Correct Answer: B
Explanation: Only visible for TestSimulate members. You can sign-up / login (it's free).
Question 3
You are debugging a stage where a prim is expected to have opinions from a referenced asset, but those opinions are not appearing in the composed scene. Which of the following are logical things to check to troubleshoot this issue?
Correct Answer: A,B
Explanation: Only visible for TestSimulate members. You can sign-up / login (it's free).
Question 4
What is the only reliable way in OpenUSD of encoding the motion of primitives whose topology is varying over time?
Correct Answer: C
Explanation: Only visible for TestSimulate members. You can sign-up / login (it's free).
Question 5
Considering the two files cars.usda and parkingLot.usda in the exhibit. When opening a stage with parkingLot.
usda as the root layer, you observed this prim hierarchy:
* ParkingLot
* car01
You expected this:
* ParkingLot
* car01
* chassis
parkingLot.usda:
#usda 1.0
(
upAxis = "Y"
)
def Xform "ParkingLot" (kind = "group")
{
def "car01" (references = @cars.usda@) {}
}
cars.usda:
#usda 1.0
(
upAxis = "Y"
)
def Xform "redCar" (kind = "component")
{
def Mesh "chassis" {}
}
def Xform "blueCar" (kind = "component")
{
def Mesh "chassis" {}
}
What are ways to fix this issue?
usda as the root layer, you observed this prim hierarchy:
* ParkingLot
* car01
You expected this:
* ParkingLot
* car01
* chassis
parkingLot.usda:
#usda 1.0
(
upAxis = "Y"
)
def Xform "ParkingLot" (kind = "group")
{
def "car01" (references = @cars.usda@) {}
}
cars.usda:
#usda 1.0
(
upAxis = "Y"
)
def Xform "redCar" (kind = "component")
{
def Mesh "chassis" {}
}
def Xform "blueCar" (kind = "component")
{
def Mesh "chassis" {}
}
What are ways to fix this issue?
Correct Answer: B,D
Explanation: Only visible for TestSimulate members. You can sign-up / login (it's free).
Question 6
Which of these are valid types for custom attributes in OpenUSD? (Choose two.)
Correct Answer: B,D
Explanation: Only visible for TestSimulate members. You can sign-up / login (it's free).
Question 7
In a complex scene with multiple composition arcs, which of the following could cause unexpected property values? Choose two.
Correct Answer: A,D
Explanation: Only visible for TestSimulate members. You can sign-up / login (it's free).
Question 8
When USD computes the position of a PointInstancer instance, what additional position-related information is used beyond the position information for a given instance?
Correct Answer: A
Explanation: Only visible for TestSimulate members. You can sign-up / login (it's free).