Parks reuses one fountain cycle clip across plazas that must start at different site times. What should they author?
Select an answer to reveal the explanation.
Short Explanation
Same fountain show, different park opening bells—reference once and offset per plaza. Baking unique copies multiplies maintenance; metadata strings don’t drive the timeline.
Full Explanation
Parks reusing one fountain cycle clip across plazas with different site start times should reference the shared fountain clip with per-plaza layer offsets for different start times. Layer offsets keep one authored show cycle while aligning each plaza’s start to local park hours or event schedules in the city twin, which is the Domain 1 pattern for staggered reuse of a single civic animation asset.
Baking unique unreferenced copies of the clip into each plaza layer fails by concept: unique copies multiply maintenance whenever the cycle art or timing curve changes and drift apart across parks. Encoding start times only in displayName metadata strings fails because displayName is not a timeCode driver—renderers and composition will not schedule animation from cosmetic metadata. Replacing the clip with a still mesh so timing is unnecessary fails because it abandons the animated civic experience the requirement asks for and removes the skill under test.
Exam caveat: per-site stagger of shared animation → layer offsets on references; metadata strings and still meshes are not time composition. Operational check: reference the fountain clip at two plazas with different offsets, play the stage, confirm start bells differ per site, update the shared clip once, and verify both plazas inherit the new cycle at their offsets without per-plaza rebakes.