Free Practice Questions for Microsoft AB-410 Exam

Technician name on one screen — Context variable; Work orders — Collection; Logic statements — Named formula

A context variable should hold the technician’s name because the value is required only on the home screen. Context variables are screen scoped, which limits the state to the place where it is needed and avoids creating wider application dependencies. A collection is the correct structure for work orders because it stores a table of records that a gallery can enumerate, filter, and display. A named formula is appropriate for reusable logic statements that should be calculated consistently without imperatively setting a variable. The original answer image selects a global variable for the technician name, but that scope is broader than required; the image is retained unchanged while the verified mapping uses Context variable. A global variable is appropriate when a scalar value must be available across screens, not when the requirement explicitly limits persistence to one screen. The app should also avoid loading an unnecessarily large work-order collection and should delegate filtering to the data source where possible. The Study Guide directly lists “manage variables and collections” and “named formulas” under Create canvas apps. The verified mapping applies each state mechanism at its intended scope and data shape.

Study Guide reference/topic: “Create canvas apps — Manage variables and collections; Create reusable components.” AB-410 Study Guide | Microsoft Learn technical reference

A custom prompt is the native low-code mechanism for generating an inspection report from current app data while following the company’s existing template instructions. The maker can define inputs for the inspection fields, specify required sections, tone, order, and formatting, and invoke the prompt from the new app. This keeps the report-generation experience within Power Platform and minimizes custom AI development. A paginated report is well suited to deterministic, pixel-precise reporting, but it does not perform the requested generative composition and generally presents a separate reporting artifact. A Word template performs deterministic field substitution and is useful when no generative rewriting is required; it does not supply the AI-driven custom narrative described in the case. The prompt should be grounded only with approved inspection data, tested for missing inputs, and reviewed for output consistency before production use. The Study Guide covers “build prompts,” “add inputs to a prompt,” and “consume a prompt in apps.” Option C is therefore the component that directly implements native generative inspection-report creation.

Study Guide reference/topic: “Create prompts and models in AI Hub — Consume a prompt in apps.” AB-410 Study Guide | Microsoft Learn technical reference

The app should pass the current user-entered values as prompt parameters and invoke the prompt directly from the button’s Power Fx logic. Parameters ensure that the generated summary is grounded in the text currently displayed in the app rather than stale or hard-coded data. Direct invocation from the button provides the immediate interactive behavior required by the scenario. A cloud flow can also consume a prompt, but it adds an orchestration layer that is u nnecessary when the requirement is limited to a synchronous canvas-app interaction. Publishing the prompt is part of making a completed component available, but it does not execute the prompt or provide the current input. Updating general app settings is unrelated. The button formula should validate blank content, handle errors, and place the returned summary in a variable or control only after a successful response. The prompt’s inputs and output should be typed and tested for expected maximum lengths. The Study Guide explicitly includes “add inputs to a prompt” and “consume a prompt in apps.” Options B and C meet those two runtime responsibilities.

Study Guide reference/topic: “Create prompts and models in AI Hub — Consume a prompt in apps.” AB-410 Study Guide | Microsoft Learn technical reference

Each prefix contains five characters: P, O, S, the system digit, and the hyphen. TRIMLEFT(Number, 5) removes those five leading characters and returns the remaining clean order number. For example, POS1-78421 becomes 78421, and POS2-78421 produces the same clean value. Removing four characters would leave the hyphen, while TRIMRIGHT would remove characters from the actual order number rather than the source-system prefix. CONCAT adds text and cannot perform the required cleanup. Because the source integration already guarantees one of the two fixed prefixes, the calculated expression can apply the same length consistently. Production design should still consider null values, unexpected prefixes, and maximum output length so malformed integrations do not produce misleading results. The result is derived rather than manually maintained, which prevents divergence between Number and the clean-number column. The AB-410 Study Guide explicitly includes “configure calculated, rollup, and formula columns.” Option C applies the calculated-text function that matches the exact prefix structure.

Study Guide reference/topic: “Implement business and process logic — Configure calculated, rollup, and formula columns.” AB-410 Study Guide | Microsoft Learn technical reference