Microsoft MB-500 Practice Test 15
Question 140
After a candidate repair, a source-control reviewer validating the candidate build needs acceptance evidence for this issue: A collections workspace shows overdue totals but analysts cannot reach the underlying disputed invoices. Which outcome demonstrates the required behavior?
- The KPI updates within the agreed delay after a controlled test posting
- A selected alert opens the matching return document, even when multiple returns exist
- User-role tests show no cross-company amounts in widgets or drill-through pages
- Selecting the overdue KPI opens exactly the relevant accessible invoices
Explanation
Correct Answer
D:Selecting the overdue KPI opens exactly the relevant accessible invoices. Seeing a correct total alone does not establish useful navigation. This observes the intended end-to-end behavior rather than only an implementation activity.
Incorrect Answers
A:A manual browser reload once per day does not meet a shorter freshness objective. Even a successful observation could leave the original defect unresolved because seeing a correct total alone does not establish useful navigation.
B:A link to the general menu does not verify contextual navigation. The required acceptance test must go further: seeing a correct total alone does not establish useful navigation.
C:A hidden tile alone can leave data exposed through the destination. Passing that check would not establish the stated outcome; seeing a correct total alone does not establish useful navigation.
Question 141
After a candidate repair, a deployment engineer before an overnight release needs acceptance evidence for this issue: A release artifact has the same friendly version label as last week's build but different compiled bytes. Which outcome demonstrates the required behavior?
- The target deployment points to the exact immutable build and checksum accepted in testing
- A reviewed merge commit builds and both feature-specific tests pass on the result
- A clean build agent produces a working package from the documented commit and dependencies
- The old credential is rejected, the new secret is not in source, and the pipeline accesses it through approved controls
Explanation
Correct Answer
A:The target deployment points to the exact immutable build and checksum accepted in testing. In the stated validation context, the decisive fact is: A release artifact has the same friendly version label as last week's build but different compiled bytes.
Incorrect Answers
B:Choosing the newest file mechanically can silently discard a feature. The required acceptance test must go further: equal folder names do not guarantee equal deployable content.
C:A clean build agent produces a working package from the documented commit and dependencies. This would not resolve the reported condition: A release artifact has the same friendly version label as last week's build but different compiled bytes. The relevant validation for this case is: The target deployment points to the exact immutable build and checksum accepted in testing.
D:A repository search with no current match does not prove the leaked key is safe. Passing that check would not establish the stated outcome; equal folder names do not guarantee equal deployable content.
Question 142
A warehouse team wants to reproduce a screen-driven process across builds. During the next test cycle, a finance application support team during issue triage must select a corrective action. Which is best?
- Discover and run the intended class through Test Explorer or the configured test runner
- Use Task recorder to capture the supported user workflow and maintain repeatable playback prerequisites
- Add SysTest boundary and negative-path tests for rejected invalid discounts
- Wait for a supported terminal job state and then assert the persisted business result
Explanation
Correct Answer
B:Use Task recorder to capture the supported user workflow and maintain repeatable playback prerequisites. In the stated repair context, the decisive fact is: A warehouse team wants to reproduce a screen-driven process across builds.
Incorrect Answers
A:Discover and run the intended class through Test Explorer or the configured test runner. This would not resolve the reported condition: A warehouse team wants to reproduce a screen-driven process across builds. The relevant repair for this case is: Use Task recorder to capture the supported user workflow and maintain repeatable playback prerequisites.
C:Unit tests must cover rejection semantics and side effects as well as happy-path outputs. The reported symptoms instead require the behavior described here: a recorded task can document UI flow but needs stable environment and data assumptions.
D:Wait for a supported terminal job state and then assert the persisted business result. This would not resolve the reported condition: A warehouse team wants to reproduce a screen-driven process across builds. The relevant repair for this case is: Use Task recorder to capture the supported user workflow and maintain repeatable playback prerequisites.
Question 143
A customer needs a risk classification on the standard vendor record while keeping upgrade-safe schema ownership. Before accepting the remediation, which result should a role-based security tester in preproduction verify?
- A duplicate within the protected scope is rejected while permitted numbers in another scope remain valid
- Reimporting a mapped sample updates or rejects duplicates according to the documented key policy
- The extended field persists across create and update operations after schema synchronization
- The projected columns return the expected joined values for several suppliers
Explanation
Correct Answer
C:The extended field persists across create and update operations after schema synchronization. Creating an unrelated table without a relationship would not meet the vendor-record requirement. This observes the intended end-to-end behavior rather than only an implementation activity.
Incorrect Answers
A:A UI-only warning is insufficient for concurrent imports. Even a successful observation could leave the original defect unresolved because creating an unrelated table without a relationship would not meet the vendor-record requirement.
B:A single first-time import cannot test entity identity handling. The required acceptance test must go further: creating an unrelated table without a relationship would not meet the vendor-record requirement.
D:A materialized duplicate could become inconsistent after updates. Passing that check would not establish the stated outcome; creating an unrelated table without a relationship would not meet the vendor-record requirement.
Question 144
A developer sees a new SysTest class in source but no executed tests in the build report. The issue is being triaged by a release manager checking the implementation checklist. What should the developer change first?
- Isolate the legal-entity setup and assert access in each intended company context
- Wait for a supported terminal job state and then assert the persisted business result
- Add SysTest boundary and negative-path tests for rejected invalid discounts
- Discover and run the intended class through Test Explorer or the configured test runner
Explanation
Correct Answer
D:Discover and run the intended class through Test Explorer or the configured test runner. A test's source existence is not evidence it executed successfully. The supplied symptoms make this the decisive implementation step.
Incorrect Answers
A:Multi-company tests must make data scope explicit to avoid false positives. Applying that approach would leave the observed path uncorrected because a test's source existence is not evidence it executed successfully.
B:Queue acceptance is not the same event as completed execution. The reported symptoms instead require the behavior described here: a test's source existence is not evidence it executed successfully.
C:Unit tests must cover rejection semantics and side effects as well as happy-path outputs. The proposed action does not remove the stated failure; a test's source existence is not evidence it executed successfully.
Question 145
A technical review by a migration engineer reviewing a failed mapping uncovers this incident: A director expects minute-by-minute order status but the proposed analytics dataset refreshes only every four hours. Which remedy best resolves it?
- Set a supported reporting pattern and explicit freshness service objective for the needed latency
- Select an operational reporting source and supported SSRS-style report design appropriate to transaction detail
- Enforce the intended report and source-data permissions rather than hiding the menu item alone
- Evaluate Electronic reporting configurations and version-controlled format mapping
Explanation
Correct Answer
A:Set a supported reporting pattern and explicit freshness service objective for the needed latency. Report platform selection must account for data staleness and expected updates. This directly addresses the configuration or execution path described.
Incorrect Answers
B:Operational documents require authorized transaction data and reproducible parameters. Applying that approach would leave the observed path uncorrected because report platform selection must account for data staleness and expected updates.
C:Access control must apply to report execution and underlying data. The reported symptoms instead require the behavior described here: report platform selection must account for data staleness and expected updates.
D:Regulatory interchange structure is not merely a printable dashboard style. The proposed action does not remove the stated failure; report platform selection must account for data staleness and expected updates.
Question 146
A product owner reviewing a go-live blocker is evaluating a proposed fix for this problem: A batch validation test ends before the asynchronous job has committed its business transaction. Which result demonstrates the intended behavior?
- The replay reaches the expected final document state in a clean test environment
- The test observes the completed batch state and verifies committed records and error logs
- The run report lists the expected methods, outcomes, and build identifier
- Separate company tests prove the write is visible only under the authorized scope
Explanation
Correct Answer
B:The test observes the completed batch state and verifies committed records and error logs. Checking that a job ID was returned proves only scheduling. This observes the intended end-to-end behavior rather than only an implementation activity.
Incorrect Answers
A:A recording opening the right menu alone does not prove the process completed. Even a successful observation could leave the original defect unresolved because checking that a job ID was returned proves only scheduling.
C:Merely compiling the test project is not an execution result. The required acceptance test must go further: checking that a job ID was returned proves only scheduling.
D:A system administrator query without company controls can hide the defect. Passing that check would not establish the stated outcome; checking that a job ID was returned proves only scheduling.
Question 147
An external calculation in a user transaction often hangs while waiting for a remote API. During the next test cycle, a test lead during a high-volume regression cycle must select a corrective action. Which is best?
- Optimize the report data provider or query to avoid N-plus-one database access
- Use the trace and query plan to target the high-cost operation before changing unrelated code
- Isolate long work with a supported asynchronous or sandboxed execution pattern where appropriate
- Partition independent work safely into supported batch tasks with clear transaction boundaries
Explanation
Correct Answer
C:Isolate long work with a supported asynchronous or sandboxed execution pattern where appropriate. Interactive threads should not be blocked by unpredictable external latency. This directly addresses the configuration or execution path described.
Incorrect Answers
A:Repeated row lookups cause nonlinear query volume as report size grows. Applying that approach would leave the observed path uncorrected because interactive threads should not be blocked by unpredictable external latency.
B:Performance work should follow measured hotspots and execution evidence. The reported symptoms instead require the behavior described here: interactive threads should not be blocked by unpredictable external latency.
D:Parallelism helps only when records and business dependencies permit safe separation. The proposed action does not remove the stated failure; interactive threads should not be blocked by unpredictable external latency.
Question 148
An operations specialist before the next maintenance window finds the following release risk: An accountant wants an editable tabular export of permitted supplier balances using familiar Office tools. Which implementation is justified?
- Apply security and query scoping to the report data provider and verify end-to-end execution
- Identify the dataset refresh or connection behavior and align the refresh policy with business expectations
- Define and implement inclusive boundary semantics for report parameters and underlying query
- Implement the supported Excel integration or export on an authorized entity or data source
Explanation
Correct Answer
D:Implement the supported Excel integration or export on an authorized entity or data source. Excel is suitable for controlled tabular work but should respect data access and integration contracts. The proposed change is tied to the observed failure, not merely to a general deployment preference.
Incorrect Answers
A:Report logic must not bypass company and authorization filtering. The reported symptoms instead require the behavior described here: excel is suitable for controlled tabular work but should respect data access and integration contracts.
B:A correct finance posting does not automatically refresh every analytics model. The proposed action does not remove the stated failure; excel is suitable for controlled tabular work but should respect data access and integration contracts.
C:Date-time boundaries must match the business meaning of inclusive report periods. Applying that approach would leave the observed path uncorrected because excel is suitable for controlled tabular work but should respect data access and integration contracts.
Question 149
A financial report works for administrators but discloses restricted salary rows to an ordinary manager. The issue is being triaged by an operations specialist before the next maintenance window. What should the developer change first?
- Enforce the intended report and source-data permissions rather than hiding the menu item alone
- Select a secure reporting datastore or data source with explicit legal-entity filtering
- Select an operational reporting source and supported SSRS-style report design appropriate to transaction detail
- Set a supported reporting pattern and explicit freshness service objective for the needed latency
Explanation
Correct Answer
A:Enforce the intended report and source-data permissions rather than hiding the menu item alone. Access control must apply to report execution and underlying data. The proposed change is tied to the observed failure, not merely to a general deployment preference.
Incorrect Answers
B:Data architecture for reporting must preserve data boundaries across joins and storage tiers. Applying that approach would leave the observed path uncorrected because access control must apply to report execution and underlying data.
C:Operational documents require authorized transaction data and reproducible parameters. The proposed action does not remove the stated failure; access control must apply to report execution and underlying data.
D:Report platform selection must account for data staleness and expected updates. The reported symptoms instead require the behavior described here: access control must apply to report execution and underlying data.
Question 150
A deployment engineer before an overnight release is evaluating a proposed fix for this problem: A new discount rule passes positive examples but accepts a discount above the contract maximum. Which result demonstrates the intended behavior?
- The replay reaches the expected final document state in a clean test environment
- The invalid discount test fails before the fix and passes afterward without persisting an unauthorized value
- The run report lists the expected methods, outcomes, and build identifier
- The test passes in isolation and when run in a different order with predictable fixtures
Explanation
Correct Answer
B:The invalid discount test fails before the fix and passes afterward without persisting an unauthorized value. A happy-path assertion cannot establish input rejection. This observes the intended end-to-end behavior rather than only an implementation activity.
Incorrect Answers
A:A recording opening the right menu alone does not prove the process completed. The required acceptance test must go further: a happy-path assertion cannot establish input rejection.
C:Merely compiling the test project is not an execution result. Passing that check would not establish the stated outcome; a happy-path assertion cannot establish input rejection.
D:Repeatedly running the same order masks shared-state coupling. Even a successful observation could leave the original defect unresolved because a happy-path assertion cannot establish input rejection.