Building The Apps practice questions

Use a label control

Why it fails: Labels are for display, not data storage.

Re-generate the entire app

Why it fails: You do not need to restart the process to add a single column.

Modify the app theme

Why it fails: Themes do not add data fields.

The app must be built using only formulas

Why it fails: Declarative UI is standard.

The app must have no external connectors

Why it fails: External connectors are supported.

The app must be set to private

Why it fails: Privacy settings do not prevent Copilot integration.

Command bar

Why it fails: Command bars manage actions, not the overall mobile layout.

Business rule

Why it fails: Business rules manage logic on forms, not layout.

View designer

Why it fails: View designer manages data displays, not the navigation structure.

Only Power BI reports

Why it fails: While supported, it's not the only type.

Only canvas app screens

Why it fails: You can include custom pages, but not 'screens' directly.

Only web pages

Why it fails: This is not a valid component type.

Use a flow

Why it fails: Flows cannot control UI visibility.

Configure a business rule

Why it fails: Business rules do not apply to canvas app controls.

Set the DisplayMode property to Disabled

Why it fails: This would make it read-only, not hidden.

Increase the local cache limit

Why it fails: Caching does not solve delegation issues for large datasets.

Reduce the number of columns

Why it fails: Column count does not fix delegation limits.

Switch to an Excel file

Why it fails: Excel has similar limitations.

Change the app sitemap

Why it fails: The sitemap does not affect agent data scope.

Create a business rule

Why it fails: Business rules do not control agent access.

Modify the canvas app formula

Why it fails: The agent's scope is independent of the app's UI formulas.

Media pane

Why it fails: The Media pane is for images and videos.

Data pane

Why it fails: The Data pane is for connections.

Properties pane

Why it fails: The Properties pane is for settings.

Print()

Why it fails: Print() sends a document to a printer or PDF output; it produces no on-screen notification within the running app. It is tempting because it is a real Power Apps function for generating printable output, and would be correct when the requirement is to produce a printable form or report rather than display a save confirmation.

Popup()

Why it fails: Popup() does not exist in Power Apps canvas formulas, so the app fails to compile. It is tempting because the name suggests a transient on-screen message, and a custom popup would be correct if you needed a bespoke overlay control rather than a standard notification banner.

Alert()

Why it fails: Alert() is not a Power Apps canvas function; the notification function is Notify(). It is tempting because the name matches the intent of alerting the user, and JavaScript's alert() would be correct in a web page context rather than a Power Apps formula.

Host a website

Why it fails: This is not the purpose of the tool.

Write complex C# code

Why it fails: This is not supported.

Edit user passwords

Why it fails: This is an administrative task.

Editing the C# source code

Why it fails: Power Apps does not allow editing source code.

Directly typing a connection string

Why it fails: This is not supported.

Purchase a separate server

Why it fails: Copilot agents are configured through Microsoft 365 admin centre and Copilot Studio, consuming existing tenant licensing; no physical or virtual server is provisioned. The distractor appeals to on-premises instincts, where dedicated infrastructure would be needed for a self-hosted bot framework, but Copilot is a cloud service.

Hard-code the database connection

Why it fails: Connections use managed connectors or environment variables with Microsoft Entra ID authentication, never literal credentials in source. Hard-coding is tempting because it is the quickest way to make a local prototype talk to a database, but it breaks secret rotation and violates the agent's governed connection model.

Recompile the app binary

Why it fails: Agents connect to apps through connectors, Graph API permissions and declarative manifests, so no binary rebuild is needed. Recompilation is tempting because embedding an SDK is how custom in-app AI historically shipped, but Copilot extensibility is configuration-driven and works against the app's existing endpoints.

Theme

Why it fails: Visual only.

Visible

Why it fails: UI only.

Custom JavaScript functions

Why it fails: Custom JavaScript functions are not a model-driven architecture element; model-driven apps extend through client scripting, plug-ins, and Power Fx rather than standalone JavaScript functions. It is tempting because JavaScript web resources can run on forms, but the architecture's elements are the data model, components, and the platform itself.

Direct SQL connections

Why it fails: Direct SQL connections are unsupported in model-driven apps, which access data through the Dataverse platform and its APIs rather than raw SQL. It is tempting because Dataverse stores data in a relational database, but model-driven architecture abstracts that layer, so direct SQL bypasses security and business logic.

Canvas screens

Why it fails: Canvas screens belong to Power Apps canvas apps, which use a drag-and-drop designer rather than metadata-driven components. It is tempting because canvas apps are also Power Platform apps, but model-driven architecture instead builds on tables, forms, views, and business rules rendered from the data model.

User profile pictures

Why it fails: This is not a validation method.

CSS styles

Why it fails: CSS is for UI, not data.

Opening the browser

Why it fails: This is not a trigger.

Changing the app theme

Why it fails: Themes cannot trigger flows.

Dragging a control

Why it fails: This does not trigger flows.

Increase the 'Data row limit' in the app settings to 20,000.

Why it fails: Increasing the data row limit allows more records to be retrieved but does not improve performance; in fact, it can worsen it by transferring more data. It also does not fix incomplete data, because the gallery still renders only a subset and the underlying performance bottleneck remains.

Enable the 'Use Power Apps for Windows' setting in the app settings.

Why it fails: This setting enables the Windows desktop player for the app but does not change how data is retrieved or rendered. It will not address the performance or incomplete data issues caused by loading 10,000 records into a gallery, because the underlying data-fetch behavior remains the same.

Replace the gallery with a Data table control and set its Items property to the full table.

Why it fails: A Data table control still renders all provided records and does not inherently improve performance for large datasets. Setting Items to the full table would load all 10,000 records, likely causing the same or worse performance and potential incomplete rendering due to delegation limits.

Configure the label's OnSelect property to call the flow and set the label text when the user taps it.

Why it fails: OnSelect only fires on user interaction, so the model response would not appear until someone taps the label, and a label is not an interactive control by default. The scenario requires the value to show automatically on screen, which this event-driven approach does not satisfy, making it unsuitable despite technically calling the flow.

Use the Set() function in the screen's OnVisible property to assign the flow output to a variable and bind the label to that variable.

Why it fails: Set() in OnVisible assigns a value when the screen loads, but the flow call inside it may not complete synchronously or may run before the label evaluates, and it does not refresh when inputs change. This introduces timing problems and stale values, whereas a direct Run expression in the label property evaluates reliably.

Store the flow output in a collection with Collect() and bind the label to First(MyCollection).

Why it fails: Collect() appends records to a collection but does not itself invoke the flow or guarantee the output exists before the label evaluates. Without first running the flow and capturing its result, the collection is empty and the label shows blank or stale data. It also adds unnecessary state management when a direct expression would render the value.

Enable the 'Explicit column selection' setting and replace the formula with a stored procedure call.

Why it fails: Explicit column selection reduces data transfer but does not address delegation limits. Stored procedures are not directly callable in canvas app formulas without a custom connector, and even then the gallery cannot delegate filtering to them. This approach adds complexity without fixing the delegation problem for a 40,000-row table.

Replace the formula with Filter(Policies, CustomerID = varCustomerID) but set the gallery's 'Load data' property to 5000.

Why it fails: Changing the gallery's Load data property only limits how many rows are displayed, not how many are retrieved or evaluated. The underlying delegation warning remains, and results will still be incomplete because the filter is not delegated to SQL Server. This option misinterprets a display setting as a performance fix.

Use the formula Filter(Policies, CustomerID = varCustomerID) but first create a view in SQL Server that filters by CustomerID and connect to that view.

Why it fails: Creating a SQL view does not change how Power Apps delegates queries. The canvas app still applies the Filter function locally unless the data source supports delegation for that function and column. A view can help with permissions or shaping, but it does not resolve the delegation limit for 40,000 rows.

Add an Image control, set its Image property to Camera1.Stream, and use the form's OnSuccess to upload the stream.

Why it fails: An Image control only renders a picture; it does not provide a capture surface, so Camera1.Stream refers to a live preview that must be sampled explicitly. The OnSuccess event on a form fires after a successful submit and has no built-in upload mechanism for arbitrary streams, so no file would be stored in the Dataverse File column.

Add an Add Picture control, then use Collect to append the image to a collection and SubmitForm to persist it.

Why it fails: The Add Picture control opens the device's photo picker and returns an image only from existing gallery media; it cannot capture a new photo with the camera. Using Collect into a local collection also loses the binary payload when the app session ends, and SubmitForm requires an attached form context that this scenario does not provide.

Add a Barcode scanner control and bind its value to the File column, then call SaveData to persist.

Why it fails: Barcode scanners return decoded text strings, not image bytes, so the value cannot populate a Dataverse File column. SaveData writes local collections to device storage, not to Dataverse, so even if the value were binary it would never reach the table. This control is intended for scanning codes, not capturing photographs.