CCNA Demonstrate the capabilities of Power Apps Questions

Model-driven apps inherit Dataverse's role-based security model, so access to tables, records and commands is governed by security roles assigned to users or teams. This built-in enforcement distinguishes them from canvas apps, which require manually configured data-source permissions.

Form controls bind individual controls to columns through data cards. Placing the camera's Photo property inside a data card mapped to an image or file column on the Work Orders table lets the form's SubmitForm write the captured image to that column on the currently selected record, which is exactly what attaching a photo to a work order requires.

Canvas apps bind directly to an Excel workbook stored in OneDrive as a tabular data source, letting the maker design screens and controls over that table. This suits a simple personal expense tracker without needing Dataverse or a data model.

Clearing the dropdown sets Dropdown.Selected to blank, so Dropdown.Selected.Value returns nothing. The Filter expression then matches no records, leaving the gallery empty. The Items property must handle the blank case, typically via an If or Coalesce wrapper.

Because model-driven apps are metadata-driven, forms and views are created from the table definitions and then tailored in the modern app designer or classic form editor. This is central to the claims scenario, where a consistent data-first experience matters more than bespoke screen design, and it is a core model-driven capability.

Enabling offline capability lets the canvas app cache submissions locally and sync them to Microsoft Dataverse once connectivity returns, directly addressing the intermittent-connection constraint in the stem. Without it, writes fail silently during outages. This is the only option that preserves data across disconnections rather than merely warning users or retrying after failure.

Model-driven apps generate a responsive UI directly from the Dataverse data model, so no manual layout is needed. Because Dynamics 365 Sales stores its records in Dataverse, the app can display and update those records natively, satisfying the automatic UI generation requirement.

Canvas apps connected to SharePoint inherit the list's item-level permissions; users lacking SharePoint list access see no data even though the app itself is shared. This explains why direct Power Apps access works but Teams access fails.

Delegation warnings arise when operations cannot be translated into Dataverse queries. Using delegable functions such as Filter and LookUp pushes record selection to the server, so only the required rows return and updates proceed without client-side limits.

Business process flow stages can carry a condition that gates progression; if its criteria are unmet, the Next button stays disabled regardless of completed fields. Checking that condition identifies why users are blocked at the stage.

Power Pages supports anonymous access, letting external vendors reach the portal without any Microsoft account sign-in. This directly satisfies the stem's constraint that users must not authenticate with Microsoft Entra ID credentials, unlike Power Apps portals requiring licensed internal users.

The AI Builder invoice processing model is prebuilt to extract header and line-item fields such as vendor, total and date from invoice documents. It satisfies the stem's requirement to extract information from uploaded invoices without training a custom model.

Dataverse provides relational data storage, rich metadata, and built-in security roles, making it ideal for complex relationships and business rules. It supports table relationships, business rules, and column-level security, which SharePoint lists lack. This aligns with the team's need for a robust data platform.

A custom connector lets the maker declare API key authentication, so Power Apps injects the key header on every call without exposing it in formulas. This satisfies the stem's requirement to fetch employee details from a REST API secured by a header key, and the connector can be shared and governed through a Power Platform environment.

The Camera control provides a live preview and allows the user to capture a photo. The captured image is available in the control's Photo property. To save it to Dataverse, you use the Patch function to create or update a record, setting the image column to the Camera control's Photo. This is the standard pattern for capturing and storing photos in a canvas app.

Canvas apps support offline capability through the SaveData and LoadData functions, storing data locally on the device and syncing when connectivity returns. This directly satisfies the requirement that store managers approve discount requests without network access.

The receipt processing model extracts merchant, date and total from scanned receipts, and Power Apps can bind those outputs to form fields. This satisfies the requirement to populate amount and date automatically from a camera capture.

A canvas app provides the responsive form and receipt upload across mobile and desktop browsers, while a Power Automate flow triggered on submission routes the report through the approval workflow. Together they satisfy the cross-device and approval requirements.

The Co-owner role allows a user to edit the app, including adding screens and changing formulas, and also to share it with others, but it does not grant publishing rights to the environment's production apps. This matches the requirement of editing structure without publishing to end users.

Dataverse mobile offline sync replicates rows to the technician's device using offline profiles, letting the app read and write locally without connectivity. Once the network returns, queued changes synchronise back to Dataverse, resolving conflicts automatically. This directly satisfies the stem's requirement for offline operation with later data synchronisation.

Dataverse table business rules run server-side whenever a record is created or updated, so the priority field is set to High automatically regardless of which app or form edits the case. This satisfies the requirement for consistent enforcement across all client interfaces.

The Office 365 Users connector's action returns profile data for a specified user, and the JSON binds the record owner's identifier as its input. This satisfies the stem's requirement to resolve the owner's profile rather than the current user's.

Model-driven apps assemble components from Microsoft Dataverse, generating responsive UI automatically from the data model, relationships and business logic. This satisfies the stem's requirement for a Power Apps app type, alongside canvas apps, without requiring manual pixel-level screen design.

SharePoint connectors cap non-delegable queries at 500 or 2000 records, so the app retrieves only a subset and processes the rest locally, causing slowness. Delegation-compatible functions and filters push filtering to SharePoint, satisfying the need to handle over 10,000 items efficiently.

Power Automate provides approval actions with configurable approvers, outcomes and notifications, and canvas apps can trigger these flows. It satisfies the stem's requirement to define the expense report approval process, which Power Apps alone cannot orchestrate.

The template gallery provides pre-built apps with predefined screens, data connections and layouts, letting the analyst start from an existing design. This satisfies the stem's requirement to build an app quickly using a pre-built template.

AddDays accepts a date and a number of days, returning that date offset forward. Passing Today() with 7 yields the date one week from now, matching the stem's requirement exactly; the function's argument order is date first, increment second.

Canvas apps provide pixel-level control over form layout and include the Attachments control, letting employees attach receipt files to the submitted expense report. This satisfies both the flexible form design and file attachment requirements, which model-driven forms handle less flexibly.

Dataverse security roles define privileges at the table level with access scopes such as User, Business Unit, or Organization. Setting the read and write privileges to User scope means users can only access records they own. Assigning this role to the group enforces record-level security directly in Dataverse, which the canvas app respects because it uses the user's credentials. This is the correct way to restrict access to owned records.

A quick view form on the Project form surfaces read-only Account fields, such as name and phone number, from the related record via the lookup. This satisfies the requirement without duplicating data or altering the Account entity.

Setting the button's DisplayMode to Disabled after submission blocks further clicks, so the OnSelect patch runs once and duplicate Dataverse records are prevented. This directly addresses the double-click cause rather than filtering duplicates after they are created.

Microsoft Dataverse requires a premium connector.

Canvas apps give pixel-level control over the mobile interface and connect to data through connectors, letting makers build and publish without pro-code development. This satisfies the stem's no-code customisation and deployment requirement, unlike model-driven apps, which are metadata-driven.

Excel workbooks stored in OneDrive for Business or SharePoint use the standard Excel connector, which is included in the Power Apps seeded licence. It therefore connects directly without consuming a premium connector, satisfying the no-premium-connector constraint in the stem.

Global variables are stored client-side in the app, so any user can inspect them at runtime via the browser or Power Apps Studio. Storing the API key there exposes the credential to end users, satisfying the stem's requirement to identify the security concern.

Business rules can set a column to required dynamically when conditions are met, so the field appears optional on the form yet blocks saving. Users believe they completed the fields, but the rule enforces a requirement the form does not visually indicate.

The map control renders address data from a form's address fields as an interactive map, letting users visualise customer locations directly. Enabling it on the form satisfies the requirement to see all customer addresses plotted geographically.

AI Builder's prebuilt sentiment analysis model classifies text as positive, negative or neutral and returns confidence scores. It plugs into Power Apps and Power Automate, so survey responses can be scored automatically without training a custom model.

A calculated field derives its value at read time from other columns using a defined formula, so quantity multiplied by unit price updates automatically whenever either source field changes, with no workflow or plug-in required.

Canvas apps offer a drag-and-drop designer with no code, and their flexible layout suits a form-based submission and approval flow. This satisfies the requirement for a no-code expense app where users submit and managers approve or reject.

The formula bar sits directly beneath the ribbon in Power Apps Studio, letting makers write and edit Power Fx expressions that drive control behaviour and properties. It satisfies the stem's requirement for a genuine Canvas app authoring component, unlike data connectors or environment settings, which belong elsewhere in the platform.

Excel locks the workbook during each write, so simultaneous submissions collide and later writes overwrite earlier ones, losing entries. This satisfies the stem's concurrency constraint: Excel is a single-user file format, not a transactional datastore. Migrating to Microsoft Dataverse or SharePoint lists would preserve every submission.

Dataverse connects natively through the built-in connector, so canvas apps query tables directly without an on-premises data gateway. The gateway requirement applies only to sources behind a network boundary, which Dataverse is not, satisfying the stem's "without using a gateway" constraint.

Security roles define privilege levels per entity, including Delete versus Write, and can be assigned to teams or users. Managers receive a role granting Delete; others receive a role with Write but no Delete, precisely satisfying the stated constraint.

Model-driven apps render Dataverse tables as forms, views and dashboards, and the timeline control automatically surfaces related visit records for each patient. This satisfies the Dataverse storage and auto-generated timeline constraints without custom canvas coding.

The Pen input control is designed for freehand drawing and signature capture on touch devices. It exposes the Image property, which returns the drawn strokes as an image that can be written to a Dataverse image column on the work order record. This directly satisfies the requirement of capturing and storing signatures.

Business rules run server-side on the table, so the discount validation applies across every form, view and API write, not just one app. This enforces the 50% limit consistently at the data layer, satisfying the model-driven app's requirement.

Canvas apps give full control over the layout and formulas, so the analyst can add date pickers and a calculated label using DateDiff to derive the number of days between start and end dates, satisfying the automatic calculation requirement.

A Power Automate flow registered on the Dataverse lead-creation message runs automatically when a lead record is created, letting it create and assign a task to the sales team, which satisfies the required automated trigger.

The Start with data wizard in Power Apps Studio automatically generates a three-screen canvas app (browse, detail, and edit/create) based on a selected data source such as a SharePoint list. It creates the necessary forms and galleries, allowing a non-developer to quickly produce a working app for submitting expense reports.

Canvas apps store data locally via the offline profile, letting the Camera and Signature controls capture images and signatures without connectivity. Dataverse queues these records and syncs them automatically once the device reconnects, satisfying the offline capture constraint for text, images, and signatures.

Model-driven apps are built on Microsoft Dataverse and automatically generate UI components such as forms, views, and dashboards from the underlying data model. They honor Dataverse security roles and business rules without custom code, which matches the requirement for field representatives to look up customers, view orders, and update accounts with minimal coding effort.

Power Automate flows trigger on Dataverse events, such as a support ticket's status changing to Resolved, then execute actions automatically — here, creating a follow-up task record. This satisfies the stem's requirement to automate task creation without user intervention, unlike manual configuration or static business rules.

A radio control presents mutually exclusive options, letting managers select a single decision such as approve or reject. This satisfies the requirement to capture one definitive choice per request, preventing contradictory selections that checkboxes or text inputs would allow.

Canvas apps render pixel-perfect interfaces that can be published as a Teams tab or personal app, satisfying the embedding requirement directly. Unlike model-driven apps, which depend on Dataverse and follow a fixed, form-based layout, canvas apps give the designer full control over the UI, making them the appropriate choice for a Teams-embedded Power Apps experience.

Power Automate cloud flows can be triggered by Dataverse events such as when a record is updated. You can configure the flow to check if the case was escalated, then send an email and update the priority. This requires no code and integrates directly with Dataverse, making it the correct solution for the scenario.

The Item property on an Edit form or Display form control determines which record the form displays. By setting this property to the gallery's Selected property, the form dynamically updates to show the details of whichever project the user selects. This is the standard way to link a gallery and a form in a canvas app so that selection drives the form content.

Canvas apps let makers place controls such as the Camera control on a blank canvas, bind them to Dataverse as a data source, and use formulas to write the captured image and work order number. This supports fast drag-and-drop development with no server-side code, matching the technician's needs.

Model-driven apps are built on Dataverse tables, and the maker must create the custom table for cases, then create a model-driven app that includes forms, views, and a dashboard. These components are defined within the app designer or solution explorer to provide the required user interface and data management.

Microsoft 365 Outlook is a cloud service, so canvas apps connect to it through the built-in Office 365 Outlook connector using standard authentication. No on-premises data gateway is required because the data never resides behind a corporate network boundary.

Functions are built-in operations in Power Fx, the canvas app formula language, performing tasks such as text manipulation, date arithmetic and conditional logic. They satisfy the stem's requirement for a formula-language component, alongside operators and identifiers, by providing the callable expressions that formulas evaluate.

Power Apps provides a low-code designer where makers build custom business apps by dragging controls and connecting data sources, requiring minimal traditional programming. This is a core platform capability, satisfying the question's requirement for a genuine Power Apps feature.

Canvas apps can be embedded as a tab in a Teams channel, allowing users to interact with the app directly within the channel. This is the recommended approach for embedding a custom app into a channel.

Canvas apps give the maker full control over layout and behaviour through a drag-and-drop designer and Power Fx formulas, so a business user can assemble screens and logic without writing code. This satisfies the no-code requirement, unlike model-driven apps, which are generated from Dataverse metadata.

Business rules in model-driven apps run client-side and server-side against Dataverse tables, enforcing field validation, required values, and conditional logic without custom code. This satisfies the stem's validation requirement directly, unlike canvas-only features. They apply consistently across forms and views, making them a core model-driven capability.

When a query is delegable, Power Apps pushes the operation to SharePoint and processes all rows server-side. Non-delegable expressions are evaluated locally and capped at the delegation limit, so only a subset returns. Restricting Filter, Search, and Sort to SharePoint-delegable constructs makes results complete across the 50,000 rows.

Command bar custom commands attach buttons to a model-driven app's command bar and can run JavaScript that creates a record of a specified table, such as Inspection. This is the supported mechanism for triggering record creation from a button in model-driven apps.

A canvas app gives mobile availability and can call the OAuth 2.0 REST API through a custom connector, while Power Automate handles the conditional second-level approval for reports over $1,000. This combination satisfies the API integration, approval threshold and mobile requirements together.

A canvas app gives makers a blank canvas where they drag and drop controls such as galleries, labels, and buttons, then bind them to a data source like SharePoint. Because the team has no developers and needs a custom layout with quick delivery, the pixel-perfect design freedom and connector-based data binding of a canvas app match the requirement exactly.

The gallery's Items property binds to SalesData, a Microsoft Dataverse data source pointing at the accounts entity, with a Filter expression restricting rows to status = 'Active'. The gallery therefore draws its records from that filtered Dataverse Accounts source, satisfying the manifest's declared dataSources constraint.

Command bar buttons can be hidden by role-based visibility rules, so users lacking the required security role never see the button. Since the form customisation is confirmed correct, the differing security role assignments across users explain the intermittent absence.

Dataverse auditing records create, update and delete operations with user, timestamp and old/new values, satisfying the audit requirement. Business unit security roles then restrict record visibility to the same business unit, meeting the second constraint without custom code.

Canvas apps provide a built-in Barcode Scanner control that can be added from the Insert menu without writing code. This control uses the device camera to scan barcodes and returns the scanned value, which can then be used to look up inventory data. This approach requires no professional development and is ideal for non-developers.

SharePoint Online is a cloud service reachable directly over the internet, so the canvas app's connector authenticates to it without any on-premises data gateway. The gateway is only needed for resources inside a private network.

Assigning the 'Help Desk Agents' security role grants that team the Dataverse privileges to edit ticket records. Combined with broader read access for all employees, this satisfies the stem's constraint that only Help Desk Agents can edit tickets while everyone can view them.