Question 350
During troubleshooting, investigators observe: The generated handler charges the same customer on every retry. The system context is: An engineer wants assistance writing an idempotent webhook handler but prompts only "retry failed deliveries". Which ONE cause most directly explains the observed failure?
- The necessary failure evidence was missing from the prompt.
- The organization-specific target pattern was not demonstrated in the prompt.
- Task-specific guidance was not captured in reusable prompt files.
- The prompt omitted idempotency and concurrency invariants.
Explanation
Correct Answer
D:The remedy should therefore be: Specify at-least-once delivery, unique event IDs, concurrency and the need to suppress duplicates.
Incorrect Answers
A:The necessary failure evidence was missing from the prompt. The prompt omitted idempotency and concurrency invariants.
B:The organization-specific target pattern was not demonstrated in the prompt. The missing change involves the prompt omitted idempotency and concurrency invariants.
C:Task-specific guidance was not captured in reusable prompt files. The prompt omitted idempotency and concurrency invariants.
Question 351
The current design is: Specify at-least-once delivery, unique event IDs, concurrency and the need to suppress duplicates. The prior failure was: The generated handler charges the same customer on every retry. Which ONE ongoing control best protects against recurrence of that specific failure?
- Maintain reviewed few-shot examples and update them with the contract version.
- Version prompt templates and keep review checklists aligned with team standards.
- Include failure modes and negative tests in transactional prompt specifications.
- Include error text and reproducible commands when requesting repairs.
Explanation
Correct Answer
C:The prompt omitted idempotency and concurrency invariants. Include failure modes and negative tests in transactional prompt specifications.
Incorrect Answers
A:Generated code requires independently defined acceptance tests and review against the real program contract. Preventing this failure involves include failure modes and negative tests in transactional prompt specifications.
B:Generated code requires independently defined acceptance tests and review against the real program contract. Preventing this failure involves include failure modes and negative tests in transactional prompt specifications. The observed condition is specify at-least-once delivery, unique event IDs, concurrency and the need to suppress duplicates. The prior failure was: The generated handler charges the same.
D:Shell commands from AI tools must be inspected for resolved paths and side effects before destructive execution. Preventing this failure involves include failure modes and negative tests in transactional prompt specifications.
Question 352
A team reports: A developer wants Copilot to refactor code without moving a public function or changing its exact export name. They observe: The generated code renames an export and breaks external callers. Which ONE technical decision most directly corrects the cause?
- Identify the exact module, symbol and signature, and attach the relevant source excerpt.
- Identify the public API, allowed implementation region, compatibility requirement and diff boundaries explicitly.
- Decompose the work into bounded functions and require public-signature and regression tests at each step.
- Provide two short representative input-output pairs followed by the new task as few-shot context.
Explanation
Correct Answer
B:The refactor prompt did not state protected interface constraints.
Incorrect Answers
A:Identifying the exact module, symbol and signature, and attaching the relevant source excerpt would not identify the public API, allowed implementation region, compatibility requirement and diff boundaries explicitly.
C:Decompose the work into bounded functions and require public-signature and regression tests at each step would not identify the public API, allowed implementation region, compatibility requirement and diff boundaries explicitly.
D:Providing two short representative input-output pairs followed by the new task as few-shot context would not identify the public API, allowed implementation region, compatibility requirement and diff boundaries explicitly.
Question 353
A team has implemented the following change: Identify the public API, allowed implementation region, compatibility requirement and diff boundaries explicitly. The original requirement was: A developer wants Copilot to refactor code without moving a public function or changing its exact export name. Which ONE validation test best demonstrates the intended behavior?
- Compare the answer to the selected method's body and call graph.
- Refactor one helper, rerun API contract tests, then proceed to the next helper.
- Check imports from dependent modules before and after the refactor.
- Ask for a third error example and compare the field names, tone and structure to the references.
Explanation
Correct Answer
C:Check imports from dependent modules before and after the refactor.
Incorrect Answers
A:Compare the answer to the selected method's body and call graph. That check cannot demonstrate verified package identity and dependency provenance.
B:Generated API calls must be verified against the installed library's actual supported signatures. Verification of this result involves checking imports from dependent modules before and after the refactor.
D:Ask for a third error example and compare the field names, tone and structure to the references. That check cannot demonstrate verified package identity and dependency provenance.
Question 354
During troubleshooting, investigators observe: The generated code renames an export and breaks external callers. The system context is: A developer wants Copilot to refactor code without moving a public function or changing its exact export name. Which ONE cause most directly explains the observed failure?
- The organization-specific target pattern was not demonstrated in the prompt.
- The refactor prompt did not state protected interface constraints.
- The task exceeded a manageable verifiable change scope.
- An ambiguous referent let conversation history select the wrong target.
Explanation
Correct Answer
B:The remedy should therefore be: Identify the public API, allowed implementation region, compatibility requirement and diff boundaries explicitly.
Incorrect Answers
A:The organization-specific target pattern was not demonstrated in the prompt. The missing change involves the refactor prompt did not state protected interface constraints.
C:The task exceeded a manageable verifiable change scope. The refactor prompt did not state protected interface constraints.
D:An ambiguous referent let conversation history select the wrong target. The refactor prompt did not state protected interface constraints.
Question 355
The current design is: Identify the public API, allowed implementation region, compatibility requirement and diff boundaries explicitly. The prior failure was: The generated code renames an export and breaks external callers. Which ONE ongoing control best protects against recurrence of that specific failure?
- Maintain reviewed few-shot examples and update them with the contract version.
- Use explicit file and symbol references in follow-up questions.
- Use incremental decomposition and checkpoint tests for large AI-assisted edits.
- Preserve API signatures in tests and review any generated symbol renames.
Explanation
Correct Answer
D:The refactor prompt did not state protected interface constraints. Preserve API signatures in tests and review any generated symbol renames.
Incorrect Answers
A:Generated code requires independently defined acceptance tests and review against the real program contract. It would leave compatibility with the pinned dependency version without the specified safeguard.
B:Use explicit file and symbol references in follow-up questions. It would leave compatibility with the pinned dependency version without the specified safeguard.
C:Generated code requires independently defined acceptance tests and review against the real program contract. Preventing this failure involves preserving API signatures in tests and review any generated symbol renames.
Question 356
A team reports: A team uses a long screenshot description of an accessibility issue but gives Copilot no semantic HTML or keyboard requirement. They observe: A proposed UI is visually correct but cannot be used without a mouse. Which ONE technical decision most directly corrects the cause?
- Treat retrieved issue text as task data, not authoritative instructions; state trusted requirements separately.
- Describe the target component, ARIA behavior, tab order and visible focus acceptance criteria.
- Use an explicit zero-shot description with parameters, expected return type and error behavior.
- State the expected JSON schema and forbid extraneous Markdown in the requested output.
Explanation
Correct Answer
B:The prompt captured appearance but omitted behavioral accessibility constraints.
Incorrect Answers
A:Treat retrieved issue text as task data, not authoritative instructions would not describe the target component, ARIA behavior, tab order and visible focus acceptance criteria.
C:Using an explicit zero-shot description with parameters, expected return type and error behavior would not describe the target component, ARIA behavior, tab order and visible focus acceptance criteria.
D:State the expected JSON schema and forbid extraneous Markdown in the requested output would not describe the target component, ARIA behavior, tab order and visible focus acceptance criteria.
Question 357
A team has implemented the following change: Describe the target component, ARIA behavior, tab order and visible focus acceptance criteria. The original requirement was: A team uses a long screenshot description of an accessibility issue but gives Copilot no semantic HTML or keyboard requirement. Which ONE validation test best demonstrates the intended behavior?
- Parse the result as JSON and validate required keys and types.
- Check that the generated signature and error branch match the verbal specification.
- Verify the model refuses to remove authorization unless approved in the actual change request.
- Run keyboard-only navigation and automated accessibility checks after the fix.
Explanation
Correct Answer
D:Run keyboard-only navigation and automated accessibility checks after the fix.
Incorrect Answers
A:Schema-driven tests enforce the expected wire-format contract across generated serialization code. It does not run keyboard-only navigation and automated accessibility checks after the fix.
B:Generated API calls must be verified against the installed library's actual supported signatures. It does not run keyboard-only navigation and automated accessibility checks after the fix.
C:Cryptographic algorithm decisions must follow authoritative security standards rather than unverified model claims. Verification of this result involves running keyboard-only navigation and automated accessibility checks after the fix.
Question 358
During troubleshooting, investigators observe: A proposed UI is visually correct but cannot be used without a mouse. The system context is: A team uses a long screenshot description of an accessibility issue but gives Copilot no semantic HTML or keyboard requirement. Which ONE cause most directly explains the observed failure?
- The task contract was too vague even for a zero-shot request.
- The output format was not specified as a machine contract.
- The prompt captured appearance but omitted behavioral accessibility constraints.
- Untrusted retrieved text was promoted to an instruction source.
Explanation
Correct Answer
C:The remedy should therefore be: Describe the target component, ARIA behavior, tab order and visible focus acceptance criteria.
Incorrect Answers
A:The task contract was too vague even for a zero-shot request. The prompt captured appearance but omitted behavioral accessibility constraints.
B:The output format was not specified as a machine contract. The prompt captured appearance but omitted behavioral accessibility constraints.
D:Untrusted retrieved text was promoted to an instruction source. The prompt captured appearance but omitted behavioral accessibility constraints.
Question 359
The current design is: Describe the target component, ARIA behavior, tab order and visible focus acceptance criteria. The prior failure was: A proposed UI is visually correct but cannot be used without a mouse. Which ONE ongoing control best protects against recurrence of that specific failure?
- Use schema validation even when the prompt asks for JSON only.
- Add parameter and return examples when a concise zero-shot prompt fails.
- Specify inclusive interaction tests for UI-generation prompts.
- Separate trusted prompts from lower-trust issue, log and documentation content.
Explanation
Correct Answer
C:The prompt captured appearance but omitted behavioral accessibility constraints. Specify inclusive interaction tests for UI-generation prompts.
Incorrect Answers
A:Schema-driven tests enforce the expected wire-format contract across generated serialization code. It would leave tested AI-assisted changes that preserve stated requirements without the specified safeguard.
B:Add parameter and return examples when a concise zero-shot prompt fails. Preventing this failure involves specify inclusive interaction tests for UI-generation prompts.
D:Separate trusted prompts from lower-trust issue, log and documentation content. Preventing this failure involves specify inclusive interaction tests for UI-generation prompts.
Question 360
A team reports: Copilot provides a plausible code change based on an external issue comment that says to disable security checks. They observe: A prompt injection in an issue causes the assistant to change permissions. Which ONE technical decision most directly corrects the cause?
- Describe the target component, ARIA behavior, tab order and visible focus acceptance criteria.
- Treat retrieved issue text as task data, not authoritative instructions; state trusted requirements separately.
- Include the exact compiler diagnostic, affected file, minimal relevant context and expected behavior.
- Express positive deliverables and explicit limits: patch and tests only; no production rollout steps.
Explanation
Correct Answer
B:Untrusted retrieved text was promoted to an instruction source.
Incorrect Answers
A:Describing the target component, ARIA behavior, tab order and visible focus acceptance criteria would not address the need for treat retrieved issue text as task data, not authoritative instructions.
C:Including the exact compiler diagnostic, affected file, minimal relevant context and expected behavior would not address the need for treat retrieved issue text as task data, not authoritative instructions.
D:Express positive deliverables and explicit limits: patch and tests only would not address the need for treat retrieved issue text as task data, not authoritative instructions.
GitHub Copilot (GH-300) Practice Tests