AB-410 Practice Test 15 — 15 Questions

Question 1

You need to send an email with an attachment that is generated by a flow. The file size is 25MB. Why might this fail?

Accepted Answer

Email message size limits are exceeded. Email message size limits are the most common cause of failure when sending large attachments. Most email systems, including Exchange Online, have a default maximum message size (e.g., 25 MB or 35 MB depending on configuration), and a 25 MB attachment plus encoding overhead (Base64 adds ~33%) can exceed that limit. This is why the flow fails.

Answer

The file type is not supported

Answer

Dataverse doesn't store files

Answer

The flow trigger is too fast

Question 2

Which TWO types of environments can be created in the Power Platform?

Accepted Answer

Developer. Option A (Developer) is correct because the Power Platform supports Developer environments, which are special-purpose environments tied to a single user for building, testing, and sharing apps and flows without affecting production resources. Option E (Production) is correct because Production environments are a standard Power Platform environment type intended for stable, live business solutions used by end users across the organization. The remaining options do not belong: Offline (B) is not a Power Platform environment type, Public (C) is not a valid environment classification in Power Platform, and Transient (D) is not an environment type offered by the platform.

Answer

Offline

Answer

Public

Answer

Transient

Question 3

Which TWO settings in Power Automate can you modify to improve the execution speed of a flow?

Accepted Answer

Trigger conditions to reduce unnecessary runs.. Option A (Trigger conditions to reduce unnecessary runs) is correct because adding trigger conditions with expressions (e.g., @equals(triggerOutputs()?['body/Status'], 'Approved')) prevents the flow from firing on irrelevant events, cutting down the number of executions and the overall time spent processing unneeded runs. Option C (Concurrency control in loops) is correct because enabling Concurrency Control on an Apply to each action (setting a degree of parallelism, e.g., 10 or 50) lets iterations run in parallel instead of sequentially, dramatically reducing the wall-clock time of loops that process many independent items. Option B is wrong because adding more variables increases memory usage and can slow execution rather than improve it. Option D is wrong because hardcoding connection strings is a security/configuration anti-pattern and has no bearing on execution speed. Option E is wrong because a Delay action at the start intentionally pauses the flow, which makes it slower, not faster.

Answer

Increasing the number of variables.

Answer

Hardcoding connection strings.

Answer

Using a Delay action at the start.

Question 4

A canvas app user reports that a gallery is not displaying data from a Dataverse table. You verify the connection is active. What is the most likely cause?

Accepted Answer

The Items property of the gallery is empty. The gallery's Items property is the data source binding that determines what records the control renders. If the connection is active but Items is empty or misconfigured (e.g., no table selected, blank formula, or a filter returning zero rows), the gallery renders nothing regardless of connectivity. This is the most common and directly diagnosable cause when the connection itself is verified as healthy.

Answer

The user does not have read access to the table

Answer

The app is using the wrong theme

Answer

The app is in edit mode

Question 5

Which THREE items are considered 'Components' in a Power Platform Solution?

Accepted Answer

Cloud flows. Cloud flows (A) are a valid solution component type, since Power Automate flows can be added to a solution and transported between environments as part of an ALM strategy. Canvas apps (B) are also solution components, as Power Apps canvas apps are packaged in solutions and can be exported/imported across environments. Environment variables (D) are solution components too, used to store configuration values like URLs or keys that differ per environment while remaining part of the solution. User passwords (C) are not solution components because credentials are managed through security settings and connections, not stored as solution artifacts. Browser bookmarks (E) are unrelated to Power Platform solutions and are simply client-side browser data.

Answer

User passwords.

Answer

Browser bookmarks.

Question 6

Which TWO properties can you configure for a column in Dataverse?

Accepted Answer

Required/Optional. Option C (Required/Optional) is correct because every Dataverse column has a 'Required' property that can be set to Optional, Recommended, or Business Required, controlling whether a value must be supplied on create/update. Option E (Data Type) is correct because when you create a column in Dataverse you must choose its data type (e.g., Text, Whole Number, Currency, Date and Time, Lookup, Choice), which defines the kind of data the column stores and cannot be changed freely afterward. The other options do not belong: A (Security group membership) is an Microsoft Entra ID/Entra concept, not a column-level property; B (Owner assignment) is a record-level table behavior (user/team ownership), not configured per column; and D (Tenant region) is set at the environment/tenant level when provisioning, not on a column.

Answer

Security group membership

Answer

Owner assignment

Answer

Tenant region

Question 7

Which THREE actions are essential when designing a robust Power Automate cloud flow that interacts with Dataverse?

Accepted Answer

Setting 'Pagination' in the trigger or action settings.. Option B is correct because enabling Pagination in the trigger or action settings (e.g., the Dataverse 'List rows' action) raises the default 5000-record threshold and uses the @odata.nextLink to retrieve all matching records, which is essential for robust flows that must process complete result sets. Option C is correct because using 'Filter rows' (OData $filter) pushes filtering to Dataverse, reducing the number of records returned, improving performance, and avoiding unnecessary API throttling and payload size. Option E is correct because 'Configure run after' lets you define behavior for success, failure, skipped, or timed-out branches, enabling proper error handling, retries, and notifications so the flow remains resilient. Option A is not appropriate because hardcoding record IDs makes the flow brittle and non-portable across environments; dynamic identifiers should be used instead. Option D is not appropriate because 'Get rows' without filter criteria returns all records, which is inefficient, can hit pagination and throttling limits, and is not a robust design practice.

Answer

Hardcoding Dataverse record IDs.

Answer

Using 'Get rows' without any filter criteria.

Question 8

Which THREE of the following are primary capabilities of Dataverse business rules?

Accepted Answer

Set field requirements (Business Required). Dataverse business rules are declarative, no-code components that operate on a table's forms and data. Option B is correct because business rules can change a column's requirement level to Business Required (or Recommended) based on conditions, without writing code. Option C is correct because business rules can validate data against conditions and display error messages to the user when validation fails. Option D is correct because business rules can set field values automatically when specified conditions are met, such as defaulting or clearing a column. Option A is not a capability of business rules, since they cannot delete records; deletion requires workflows, Power Automate, or code. Option E is not correct because business rules are declarative and do not support custom C# code, which would require plug-ins or custom APIs.

Answer

Delete records automatically

Answer

Write custom C# code

Question 9

Which TWO of the following are valid relationship types in Dataverse?

Accepted Answer

Many-to-Many. In Microsoft Dataverse, the supported table relationship types are One-to-Many (1:N), Many-to-One (N:1, the same relationship viewed from the other side), and Many-to-Many (N:N), so option A (Many-to-Many) and option B (One-to-Many) are both valid relationship types. One-to-Many is the most common relationship, where a single row in one table relates to many rows in another (for example, one Account to many Contacts), and Many-to-Many allows many rows in each table to relate to many rows in the other, typically implemented via an intersect table. The other options are not real Dataverse relationship types: 'Universal-to-Many' (C) and 'Hierarchical-to-Flat' (E) are invented terms, and 'One-to-One-to-One' (D) does not exist as a relationship type — Dataverse does not define a three-way 1:1:1 relationship.

Answer

Universal-to-Many

Answer

One-to-One-to-One

Answer

Hierarchical-to-Flat

Question 10

Which TWO field types allow for mathematical calculations?

Accepted Answer

Calculated. Option C, Calculated, is correct because a calculated field stores a formula that evaluates expressions using operators and functions, so it directly performs mathematical calculations. Option E, Rollup, is correct because a rollup field aggregates values from related records using functions such as SUM, COUNT, MIN, MAX, and AVG, which are mathematical operations. The unmarked options do not belong: Lookup (A) only retrieves a value from a related record, Text (B) stores alphanumeric strings, and Choice (D) stores a selected value from a predefined list — none of these perform calculations.

Answer

Lookup

Answer

Text

Answer

Choice

Question 11

Which TWO actions can be performed in the Power Platform admin center?

Accepted Answer

Manage Data Loss Prevention (DLP) policies. Option A is correct because the Power Platform admin center provides a dedicated Data policies (DLP) section where administrators can create, edit, and apply Data Loss Prevention policies that govern which connectors can be used together across environments and tenants. Option D is correct because the admin center includes an Environments page where administrators can create new environments, selecting region, type (Sandbox, Production, Trial, Developer), and assigning a Dataverse database if needed. Options B and C are incorrect because designing forms and creating business rules are authoring tasks performed in Power Apps (model-driven or canvas app designer) or Dynamics 365 customization tools, not in the admin center. Option E is incorrect because editing records is a data-entry operation done in model-driven apps, canvas apps, or Dataverse tables, not an administrative function of the Power Platform admin center.

Answer

Design forms

Answer

Create Business Rules

Answer

Edit records

Question 12

Which THREE features are part of Dataverse security?

Accepted Answer

Security Roles. Security Roles (A) are a core Dataverse access-control mechanism: they bundle table privileges (Create, Read, Write, Delete, Append, Append To, Assign, Share) at user/team level and are scoped by Business Unit, so they directly govern who can do what in Dataverse. Field Security Profiles (C) are also part of Dataverse security: they are applied to specific columns marked as secured, and combined with a user's security role they restrict read/create/update access to sensitive field values. Business Units (E) form the hierarchical ownership and scoping structure of Dataverse, defining the boundaries (User, Business Unit, Parent: Child Business Unit, Organization) within which security roles grant privileges. The remaining options are not security features: Form-level scripting (B) is client-side model-driven app behavior implemented with JavaScript, and App-level branding (D) is a model-driven app customization for colors, icons, and theming, neither of which controls Dataverse data access.

Answer

Form-level scripting

Answer

App-level branding

Question 13

You need to update a flow that is used by hundreds of employees. You want to test the update without affecting the production version. What should you use?

Accepted Answer

Environment-based deployment. Environment-based deployment in Power Platform allows you to promote a flow through separate environments (e.g., Dev → Test → Prod) using solutions, so the production version used by hundreds of employees remains untouched while you validate the update in a non-production environment. This is the standard ALM pattern for testing changes safely before release.

Answer

Temporary variables

Answer

Disable the flow during editing

Answer

Save as a new flow

Answer

Solution layers

Question 14

Which TWO ways can you optimize a canvas app for mobile users?

Accepted Answer

Use large, touch-friendly controls. Option B is correct because large, touch-friendly controls sized for finger input (typically at least 40x40 pixels with adequate spacing) reduce mistaps and improve usability on small mobile touchscreens. Option D is correct because enabling responsive layout settings in Power Apps (such as the 'Scale to fit' and 'Lock aspect ratio' settings, or using containers with flexible height/width) lets the app adapt to different screen sizes and orientations on phones and tablets. Option A is not appropriate because a high-resolution video background increases load time and bandwidth consumption, hurting performance on mobile networks. Option C is wrong because increasing the number of columns crowds the limited screen width and makes content harder to read and interact with on a phone. Option E is incorrect because mouse-hover triggers do not exist on touch devices, so that interaction would be unusable for mobile users.

Answer

Add a high-resolution video background

Answer

Increase the number of columns

Answer

Use a mouse-hover trigger

Question 15

You need to import a large volume of data into Dataverse. Which feature allows you to perform bulk operations efficiently?

Accepted Answer

Dataflows. Dataflows in Power Platform provide a scalable way to ingest, transform, and load large volumes of data into Dataverse and other destinations. They use Power Query Online to perform ETL operations and can handle bulk data movement efficiently, including scheduled refreshes and incremental loads. This makes Dataflows the appropriate feature for high-volume data import into Dataverse.

Answer

Excel Online

Answer

Power Automate

Answer

Command line interface