You are debugging a complex scene composed of multiple layers.

Usd.Property.GetPropertyStack() is the most appropriate choice because the debugging goal is to determine where a composed property value is coming from. In USD, a final property value can be affected by multiple authored opinions across sublayers, references, payloads, variants, inherits, specializes, and local overrides. NVIDIA’s Learn OpenUSD glossary defines a property stack as the ordered list of property specs that contribute values or metadata for a composed property, and notes that UsdProperty::GetPropertyStack() is specifically useful for debugging, not as the primary value-resolution mechanism. It also explains that USD resolves values by traversing composition information in strength order.

Option C is therefore correct because it exposes the contributing property specs and their layer origins, helping identify why a stronger opinion produced an unexpected result. Option A only traverses prims on the composed stage and does not explain value provenance. Option B reports aggregate stage statistics, not composition-source details. Option D exports the stage or layer contents but does not provide targeted diagnostic ordering for a property. This aligns with Debugging and Troubleshooting → Value Resolution, Property Stack, Composition Debugging, and Layer Opinion Inspection .