Scenario intake checklist (per 2-hour scenario)
A fixed routine for each of the four scenarios. Independent scenarios - reset your mind; carry nothing over. No backward navigation, so decide and commit.
First ~10 minutes - read and capture (don't answer yet)
- Read all background + topology before answering anything.
- Capture requirements and constraints in four buckets as you read:
| Technical | Operational | Application | Business / regulatory |
|---|---|---|---|
- Note the business driver in one sentence - it is the lens for every answer.
- Flag dual-stack: is there an explicit IPv6 requirement? Assume v4 and v6 unless told otherwise.
While answering
- Answer the intent. Partial credit is by question intent - align to the business/technical driver, show the reasoning chain.
- Time-box ~10 minutes per decision; "defensible and good enough" beats "perfect."
- Architect mindset, not operator. No CLI; do not map answers to config snippets.
- Watch for the twist. Mid-scenario, management may change direction or add info that
invalidates an earlier assumption - re-derive from the (new) requirement; this is the point of the "validate and adapt" skill.
- Use cisco.com docs for fact lookup (it's available); use your own reasoning for the design call.
Reminders
- Unused time does not carry to the next scenario - but don't rush into errors.
- You must clear each scenario's minimum and the aggregate pass - the elective (4th)
can sink you, so treat AI-Infra depth as mandatory.
Spaced repetition
Partial credit on the Practical is awarded by
question intent (align answers to the business/technical driver).
Two scoring conditions you must both satisfy
clear each scenario's minimum AND the aggregate pass score.