Free MB-820 Practice Questions (12 Scenario Questions)

Correct: A. Multi-root workspaces are the AL/VS Code mechanism explicitly named in the objectives for managing multiple AL extensions in one workspace. Merging into a single app.json misrepresents two independently versioned, dependency-linked apps as one app. Running two launch configurations manually, one at a time, doesn't satisfy working with both together. AL doesn't structure separate extensions as objects crammed into one file.

Correct: A. Event subscribers on publisher events are exactly the extensibility pattern the objectives name ("use events and triggers") for reacting to base app actions without touching its source. Copying and modifying base app code isn't how the extension model works and breaks on the next update. Adding a field doesn't create behavior by itself — it needs code behind it, which is the point being tested. Polling every minute is an inefficient workaround that ignores the native event model AL already provides.

Correct: A. AL interfaces — a named objective under "develop codeunits" — let you define a contract once and swap implementations (one codeunit per carrier) without ever changing the calling code. A branching case statement still requires editing the same codeunit every time a carrier is added. A table of hardcoded costs stores data, not calculation logic. A single procedure with a parameter still centralizes and couples every carrier's logic in one place, needing edits for each addition — the opposite of swappable.

Correct: A. Permission sets are the mechanism for scoping object access at different granularities to different users — exactly what "create and extend permission sets" covers. A single blanket permission set can't support a minimal-access basic tier. Entitlements map licensed features to permission sets and grant inherent permissions; they don't replace the underlying access definition, so an entitlement alone doesn't solve the granularity requirement either way.

Correct: A. Error() halts execution and rolls back the current transaction while showing the message to the user — the standard way to enforce a hard validation rule, under the "manage errors" objective. Message() only displays informational text without stopping anything. Session.LogMessage() writes a telemetry event, unrelated to blocking user action. Confirm() prompts for a yes/no choice; it doesn't itself enforce a stop or a rollback the way Error() does.

Correct: A. Read Scale-Out is the platform feature specifically for routing read-only report and API traffic to a secondary replica, reducing load on the primary database — directly the "use Read Scale-Out to improve performance" objective. A bound OData action triggers an operation on a record; it isn't a performance or replica mechanism. Tightening a permission set changes access rights, not database load or routing. Changing an XMLport's schedule doesn't address database contention — it just changes how often a batch job runs.