Microsoft GH-300 Practice Test 43
Question 420
A Copilot performance patch introduces caching and parallel database calls. Which THREE measurements are needed before approving its claimed speedup? (Select THREE.)
- Observe backend connection saturation, error rate, and queueing under concurrency.
- Ignore data correctness if throughput increases.
- Check cache hit rate, invalidation, and memory utilization.
- Test only a single tiny input that bypasses the cache.
- Measure before-and-after end-to-end latency on representative traffic.
- Trust the generated complexity claim without profiling.
Explanation
Correct Answers
A:Extra parallelism can overload shared dependencies.
C:Cache behavior determines whether its benefit survives real workloads.
E:The optimization must improve observed user-level performance.
Incorrect Answers
B:Performance must not compromise business integrity.
D:Nonrepresentative samples cannot validate the design.
F:Model prose is not a measured system property.
Question 421
A generated test file was committed but never run in CI. What is missing?
- Execute it in the approved pipeline and retain the actual test outcome.
- Capture the executed command, exit status, and relevant run artifacts.
- Add direct branch-level negative tests and review the uncovered path.
- Inject a controllable clock and assert deterministic timestamps.
Explanation
Correct Answer
A:Source code for tests is not evidence of execution.
Incorrect Answers
B:A success claim without execution evidence is not a release gate. source code for tests is not evidence of execution.
C:Aggregate coverage percentages can mask critical untested logic. What is missing. Source code for tests is not evidence of execution.
D:Stable time dependencies prevent nondeterministic CI failures. source code for tests is not evidence of execution.
Question 422
A Copilot-written test asserts the same output produced by the function under test. What should be changed?
- Execute it in the approved pipeline and retain the actual test outcome.
- Use independent expected values or a trusted oracle.
- Add direct branch-level negative tests and review the uncovered path.
- Inject a controllable clock and assert deterministic timestamps.
Explanation
Correct Answer
B:Circular expected values can validate the same bug twice.
Incorrect Answers
A:Source code for tests is not evidence of execution. Circular expected values can validate the same bug twice.
C:Aggregate coverage percentages can mask critical untested logic. What should be changed. Circular expected values can validate the same bug twice.
D:Stable time dependencies prevent nondeterministic CI failures. circular expected values can validate the same bug twice.
Question 423
An agent says all tests pass but provides no command or log. What should the reviewer request?
- Capture the executed command, exit status, and relevant run artifacts.
- Use independent expected values or a trusted oracle.
- Execute it in the approved pipeline and retain the actual test outcome.
- Inject a controllable clock and assert deterministic timestamps.
Explanation
Correct Answer
A:A success claim without execution evidence is not a release gate.
Incorrect Answers
B:Circular expected values can validate the same bug twice. a success claim without execution evidence is not a release gate.
C:Source code for tests is not evidence of execution. A success claim without execution evidence is not a release gate.
D:Stable time dependencies prevent nondeterministic CI failures. a success claim without execution evidence is not a release gate.
Question 424
A test suite passes but coverage excludes a security-sensitive branch. What should happen?
- Add direct branch-level negative tests and review the uncovered path.
- Capture the executed command, exit status, and relevant run artifacts.
- Use independent expected values or a trusted oracle.
- Execute it in the approved pipeline and retain the actual test outcome.
Explanation
Correct Answer
A:Aggregate coverage percentages can mask critical untested logic.
Incorrect Answers
B:A success claim without execution evidence is not a release gate. What should happen. Aggregate coverage percentages can mask critical untested logic.
C:Circular expected values can validate the same bug twice. aggregate coverage percentages can mask critical untested logic.
D:Source code for tests is not evidence of execution. Aggregate coverage percentages can mask critical untested logic.
Question 425
A generated regression test is flaky due to current time. What should be corrected?
- Inject a controllable clock and assert deterministic timestamps.
- Capture the executed command, exit status, and relevant run artifacts.
- Use independent expected values or a trusted oracle.
- Add direct branch-level negative tests and review the uncovered path.
Explanation
Correct Answer
A:Stable time dependencies prevent nondeterministic CI failures.
Incorrect Answers
B:A success claim without execution evidence is not a release gate. What should be corrected. Stable time dependencies prevent nondeterministic CI failures.
C:Circular expected values can validate the same bug twice. stable time dependencies prevent nondeterministic CI failures.
D:Aggregate coverage percentages can mask critical untested logic. stable time dependencies prevent nondeterministic CI failures.
Question 426
An organization must prevent supported Copilot features from using files under `secrets/`. What configuration should admins evaluate?
- Set scoped repository-path content exclusion rules in the organization or enterprise settings.
- Use the authorized GitHub content exclusion settings rather than an informal comment.
- Verify that exclusion patterns cover supported nonrepository filesystem paths where needed.
- Test the exclusion rule against the intended paths and correct its matching syntax.
Explanation
Correct Answer
A:Managed exclusions specify which sources compatible clients should omit from context.
Incorrect Answers
B:Administrative policy is distinct from source text. Managed exclusions specify which sources compatible clients should omit from context.
C:Repo-based patterns alone may not describe every local source location. What configuration should admins evaluate. Managed exclusions specify which sources compatible clients should omit from context.
D:A configured rule is not effective if it fails to match the target files. managed exclusions specify which sources compatible clients should omit from context.
Question 427
A team wants to exclude one confidential config file but not the whole repository. What should it define?
- Test the exclusion rule against the intended paths and correct its matching syntax.
- Use the authorized GitHub content exclusion settings rather than an informal comment.
- Specify the precise supported file path or pattern rather than an entire-repo exclusion.
- Set scoped repository-path content exclusion rules in the organization or enterprise settings.
Explanation
Correct Answer
C:Narrow paths protect the sensitive file while preserving useful code context.
Incorrect Answers
A:A configured rule is not effective if it fails to match the target files. narrow paths protect the sensitive file while preserving useful code context.
B:Administrative policy is distinct from source text. Narrow paths protect the sensitive file while preserving useful code context.
D:Managed exclusions specify which sources compatible clients should omit from context. narrow paths protect the sensitive file while preserving useful code context.
Question 428
A repository's copied secrets are in an untracked local folder. What must admins check?
- Use the authorized GitHub content exclusion settings rather than an informal comment.
- Set scoped repository-path content exclusion rules in the organization or enterprise settings.
- Verify that exclusion patterns cover supported nonrepository filesystem paths where needed.
- Configure an exclusion for an unrelated tracked repository and assume it covers this local directory.
Explanation
Correct Answer
C:Repo-based patterns alone may not describe every local source location.
Incorrect Answers
A:Administrative policy is distinct from source text. Repo-based patterns alone may not describe every local source location.
B:Managed exclusions specify which sources compatible clients should omit from context. repo-based patterns alone may not describe every local source location.
D:Excluding a different repository does not establish protection for an untracked local folder that was outside that rule.
Question 429
A new organization policy excludes the wrong folder due to a pattern typo. What should be done?
- Set scoped repository-path content exclusion rules in the organization or enterprise settings.
- Specify the precise supported file path or pattern rather than an entire-repo exclusion.
- Test the exclusion rule against the intended paths and correct its matching syntax.
- Verify that exclusion patterns cover supported nonrepository filesystem paths where needed.
Explanation
Correct Answer
C:A configured rule is not effective if it fails to match the target files.
Incorrect Answers
A:Managed exclusions specify which sources compatible clients should omit from context. a configured rule is not effective if it fails to match the target files.
B:Narrow paths protect the sensitive file while preserving useful code context. What should be done. A configured rule is not effective if it fails to match the target files.
D:Repo-based patterns alone may not describe every local source location. a configured rule is not effective if it fails to match the target files.
Question 430
A Copilot Business administrator needs to exclude a sensitive repository subfolder without blocking the entire source tree. Which TWO steps fit? (Select TWO.)
- Assume the exclusion automatically applies to every MCP tool and agent.
- Test the rule in a client and feature that documents enforcement support.
- Configure a precise supported content-exclusion path pattern through administrative settings.
- Make the entire repository public to simplify policy troubleshooting.
- Put a comment in the confidential file asking Copilot not to read it.
Explanation
Correct Answers
B:A saved path rule is not proof of correct matching and client coverage.
C:Narrow patterns target confidential files without suppressing unrelated code.
Incorrect Answers
A:Documented support excludes some modes and third-party integrations.
D:Publication is unrelated and would expose sensitive code.
E:A source comment is not enforceable administrative policy.