A business analyst must explain to stakeholders when to assign background development work in GitHub versus when to build a tailored assistant for contract reviews with custom instructions and company knowledge. Which statement best differentiates Copilot cloud agents from custom agents for this business choice?
Select an answer to reveal the explanation.
Short Explanation
You’re matching the right helper to the right job for your stakeholders. Agent purpose is the key: a cloud agent handles assigned background work, while a custom agent applies your instructions and company knowledge to repeat domain tasks. That makes the cloud agent a delivery driver and the custom agent a specialist with your playbook.
Full Explanation
The statement that pairs autonomous background coding tasks from assigned GitHub issues with custom agents applying tailored instructions for domain work fits the business choice. An assigned issue gives a cloud agent scope and repository context to plan edits, validate code and propose a pull request; custom instructions and company knowledge can guide repeatable contract reviews. Describing cloud agents as real-time code completions in the IDE confuses interactive suggestions with delegated background execution. Pairing issue-driven coding with custom agents automating dependency updates across repositories correctly describes the cloud-agent task but misses the custom agent’s role in tailored domain work. Saying cloud agents start background tasks from chat conversations instead of assigned issues misstates their trigger, even though it correctly connects custom agents with tailored contract-review guidance. As an exam caveat, do not decide by coding vocabulary alone: match the trigger and output to the need. As a practical check, choose a cloud agent when stakeholders need an assigned issue handled in the background and a proposed pull request; choose a custom agent when reviewers need consistent clause analysis guided by company knowledge and tailored instructions.