Phase 5 · Power Automate · Level 3 · Power User
Power Automate: Power User Quiz · 10 min
Why it matters A quick check of your judgement before you move on. There's no penalty for a low score, and you can retake it, or take it first to test out of a level you already know.
These are the judgement calls a Power Automate power user actually faces: putting AI inside a flow without letting it run unchecked, keeping flows reliable enough to leave running, answering to IT, and knowing when a job has outgrown a flow altogether. Pick the best option for each scenario, and you'll see an explanation after each one.
Passing this checkpoint: work through the level first, then score 70% or more here.
Skipping this level: already confident? Take this cold and score 80% or more to test out and jump ahead. Below that, nothing is lost, you just study the level as normal.
1. You add an AI Builder step that classifies incoming feedback emails as Billing, Technical, Praise or Other, then routes each to the right person. A furious complaint gets labelled 'Praise', files itself with a green tick, and is never chased. What does this teach about AI inside a flow? The flow is broken and should be deleted and rebuilt. A green tick means the step ran, not that the AI was right; the one AI step can be confidently wrong, so you need a human spot-check and a fallback rather than treating 'the flow succeeded' as 'the answer is correct'. AI Builder should never be used to classify emails. The email must have been written in a confusing way, so it's the customer's fault. 2. You want a flow to route an email based on whether the subject line contains the word 'invoice'. A colleague suggests adding an AI Builder step to decide. What's the better-informed call? Always use AI; it's more modern than a plain condition. Use a plain condition: 'does the subject contain invoice' is a rule, so it's free, instant and never hallucinates; save AI Builder for judgements that can't be written as a rule. You can't check text in a condition; only AI can read a subject line. Use both an AI step and a condition together for safety. 3. You write an AI Builder extraction prompt to pull the customer's account number and a renewal date out of feedback emails. Some emails don't mention a renewal date. What's the most important line to include in the prompt? Ask it to always provide a date, guessing if necessary so no field is ever blank. Tell it to write 'Not stated' when a detail isn't in the email, and never to guess or invent one. Tell it to reply in a friendly, conversational tone. Ask it to make the date look realistic. 4. A flow that quietly logs customer feedback has run fine for months, so no one checks it. One day a step fails, the flow stops, and no one notices for two weeks, and a fortnight of feedback simply isn't logged. What's the fix, and why is this worse than not automating? Nothing can be done; flows fail sometimes and that's that. Turn on failure notifications so the flow alerts you when it breaks; a silent automated task is worse than a manual one because a manual task that stops is visible, whereas a stopped flow is invisible until someone goes looking. Check the flow manually every hour, forever. Rebuild the flow in a different tool. 5. A business-critical flow suddenly fails the morning after the person who built it changed their Microsoft password, with an 'unauthorised' error. Beyond re-authenticating the connection, what's the deeper lesson for an important flow? Never change your password. A flow whose connections are signed in as one individual is fragile: a password change, leave or leaver breaks it; important flows should be co-owned and, where possible, run their connections on a shared service account owned by IT. Password changes have nothing to do with flow failures. The flow should be moved to a personal account to avoid IT involvement. 6. You ask IT to let your flow run on shared customer data. Which set of answers is most likely to get a quick yes? 'Only I can fix it, it's on my personal login, and I'm not sure what happens if it fails, but it hasn't failed yet.' 'It's co-owned with Maya, the connections run on a service account, no personal data leaves Fernway, it alerts us on failure, and it respects our DLP policy.' 'It's really clever and uses AI, so it must be fine.' 'I built it quickly so it doesn't need any oversight.' 7. You want a tool that lets colleagues ask, in their own words, questions about the remote-working policy and get sensible answers. You start building it as a flow with nested conditions and quickly have fifteen branches. What does this tell you? You just need more conditions; keep adding branches until every question is covered. This job has outgrown a flow: an open-ended conversation answering from a body of knowledge is agent-shaped work (Copilot Studio), not a fixed path you can draw. Flows can never handle text, so it's impossible. You should force it into a single condition to keep it simple. 8. A colleague is excited to rebuild the simple feedback-routing flow (email arrives, one AI step classifies it, a condition routes it) as a Copilot Studio agent, because agents are 'more advanced'. What's the better view? Agree; newer tools are always the better choice. Keep it as a flow: it's event-triggered and the same every time, so it's flow-shaped; an agent would add cost and unpredictability for no gain, and anything that chooses its own actions needs more governance, not less. Rebuild it as an agent and remove the human check to save time. Agents can't classify emails, so it wouldn't work at all. 9. For your capstone you automate Dan's expenses process. It works beautifully in a five-minute demo, so you write it up as finished. What's most likely missing from a power-user standard? Nothing; a working demo is the finished article. The parts that matter when you're not watching: error handling for messy inputs, a fallback branch, failure alerts, a human check on the risky step, and an honest baseline-and-saving measurement; a demo proves it can work, not that it's dependable. A nicer colour scheme for the flow diagram. More AI steps to make it look advanced. Answered 0 of 9.
Answer every question to see your score