NVIDIA-Certified Professional: OpenUSD Development (NCP-OUSD) - NCP-OUSD Exam Practice Test

Why is extract, transform, load (ETL) a useful design pattern for USD data exchange? Choose two.

Why is a well-designed model kind hierarchy important for an efficient pipeline?

If you have a Usd.Prim object named my_prim and you want to specifically retrieve an attribute named
"size", which method would you typically use?

Consider the following HelloWorld.usda OpenUSD layer:
#usda 1.0
(
defaultPrim = "hello"
)
def Xform "hello"
{
double3 xformOp:translate = (4, 5, 6)
uniform token[] xformOpOrder = ["xformOp:translate"]
def Sphere "world"
{
float3[] extent = [(-2, -2, -2), (2, 2, 2)]
color3f[] primvars:displayColor = [(0, 0, 1)]
double radius = 2
}
}
What would be the output of the following Python snippet?
from pxr import Usd
refStage = Usd.Stage.CreateInMemory()
refSphere = refStage.OverridePrim("/refSphere")
refSphere.GetReferences().AddReference("./HelloWorld.usda")
print(refStage.GetRootLayer().ExportToString())

What is the correct prim type in UsdShade for sharing reusable portions of shading networks, allowing for parameterization?

Which of these is a viable approach for mapping or grouping compound types from other data sources to OpenUSD?

In OpenUSD, a composed stage aggregates opinions from multiple sublayers. Why might an opinion in one layer not take effect in the final composed stage?

Why would you not see a sphere when opening this scene?
#usda 1.0
(
defaultPrim = "wall_a_inst"
upAxis = "Z"
)
def Xform "wall_a_inst" (
instanceable = true
variants = {
string Emissive = "Default"
}
prepend variantSets = "Emissive"
)
{
def Sphere "Sphere"
{
}
variantSet "Emissive" = {
"Daytime" {
}
"Default" {
}
}
}