12 original questions to validate Agents & Copilot Studio: the nature of agents, no-code creation, business data, actions and controlled deployment.
Answer everything, then click Check: your score and explanations will appear.
5.1 · Recall
1. What distinguishes an agent from a simple Copilot assistant?
Its own role, dedicated knowledge, sometimes actions: created once, reused a thousand times with no re-briefing.
5.1 · Application
2. Hicham answers the same leave questions ten times a day. What does an agent bring him?
Persistence: created once on the department's documents, the agent serves the whole team continuously.
5.2 · Application
3. Hicham describes his leave agent in one sentence in Copilot Studio. Where does most of what follows come down to?
90% of quality: a written role, tone and scope, plus clean, up-to-date sources.
5.2 · Recall
4. Which step is non-negotiable before sharing an agent?
A published agent speaks on behalf of the organization: testing catches failures before release.
5.2 · Arbitration
5. Hicham's agent answers well about leave but slips on payroll. Your call?
Out-of-scope cases are handled in writing (human handoff) then retested — never by hasty publication.
5.3 · Application
6. Hicham connects his agent to the internal policies SharePoint. First curation move?
Few sources, relevant and up to date: outdated content makes the agent answer wrongly and confidently.
5.3 · Application
7. How does Hicham check that no restricted document leaks via his agent?
The limited-rights test proves that everyone only sees via the agent what they are entitled to.
5.3 · Recall
8. What must an agent connected to SharePoint respect?
The agent inherits the scope: it never bypasses access control.
5.4 · Application
9. Hicham adds support ticket creation to his agent. Which guardrail before each write?
Writing is risky and irreversible: explicit human confirmation before execution.
5.4 · Arbitration
10. Hicham's agent must check a status then send an external email. Your call?
Reading is benign, writing is framed: autonomy is earned through supervision.
5.5 · Application
11. Before rolling out his agent to the whole organization, what does Hicham do?
Governance, pilot-measured cost, trained adoption: a proven rollout, not a bet.
5.5 · Arbitration
12. Hicham's pilot is conclusive. Who approves scope, authorizations and access before wide release?
Publishing commits the organization: the IT department approves authorizations and scope before generalization.
What's next?
Score ≥ 80%: move on to Level 6 'In practice' — concrete cases, troubleshooting and the Copilot 365 toolbox (NO exam).
Score 50-79%: re-read the explanations above — each one re-explains the concept — then redo the 48h challenges and the template sheets of the failed sections.
Score < 50%: revisit sheets 5.1 (instructions-knowledge-actions trio) and 5.3 (permissions), your two vital moves, before continuing.