CCNA Building The Apps Questions — Page 2 of 2

MCQmedium

In a canvas app, you want to allow users to upload images to Dataverse. Which control is best suited for this?

A.Gallery control

B.Text input control

C.Add Picture control

D.Label control

AnswerC

The Add Picture control renders a native image picker that captures or selects a file and exposes it as an image value, which can be written directly to a Dataverse image column. Other controls cannot produce image data for upload.

Why this answer

The Add Picture control in Power Apps is specifically designed to let users select and upload image files from their device. It provides a built-in file picker, preview, and exposes the image content via the .Photo property, which can be patched to a Dataverse image or file column.

Exam trap

The trap is choosing a Gallery control because it displays images, or a Text input because it accepts user input — candidates conflate 'displays images' or 'accepts input' with 'uploads image files,' but only the Add Picture control provides a file picker and binary image data.

How to eliminate wrong answers

Option A is wrong because a Gallery control is a display container for browsing records — it shows images but does not provide an upload mechanism. Option B is wrong because a Text input control accepts typed text only; it cannot handle binary image data or file selection. Option D is wrong because a Label control is read-only display text — it has no input or upload capability.

Practice this question →

Multi-Selectmedium

Which THREE features help ensure your canvas app is performant?

Select 3 answers

A.Adding more images

B.Using delegation

C.Minimizing the number of controls

D.Caching data in collections

E.Using Power Automate flows

AnswersB, C, D

Delegation pushes filtering, sorting and aggregation to the data source rather than pulling every record to the client. This limits transferred row counts, so large tables stay responsive and avoid the truncation and slow-loading problems that undermine canvas app performance.

Why this answer

Using delegation (B) is correct because it lets Power Apps push filtering, sorting, and aggregation operations to the data source so only the needed records are retrieved, avoiding the default 500/2000-record limit and reducing client-side processing. Minimizing the number of controls (C) is correct because each control adds to the app's render tree and load time, so fewer controls mean faster screen rendering and lower memory usage. Caching data in collections (D) is correct because loading data once into a local collection with ClearCollect or Collect avoids repeated network calls to the data source, cutting latency on subsequent operations.

Adding more images (A) is not correct because images increase app size and load time, hurting performance. Using Power Automate flows (E) is not correct because flows run asynchronously and add network round-trips, so they do not inherently improve canvas app performance.

Exam trap

AB-410 often tests whether candidates recognize that delegation and collections are performance enablers while adding controls or images are performance detractors — the trap is picking features that sound useful but actually add overhead.

Practice this question →

MCQhard

You have an app that needs to connect to an on-premises SQL Server. What is required to facilitate this?

A.On-premises data gateway

B.A custom API

C.Public IP address

D.A cloud-native connector

AnswerA

An on-premises data gateway brokers connectivity from cloud services to resources behind your firewall without inbound ports, satisfying the requirement to reach an on-premises SQL Server. It relays queries over outbound TLS, so Microsoft Entra ID-authenticated apps can access the database securely without exposing it directly to the internet.

Why this answer

The on-premises data gateway acts as a secure bridge that allows cloud services (Power Platform, Azure Logic Apps, Fabric, etc.) to reach on-premises data sources like SQL Server without exposing them to the public internet. It establishes outbound connections from the on-premises network to the cloud service, so no inbound firewall ports need to be opened. This is the standard, supported mechanism for hybrid connectivity to on-prem SQL Server.

Exam trap

AB-410 often tests the assumption that any network path (public IP, API, cloud connector) can bridge cloud-to-on-prem — candidates miss that the on-premises data gateway is the specific, required component for secure hybrid data access.

How to eliminate wrong answers

Option B is wrong because a custom API is a bespoke development effort that would require building, hosting, and securing an intermediary — it is not the required or standard mechanism and adds unnecessary complexity. Option C is wrong because a public IP address alone does not provide the secure authenticated relay, and exposing SQL Server directly to the internet is a serious security anti-pattern. Option D is wrong because a cloud-native connector connects to cloud services or SaaS, not to on-premises SQL Server; on-prem access specifically requires the gateway.

Practice this question →

MCQhard

You need to trigger a Cloud Flow from a canvas app when a button is clicked. How do you integrate the flow?

A.Add the flow in the Power Automate pane and call it in the OnSelect property

B.Use a business rule

C.Embed it as a web page

D.Add it to the sitemap

AnswerA

Adding the flow via the Power Automate pane binds it to the app, then invoking it from the button's OnSelect property triggers execution on click. This is the supported mechanism for canvas app to Cloud Flow invocation.

Why this answer

To trigger a cloud flow from a canvas app, you add the flow to the app via the Power Automate pane (Data > Add data > Power Automate), which makes the flow available as a method. You then call it in the OnSelect property of a button, typically using the syntax FlowName.Run(parameters). This is the standard integration pattern for invoking a flow from a canvas app.

Exam trap

AB-410 often tests the misconception that flows can be triggered from model-driven app sitemaps or business rules, when the correct method for canvas apps is the Power Automate pane and OnSelect.

How to eliminate wrong answers

Option B is wrong because business rules are used in Dataverse to enforce logic at the data layer, not to trigger flows from canvas apps. Option C is wrong because embedding a flow as a web page is not a supported integration method; flows are not web pages and cannot be embedded. Option D is wrong because the sitemap is a navigation component in model-driven apps, not a mechanism for triggering flows from canvas apps.

Practice this question →

MCQmedium

You are building a model-driven app and need a field to be mandatory only when another field is filled. How do you achieve this?

A.Dataverse validation

B.Form component

C.Power Fx code

D.Business rule

AnswerD

A business rule applies client-side logic that makes a field required based on another column's value, directly satisfying the conditional mandatory constraint. Unlike column-level required settings, which are unconditional, business rules evaluate conditions at runtime, so the field becomes mandatory only when the dependent field is populated.

Why this answer

A business rule in Dataverse is the correct mechanism to make a field mandatory conditionally based on another field's value. Business rules run client-side (and optionally server-side) and support conditions and actions such as 'set field requirement level' when a condition is met. This allows dynamic mandatory behavior without writing code.

Exam trap

AB-410 often tests whether candidates confuse business rules (declarative, table-level logic) with Power Fx (canvas apps) or column-level required settings (static, not conditional).

How to eliminate wrong answers

Option A is wrong because Dataverse validation typically refers to column-level constraints (like required at the column level) which are static, not conditional on other fields. Option B is wrong because a form component is a UI control, not a logic mechanism for conditional field requirements. Option C is wrong because Power Fx code is used in canvas apps and custom pages, not the standard way to enforce conditional mandatory fields in model-driven forms — business rules are the declarative, supported approach.

Practice this question →

Multi-Selecteasy

Which TWO types of components can be included in a Power Apps Solution?

Select 2 answers

A.Operating system updates

B.Browser extensions

C.Canvas apps

D.User personal files

E.Model-driven apps

AnswersC, E

Canvas apps are first-party Power Apps components, so they can be packaged into a solution and transported between environments alongside their dependencies. This satisfies the stem's requirement to identify component types that a Power Apps Solution can contain.

Why this answer

Canvas apps (option C) are a valid Power Apps solution component because solutions package app artifacts such as canvas apps, their connections, and related resources for transport between environments. Model-driven apps (option E) are likewise a supported solution component, since they are built on Dataverse and are explicitly included in solution packaging and ALM. Operating system updates (A) are managed by the OS or update management tooling, not by Power Apps solutions, which only contain app and platform metadata components.

Browser extensions (B) are client-side software installed in a browser and are not solution-aware Power Platform components. User personal files (D) are end-user data stored in OneDrive or similar storage, not solution components, which contain configuration and app artifacts rather than personal content.

Exam trap

AB-410 often tests what belongs in a solution versus what is external IT infrastructure, so distractors like 'OS updates' and 'browser extensions' exploit the word 'component' to lure candidates away from the actual Power Platform artifacts.

Practice this question →

Multi-Selecteasy

Which TWO items are visible in the Power Apps 'Tree View' pane?

Select 2 answers

A.User profiles

B.Screens

C.Dataverse environments

D.Controls

E.Power Automate flows

AnswersB, D

Screens appear as top-level nodes in the Tree View pane, letting makers select, reorder and navigate between them while building an app. This satisfies the stem's requirement for items visible in that pane, since Tree View exposes the app's screen hierarchy alongside controls nested within each screen.

Why this answer

In Power Apps Studio, the Tree View pane displays the hierarchical structure of the app's UI, so option B (Screens) is correct because every screen in the app appears as a top-level node in that hierarchy. Option D (Controls) is also correct because the controls placed on each screen (such as labels, buttons, galleries, and containers) are shown nested under their parent screen within the Tree View. Option A (User profiles) is incorrect because user account information is managed in Microsoft 365/admin centers, not in the app-authoring Tree View.

Option C (Dataverse environments) is incorrect because environments are managed in the Power Platform admin center, not displayed in the Tree View. Option E (Power Automate flows) is incorrect because flows are separate Power Automate resources that can be called from an app but are not listed as nodes in the Tree View pane.

Exam trap

The trap is confusing the app designer's Tree View with platform-level navigation — candidates may pick Dataverse environments or flows because those are Power Platform concepts, but Tree View is strictly the canvas app's screen/control hierarchy.

Practice this question →

MCQmedium

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?

A.The Items property of the gallery is empty

B.The user does not have read access to the table

C.The app is using the wrong theme

D.The app is in edit mode

AnswerA

A gallery renders only what its Items property supplies, so an empty Items value produces no rows regardless of an active Dataverse connection. Populating Items with the table or a filtered collection restores the display.

Why this answer

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.

Exam trap

AB-410 often tests the distinction between connectivity/permission failures and binding/configuration failures — candidates jump to permissions (B) when the question explicitly says the connection is active, missing that the Items property is the actual rendering gate.

How to eliminate wrong answers

Option B is wrong because a missing read permission would typically surface as an authorization error or empty result set with a visible error, and the question states the connection is active — permissions issues usually manifest as explicit access-denied errors rather than silent blank galleries. Option C is wrong because app theme only affects colors, fonts, and styling, not data retrieval or rendering of records. Option D is wrong because edit mode is a maker-side state; end users run the published app, and edit mode does not suppress data binding in a gallery.

Practice this question →