Skip to content

Power Platform App Maker Associate (PL-100) - Practice Questions

15 questions for PL-100 prep, weighted toward creating apps (30-35%), then designing business solutions (20-25%), working with data and services (15-20%), and deployment and business logic.

Cert page: exams/azure/pl-100/

Question 1

Scenario: Requirements gathering reveals a process with several stages, approvals, and a consistent data model used by internal staff.

A. A canvas app B. A model-driven app with a business process flow C. A Power BI report D. A Power Pages site

Answer **Correct: B** **Why:** Model-driven apps generate consistent forms and views from the Dataverse model, and business process flows guide users through defined stages. Canvas apps would mean hand-building each screen and reimplementing stage logic. Process-heavy internal applications are the model-driven sweet spot.

Question 2

Scenario: A canvas app gallery should show only records assigned to the signed-in user, and the data source has 20,000 rows.

A. Filter(Cases, Owner.Email = User().Email) using a delegable source and column B. Filter(Cases, Owner.Email = User().Email) with a non-delegable expression C. Load all records into a collection first D. Set the row limit to 2,000

Answer **Correct: A** **Why:** Delegation is the central canvas app performance concept: when an expression is delegable, the filter runs at the data source, so only matching rows come back. Non-delegable expressions silently operate on the first 500 to 2,000 rows and give wrong results without an error. Collecting everything locally has the same ceiling.

Question 3

Scenario: A field must be required only when another field equals "Other".

A. A business rule in Dataverse with a condition and a set-requirement action B. A workflow C. A DLP policy D. A security role

Answer **Correct: A** **Why:** Business rules apply declarative field logic (show or hide, set required, set value, validate) at the table level, so they apply consistently in every model-driven app and form. Implementing it in one form's script would leave the other entry points unvalidated.

Question 4

Scenario: Data is currently in an Excel file on SharePoint and must move into Dataverse.

A. Dataflows to import and map columns, or the import wizard for one-off loads B. Copy and paste rows manually C. Rebuild the app around Excel D. Use Power BI

Answer **Correct: A** **Why:** Dataflows handle the transform and the column mapping and can be refreshed on a schedule, which is what you want if the source keeps producing files. Keeping Excel as the backing store means no relational integrity, no row-level security, and delegation problems.

Question 5

Scenario: A canvas app should navigate to a detail screen and pass the selected record.

A. Navigate(DetailScreen, ScreenTransition.Cover, {SelectedItem: Gallery1.Selected}) B. Set(DetailScreen) C. Patch(DetailScreen) D. Refresh(Gallery1)

Answer **Correct: A** **Why:** `Navigate` moves between screens and its third argument passes context variables. `Patch` writes records, `Set` creates a global variable, and `Refresh` re-reads a data source. Using a context variable rather than a global keeps the value scoped to the screen that needs it.

Question 6

Scenario: A form should save a new record and handle failure gracefully.

A. SubmitForm(Form1) with OnFailure showing the error, and OnSuccess navigating away B. Patch() with no error handling C. Navigate() only D. Reset(Form1)

Answer **Correct: A** **Why:** `SubmitForm` performs validation and writes, and the form's `OnSuccess` and `OnFailure` properties are where you handle both outcomes. Navigating away unconditionally is the common bug that hides save failures from users.

Question 7

Scenario: A solution must be moved from development to production so that production components cannot be edited directly.

A. Export as a managed solution and import into production B. Export as unmanaged C. Copy the app by hand D. Share the development environment

Answer **Correct: A** **Why:** Managed solutions lock components in the target environment and can be cleanly uninstalled, which is why they are the standard for anything downstream of development. Unmanaged solutions are for the development environment where components are still being authored.

Question 8

Scenario: A connection reference and an environment variable are used in a solution. Why?

A. To hard-code values B. So connections and configuration values can differ per environment without editing the components C. To improve performance D. They are mandatory in canvas apps

Answer **Correct: B** **Why:** Without them, a flow imported into production would still point at the development SharePoint site and the developer's connection. Connection references and environment variables are the parameterization that makes a solution genuinely portable across environments.

Question 9

Scenario: An app must be usable by someone relying on a screen reader.

A. Set accessible labels on controls, ensure tab order and focus are logical, and check color contrast with the accessibility checker B. Increase the font size only C. Add more images D. Nothing, Power Apps handles it

Answer **Correct: A** **Why:** The accessibility checker in Power Apps Studio flags missing labels, contrast problems, and tab order issues. PL-100 explicitly covers accessibility, and it is one of the areas where a low-code tool will happily let you ship something unusable if you never check.

Question 10

Scenario: Users report the app is slow to open.

A. Reduce controls per screen, avoid heavy OnStart work, use concurrent loading, and delegate queries B. Add more screens C. Increase the license tier D. Disable delegation warnings

Answer **Correct: A** **Why:** Startup cost is dominated by `OnStart` logic and the number of controls loaded. `Concurrent()` parallelizes independent calls, and delegation keeps data volumes small. Suppressing delegation warnings hides the problem that is most likely causing both slowness and wrong data.

Question 11

Scenario: A model-driven app must show related cases on the account form.

A. A one-to-many relationship with a related records subgrid on the form B. A separate app C. A Power BI tile D. A canvas gallery

Answer **Correct: A** **Why:** The relationship is what makes the subgrid possible, so the data model comes first and the form follows. This is the model-driven pattern in miniature: define the relationship in Dataverse and the UI capability follows automatically.

Question 12

Scenario: An app must send a notification when a record's status becomes Approved.

A. A Dataverse-triggered cloud flow filtered on the status column change B. A scheduled flow every minute C. Manual email D. A business rule

Answer **Correct: A** **Why:** The Dataverse connector's "when a row is modified" trigger supports filtering to specific columns, so the flow only fires on the change you care about. A one-minute schedule burns API calls and adds latency. Business rules do field logic and cannot send mail.

Question 13

Scenario: Sensitive salary data in a Dataverse table must be hidden from most users but visible to HR.

A. Column-level security with a security profile granting HR read access B. Hiding the column on the form C. A different table D. A canvas app filter

Answer **Correct: A** **Why:** Column (field) level security enforces at the platform, so the value is masked in every app, view, export, and API call. Hiding a column in a form or filtering in a canvas app is presentation only and is bypassed by anyone using another client.

Question 14

Scenario: A maker needs to validate that a solution meets requirements before release.

A. User acceptance testing against the documented requirements, plus the solution checker for code and configuration issues B. Ship and see C. A performance test only D. Peer review of screenshots

Answer **Correct: A** **Why:** Solution checker analyzes for performance, stability, and security issues automatically, and UAT validates the thing nobody can automate: whether it solves the business problem. PL-100 treats requirements traceability as part of the maker's job, not the sponsor's.

Question 15

Scenario: An app should be shared with a department of 200 users with the least ongoing administration.

A. Share with a Microsoft Entra security group rather than individual users B. Share with each user individually C. Make the environment public D. Email the app link

Answer **Correct: A** **Why:** Group-based sharing means joiners and leavers are handled by group membership, which is already maintained. Individual sharing turns every personnel change into an administrative task and reliably leaves ex-members with access.

Where to go deeper