Knowledge check Catwalk Scenarios + Post-Production + Delivery
12 questions in pool · live exam draws 5
SPVC04
Q1 multiple-choice · scenarios-definition A “scenario” in Catwalk’s Controls is:
Source: SPVC04 §1 — Scenarios: the productivity multiplier.
Explanation: Scenarios = saved belt + rotation choreography. Reusable per outfit. The productivity multiplier that makes Catwalk scalable.
Q2 multiple-choice · why-scenarios-matter Why are scenarios commercially important?
Source: SPVC04 §1.1 — Why scenarios matter commercially.
Explanation: Scenarios turn Catwalk from “neat hardware” into “production line for fashion video.” Consistency + throughput.
Q3 multiple-choice · scenario-naming Best practice for scenario naming in studio library:
Source: SPVC04 §2.7 — Discipline.
Explanation: Convention enables library navigation 6 months later. Numeric = unmemorable; random = chaos; customer-only = inflexible.
Q4 multiple-choice · scenario-choice Customer brief: sportswear collection, energetic feel, social-media-first deliverables. Best scenario from starter library:
Source: SPVC04 §2.2 — Brisk runway use case.
Explanation: Sportswear + energetic + social = brisk runway (belt 50%, shorter total length, energetic feel).
Q5 multiple-select · deliverables Which are the four primary deliverables of a Catwalk session? (Select all that apply.)
Source: SPVC04 §4 — The four primary deliverables.
Explanation: Video + 360 spin + key-frame stills + VR/AR plates. Live broadcast is a different production (event streaming, not Catwalk session).
Q6 multiple-choice · aspect-ratios Catwalk motion video for Instagram Reel / TikTok delivery — correct aspect ratio:
Source: SPVC04 §6 delivery format table.
Explanation: Reels + TikTok = 9:16 vertical (mobile-first). 16:9 = web hero, 1:1 = Instagram feed, 4:5 = catalog portrait.
Q7 multiple-choice · post-handoff What does operator hand off to post-production after a Catwalk session?
Source: SPVC04 §5.1 — What operator delivers to post.
Explanation: Post needs raw files + reference data (color checker, scenarios used, outfit metadata, take preferences) to be productive. Operator’s handoff hygiene = post efficiency.
Q8 multiple-choice · mid-session-edit Mid-session, operator realises the “slow-runway” scenario is too fast for the bridal outfit about to shoot. Best response:
Source: SPVC04 §3.1 — Mid-session scenario edits.
Explanation: Quick variant is reasonable. Building new scenarios from scratch mid-session is exception, not rule — pre-session library building avoids 90% of these.
Q9 multiple-choice · takes-per-outfit Typical takes per outfit on Catwalk:
Source: SPVC04 §5.3 + mistake 5 — Don’t over-shoot.
Explanation: 3-5 takes is plenty for most fashion. 15+ overwhelms post + suggests floor indecision.
Q10 multiple-choice · operator-vs-post-lane Customer review comes back: “Outfit 3 — re-grade slightly warmer please.” Who handles this?
Source: SPVC04 mistake 8 + §5.3 — Operator stays in lane.
Explanation: Color grading is colorist / post team’s job, not operator’s. Operator captures cleanly; downstream owns grading.
Q11 multiple-choice · session-closeout End-of-session closeout discipline includes:
Source: SPVC04 §7 — Session closeout per Operator Standard discipline.
Explanation: 7-step checklist. Standard Operator Standard discipline applied to Catwalk specifics. Don’t skip steps.
Q12 multiple-choice · scenario-library-size Recommended starter scenario library size for most fashion studios:
Source: SPVC04 Q&A “How many scenarios should our studio have?”.
Explanation: 3-7 = manageable + memorable. 1 is too restrictive. 20+ becomes navigation problem. Add as need is demonstrated, not preemptively.
Ready to commit? You can review and change your answers before submitting. Once submitted, this attempt is final and we'll show you your score, correct answers, and explanations.
Submit final answers
