Question 200
A team has implemented the following change: Generate an AI-assisted pull request summary, then verify its statements against the actual changed files. The original requirement was: An author wants Copilot to summarize a 40-file pull request for reviewers who lack time to read every commit individually. Which ONE validation test best demonstrates the intended behavior?
- Open a test pull request containing an intentionally unsafe access check and inspect the AI review and human gate.
- Sample claims from the summary and confirm the corresponding diff sections and tests exist.
- Verify the draft branch, changed files, checks and required pull-request approvals before merging.
- Ask a factual question about a specific section and verify the file reference was used.
Explanation
Correct Answer
B:Sample claims from the summary and confirm the corresponding diff sections and tests exist.
Incorrect Answers
A:Generated code requires independently defined acceptance tests and review against the real program contract. Verification of this result involves sample claims from the summary and confirm the corresponding diff sections and tests exist.
C:Verify the draft branch, changed files, checks and required pull-request approvals before merging. That check cannot demonstrate tested AI-assisted changes that preserve stated requirements.
D:Ask a factual question about a specific section and verify the file reference was used. Verification of this result involves sample claims from the summary and confirm the corresponding diff sections and tests exist.
Question 201
During troubleshooting, investigators observe: The summary says no API contract changed despite a breaking response-field rename. The system context is: An author wants Copilot to summarize a 40-file pull request for reviewers who lack time to read every commit individually. Which ONE cause most directly explains the observed failure?
- A generated change narrative can omit important modifications.
- Cloud delegation creates a proposed change, not automatic correctness or release approval.
- Review guidelines and requested focus were missing from the tool's context.
- The actual file context was omitted from the terminal prompt.
Explanation
Correct Answer
A:The remedy should therefore be: Generate an AI-assisted pull request summary, then verify its statements against the actual changed files.
Incorrect Answers
B:Cloud delegation creates a proposed change, not automatic correctness or release approval. A generated change narrative can omit important modifications.
C:Review guidelines and requested focus were missing from the tool's context. A generated change narrative can omit important modifications.
D:The actual file context was omitted from the terminal prompt. A generated change narrative can omit important modifications.
Question 202
The current design is: Generate an AI-assisted pull request summary, then verify its statements against the actual changed files. The prior failure was: The summary says no API contract changed despite a breaking response-field rename. Which ONE ongoing control best protects against recurrence of that specific failure?
- Attach explicit approved paths and avoid unnecessary secrets in CLI prompts.
- Keep PR diff and required human review as the source of truth, not the summary.
- Maintain human code-owner review and security scanners even with AI code review enabled.
- Keep branch protections and required checks for agent-created pull requests.
Explanation
Correct Answer
B:A generated change narrative can omit important modifications. Keep PR diff and required human review as the source of truth, not the summary.
Incorrect Answers
A:Cryptographic algorithm decisions must follow authoritative security standards rather than unverified model claims. Preventing this failure involves keep PR diff and required human review as the source of truth, not the summary.
C:Generated code requires independently defined acceptance tests and review against the real program contract. Preventing this failure involves keep PR diff and required human review as the source of truth, not the summary.
D:Keep branch protections and required checks for agent-created pull requests. Preventing this failure involves keep PR diff and required human review as the source of truth, not the summary.
Question 203
A team reports: A repository uses Copilot code review and wants consistent attention to authorization checks in `src/security` changes. They observe: AI review comments focus on style while missing a sensitive permission regression. Which ONE technical decision most directly corrects the cause?
- Use a configured custom agent with relevant instructions and tool restrictions for the review task.
- Generate an AI-assisted pull request summary, then verify its statements against the actual changed files.
- Provide supported repository and path-scoped review instructions and verify the policy is enabled for the repository.
- Provide the codebase style conventions through supported instructions and reference examples rather than rely on default responses.
Explanation
Correct Answer
C:Review guidelines and requested focus were missing from the tool's context.
Incorrect Answers
A:Using a configured custom agent with relevant instructions and tool restrictions for the review task would not provide supported repository and path-scoped review instructions and verify the policy is enabled for the repository.
B:Generating an AI-assisted pull request summary, then verify its statements against the actual changed files would not provide supported repository and path-scoped review instructions and verify the policy is enabled for the repository.
D:Repository-specific conventions were missing or not available as prompt context. The missing change involves provide supported repository and path-scoped review instructions and verify the policy is enabled for the repository.
Question 204
A team has implemented the following change: Provide supported repository and path-scoped review instructions and verify the policy is enabled for the repository. The original requirement was: A repository uses Copilot code review and wants consistent attention to authorization checks in `src/security` changes. Which ONE validation test best demonstrates the intended behavior?
- Request a sample class and compare naming, imports and test framework with repo policy.
- Open a test pull request containing an intentionally unsafe access check and inspect the AI review and human gate.
- Sample claims from the summary and confirm the corresponding diff sections and tests exist.
- Run it against a sample auth change and inspect the reported code references without unexpected edits.
Explanation
Correct Answer
B:Open a test pull request containing an intentionally unsafe access check and inspect the AI review and human gate.
Incorrect Answers
A:Generated code requires independently defined acceptance tests and review against the real program contract. Verification of this result involves open a test pull request containing an intentionally unsafe access check and inspect the AI review and human gate.
C:Generated code requires independently defined acceptance tests and review against the real program contract. Verification of this result involves open a test pull request containing an intentionally unsafe access check and inspect the AI review and human gate. The observed condition is a team has implemented the following change: Provide supported repository and path-scoped review instructions and verify the policy is enabled for the repository..
D:Run it against a sample auth change and inspect the reported code references without unexpected edits. Verification of this result involves open a test pull request containing an intentionally unsafe access check and inspect the AI review and human gate.
Question 205
During troubleshooting, investigators observe: AI review comments focus on style while missing a sensitive permission regression. The system context is: A repository uses Copilot code review and wants consistent attention to authorization checks in `src/security` changes. Which ONE cause most directly explains the observed failure?
- Specialized objectives and tool boundaries were not provided.
- A generated change narrative can omit important modifications.
- Review guidelines and requested focus were missing from the tool's context.
- Repository-specific conventions were missing or not available as prompt context.
Explanation
Correct Answer
C:The remedy should therefore be: Provide supported repository and path-scoped review instructions and verify the policy is enabled for the repository.
Incorrect Answers
A:Specialized objectives and tool boundaries were not provided would not review guidelines and requested focus were missing from the tool's context.
B:A generated change narrative can omit important modifications would not review guidelines and requested focus were missing from the tool's context.
D:Repository-specific conventions were missing or not available as prompt context would not review guidelines and requested focus were missing from the tool's context.
Question 206
The current design is: Provide supported repository and path-scoped review instructions and verify the policy is enabled for the repository. The prior failure was: AI review comments focus on style while missing a sensitive permission regression. Which ONE ongoing control best protects against recurrence of that specific failure?
- Keep custom agent scopes explicit and check output against human review requirements.
- Keep concise, tested repository-wide instructions alongside the code.
- Keep PR diff and required human review as the source of truth, not the summary.
- Maintain human code-owner review and security scanners even with AI code review enabled.
Explanation
Correct Answer
D:Review guidelines and requested focus were missing from the tool's context. Maintain human code-owner review and security scanners even with AI code review enabled.
Incorrect Answers
A:Generated code requires independently defined acceptance tests and review against the real program contract. Preventing this failure involves maintaining human code-owner review and security scanners even with AI code review enabled.
B:Generated code requires independently defined acceptance tests and review against the real program contract. Preventing this failure involves maintaining human code-owner review and security scanners even with AI code review enabled. The observed condition is provide supported repository and path-scoped review instructions and verify the policy is enabled for the repository. The prior failure was: AI review comments.
C:Generated code requires independently defined acceptance tests and review against the real program contract. Preventing this failure involves maintaining human code-owner review and security scanners even with AI code review enabled. The observed condition is provide supported repository and path-scoped review instructions and verify the policy is enabled for the repository. The prior failure was: AI review comments. Preventing this failure involves maintaining human code-owner review and security scanners even with AI code review enabled. The named alternative instead concerns keep pr diff and required human review as the source of truth, not the summary.
Question 207
A team reports: A repository maintainer delegates an issue to the cloud Copilot agent and needs a normal reviewable proposal rather than direct default-branch writes. They observe: A generated patch is treated as merged work before anyone has assessed the diff. Which ONE technical decision most directly corrects the cause?
- Use a bounded multi-file editing workflow and manually review all proposed edits rather than authorizing agent tool execution.
- Use supported IDE Agent mode with the repository, test commands, and precise acceptance criteria while supervising tool actions.
- Start an authorized cloud agent task scoped to the repository and base branch, then review its proposed pull request.
- Use a configured custom agent with relevant instructions and tool restrictions for the review task.
Explanation
Correct Answer
C:Cloud delegation creates a proposed change, not automatic correctness or release approval.
Incorrect Answers
A:The selected workflow granted broader tools than the task required. Cloud delegation creates a proposed change, not automatic correctness or release approval.
B:The task required multi-step file/tool coordination, not a single inline continuation. Cloud delegation creates a proposed change, not automatic correctness or release approval.
D:Specialized objectives and tool boundaries were not provided. Cloud delegation creates a proposed change, not automatic correctness or release approval.
Question 208
A team has implemented the following change: Start an authorized cloud agent task scoped to the repository and base branch, then review its proposed pull request. The original requirement was: A repository maintainer delegates an issue to the cloud Copilot agent and needs a normal reviewable proposal rather than direct default-branch writes. Which ONE validation test best demonstrates the intended behavior?
- Run it against a sample auth change and inspect the reported code references without unexpected edits.
- Inspect the entire change set and validate the requested files changed as intended.
- Verify the draft branch, changed files, checks and required pull-request approvals before merging.
- Inspect the proposed multi-file diff and run the project's migration and test suite.
Explanation
Correct Answer
C:Verify the draft branch, changed files, checks and required pull-request approvals before merging.
Incorrect Answers
A:Run it against a sample auth change and inspect the reported code references without unexpected edits. Verification of this result involves verifying the draft branch, changed files, checks and required pull-request approvals before merging.
B:Inspect the entire change set and validate the requested files changed as intended. It does not verify the draft branch, changed files, checks and required pull-request approvals before merging.
D:Generated code requires independently defined acceptance tests and review against the real program contract. It does not verify the draft branch, changed files, checks and required pull-request approvals before merging.
Question 209
During troubleshooting, investigators observe: A generated patch is treated as merged work before anyone has assessed the diff. The system context is: A repository maintainer delegates an issue to the cloud Copilot agent and needs a normal reviewable proposal rather than direct default-branch writes. Which ONE cause most directly explains the observed failure?
- The task required multi-step file/tool coordination, not a single inline continuation.
- The selected workflow granted broader tools than the task required.
- Cloud delegation creates a proposed change, not automatic correctness or release approval.
- Specialized objectives and tool boundaries were not provided.
Explanation
Correct Answer
C:The remedy should therefore be: Start an authorized cloud agent task scoped to the repository and base branch, then review its proposed pull request.
Incorrect Answers
A:The task required multi-step file/tool coordination, not a single inline continuation would not address the need for cloud delegation creates a proposed change, not automatic correctness or release approval.
B:The selected workflow granted broader tools than the task required would not address the need for cloud delegation creates a proposed change, not automatic correctness or release approval.
D:Specialized objectives and tool boundaries were not provided would not address the need for cloud delegation creates a proposed change, not automatic correctness or release approval.
Question 210
The current design is: Start an authorized cloud agent task scoped to the repository and base branch, then review its proposed pull request. The prior failure was: A generated patch is treated as merged work before anyone has assessed the diff. Which ONE ongoing control best protects against recurrence of that specific failure?
- Keep custom agent scopes explicit and check output against human review requirements.
- Review agent tool approvals, modified files and generated tests before merging.
- Keep branch protections and required checks for agent-created pull requests.
- Choose the least-privileged Copilot interaction mode for the requested work.
Explanation
Correct Answer
C:Cloud delegation creates a proposed change, not automatic correctness or release approval. Keep branch protections and required checks for agent-created pull requests.
Incorrect Answers
A:Generated code requires independently defined acceptance tests and review against the real program contract. It would leave keep branch protections and required checks for agent-created pull requests without the specified safeguard.
B:Generated code requires independently defined acceptance tests and review against the real program contract. Preventing this failure involves keep branch protections and required checks for agent-created pull requests.
D:Generated code requires independently defined acceptance tests and review against the real program contract. Preventing this failure involves keep branch protections and required checks for agent-created pull requests. The observed condition is start an authorized cloud agent task scoped to the repository and base branch, then review its proposed pull request. The prior failure was: A generated patch is.
GitHub Copilot (GH-300) Practice Tests