Microsoft GH-300 Practice Test 39

Question 380

During troubleshooting, investigators observe: Mocks pass even though the real insert fails on a missing column. The system context is: An HTTP service has unit tests with mocked database calls, but the team needs confidence the live SQL migrations work together. Which ONE cause most directly explains the observed failure?

Unit isolation did not validate integration across schema and data layers.
Unrealistic positive-only mocks hid throttling behavior.
Tests based only on happy-path integers missed precision behavior.
The test suite did not cover duplicate delivery under race conditions.

Explanation

Correct Answer

The remedy should therefore be: Use Copilot to draft integration tests against an ephemeral test database and real schema migrations.

Incorrect Answers

Unrealistic positive-only mocks hid throttling behavior would not address the need for unit isolation did not validate integration across schema and data layers.

Tests based only on happy-path integers missed precision behavior would not address the need for unit isolation did not validate integration across schema and data layers.

The remedy should therefore be: Ask Copilot to add an idempotency regression test plus a minimal deduplication implementation. That does not establish conformance to the documented serialized payload format.

Question 381

The current design is: Use Copilot to draft integration tests against an ephemeral test database and real schema migrations. The prior failure was: Mocks pass even though the real insert fails on a missing column. Which ONE ongoing control best protects against recurrence of that specific failure?

Keep independent decimal boundary fixtures to validate AI-generated tests.
Audit mock fidelity against provider contracts and adverse responses.
Retain concurrency and duplicate-event tests on every billing release.
Maintain a repeatable integration test environment and migration checkpoints.

Explanation

Correct Answer

Unit isolation did not validate integration across schema and data layers. Maintain a repeatable integration test environment and migration checkpoints.

Incorrect Answers

Approved dependency sources and lockfiles protect builds against invented or impersonated packages. Preventing this failure involves maintaining a repeatable integration test environment and migration checkpoints.

Audit mock fidelity against provider contracts and adverse responses. Preventing this failure involves maintaining a repeatable integration test environment and migration checkpoints.

Generated code requires independently defined acceptance tests and review against the real program contract. Preventing this failure involves maintaining a repeatable integration test environment and migration checkpoints.

Question 382

A team reports: A generated URL parser passes five examples but mishandles an empty hostname and percent-encoded slash. They observe: An attacker-controlled URL bypasses an allowlist using ambiguous escaping. Which ONE technical decision most directly corrects the cause?

Model rate limits and retry-after headers in mocks using the provider's real contract.
Ask Copilot to add an idempotency regression test plus a minimal deduplication implementation.
Prompt Copilot for explicit edge-case assertions rather than another implementation rewrite.
Use Copilot to draft integration tests against an ephemeral test database and real schema migrations.

Explanation

Correct Answer

The existing examples did not probe normalization and boundary behavior.

Incorrect Answers

Model rate limits and retry-after headers in mocks using the provider's real contract would not prompt Copilot for explicit edge-case assertions rather than another implementation rewrite.

Asking Copilot to add an idempotency regression test plus a minimal deduplication implementation would not prompt Copilot for explicit edge-case assertions rather than another implementation rewrite.

Using Copilot to draft integration tests against an ephemeral test database and real schema migrations would not prompt Copilot for explicit edge-case assertions rather than another implementation rewrite.

Question 383

A team has implemented the following change: Prompt Copilot for explicit edge-case assertions rather than another implementation rewrite. The original requirement was: A generated URL parser passes five examples but mishandles an empty hostname and percent-encoded slash. Which ONE validation test best demonstrates the intended behavior?

Run backoff tests and confirm bounded exponential retry behavior on 429 responses.
Deliver the same event concurrently and verify one invoice record and one downstream send.
Run fixtures for empty hosts, percent escapes, Unicode, invalid schemes and trailing slashes.
Run the migration and create/read/delete workflow in CI with an isolated database.

Explanation

Correct Answer

Run fixtures for empty hosts, percent escapes, Unicode, invalid schemes and trailing slashes.

Incorrect Answers

Generated code requires independently defined acceptance tests and review against the real program contract. That check cannot demonstrate correct Unicode normalization and comparison behavior.

Deliver the same event concurrently and verify one invoice record and one downstream send. That check cannot demonstrate correct Unicode normalization and comparison behavior.

Run the migration and create/read/delete workflow in CI with an isolated database. That check cannot demonstrate correct Unicode normalization and comparison behavior.

Question 384

During troubleshooting, investigators observe: An attacker-controlled URL bypasses an allowlist using ambiguous escaping. The system context is: A generated URL parser passes five examples but mishandles an empty hostname and percent-encoded slash. Which ONE cause most directly explains the observed failure?

Unrealistic positive-only mocks hid throttling behavior.
The test suite did not cover duplicate delivery under race conditions.
Unit isolation did not validate integration across schema and data layers.
The existing examples did not probe normalization and boundary behavior.

Explanation

Correct Answer

The remedy should therefore be: Prompt Copilot for explicit edge-case assertions rather than another implementation rewrite.

Incorrect Answers

Unrealistic positive-only mocks hid throttling behavior. The existing examples did not probe normalization and boundary behavior.

The test suite did not cover duplicate delivery under race conditions. The existing examples did not probe normalization and boundary behavior.

Unit isolation did not validate integration across schema and data layers. The existing examples did not probe normalization and boundary behavior.

Question 385

The current design is: Prompt Copilot for explicit edge-case assertions rather than another implementation rewrite. The prior failure was: An attacker-controlled URL bypasses an allowlist using ambiguous escaping. Which ONE ongoing control best protects against recurrence of that specific failure?

Maintain a repeatable integration test environment and migration checkpoints.
Audit mock fidelity against provider contracts and adverse responses.
Retain concurrency and duplicate-event tests on every billing release.
Keep security-relevant URL parsing tests separate from generation prompts.

Explanation

Correct Answer

The existing examples did not probe normalization and boundary behavior. Keep security-relevant URL parsing tests separate from generation prompts.

Incorrect Answers

Audit mock fidelity against provider contracts and adverse responses. Preventing this failure involves keep security-relevant URL parsing tests separate from generation prompts.

Generated code requires independently defined acceptance tests and review against the real program contract. Preventing this failure involves keep security-relevant URL parsing tests separate from generation prompts. The observed condition is prompt Copilot for explicit edge-case assertions rather than another implementation rewrite. The prior failure was: An attacker-controlled URL bypasses an allowlist.

Question 386

A team reports: A controller posts an invoice twice when the upstream webhook retries the same event ID. They observe: Concurrent retries insert duplicate rows despite passing sequential tests. Which ONE technical decision most directly corrects the cause?

Use Copilot to draft integration tests against an ephemeral test database and real schema migrations.
Ask Copilot to propose parameterized tests with zero, negative, huge and fractional-precision inputs tied to the contract.
Ask Copilot to add an idempotency regression test plus a minimal deduplication implementation.
Prompt Copilot for explicit edge-case assertions rather than another implementation rewrite.

Explanation

Correct Answer

The test suite did not cover duplicate delivery under race conditions.

Incorrect Answers

Using Copilot to draft integration tests against an ephemeral test database and real schema migrations would not ask Copilot to add an idempotency regression test plus a minimal deduplication implementation.

Asking Copilot to propose parameterized tests with zero, negative, huge and fractional-precision inputs tied to the contract would not ask Copilot to add an idempotency regression test plus a minimal deduplication implementation.

Prompting Copilot for explicit edge-case assertions rather than another implementation rewrite would not ask Copilot to add an idempotency regression test plus a minimal deduplication implementation.

Question 387

A team has implemented the following change: Ask Copilot to add an idempotency regression test plus a minimal deduplication implementation. The original requirement was: A controller posts an invoice twice when the upstream webhook retries the same event ID. Which ONE validation test best demonstrates the intended behavior?

Run generated tests and confirm exact decimal arithmetic outcomes and exceptions.
Run fixtures for empty hosts, percent escapes, Unicode, invalid schemes and trailing slashes.
Deliver the same event concurrently and verify one invoice record and one downstream send.
Run the migration and create/read/delete workflow in CI with an isolated database.

Explanation

Correct Answer

Deliver the same event concurrently and verify one invoice record and one downstream send.

Incorrect Answers

Generated code requires independently defined acceptance tests and review against the real program contract. That check cannot demonstrate deliver the same event concurrently and verify one invoice record and one downstream send.

Unicode behavior must be tested with composed, decomposed and boundary-case text, not only ASCII samples. Verification of this result involves deliver the same event concurrently and verify one invoice record and one downstream send.

Run the migration and create/read/delete workflow in CI with an isolated database. That check cannot demonstrate deliver the same event concurrently and verify one invoice record and one downstream send.

Question 388

During troubleshooting, investigators observe: Concurrent retries insert duplicate rows despite passing sequential tests. The system context is: A controller posts an invoice twice when the upstream webhook retries the same event ID. Which ONE cause most directly explains the observed failure?

Unit isolation did not validate integration across schema and data layers.
Tests based only on happy-path integers missed precision behavior.
The test suite did not cover duplicate delivery under race conditions.
The existing examples did not probe normalization and boundary behavior.

Explanation

Correct Answer

The remedy should therefore be: Ask Copilot to add an idempotency regression test plus a minimal deduplication implementation. The missing change involves the test suite did not cover duplicate delivery under race conditions.

Incorrect Answers

Unit isolation did not validate integration across schema and data layers. The test suite did not cover duplicate delivery under race conditions.

Tests based only on happy-path integers missed precision behavior. The test suite did not cover duplicate delivery under race conditions.

The existing examples did not probe normalization and boundary behavior. The test suite did not cover duplicate delivery under race conditions.

Question 389

The current design is: Ask Copilot to add an idempotency regression test plus a minimal deduplication implementation. The prior failure was: Concurrent retries insert duplicate rows despite passing sequential tests. Which ONE ongoing control best protects against recurrence of that specific failure?

Keep independent decimal boundary fixtures to validate AI-generated tests.
Retain concurrency and duplicate-event tests on every billing release.
Keep security-relevant URL parsing tests separate from generation prompts.
Maintain a repeatable integration test environment and migration checkpoints.

Explanation

Correct Answer

Retain concurrency and duplicate-event tests on every billing release.

Incorrect Answers

Approved dependency sources and lockfiles protect builds against invented or impersonated packages. Preventing this failure involves retain concurrency and duplicate-event tests on every billing release.

Generated code requires independently defined acceptance tests and review against the real program contract. Preventing this failure involves retain concurrency and duplicate-event tests on every billing release. The observed condition is ask Copilot to add an idempotency regression test plus a minimal deduplication implementation. The prior failure was: Concurrent retries insert duplicate rows.

Question 390

A team reports: A team uses Copilot to generate API mocks, but they return success for cases in which production returns 429. They observe: The client floods the service after rate limiting. Which ONE technical decision most directly corrects the cause?

Ask Copilot to propose parameterized tests with zero, negative, huge and fractional-precision inputs tied to the contract.
Use Copilot to draft integration tests against an ephemeral test database and real schema migrations.
Prompt Copilot for explicit edge-case assertions rather than another implementation rewrite.
Model rate limits and retry-after headers in mocks using the provider's real contract.

Explanation

Correct Answer

Confirm it by checking: Run backoff tests and confirm bounded exponential retry behavior on 429 responses.

Incorrect Answers

Asking Copilot to propose parameterized tests with zero, negative, huge and fractional-precision inputs tied to the contract would not address the need for model rate limits and retry-after headers in mocks using the provider's real contract.

Using Copilot to draft integration tests against an ephemeral test database and real schema migrations would not address the need for model rate limits and retry-after headers in mocks using the provider's real contract.

Prompting Copilot for explicit edge-case assertions rather than another implementation rewrite would not address the need for model rate limits and retry-after headers in mocks using the provider's real contract.

GitHub Copilot (GH-300) Practice Tests

Microsoft GH-300 Practice Test 37 - 10 Questions (Last Reviewed 08-Oct-2026)
Microsoft GH-300 Practice Test 38 - 10 Questions (Last Reviewed 07-Oct-2026)
Microsoft GH-300 Practice Test 39 - 10 Questions (Last Reviewed 06-Oct-2026)
Microsoft GH-300 Practice Test 40 - 10 Questions (Last Reviewed 05-Oct-2026)
Microsoft GH-300 Practice Test 41 - 10 Questions (Last Reviewed 04-Oct-2026)

Pass Your Microsoft GH-300 Exam Easy!

Question 380

Explanation

Correct Answer

Incorrect Answers

Question 381

Explanation

Correct Answer

Incorrect Answers

Question 382

Explanation

Correct Answer

Incorrect Answers

Question 383

Explanation

Correct Answer

Incorrect Answers

Question 384

Explanation

Correct Answer

Incorrect Answers

Question 385

Explanation

Correct Answer

Incorrect Answers

Question 386

Explanation

Correct Answer

Incorrect Answers

Question 387

Explanation

Correct Answer

Incorrect Answers

Question 388

Explanation

Correct Answer

Incorrect Answers

Question 389

Explanation

Correct Answer

Incorrect Answers

Question 390

Explanation

Correct Answer

Incorrect Answers

GitHub Copilot (GH-300) Practice Tests