What will be the composed value of /World/Tree/Canopy.primvars:displayColor when you open stage.usda?
#usda 1.0
(
defaultPrim = "World"
metersPerUnit = 1.0
upAxis = "Z"
)
def Xform "World"
{
def Xform "Tree" (
variantSets = ["foliage_color"]
variants = { string foliage_color = "default" }
)
{
def Cone "Canopy" (
references = [ < /_base_foliage_color > ]
)
{
double3 xformOp:translate = (0, 0, 1.3)
token[] xformOpOrder = ["xformOp:translate"]
}
def Cylinder "Trunk"
{
color3f[] primvars:displayColor = [(0.2, 0.1, 0.05)]
double3 xformOp:scale = (0.4, 0.4, 0.4)
token[] xformOpOrder = ["xformOp:scale"]
}
variantSet "foliage_color" = {
"default" {
}
"evergreen" {
over "Canopy"
{
color3f[] primvars:displayColor = [(0.05, 0.15, 0.05)]
}
}
"orange" {
over "Canopy"
{
color3f[] primvars:displayColor = [(0.5, 0.3, 0.05)]
}
}
}
}
}
class "_base_foliage_color"
{
color3f[] primvars:displayColor = [(0.2, 0.75, 0.1)]
}

• A. [(0.2, 0.75, 0.1)]
• B. [(0.5, 0.3, 0.05)]
• C. unset
• D. [(0.05, 0.15, 0.05)]

Consider a USD that has a root Xform, that has a child Sphere, that in turn has a child Cube.
Xform
- Sphere
-- Cube
When you open the USD, you see the sphere and the cube. But when you author the Sphere to be invisible, the sphere disappears, but the Cube is still visible.
What could be causing this behavior?

• A. Visibility is hierarchical in OpenUSD, so the root Xform must be made invisible in order for all of its descendants to be invisible.
• B. Nested gprims are illegal in OpenUSD, and their imaging behavior is undefined.
• C. Visibility is explicit in OpenUSD, so the Cube must be explicitly authored as invisible.

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?

• A. upAxis
• B. kilogramsPerUnit
• C. metersPerUnit
• D. timeCodesPerSecond

Which of the following statements best describes the purpose of OpenUSD file format plugins?

• A. They are designed to compress OpenUSD asset files for faster loading times.
• B. They convert OpenUSD files to other formats without any loss of data or information.
• C. They extend OpenUSD's functionality by allowing it to read and write from various file formats.
• D. They are only used for visualizing OpenUSD data and geometry in 3D applications.