PL-600 sample exam questions

A custom connector wraps the third-party API, a Power Automate cloud flow triggers on lead create/update events, and the Dataverse connector creates or updates the lead in the Power Apps app. Dual-write is only for Finance and Operations apps, and dataflows are scheduled bulk imports, not event-driven sync.

Using a value/effort priority matrix, helping sales reps find assets faster is high value with low effort (a quick win, for example better views and search). Consolidating three systems so management can view inventory and asset details is high value but high effort, a big investment.

Good requirements are specific and measurable. Viewing current month sales is a concrete data need, GDPR names a specific regulation unlike vague local regulations, and making users more efficient is a measurable people outcome rather than a subjective goal like happiness.

An alternate key uniquely identifies records using source values, so imports update existing rows instead of creating duplicates. Orphaned records appear when children load before their parents, so parent tables must be imported first to let lookups resolve. Data Integrator is being retired in favor of dataflows.

A parental relationship cascades delete, so removing a manufacturer also removes its models. Field mappings on a 1:N relationship copy parent values into a child row created from the parent's related list. An N:N relationship would break the one-manufacturer rule.

Users are added to the environment's user table automatically on first access or via sync, but without a security role they still cannot open the app. Adding them to the user table alone does not grant app access, so the goal is not met.

Review the Dataverse analytics dashboard in the Power Platform admin center to see API call volume and which users or apps consume it, then resolve the shortfall by adding capacity add-ons (for example Power Platform request capacity). The Power Apps usage and Power Automate runs dashboards do not show Dataverse API consumption.

Lookups resolve only if the parent records already exist, so accounts must be imported before the records that reference them. An embedded Power BI dashboard appears only for users it has been shared with, because sharing the app does not share Power BI content.

Dynamics 365 model-driven apps provide built-in charts, dashboards and reports over Dataverse data, and Power BI provides interactive, cross-source reports and dashboards, so each is a complete reporting solution. AI Builder is for AI models, and SSRS is a legacy on-premises reporting server not used directly with Dataverse online.

Relecloud's scenario centers on agents handling customer interactions, reservations and reported issues, which matches Dynamics 365 Customer Service with cases, queues, knowledge and routing. Field Service targets onsite technicians, Sales targets pipeline management, and Project Operations targets project delivery.

The Microsoft Dataverse connector (for example in Power Automate) can create and update the machine (customer asset) rows that Dynamics 365 Field Service stores in Dataverse. Dual-write is only for syncing with finance and operations apps, and Lifecycle Services is a finance and operations project management portal.

Virtual tables expose the historical job placement data from the external source inside Dataverse without migrating it, so users can view it in their apps on demand. Power BI only reports on it, flows would copy data, and chatbots do not provide data access in the app.

Meal selections change over time and may carry extra details, so storing them in a separate table and referencing it with a Lookup column lets the business maintain meals as data without customizing the solution. Option sets (local or global) and Two Options are fixed lists that require customization to change.

Installing the inspection solution in the existing Dynamics 365 Field Service environment lets it use the same Dataverse data (work orders, assets, customers) without integration. Separate environments would require data synchronization, and the default environment is not the Field Service production environment.

App checker in Power Apps Studio flags formula errors, accessibility and performance issues in a canvas app, and solution checker runs static analysis against the solution containing the app. The Errors function only returns data source errors at runtime, and the admin center does not diagnose app functionality.