Microsoft MB-500 Practice Test 2
Question 10
After a candidate repair, a sandbox engineer after configuration changes needs acceptance evidence for this issue: A new menu item is visible to every employee even though the underlying function is privileged. Which outcome demonstrates the required behavior?
- The auditor's queries return company A records only and deny company B
- An unauthorized user cannot invoke the menu action directly or through navigation
- Job logs identify the restricted service principal and deny unauthorized deployment actions
- Role tests demonstrate that creators cannot approve the same controlled payment
Explanation
Correct Answer
B:An unauthorized user cannot invoke the menu action directly or through navigation. Removing the menu tile alone may leave direct execution accessible. This observes the intended end-to-end behavior rather than only an implementation activity.
Incorrect Answers
A:Changing the company's selector alone does not restrict authorized access. Even a successful observation could leave the original defect unresolved because removing the menu tile alone may leave direct execution accessible.
C:A clean run under shared admin credentials does not prove the safer identity model. The required acceptance test must go further: removing the menu tile alone may leave direct execution accessible.
D:An approval email without enforced security can still permit self-approval. Passing that check would not establish the stated outcome; removing the menu tile alone may leave direct execution accessible.
Question 11
A technical review by a solution consultant preparing a reproducible defect uncovers this incident: A new subclass inherits behavior but must implement a required abstract calculation. Which remedy best resolves it?
- Attach the listener to the appropriate delegate or event subscription contract
- Check available extension mechanisms and use a supported extension point rather than modifying vendor code
- Implement the abstract member using the declared signature and business contract
- Decorate the implementation with the supported attribute and register the intended contract
Explanation
Correct Answer
C:Implement the abstract member using the declared signature and business contract. An abstract base contract cannot be instantiated through an incomplete concrete subclass. The supplied symptoms make this the decisive implementation step.
Incorrect Answers
A:A callback must be wired to the designated publisher and event payload. Applying that approach would leave the observed path uncorrected because an abstract base contract cannot be instantiated through an incomplete concrete subclass.
B:Extensibility limits are governed by the target element's exposure and compatibility. The reported symptoms instead require the behavior described here: an abstract base contract cannot be instantiated through an incomplete concrete subclass.
D:Metadata-based discovery depends on correct attributes and compatible interfaces. The proposed action does not remove the stated failure; an abstract base contract cannot be instantiated through an incomplete concrete subclass.
Question 12
A technical review by a solution consultant preparing a reproducible defect uncovers this incident: Two feature branches both modify the same extension method and the merge reports an overlap. Which remedy best resolves it?
- Pin the pipeline to an immutable build identifier and record artifact checksums
- Submit the change through the approved review and protected-branch policy
- Revoke the exposed credential and move secret handling to a controlled vault-backed process
- Resolve the conflict against reviewed business behavior and run the merged build and tests
Explanation
Correct Answer
D:Resolve the conflict against reviewed business behavior and run the merged build and tests. A text merge is not proof that the combined X++ semantics remain correct. The supplied symptoms make this the decisive implementation step.
Incorrect Answers
A:Names alone cannot prove that two deployments use the same binary artifact. Applying that approach would leave the observed path uncorrected because a text merge is not proof that the combined X++ semantics remain correct.
B:Source control review is a production quality and provenance control. The proposed action does not remove the stated failure; a text merge is not proof that the combined X++ semantics remain correct.
C:Removing a value from the latest commit does not undo potential exposure in prior history. The reported symptoms instead require the behavior described here: a text merge is not proof that the combined X++ semantics remain correct.
Question 13
A developer reviewing the latest integration failure is evaluating a proposed fix for this problem: A cross-company job unexpectedly changes records owned by a different legal entity. Which result demonstrates the intended behavior?
- Tests show target-company records change while an out-of-scope company's records remain untouched
- A multi-record test produces only each record's own payload with bounded memory behavior
- The required validations pass and measured query or row-operation counts drop on a representative workload
- A concurrent test preserves both intended changes or returns a controlled conflict without data loss
Explanation
Correct Answer
A:Tests show target-company records change while an out-of-scope company's records remain untouched. Checking only a global affected-row count hides company leakage. This observes the intended end-to-end behavior rather than only an implementation activity.
Incorrect Answers
B:A one-record test cannot reveal stale state reuse. Even a successful observation could leave the original defect unresolved because checking only a global affected-row count hides company leakage.
C:An unmeasured speed claim does not establish safe set-based equivalence. Passing that check would not establish the stated outcome; checking only a global affected-row count hides company leakage.
D:A single-user test cannot expose the race condition. The required acceptance test must go further: checking only a global affected-row count hides company leakage.
Question 14
A breakpoint in a custom X++ handler never binds even though users reach the associated business process. Before accepting the remediation, which result should a deployment engineer before an overnight release verify?
- The project compiles cleanly and resolves the referenced type without copying its source
- The breakpoint binds and is hit by a reproducible transaction in the target environment
- The target schema contains the field and an application transaction reads and writes it successfully
- Both developers see the same object identity and commit revision after metadata refresh
Explanation
Correct Answer
B:The breakpoint binds and is hit by a reproducible transaction in the target environment. A successful compile on a different machine cannot establish runtime symbol alignment. This observes the intended end-to-end behavior rather than only an implementation activity.
Incorrect Answers
A:Duplicating the original class would introduce conflicting ownership. Passing that check would not establish the stated outcome; a successful compile on a different machine cannot establish runtime symbol alignment.
C:Seeing the field in Application Explorer proves metadata presence only. The required acceptance test must go further: a successful compile on a different machine cannot establish runtime symbol alignment.
D:Changing an unrelated compiler option does not reconcile source versions. Even a successful observation could leave the original defect unresolved because a successful compile on a different machine cannot establish runtime symbol alignment.
Question 15
A complex SSRS report runs a per-row lookup for each of twenty thousand lines. Before accepting the remediation, which result should a sandbox engineer after configuration changes verify?
- A repeat trace shows reduced elapsed time for the identified query without business regression
- A measured full-volume run completes within target with no duplicate or missed orders
- The rendered report reconciles to the baseline while trace counts scale acceptably at high volume
- Representative query plans and write benchmarks improve overall cost without unacceptable insert overhead
Explanation
Correct Answer
C:The rendered report reconciles to the baseline while trace counts scale acceptably at high volume. Lowering the displayed page length could hide continued expensive backend access. This observes the intended end-to-end behavior rather than only an implementation activity.
Incorrect Answers
A:Restarting the environment may temporarily change cache timing without fixing the query. Passing that check would not establish the stated outcome; lowering the displayed page length could hide continued expensive backend access.
B:A high CPU percentage alone does not prove correct partitioning. Even a successful observation could leave the original defect unresolved because lowering the displayed page length could hide continued expensive backend access.
D:A faster single read cannot establish workload-wide index benefit. The required acceptance test must go further: lowering the displayed page length could hide continued expensive backend access.
Question 16
The following issue is under review by a sandbox engineer after configuration changes: A new menu item is visible to every employee even though the underlying function is privileged. Which engineering response best addresses this failure?
- Replace shared privileged credentials with a scoped service identity and controlled pipeline secrets
- Separate the creation and approval duties and test the effective user roles
- Apply company-scoped role assignment and verify underlying data permissions
- Secure the entry point through the proper privileges and role assignments
Explanation
Correct Answer
D:Secure the entry point through the proper privileges and role assignments. Menu visibility and execution access are governed by security metadata, not button color or labels. The proposed change is tied to the observed failure, not merely to a general deployment preference.
Incorrect Answers
A:Administrative credentials in automation broaden compromise impact and weaken attribution. The proposed action does not remove the stated failure; menu visibility and execution access are governed by security metadata, not button color or labels.
B:Separation of duties prevents one identity from completing incompatible financial actions. Applying that approach would leave the observed path uncorrected because menu visibility and execution access are governed by security metadata, not button color or labels.
C:Legal-entity access requires explicit authorization, not a default global role. The reported symptoms instead require the behavior described here: menu visibility and execution access are governed by security metadata, not button color or labels.
Question 17
In a retest by a compliance tester examining security boundaries, the original problem was: An Azure integration app stores a finance endpoint secret in a plaintext configuration repository. Which observation offers the strongest proof of resolution?
- The runtime retrieves a rotated secret under its managed identity while unprivileged identities are denied
- Dataverse users see current authorized source records without duplicate finance ledger rows
- Duplicate test notifications produce one effective approval request and a logged replay outcome
- Edits from each permitted system propagate once with the agreed conflict result
Explanation
Correct Answer
A:The runtime retrieves a rotated secret under its managed identity while unprivileged identities are denied. Encrypting a file in source control without rotation controls is insufficient. This observes the intended end-to-end behavior rather than only an implementation activity.
Incorrect Answers
B:A dual-write job showing a replicated copy would not meet the no-copy goal. The required acceptance test must go further: encrypting a file in source control without rotation controls is insufficient.
C:A working single event does not test duplicate delivery. Even a successful observation could leave the original defect unresolved because encrypting a file in source control without rotation controls is insufficient.
D:A one-way initial export cannot prove bidirectional synchronization. Passing that check would not establish the stated outcome; encrypting a file in source control without rotation controls is insufficient.
Question 18
A helper variable declared in a method is being accessed from a different class instance. Before accepting the remediation, which result should a product owner reviewing a go-live blocker verify?
- The extension compiles using a documented supported hook without patching base source
- Compilation and a multi-instance test confirm values are conveyed without accidental shared state
- A factory test resolves the intended class and calls its override for the requested configuration
- The subscriber receives the exact parameters and executes once during the intended event
Explanation
Correct Answer
B:Compilation and a multi-instance test confirm values are conveyed without accidental shared state. A global static variable would change the state and concurrency semantics. This observes the intended end-to-end behavior rather than only an implementation activity.
Incorrect Answers
A:Suppressing compiler diagnostics does not make an unsupported wrapper safe. Even a successful observation could leave the original defect unresolved because a global static variable would change the state and concurrency semantics.
C:Renaming the base variable cannot change the constructed type. The required acceptance test must go further: a global static variable would change the state and concurrency semantics.
D:A standalone call to the subscriber bypasses actual wiring. Passing that check would not establish the stated outcome; a global static variable would change the state and concurrency semantics.
Question 19
In a retest by a technical lead checking production readiness, the original problem was: A query scans all historical invoices despite an exact company and status filter in the request. Which observation offers the strongest proof of resolution?
- Measured operation counts and functional regression tests show faster processing with unchanged results
- Repeated lookups reduce database calls and reflect changes after the documented invalidation
- The plan shows reduced examined rows and the same authorized result set
- Load tests show bounded retries and no lost updates under concurrent posting
Explanation
Correct Answer
C:The plan shows reduced examined rows and the same authorized result set. A smaller UI page size can hide a large backend scan. This observes the intended end-to-end behavior rather than only an implementation activity.
Incorrect Answers
A:A stopwatch improvement alone cannot prove all business hooks remained correct. Passing that check would not establish the stated outcome; a smaller UI page size can hide a large backend scan.
B:A fast warm-cache test without update coverage can hide stale results. The required acceptance test must go further: a smaller UI page size can hide a large backend scan.
D:A single-threaded benchmark cannot establish concurrency safety. Even a successful observation could leave the original defect unresolved because a smaller UI page size can hide a large backend scan.
Question 20
A service credential was mistakenly committed to a repository with several read-only collaborators. Which test result should a finance application support team during issue triage require before closing the defect?
- The prior approved service behavior returns and the rollback record identifies package and data compatibility
- The pull request shows authorized review and the resulting build links to the approved commit
- A reviewed merge commit builds and both feature-specific tests pass on the result
- The old credential is rejected, the new secret is not in source, and the pipeline accesses it through approved controls
Explanation
Correct Answer
D:The old credential is rejected, the new secret is not in source, and the pipeline accesses it through approved controls. A repository search with no current match does not prove the leaked key is safe. This observes the intended end-to-end behavior rather than only an implementation activity.
Incorrect Answers
A:Reverting source code without deploying a compatible artifact may not restore service. Passing that check would not establish the stated outcome; a repository search with no current match does not prove the leaked key is safe.
B:A developer's successful manual deployment cannot substitute for review traceability. The required acceptance test must go further: a repository search with no current match does not prove the leaked key is safe.
C:Choosing the newest file mechanically can silently discard a feature. Even a successful observation could leave the original defect unresolved because a repository search with no current match does not prove the leaked key is safe.