A parks supervisor needs a new Copilot agent and does not want to configure every field from a blank form. What should the supervisor do?
Select an answer to reveal the explanation.
Short Explanation
Blank forms are slow—start from a template. It’s like using a parks memo template instead of formatting a letterhead from scratch every Monday.
Full Explanation
Template-based creation lets municipal users start Copilot agents with structured fields instead of configuring every blank setting. A parks supervisor who does not want to fill an empty form should create the agent from a template rather than starting from a completely blank configuration. Templates accelerate setup, promote consistent agent anatomy (instructions, prompts, capabilities scaffolding), and reduce omitted fields during first-time agent creation.
Refusing templates and typing every field from an empty screen fails speed and consistency goals stated in the scenario. Downloading an unrelated desktop macro tool fails platform fit—macros are not a substitute for Copilot agent templates. Waiting for residents to build the agent template on a public website fails municipal ownership and control; public visitors should not define city agent create paths.
Exam caveat: starting from a template does not finish the job—parks-specific instructions, knowledge, and review still matter. Templates are scaffolding, not a waiver of configuration quality.
Operational check: open the Copilot agent create flow, select a suitable template, complete parks-specific fields, save the agent, and compare setup time and completeness against a blank-agent baseline for the same purpose.