What should be avoided when using computational workstreams?

• A.Hybrid workflows
• B.Dynamically growing layer stacks over time
• C.Using sublayers for data combination
• D.Using primvars

Comment: *

Name: *

Email: *

Verification: *

Which statement best captures a key benefit of strict encapsulation across projects?

• A.Safe reuse of assets without broken dependencies
• B.Automatic variant generation for materials
• C.Forced real-time playback
• D.Elimination of the need for default prims

Comment: *

Name: *

Email: *

Verification: *

Why use sublayers in large scenes?

• A.To allow parallel work on separate aspects like lighting and geometry
• B.To enforce destructive edits
• C.To reduce rendering quality
• D.To automatically delete old prims

Comment: *

Name: *

Email: *

Verification: *

What is a practical advantage of using references for workflows?

• A.References reduce rendering resolution
• B.References are stronger than local edits
• C.References erase encapsulation
• D.The same asset can be reused modularly without duplication of data

Comment: *

Name: *

Email: *

Verification: *

Referring to dining_room.usda, which of the following best describes the role of the references composition arc on the /Root/Chair prim?
#usda 1.0
def Xform "Root"
{
def Xform "Chair" (
references = @chair.usda@
)
{
float3 xformOp:scale = (1.5, 1.5, 1.5)
}
}

• A.It creates a bidirectional link between the local /Root/chair prim and chair.usda so that any changes in one are automatically reflected in the other.
• B.It is used to import variant sets from chair.usda into the local /Root/chair prim.
• C.It completely replaces the local /Root/chair prim with the contents of chair.usda, ignoring any local attribute definitions such as scale.
• D.It composes the definition from chair.usda with the local /Root/Chair. The local xformOp:scale overrides corresponding referenced opinions.

Comment: *

Name: *

Email: *

Verification: *