AB-410 Building The Apps Practice Test 1 — 15 Questions

Question 1

You are generating a canvas app using natural language. The generator creates a table for 'Event Planning' but lacks a 'Venue' field. How do you add this field?

Accepted Answer

Edit the data source in the Data pane. In Power Apps, the Data pane is where you view and edit the schema of connected data sources, including adding new fields (columns) to a table. To add a missing 'Venue' field, you edit the data source in the Data pane so the field becomes available to bind to controls. This is the correct, targeted way to extend the data model without rebuilding the app.

Answer

Use a label control

Answer

Re-generate the entire app

Answer

Modify the app theme

Question 2

You want to create a Copilot Studio agent from an existing canvas app to allow users to query data via chat. What is the primary requirement for this?

Accepted Answer

The app must be published to a Power Apps environment. To create a Copilot Studio agent from a canvas app, the app must be published to a Power Apps environment so Copilot Studio can access its data sources and logic. Publishing makes the app's connections and Dataverse tables available for the agent to query via chat. This is the documented prerequisite for the 'Create an agent from an app' flow.

Answer

The app must be built using only formulas

Answer

The app must have no external connectors

Answer

The app must be set to private

Question 3

You are creating a model-driven app and need to ensure that the mobile experience is optimized for field technicians. Which component should you configure to define the mobile layout?

Accepted Answer

App sitemap. The app sitemap defines the navigation structure and layout of a model-driven app, including which entities, dashboards, and custom pages appear and how they are grouped. For mobile optimization, the sitemap controls the mobile navigation experience, such as the bottom tab bar and the site map menu. Configuring the sitemap allows you to tailor the mobile interface specifically for field technicians by prioritizing relevant tables and simplifying navigation.

Answer

Command bar

Answer

Business rule

Answer

View designer

Question 4

When adding a page to a model-driven app, what type of pages can you include?

Accepted Answer

Tables and dashboards. When adding a page to a model-driven app, you can include table-based pages (list and form views of Dataverse tables) and dashboard pages. These are the native page types supported by the model-driven app designer. Other content types like custom pages (canvas-based) exist but the standard answer for table and dashboard pages reflects the core supported types.

Answer

Only Power BI reports

Answer

Only canvas app screens

Answer

Only web pages

Question 5

You need to ensure that a specific button in a canvas app is only visible to users with a 'Manager' role. How do you implement this?

Accepted Answer

Set the Visible property using a logic check on the user role. In a canvas app, the Visible property of a control accepts a Power Fx boolean expression, so you can bind it to a role check such as IsMember(User().id, LookUp(Roles, ...)) or a custom check against the current user's security roles. This dynamically hides the button for non-Managers at runtime. This is the standard, supported approach for role-based UI visibility in canvas apps.

Answer

Use a flow

Answer

Configure a business rule

Answer

Set the DisplayMode property to Disabled

Question 6

You are building a canvas app that uses a SharePoint list. When the list grows to 5000+ items, the app fails to filter correctly. How do you resolve this?

Accepted Answer

Use delegation-friendly functions like Filter(). Power Apps applies a default delegation limit (typically 500 or 2000 records depending on the connector) for non-delegable functions. SharePoint supports delegation for Filter, so using delegation-friendly functions like Filter() with delegable predicates pushes the query to SharePoint and returns correct results beyond the limit. This is the documented fix for the 5000+ item filtering failure.

Answer

Increase the local cache limit

Answer

Reduce the number of columns

Answer

Switch to an Excel file

Question 7

You are configuring a Copilot agent to use a specific Dataverse table. You want to restrict it to only look at records owned by the user. How do you set this?

Accepted Answer

Configure the security scope in Copilot Studio. In Copilot Studio, when you connect a Copilot agent to a Dataverse table as a knowledge source or via a Power Automate flow, you configure the security scope to control which records the agent can access. Setting the scope to 'User' ensures the agent only retrieves records owned by the signed-in user, enforcing row-level security. This is the correct configuration point for restricting the agent's data access.

Answer

Change the app sitemap

Answer

Create a business rule

Answer

Modify the canvas app formula

Question 8

Which pane in the Power Apps Studio is used to add new screens to a canvas app?

Accepted Answer

Tree view. The Tree view pane in Power Apps Studio displays the hierarchical structure of the app, including screens, controls, and containers. It is the pane where you add new screens (via the New screen button or right-click context menu) and manage the overall app layout.

Answer

Media pane

Answer

Data pane

Answer

Properties pane

Question 9

You are configuring a canvas app to show a notification message when a user saves a form. Which function is used for this?

Accepted Answer

Notify(). The Notify() function in Power Apps displays a banner message at the top of the screen, with options for the message text and notification type (Success, Error, Warning, Information). It is the standard function for showing transient feedback to users, such as confirming a successful save. Unlike other functions, Notify() is built specifically for this purpose and supports customization of the notification's appearance and duration.

Answer

Print()

Answer

Popup()

Answer

Alert()

Question 10

Which TWO actions can you perform in the Power Apps App designer?

Accepted Answer

Configure the app sitemap. In the Power Apps App designer, you can configure the app sitemap (option C) because model-driven apps use the sitemap to define the navigation structure—areas, groups, and subareas—and this is editable directly within the app designer's navigation pane. You can also create a new Dataverse table (option D) from within the app designer, since Power Apps is natively integrated with Microsoft Dataverse and allows makers to add tables and columns without leaving the designer. Option A is incorrect because hosting a website is not a function of the App designer; that would require a web hosting service such as Azure App Service or Power Pages. Option B is incorrect because Power Apps uses Power Fx as its formula language, not C#; complex C# code belongs to plug-ins or Azure Functions, not the App designer. Option E is incorrect because editing user passwords is an administrative task performed in Microsoft 365 admin center or Microsoft Entra ID (Entra ID), not in the Power Apps App designer.

Answer

Host a website

Answer

Write complex C# code

Answer

Edit user passwords

Question 11

Which THREE methods can you use to connect a canvas app to a data source?

Accepted Answer

Insert > Data. Option B (Insert > Data) is correct because in Power Apps Studio the Insert menu's Data command opens the data source picker, letting you add connectors such as SharePoint, SQL Server, or Dataverse to the canvas app. Option C (Using a connector in the App designer) is correct because the App designer's Data pane exposes standard and custom connectors that you select to bind the app to a data source. Option E (Data pane) is correct because the Data pane (View > Data or the Data icon) is the primary surface for adding, removing, and refreshing data sources in a canvas app. Options A and D are not valid: canvas apps are built with Power Fx formulas in a low-code designer, not by editing C# source code, and connections are configured through connectors/credentials rather than by directly typing a raw connection string.

Answer

Editing the C# source code

Answer

Directly typing a connection string

Question 12

Which TWO steps are required to set up a Copilot agent for a specific app?

Accepted Answer

Create a bot in Copilot Studio. Option A is correct because setting up a Copilot agent for a specific app requires creating the bot in Copilot Studio, which is the authoring environment where the agent's topics, triggers, and actions are defined. Option E is correct because the agent must have data connections enabled so it can reach the app's underlying data sources and services through connectors rather than embedding credentials directly. Purchasing a separate server (B) is unnecessary since Copilot Studio and its agents run on Microsoft's cloud infrastructure. Hard-coding the database connection (C) is wrong because connections should be configured through secure connectors, not embedded in code. Recompiling the app binary (D) is not required, as Copilot agents integrate with apps through external connectors and APIs without modifying the app's compiled code.

Answer

Purchase a separate server

Answer

Hard-code the database connection

Answer

Recompile the app binary

Question 13

Which THREE properties of a form control are essential for data submission?

Accepted Answer

OnSuccess. Option E (DataSource) is essential because a form control must be bound to a data source (e.g., a SharePoint list, SQL table, or Dataverse entity) so that submitted values have a destination to be written to. Option C (Item) is essential because it identifies the specific record being edited or created; without a valid Item reference, the control cannot determine which row to update or how to create a new record. Option A (OnSuccess) is essential because it defines the behavior executed after a successful submission, such as navigating away, resetting the form, or showing a confirmation, which completes the submission workflow. Option B (Theme) is not required for submission since it only affects visual styling, and Option D (Visible) is not required because a control can still submit data even when hidden (e.g., hidden fields carrying values).

Answer

Theme

Answer

Visible

Question 14

Which TWO elements are part of the 'Model-driven' app architecture?

Accepted Answer

Dataverse tables. In the Power Platform model-driven app architecture, Dataverse tables (B) are a core element because model-driven apps are built entirely on top of the Dataverse data model, where tables define the entities, columns, and relationships that drive the app's forms, views, and business logic. The sitemap (C) is also a required architectural element, as it defines the navigation structure and the areas, groups, and subareas that users see when they open the model-driven app. Custom JavaScript functions (A) are used for client-side scripting in model-driven apps but are an extensibility mechanism, not a defining architectural element. Direct SQL connections (D) are not part of the model-driven architecture, since Dataverse access is abstracted through the platform and its APIs rather than direct SQL. Canvas screens (E) belong to canvas apps, which use a completely different designer and runtime than model-driven apps.

Answer

Custom JavaScript functions

Answer

Direct SQL connections

Answer

Canvas screens

Question 15

Which THREE types of validations can you add to a Dataverse table?

Accepted Answer

Business rules. Business rules (A) are correct because Dataverse supports business rules that run client-side and server-side to enforce validation logic, set field values, show error messages, and control field visibility across model-driven apps and forms. Field requirements (D) are correct because Dataverse lets you configure columns as Business Required, Recommended, or Optional, which enforces validation on whether a value must be supplied before a record is saved. Data constraints (E) are correct because Dataverse supports constraints such as column-level constraints (e.g., min/max values, text length, date ranges) and table-level constraints to validate data integrity at the platform level. User profile pictures (B) are not a validation type; they are user record data/attributes unrelated to enforcing data validity. CSS styles (C) are presentation/formatting concerns and cannot be added as validations to a Dataverse table.

Answer

User profile pictures

Answer

CSS styles