AB-410

Free AB-410 practice questions

10 questions from our AB-410 practice tests, each with the correct answer and a written explanation. Read them with the answers shown, or switch to quiz mode and answer first.

Back to the AB-410 practice exams

Question 1 of 10, Create a foundation for intelligent applications

A cloud flow in a solution calls a SharePoint site URL that differs between test and production. Administrators want to change the URL during deployment without editing the flow. What should the maker add to the solution?

  1. AA static variable initialized at the start of the flow
  2. BAn environment variable that stores the site URL Correct answer
  3. CA connection reference that points to the SharePoint connector
  4. DA Dataverse table row that holds configuration values

Answer and explanation: Environment variables are solution components designed to hold configuration such as site URLs, and their values can be supplied per target environment during import or by a pipeline. A connection reference stores which connection a flow uses, not arbitrary values like a URL. A configuration row in a custom table works but is not set during deployment and must be maintained separately. A variable initialized in the flow is hard-coded and requires editing the flow.

Question 2 of 10, Create a foundation for intelligent applications

An organization wants governance controls on its production environments: limiting how widely makers can share canvas apps, receiving weekly usage insights, and enforcing solution checker validation on import. Which approach provides these controls with the LEAST custom effort?

  1. AEnable Managed Environments on the production environments and configure sharing limits and solution checker enforcement Correct answer
  2. BAssign makers a dedicated Dataverse security role in each production environment that removes their Share privilege on apps
  3. CBuild a governance flow that reads the admin connectors and emails a weekly report to administrators
  4. DCreate data policies that classify every connector as Business and block the rest

Answer and explanation: Managed Environments add built-in governance such as sharing limits, weekly usage digests, and solution checker enforcement, configured per environment. A custom governance flow can report usage but would take substantial effort and cannot enforce sharing limits or checker validation. Data policies govern which connectors can be combined, not sharing or solution quality. A custom security role does not control canvas app sharing limits or import validation.

Question 3 of 10, Create a foundation for intelligent applications

A company plans an employee onboarding solution. HR staff need a structured, data-dense back-office app over many related Dataverse tables, while new hires need a branded, mobile-friendly app with a custom layout for a few tasks. External contractors must submit documents without a Microsoft Entra account in the tenant. Which combination of components best fits these requirements?

  1. AA model-driven app for HR staff and new hires, and a shared canvas app for contractors
  2. BA Power Pages site for HR staff and contractors, and a canvas app for new hires
  3. CA canvas app for HR staff, a model-driven app for new hires, and a Power Pages site for contractors
  4. DA model-driven app for HR staff, a canvas app for new hires, and a Power Pages site for contractors Correct answer

Answer and explanation: Model-driven apps suit data-dense processes across many related tables, canvas apps give pixel-level control for a tailored mobile experience, and Power Pages serves external users who are not internal tenant members. Swapping canvas and model-driven reverses their strengths. Giving contractors a canvas app requires them to be licensed tenant users. Using Power Pages for internal HR back-office work gives up the built-in forms, views, and process features of model-driven apps.

Question 4 of 10, Create intelligent applications. Choose 2.

A canvas app uses a form control to edit orders. The maker needs to submit the form, show a success message, and navigate back only if the save succeeds, and show the error message from the data source if it fails. Which TWO properties or functions should the maker use? (Choose two.)

  1. AThe form's OnSuccess property to notify and navigate Correct answer
  2. BSubmitForm in the button's OnSelect
  3. CNavigate in the button's OnSelect right after SubmitForm
  4. DThe form's OnFailure property to notify with the form's Error property Correct answer
  5. EPatch the data source instead of using the form

Answer and explanation: OnSuccess runs only after a successful submission, so it is where to notify and navigate, and OnFailure runs when the save fails, where the form's Error property provides the message. Calling SubmitForm is needed but is not one of the behaviors that handle the outcome. Navigating right after SubmitForm runs regardless of success. Replacing the form with Patch abandons the form's built-in handling.

Question 5 of 10, Create intelligent applications

A canvas app calls several data sources on many screens. The maker wants a single place to catch any unhandled error, log it to Application Insights with the screen name, and show a generic message instead of the default banner. What should the maker configure?

  1. AEnable the App checker's runtime error report
  2. BWrap every formula in IfError with a Notify fallback
  3. CTurn on Formula-level error management and add Errors() checks on each screen
  4. DSet App.OnError to a formula that uses Trace and Notify Correct answer

Answer and explanation: App.OnError runs for unhandled errors anywhere in the app, can call Trace to send telemetry to Application Insights, and replaces the default error banner. Wrapping every formula in IfError works locally but is not a single central handler. Checking Errors() on each screen is also distributed and only covers data source errors. App checker reports design-time issues, not runtime errors.

Question 6 of 10, Create intelligent applications

A maker wants users of a model-driven app to see the Quick Order form only if they have the Order Desk security role, while all other users see the standard main form. What should the maker configure?

  1. AEnable the Quick Order form only for the Order Desk security role Correct answer
  2. BSet a form order so that the Quick Order form is listed last
  3. CUse a business rule to hide the tabs of the Quick Order form
  4. DHide the Quick Order form in the app designer for users without the role

Answer and explanation: Forms can be assigned to specific security roles, so only users with the Order Desk role can access the Quick Order form while others fall back to the main form. The app designer controls which forms are included in the app, not per-role visibility. A business rule can hide fields or sections but the form would still be available. Form order sets the default form among those a user can access but does not restrict access.

Question 7 of 10, Build business application logic and automation

A flow must try to create an invoice in an ERP system and, if any action in that part fails, log the error to a Dataverse table and notify the support team, then mark the run as failed. Which design meets these requirements?

  1. AEnable the retry policy on every ERP action with an exponential interval and let the run fail naturally
  2. BPut the ERP actions in a Try scope, add a Catch scope set to run after Try fails, and end the Catch with Terminate (Failed) Correct answer
  3. CPut the logging actions in a parallel branch next to the ERP actions so both always run
  4. DAdd a Condition after each ERP action that checks its status code and sends the support notification in the 'If no' branch

Answer and explanation: Grouping actions in scopes and configuring 'Configure run after' on the Catch scope gives a try-catch pattern, and a Terminate action with status Failed marks the run correctly. Conditions after each action cannot catch failures because a failed action stops the following actions unless run-after is changed. Retry policies only repeat transient calls and do not log or notify. A parallel branch runs regardless of whether the ERP actions succeed.

Question 8 of 10, Build business application logic and automation

A Dataverse-triggered cloud flow should run only when the Status column of an Order row changes, not when other columns are updated. What should the maker configure on the 'When a row is added, modified or deleted' trigger?

  1. ASet the trigger's Scope to Organization
  2. BSet Select columns to the Status column Correct answer
  3. CAdd a Condition action that compares Status to its old value
  4. DAdd a trigger condition that checks whether Status is not empty

Answer and explanation: The Select columns setting of the Dataverse trigger limits modification events to changes in the listed columns, so the flow fires only when Status changes. A Condition action runs after the flow has already triggered and the trigger output has no previous value to compare. Scope controls whose rows trigger the flow, not which columns. A trigger condition checking for a non-empty Status would fire on any update where Status has a value.

Question 9 of 10, Build business application logic and automation

A team needs to classify incoming support emails into one of eight company-specific categories. They have several thousand labeled historical emails, and the categories rarely change. They want predictable results and minimal per-request tuning. Which approach is the BEST fit?

  1. AThe prebuilt sentiment analysis model
  2. BA prompt with the eight categories listed in its instructions
  3. CA custom category classification model trained on the labeled emails Correct answer
  4. DThe prebuilt key phrase extraction model

Answer and explanation: A custom category classification model trained on labeled examples fits stable, company-specific categories and gives consistent predictions. A prompt can also classify but relies on instructions and may vary more, while the large labeled set favors training. Sentiment analysis returns positive, negative, or neutral, not company categories. Key phrase extraction returns phrases, not a classification.

Question 10 of 10, Build business application logic and automation

An expense flow requires approval from the employee's manager and then from the finance lead, in that order. Finance must not receive the request unless the manager approves. How should the maker design the flow?

  1. AOne approval action of type 'First to respond' assigned to both approvers
  2. BTwo parallel branches, each containing an approval for one approver
  3. COne 'Start and wait for an approval' action of type 'Everyone must approve' with both approvers
  4. DTwo sequential 'Start and wait for an approval' actions, with a condition on the first outcome Correct answer

Answer and explanation: Sequential approval actions, with a condition that only continues to finance when the manager approves, enforce the required order. 'Everyone must approve' sends the request to both people at the same time. 'First to respond' completes when either person responds, so finance could decide alone. Parallel branches also notify both approvers simultaneously.