Home/Blog/How to Prompt an AZ-900 Scenario Coach
Blog

How to Prompt an AZ-900 Scenario Coach

P
promptstudio
How to Prompt an AZ-900 Scenario Coach

AZ-900 coaches fail when they dump stems. Verify against Microsoft Learn. Keep the not-a-dump banner.

The matching generator is the AZ-900 Scenario Coach (Verify Against Docs, No 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).

Print the not-an-exam-dump banner first

Coach AZ-900-style cloud scenarios with verify-against-docs notes. 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:

Study brief / topics I lock: [Brief]
Number of drills I allow: [N or 3]
Docs excerpt I allow (or NONE): [Docs]
Words I must not use: [Banned]
What I must never invent: [Never]
Output format: [Format]
Language: [Lang]
Banner I require: [Banner or Not an exam dump]

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.

Build drills only from the study brief

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:

  1. Honesty ledger: Brief nouns, N, Docs status, Banner, Lang.
  2. Banner line first.
  3. Up to N scenario drills. Each: setup from Brief, question, model answer outline, VERIFY AGAINST MICROSOFT LEARN note.
  4. If Docs is NONE, write VERIFY AGAINST MICROSOFT LEARN (excerpt NOT IN INPUTS) on every drill.
  5. Refuse: remembered exam stems, AZ-104 admin labs, inventing score reports.
  6. Topic coverage map: only topics in Brief.
  7. Study tip: one line pointing learner to Docs or Microsoft Learn, not to dumps.
  8. Compliance pass: Banned and Never. 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.

Write VERIFY AGAINST MICROSOFT LEARN when Docs is blank

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:

  • AZ-900 scenarios from Brief only. Not an exam dump and not AZ-104.
  • Never invent remembered exam items.
  • Keep Banner visible.
  • 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 remembered exam items and AZ-104 labs

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 (az-900 scenario coach, verify against docs no dump, azure fundamentals practice scenarios) 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.