How to Prompt an AWS SOA-C02 Scenario Coach

SOA coaches fail when they paste a remembered stem and mint a docs URL. Tag Monitoring. Leave Docs UNKNOWN if you do not have it.
The matching generator is the AWS SOA-C02 Scenario Coach (Domain-Tagged, Verify Against Docs, No Exam Dump) (Aws Soa C02 Scenario Coach Domain Tagged Verify Against Docs No Exam Dump) prompt. Browse related cards in the PromptDig library (Browse more prompts). When a filled run survives, share the version you actually use (Share a prompt).
Banner that this is not an exam dump
Coach AWS SOA-C02 SysOps scenarios with domain tags. Verify against docs. Not an exam dump and not a brain dump. Start by filling Inputs, not by asking the model to remember last week's run. If a field is blank, write NONE or NOT IN INPUTS and leave it blank through Generate. The card is built so the model cannot honestly invent a number, owner, URL, or command that you did not paste.
Paste these fields before you hit run:
Objective or task I allow: [Objective]
Domain I lock (Monitoring, Reliability, Deployment, Security, Networking, Cost, or UNKNOWN): [Domain]
Docs snippet I may quote (or NONE): [Docs]
Docs URL I may print (or UNKNOWN): [DocsURL]
Words I must not use: [Banned]
What I must never invent (stems, dumps, limits): [Never]
Output format: [Format]
Language: [Lang]
What this is not: [Not]
Service names I may use: [Services]
That inventory is the honesty ledger. Anything that does not appear there is forbidden in the draft. If you catch yourself adding a nice-to-have after the run, you are no longer using the card. You are ghostwriting. Put the extra fact in Inputs and run again.
Tag every drill with the pasted domain
Generate is numbered on purpose. Do not skip a step because the first paragraph looked done. The early steps exist to stop later prose from smuggling claims.
Walk the Generate list in order:
- Banner: not an exam dump, not SAA-C03, not DVA-C02. Quote Not.
- Honesty ledger: Objective, Domain, Services, DocsURL, Lang. Forbidden: remembered stems, invented quotas, extra services.
- Scenario: one SysOps job from Objective. Tag Domain on the first line. Use only Services.
- Coach questions: three questions that force a runbook choice. No lettered multiple-choice dump key.
- Verify: if Docs is NONE, write VERIFY AGAINST DOCS: UNKNOWN rather than minting a docs URL. If DocsURL is known, quote it.
- Refuse: SAA-C03 multi-account landing zone stems, DVA-C02 code-pipeline trivia, brain-dump phrases.
- Never: do not write 'the correct answer is C'.
- Compliance pass: quote Banned and Never hits. Cut them. Format as Format.
If a step asks for a version lock, quote the version from Inputs in the output. If a step asks for a refuse list, keep the refuse list in the published artifact, not in a sidebar you delete. Reviewers should see what the model was not allowed to do.
Verify against docs or write UNKNOWN
Most failures are the same shape: a missing field gets a confident fill. A conversion rate appears. A Gradle task appears. A flash point appears. A caption appears on a job that asked for slide text only. Your review is to search the draft for numbers, names, and commands, then grep Inputs. No match means cut.
Honor the constraints as hard stops, not vibes:
- SOA-C02 SysOps coach from Objective. Not SAA-C03, not DVA-C02, not an exam dump.
- Domain-tag every scenario. Verify against Docs or write UNKNOWN.
- Only Services named in Inputs.
- No emojis.
When the card says not legal advice, not certification, not an exam dump, or not a caption engine, that sentence belongs at the top of the output. Deleting it to look more finished is how you inherit risk.
Refuse SAA-C03 architecture stems
Finish with the compliance pass the prompt already asks for. Quote the banned-word hits. Cut them. Print character counts when the job has a cap. Print word counts when the job has a budget. List gaps as gaps. Five missing facts are more useful than one smooth paragraph.
Tags on the card (aws soa-c02 scenario coach, sysops domain tagged verify docs, no soa-c02 exam dump) are a reminder of the job shape, not an invitation to wander into a neighboring cluster. If you need a different surface, open a different PromptDig card rather than stretching this one.
Fill the card, then run
Replace every bracket. Run on ChatGPT, Claude, or Gemini. Read the ledger first, then the artifact. If the model invents a commit, KPI, DOI, PEL, bid, or logo, discard the run. Tighten Inputs. Run again. Share the filled card that survived, not the first draft that sounded done.