Microsoft Building Intelligent Applications (AB-410)

✅ Option A (Correct)

Reasoning: In model-driven apps, you can control the visibility of public views within an application by assigning them to specific security roles in the App Designer. By restricting the sensitive public view to the manager security role, only managers will see it. Other users, not assigned that role, will not see this view, thus fulfilling both requirements of restricting access and displaying only context-relevant views.

❌ Why the other choices are incorrect:

• Option B is incorrect: Table-level permissions control data access, not the visibility of specific public views in the user interface. Users might still see the view even if they lack record access.
• Option C is incorrect: Removing the view from app navigation makes it inaccessible to all users, including managers, which violates the requirement for managers to access it.
• Option D is incorrect: Quick find views define search behavior and displayed columns for searches, not the overall visibility or access restrictions of a specific public view based on user roles.

The Parental relationship behavior is designed to ensure that all actions performed on the parent record, including assigning ownership, automatically cascade to associated child records. This directly satisfies the requirement for child records to be reassigned to the new owner when the parent record's owner changes.

Referential relationships do not cascade ownership changes. Referential, Restrict Delete prevents parent deletion but does not cascade owner assignment. Restrict is generally associated with preventing deletion, not cascading assignment.

Solution Breakdown:

The solution correctly maps Dataverse components to the specified business requirements for extending standard tables.

✅ Step 1: Choice column matches with -> Add a classification value to the Accounts table.
Reasoning: A 'Choice' column (formerly known as an Option Set) is the correct component for implementing a field with a predefined, static list of options. This ensures data consistency for classification values.

✅ Step 2: Choice column matches with -> Add a customer engagement tier to the Contacts table.
Reasoning: Similar to the first requirement, an engagement tier represents a fixed set of categories (e.g., Gold, Silver, Bronze). A 'Choice' column is the standard way to implement this type of field in Dataverse.

✅ Step 3: Alternate key matches with -> Improve lookup performance and enforce uniqueness.
Reasoning: An 'Alternate key' is specifically designed for this purpose. It creates a unique index on one or more columns in a table. This index significantly improves the performance of queries that filter on those columns and also enforces data integrity by preventing duplicate values.

Reference: https://learn.microsoft.com/en-us/power-apps/maker/data-platform/define-alternate-keys-reference-records

Chart and dashboard configuration

Here are the correct settings for each requirement:

Requirement 1: Show each sales stage as a percentage of the regional total.

✅ Configure a stacked column chart.

Reasoning: A stacked column chart is the ideal visualization for comparing the proportional contributions of different sub-categories (sales stages) to a total value, across several main categories (sales regions). Each column represents a region, and the stacked segments within it represent the stages.

Requirement 2: Make the new chart available in the app.

✅ Select the chart for the table in the app designer.

Reasoning: For a new component like a chart to be accessible to users within a model-driven app, it must be explicitly added as an asset to that app. This is done in the app designer by selecting the chart for the relevant table (Opportunities).

Requirement 3: Use the My Open Opportunities dataset when the dashboard loads.

✅ Set the Default View.

Reasoning: The data displayed in a dashboard component is determined by its underlying view. Setting the Default View for the chart component to 'My Open Opportunities' ensures that this specific dataset is used when the dashboard is first loaded.

Requirement 4: Prevent users from switching charts.

✅ Clear Display Chart Selection.

Reasoning: In the properties of a chart component on a dashboard, there is an option to allow users to switch between different charts available for that table. To prevent this, you must clear (uncheck) the 'Display chart selection' or 'Show chart selector' option, which hides the chart picker from the user.

Reference: https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/create-edit-dashboards

Power Automate cloud flows are server-side processes that run asynchronously, typically triggered by data events like record creation or updates. They are not designed for real-time, client-side manipulation of form components while a user is actively interacting with an unsaved form. Client-side dynamic behavior (e.g., showing/hiding fields, enabling/disabling controls, real-time validation) requires JavaScript (form scripts) or Business Rules within the model-driven app. Therefore, this solution does not meet the goal.

Reference: https://docs.microsoft.com/power-apps/maker/model-driven-apps/overview-business-rules

✅ Option A is correct: Dataverse formula columns are virtual columns that calculate their value dynamically when accessed. They evaluate expressions using other numerical columns in the same row, and their results are NOT stored in the database. This fulfills all requirements, minimizing custom code.

❌ Option B is incorrect: Real-time workflows update and store values in the table, contradicting the requirement that the result should NOT be stored.

❌ Option C is incorrect: Business rules populate and store values in the table, failing the requirement that the result should NOT be stored.

❌ Option D is incorrect: Plugins involve custom code, which the solution aims to minimize. A formula column offers a no-code alternative.

A global choice (global option set) is the correct column type. It allows the Priority options (Low, Medium, High, Critical) to be defined once and reused across multiple tables, fulfilling the requirement that a new option automatically propagates to all columns using that set. This ensures consistency and simplifies management across the data model.

View Access Configuration Breakdown:

The solution requires configuring access for two different types of views based on the provided scenario.

1. Senior technicians → Security roles

The case study states that 'Senior technicians' is a public view. The visibility of public (system) views within a model-driven app is controlled by associating them with specific security roles. This ensures that only users who are assigned one of the designated roles can see and use that view.

2. Hot Assets → Sharing

The 'Hot Assets' view is described as a personal view created by a tester. To make a personal view accessible to other users or teams, the owner of the view must explicitly share it. The tester can share this view with the 'Testers' team, granting them permissions to use it.

Reference: https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/ui-best-practices/control-access-to-views

✅ Option D (Correct)
Reasoning: AI Builder models, once published, are designed for native consumption in Power Apps. To classify images during user interaction, the Canvas app must call the AI model directly from its app logic. This allows the app to send the user-submitted image to the model and receive predictions in real time.

❌ Why the other choices are incorrect:

• Option A is incorrect: Retraining the model for each submission is highly inefficient, resource-intensive, and defeats the purpose of a pre-trained model for real-time predictions.
• Option B is incorrect: The requirement is to classify new images submitted by users. Reusing previously stored predictions would not apply to new, unique submissions.
• Option C is incorrect: Exporting the solution is an Application Lifecycle Management (ALM) step for deployment, not the action for consuming the model's prediction capability within the app's logic.

Correct Sequence of Actions:

The flow must be configured in a logical sequence to meet the requirements. The correct order ensures that data is available before it is used.

✅ Step 1: Initialize the variable.
Reasoning: A variable must be created before it can be used. This action declares a variable (e.g., `customerEmail`) to store the email address. This step must precede any action that sets or reads the variable's value.

✅ Step 2: Get a row by ID (Dataverse).
Reasoning: This action retrieves the specific customer record from Dataverse. The output of this step provides the necessary dynamic content, including the customer's email address, for the next actions.

✅ Step 3: Set the variable.
Reasoning: This action takes the email address from the output of the 'Get a row by ID' step and assigns its value to the variable initialized in Step 1. This fulfills the requirement to store the email address for later use.

✅ Step 4: Send an email.
Reasoning: The final step uses the data that has been retrieved and stored. The 'Send an email' action is configured to use the `customerEmail` variable in the recipient field, thus fulfilling the last requirement.

Reference: https://learn.microsoft.com/en-us/power-automate/use-variables