Microsoft Power Platform Functional Consultant PL-200 Exam Dumps and Practice Test Questions Set 9 Q161-180

Visit here for our full Microsoft PL-200 exam dumps and practice test questions.

Question 161:

A company wants to ensure that when a new Dataverse record is created, an approval workflow is automatically initiated and approvers can respond via email. Which solution should they implement?

A) Power Automate approvals

B) Canvas app buttons

C) Scheduled cloud flow

D) Model-driven form rules

Answer: A) Power Automate approvals

Explanation:

Power Automate approvals allow organizations to create automated, multi-step approval workflows. When a new Dataverse record is created, the approval process can trigger automatically, sending requests via email to the assigned approvers. Approvers can respond directly in email or through Microsoft Teams, and the workflow can automatically update the record’s status based on their decisions. The process is fully auditable, and comments can be captured for accountability. This ensures that approvals happen consistently without manual intervention and integrates seamlessly with Dataverse records. Approvals can include conditional branching, multiple approvers, or escalations depending on business requirements, providing a flexible and robust solution for automation.

Canvas app buttons are triggered manually by users and cannot initiate workflows automatically when a record is created. Relying on users to trigger approvals introduces delays and the possibility of human error.

Scheduled cloud flows run at predefined intervals, such as daily or hourly, and cannot respond immediately to the creation of new records. They are not suitable for real-time approval processes that require instant notification.

Model-driven form rules enforce behaviors within a specific form, such as field visibility, required fields, or data validation, but they do not automate approval processes. They are designed to guide user input and maintain data integrity within the form, but they cannot send emails, route requests, or update statuses automatically based on user actions. Power Automate approvals, on the other hand, provide a comprehensive solution for automating approval workflows. They enable real-time, email-based approval requests that are integrated with Dataverse, allowing designated approvers to review and respond without manual follow-up. By automating the routing, notifications, and tracking of approvals, Power Automate approvals streamline business processes, reduce errors, and ensure consistency across the organization, making them the correct choice for managing automated approval workflows.

Question 162:

A company wants to restrict users so that they can only see the Dataverse records they own, while managers can see all records. Which feature should they configure?

A) Row-level security with security roles

B) Canvas app filters

C) Power BI row-level security

D) Business process flow stages

Answer: A) Row-level security with security roles

Explanation:

Row-level security in Dataverse allows organizations to define access permissions at the record level using security roles and business units. By assigning appropriate roles, users can be restricted to viewing only the records they own, while managers can be given broader access to view all records. This enforcement occurs at the database level, ensuring that permissions apply consistently across all apps, including canvas apps, model-driven apps, and portals. Row-level security supports different privileges like create, read, write, and delete, enabling fine-grained control over data access. Using business units further allows organizations to structure access hierarchies that reflect real-world reporting lines or departmental divisions.

Canvas app filters can limit what is displayed within a specific app, but they do not enforce security at the database level. Users could access the same records through another app or API, bypassing the filters.

Power BI row-level security only restricts what users see in reports and dashboards. It does not prevent users from accessing the underlying records in Dataverse through other applications.

Business process flow stages guide users through a sequence of steps, but do not enforce record-level access restrictions. They help ensure workflow compliance, but cannot prevent unauthorized viewing or editing of data. Canvas app filters allow users to limit or customize the data displayed within a specific app interface, but they only affect the view in that app and cannot enforce database-level security. Power BI row-level security restricts data visibility within Power BI reports, but it does not control access to the underlying Dataverse or database records outside of the reporting context. Business process flow stages guide users through tasks and processes to ensure correct steps are followed, but they do not restrict which records users can see or edit. Row-level security using security roles and business units, however, enforces consistent, database-level access control. It ensures that users can only view or modify records according to their role or ownership, providing a reliable and system-wide mechanism for protecting sensitive data. This makes row-level security the correct choice for controlling record access across an organization.

Row-level security with security roles is the correct solution because it provides consistent, database-level access control across all interfaces and applications.

Question 163:

A company wants to track the duration between the creation of a case and its resolution automatically. Users should not have to enter timestamps manually. Which feature should they implement?

A) Dataverse calculated columns

B) Canvas app timers

C) Power BI measures

D) Model-driven form rules

Answer: A) Dataverse calculated columns

Explanation:

Dataverse calculated columns enable automatic computation of values based on other fields, including timestamps. For tracking duration between case creation and resolution, a calculated column can subtract the creation date from the resolution date to determine elapsed time. These calculations occur at the database level, ensuring consistency across all apps and interfaces accessing Dataverse. Users do not need to enter any values manually, reducing errors and administrative effort. Calculated columns update dynamically as underlying fields change, providing real-time accuracy. This allows metrics to be used in reporting, workflows, or automation without additional user intervention.

Canvas app timers depend on users interacting with the app and only run when the app is open. They cannot perform database-level automatic calculations across all records.

Power BI measures calculate data for visualizations but do not write results back to Dataverse. While they can display durations in reports, they cannot provide persistent tracking in the database itself.

Model-driven form rules enforce validation or behavior in forms, but do not automatically calculate durations at the system level. They only work when records are accessed in specific forms.

Dataverse calculated columns are the correct solution because they provide automatic, consistent, and accurate tracking of durations without requiring user input. Dataverse calculated columns are a feature within Microsoft Dataverse that allows users to create fields whose values are automatically computed based on other columns in the same table. These calculations are performed at the database level, ensuring that the resulting data is always consistent and up-to-date without requiring manual intervention. Calculated columns can perform mathematical operations, concatenate text, or evaluate logical conditions, allowing organizations to implement business logic directly within the data layer. For example, a calculated column could automatically determine a discount amount based on the total order value or compute a full name by combining first and last name fields. Because the calculation is handled within Dataverse, the computed data is available to all apps and processes connected to the table, including model-driven apps, canvas apps, workflows, and Power Automate flows. This centralized approach reduces redundancy, ensures accuracy, and simplifies reporting and integration with other systems.

Canvas app timers, in contrast, are components within Power Apps Canvas apps that allow developers to trigger actions based on time intervals or delays. A timer can start automatically when a screen loads or when a user interacts with an element, and it can execute functions such as updating a variable, navigating to another screen, or triggering a flow after a specified duration. While timers are useful for creating interactive or dynamic experiences in a canvas app, they do not perform database-level calculations or enforce business logic. Their functionality is limited to controlling events within the app interface, and any calculated results produced using a timer are temporary unless explicitly stored back into Dataverse or another data source. Timers are primarily a user interface tool to manage events and improve app interactivity, not a mechanism for consistent, centralized data computation.

Power BI measures are DAX (Data Analysis Expressions) formulas used to create dynamic calculations in reports and dashboards. Measures allow analysts to compute totals, averages, percentages, or more complex aggregations on data that may change depending on filters or slicers applied in the report. They are extremely powerful for visualizing trends and performing analytical calculations without modifying the underlying data. However, measures are calculated at the reporting layer, meaning they do not create persistent values in the database and are only visible within Power BI reports. While measures enhance reporting and analytics capabilities, they cannot enforce real-time calculations or business logic at the data level, and their results cannot be directly leveraged by other apps or automated processes without additional integration.

Model-driven form rules are used within model-driven apps in Power Apps to enforce behaviors, validations, or conditional logic at the form level. They can make fields required, set default values, hide or show fields, or display error messages based on user input. Form rules help ensure data consistency and guide users when entering information in a form. However, they operate only within the context of the form being used and do not create persistent calculated values in Dataverse. They cannot automatically compute field values that are accessible across multiple apps or enforce business logic at the database level. Their effect is limited to the user interface experience and does not extend to workflows, integrations, or reporting outside the form.

In summary, Dataverse calculated columns provide centralized, database-level calculations that are automatically maintained and accessible across all apps and processes using the table. Canvas app timers enable time-based actions within canvas apps, but do not enforce persistent calculations. Power BI measures perform dynamic analytical calculations for reporting, but do not create database-level values. Model-driven form rules enforce behaviors and validation at the form interface but cannot perform centralized, persistent calculations. For scenarios requiring automated, consistent, and universally available calculated values, Dataverse calculated columns are the correct choice. They ensure accuracy, maintainability, and integration across the Microsoft Power Platform ecosystem, making them essential for implementing business logic at the data level.

Question 164:

A company wants external partners to submit support tickets online securely, without requiring Power Apps licenses. The data must be stored in Dataverse and integrated with existing workflows. Which platform should they use?

A) Power Pages

B) Canvas apps

C) Desktop flows

D) Business process flows

Answer: A) Power Pages

Explanation:

Power Pages enables organizations to build secure web portals that connect directly to Dataverse. External partners can submit support tickets via forms, and the data is stored in Dataverse for integration with existing workflows such as approvals, notifications, and automated processes. Power Pages provides authentication and role-based access, ensuring secure and controlled submissions. The low-code platform allows rapid development, customization, and deployment of portals without requiring users to have Power Apps licenses. It also supports responsive design for mobile devices and secure data management.

Canvas apps are designed for internal users and cannot be shared externally without licenses. They do not provide the same level of security or public web access.

Desktop flows automate tasks on local computers and cannot provide an external-facing web interface or authentication for external users.

Business process flows guide internal users through steps within Dataverse, but cannot serve as a portal for external submissions. They do not provide a web interface or secure access for external users.

Power Pages is the correct solution because it provides secure, authenticated, external-facing forms that integrate directly with Dataverse and existing workflows. Power Pages is a Microsoft Power Platform tool that enables organizations to create secure, low-code websites that can interact with data stored in Dataverse. It allows users to design external-facing portals for customers, partners, or employees, providing access to specific data, forms, and workflows without requiring extensive coding knowledge. Power Pages supports features such as authentication, role-based access, customizable forms, and responsive design, making it ideal for scenarios where organizations need to expose data or services online in a controlled and secure manner. Unlike canvas apps, which are primarily used for internal applications and interactive app experiences, Power Pages focuses on web portals that are accessible via browsers to external users.

Canvas apps are designed to create internal apps with flexible layouts and interactive components, suitable for mobile devices or desktops. They allow users to design custom interfaces and connect to various data sources, but they are not intended to create public-facing websites. Desktop flows are automation tools for performing repetitive tasks on a desktop or local system, using robotic process automation (RPA) to mimic human actions. They are focused on internal process automation rather than providing web access to external users. Business process flows guide users through business processes within model-driven apps, ensuring consistent task completion, but they do not provide external-facing web interfaces.

In summary, Power Pages is the correct choice because it is specifically designed to build secure, external-facing websites that interact with Dataverse data, enabling organizations to share information and services with external audiences. Canvas apps, desktop flows, and business process flows serve internal purposes and do not provide public web portals or secure external access, making them unsuitable for scenarios requiring an external-facing site.

Question 165:

A company wants to send notifications to managers when a Dataverse case is escalated. The notifications should include the current owner and case details automatically. What tool should they implement?

A) Power Automate cloud flow

B) Canvas app buttons

C) Desktop flows

D) Model-driven form rules

Answer: A) Power Automate cloud flow

Explanation:

Power Automate cloud flows can automatically trigger when a Dataverse record meets specified conditions, such as a case being escalated. The flow can gather related information, including case details and the current owner, and send notifications via email, Teams, or other channels. This provides real-time alerts to managers without requiring manual monitoring. Cloud flows operate at the database level and ensure notifications are sent regardless of which app or interface users interact with. Conditions, branching logic, and multiple recipients can be included to handle complex escalation rules. Automated flows improve efficiency and reduce delays in response.

Canvas app buttons require manual user interaction to initiate an action and cannot provide automatic notifications for record changes.

Desktop flows automate tasks on a local machine and cannot monitor real-time record changes in Dataverse or send notifications automatically.

Model-driven form rules enforce field behavior or validation in forms but do not provide automated notifications or integration with external communication channels.

Power Automate cloud flows are the correct solution because they provide automated, real-time notifications based on Dataverse record changes.

Question 166:

A company wants to ensure that only specific users can edit sensitive fields in Dataverse, while others can view them. The restriction must apply across all apps and portals. What feature should they configure?

A) Field-level security

B) Canvas app visibility rules

C) Model-driven form rules

D) Business process flow stages

Answer: A) Field-level security

Explanation:

Field-level security in Dataverse allows administrators to control who can read, update, or delete specific fields at the database level. Once configured, these rules apply across all apps, portals, and APIs, ensuring sensitive data remains protected regardless of access point. Security profiles determine which users or roles can edit or view specific fields. This mechanism is critical for compliance with privacy and regulatory requirements. Field-level security is enforced automatically, preventing unauthorized edits without relying on form-specific or app-specific logic.

Canvas app visibility rules can hide fields or make them read-only in a particular app, but they do not enforce security across all access points. Users accessing the same data via another app, portal, or API could bypass restrictions.

Model-driven form rules can control field behavior in specific forms, like making a field read-only, but these rules do not enforce database-level protection and are limited to the form where they are applied.

Business process flow stages guide users through a workflow, but do not enforce access restrictions on individual fields. They help maintain process compliance, but cannot prevent unauthorized editing.

Field-level security is the correct solution because it provides consistent, enterprise-level enforcement of field access across all interfaces.

Question 167:

A company wants to automatically assign new customer support cases to a team based on case category. The assignment should happen without user interaction. Which tool should they use?

A) Power Automate cloud flow

B) Canvas app button

C) Model-driven form rule

D) Scheduled cloud flow

Answer: A) Power Automate cloud flow

Explanation:

Power Automate cloud flows can be triggered automatically when a Dataverse record is created. By configuring a flow to check the category of a case, it can assign the record to the correct team or user without manual input. This ensures that cases are routed efficiently and consistently according to business rules. The flow can include conditional logic, escalation paths, and notifications, providing a robust automated solution for case assignment. Because flows operate at the database level, assignments are applied consistently regardless of the app or interface used to create the record.

Canvas app buttons require manual triggering by a user, making them unsuitable for fully automated assignment. They are dependent on user actions within the app.

Model-driven form rules can influence behavior within a form, but cannot automate assignments without user interaction. They are limited to UI-level enforcement.

Scheduled cloud flows run on predetermined intervals and cannot respond immediately to new record creation, making them unsuitable for real-time automated assignment.

Power Automate cloud flows are the correct solution because they provide real-time, automated, and conditional record assignments.

Question 168:

A company wants to allow external customers to submit feedback online, which will be stored in Dataverse and trigger follow-up workflows. The external users should not need Power Apps licenses. Which platform should they implement?

A) Power Pages

B) Canvas apps

C) Desktop flows

D) Model-driven form rules

Answer: A) Power Pages

Explanation:

Power Pages allows organizations to build secure, external-facing web portals connected to Dataverse. Customers can submit feedback forms, which are stored in Dataverse for subsequent processing. Role-based access and authentication ensure secure submissions, while low-code design allows rapid creation of forms and workflows. The submitted data can trigger Power Automate flows, such as follow-up emails or case creation, ensuring integration with internal processes. This solution does not require external users to have Power Apps licenses, making it cost-effective and user-friendly for public-facing interactions.

Canvas apps are designed for internal users and cannot provide secure external access without licenses. They are not suitable for public-facing web submissions.

Desktop flows automate local tasks and cannot provide web forms or secure external submission. They operate on the user’s computer and are unsuitable for external-facing processes.

Model-driven form rules control behavior in specific forms within apps, but do not provide a portal for external users to submit data securely.

Power Pages is the correct solution because it provides a secure, license-free, external-facing platform integrated with Dataverse and workflows.

Question 169:

A company wants to calculate the total time a support case remains in each stage automatically, without user input. Which feature should they use?

A) Dataverse calculated columns

B) Canvas app timers

C) Power BI measures

D) Model-driven form rules

Answer: A) Dataverse calculated columns

Explanation:

Dataverse calculated columns allow automatic computation of values based on other fields, including timestamps. For tracking the duration of each stage, calculated columns can subtract the timestamp of the previous stage from the current stage timestamp to produce elapsed time. Calculations are performed at the database level, ensuring accuracy across all apps and interfaces. Users are not required to input timestamps manually, which reduces errors and ensures consistent tracking. Calculated columns update dynamically as the underlying data changes, enabling real-time analytics and integration with flows or dashboards.

Canvas app timers operate only while a user interacts with the app and cannot perform database-level calculations for all records automatically.

Power BI measures compute metrics for reports, but does not store results in Dataverse, making them unsuitable for operational tracking of stage durations.

Model-driven form rules enforce field behavior and validation, but cannot perform automatic duration calculations across records without user interaction.

Dataverse calculated columns are the correct solution because they provide automated, accurate stage duration calculations without manual input.

Question 170:

A company wants to notify managers whenever a Dataverse case is escalated, including case details and the current owner. The notifications must be automated. Which tool should they use?

A) Power Automate cloud flow

B) Canvas app button

C) Desktop flow

D) Model-driven form rule

Answer: A) Power Automate cloud flow

Explanation:

Power Automate cloud flows can be configured to trigger automatically when a Dataverse record meets specific conditions, such as an escalation. The flow can retrieve related details, including the current owner and other case information, and send notifications via email or Teams. This ensures real-time, automated alerts without requiring manual monitoring or user interaction. Cloud flows run at the database level, ensuring consistency across all interfaces and applications. They can include conditional logic to handle complex rules, multiple recipients, or escalation paths. Automated notifications improve responsiveness and reduce delays in critical case management.

Canvas app buttons depend on user interaction and cannot trigger notifications automatically when a record is updated.

Desktop flows automate tasks on a local machine and cannot monitor Dataverse in real-time or send automatic notifications.

Model-driven form rules enforce field behavior in specific forms but cannot send automated notifications or integrate with external communication channels.

Power Automate cloud flows are the correct solution because they provide automated, real-time notifications for record changes in Dataverse.

Question 171:

A company wants to create an app that allows sales representatives to update customer data from mobile devices, including dynamic fields that appear based on previous selections. The data must sync with Dataverse. Which platform should they use?

A) Canvas app

B) Power BI report

C) Desktop flow

D) Business process flow

Answer: A) Canvas app

Explanation:

Canvas apps provide a low-code platform to design interactive applications with complete control over layout, input fields, and behavior. For mobile sales representatives, canvas apps can dynamically display fields based on previous user selections, ensuring a responsive and user-friendly interface. The app connects directly to Dataverse, ensuring that all updates are synchronized and stored securely. Offline capabilities allow users to continue data entry in areas with limited connectivity, syncing data automatically when the connection is restored. Conditional formulas enable validation, real-time calculations, and automated updates, ensuring data integrity. Canvas apps are ideal for scenarios that require custom user interfaces, mobile accessibility, and dynamic behavior.

Power BI reports are for visualization and analytics, not data entry. They cannot provide interactive forms or mobile input capabilities.

Desktop flows automate tasks on a local computer and are not designed for interactive mobile applications or dynamic forms.

Business process flows guide users through a sequence of stages in Dataverse, but do not provide interactive, customizable mobile applications. They enforce workflows but cannot implement dynamic field behavior for mobile use.

Canvas apps are the correct choice because they provide dynamic, mobile-accessible, and Dataverse-integrated applications.

Question 172:

A company wants to ensure that critical fields in Dataverse are always filled during record creation, regardless of which app is used. What feature ensures this?

A) Required field property in Dataverse

B) Canvas app validation formulas

C) Model-driven form rules

D) Business process flow stages

Answer: A) Required field property in Dataverse

Explanation:

Setting a field as required at the Dataverse table level enforces data entry rules across all applications and interfaces. Users cannot create or save records without completing required fields, ensuring consistent and complete data. This enforcement applies to model-driven apps, canvas apps, Power Pages, and API calls, providing organization-wide data integrity. Required fields eliminate the need to configure validations in multiple apps or forms, reducing administrative overhead and errors. It also supports compliance and reporting by ensuring essential information is always captured.

Canvas app validation formulas only apply within a specific app. Users accessing the same table through another app or portal could bypass these rules.

Model-driven form rules enforce validation in specific forms but do not apply database-wide. They cannot prevent incomplete records from being saved if accessed through other interfaces.

Business process flow stages guide users through a workflow and can prompt for field completion, but cannot enforce mandatory values at the database level.

Required field properties at the Dataverse table level are the correct solution for consistent, application-wide enforcement of critical data entry.

Question 173:

A company wants to automatically send an alert to a manager when a high-priority case is created in Dataverse. The alert should include all relevant details and happen without manual intervention. Which tool should they use?

A) Power Automate cloud flow

B) Canvas app button

C) Desktop flow

D) Model-driven form rule

Answer: A) Power Automate cloud flow

Explanation:

Power Automate cloud flows allow automated triggering based on Dataverse record events. By configuring the flow to trigger when a high-priority case is created, the flow can collect necessary details such as the case owner, description, and priority level, and send an automated alert via email or Microsoft Teams. This ensures real-time notifications without user intervention. Flows operate at the database level, applying to all applications and forms accessing Dataverse, ensuring consistent delivery. Conditional logic can route notifications differently based on business rules, ensuring that escalations are handled appropriately.

Canvas app buttons require manual user interaction to trigger actions and cannot provide automated notifications based on record creation.

Desktop flows automate tasks on a local computer and cannot respond to database events or send automated alerts.

Model-driven form rules enforce validation or field behavior within specific forms but cannot trigger automated notifications or communicate with external systems.

Power Automate cloud flows are the correct solution because they provide automated, real-time alerts integrated with Dataverse.

Question 174:

A company wants to centralize a list of standard categories used across multiple Dataverse tables. Updating the list in one place should automatically update it in all tables. What should they configure?

A) Global choice column

B) Local choice column

C) Canvas app dropdown

D) Business process flow

Answer: A) Global choice column

Explanation:

Global choice columns in Dataverse allow the creation of a single reusable list of values that can be applied across multiple tables. When updates are made to the global choice, all tables using it automatically reflect the changes, ensuring data consistency and reducing maintenance effort. This is ideal for standardized fields such as categories, priorities, or statuses used in multiple tables. Global choices maintain consistency across apps, flows, and portals connected to Dataverse, reducing errors and ensuring uniform reporting.

Local choice columns are confined to a single table. Changes in one table do not propagate to others, leading to potential inconsistencies.

Canvas app dropdowns can provide lists within the app, but are not centrally managed. Updates must be made individually in each app, creating duplication and possible errors.

Business process flows guide workflow stages, but do not provide reusable centralized lists for multiple tables. They cannot enforce consistent data entry across the system.

Global choice columns are the correct solution because they provide centralized management and automatic propagation across multiple tables.

Question 175:

A company wants to create a secure portal for customers to submit requests, with authentication and role-based access, storing the data directly in Dataverse. External users should not require Power Apps licenses. Which platform should they implement?

A) Power Pages

B) Canvas apps

C) Desktop flows

D) Model-driven form rules

Answer: A) Power Pages

Explanation:

Power Pages provides a low-code platform for building external-facing web portals that connect directly to Dataverse. Customers can submit requests through secure forms, with authentication and role-based access ensuring data is only accessible by authorized users. The submitted information is stored in Dataverse, allowing integration with workflows, approvals, and reporting. Power Pages eliminates the need for external users to have Power Apps licenses, making it cost-effective and user-friendly for external submissions. It supports responsive design, customization, and security features required for enterprise portals.

Canvas apps cannot be shared with external users without licenses, making them unsuitable for public-facing submission portals.

Desktop flows automate local tasks and cannot provide secure web forms or external user access.

Model-driven form rules manage field behavior in specific internal forms but do not provide external-facing portals or authentication mechanisms.

Power Pages is the correct solution because it provides secure, authenticated, and external-facing submissions integrated with Dataverse.

Question 176:

A company wants to track how long a support ticket remains in each stage automatically without requiring users to enter any timestamps. Which feature should they configure?

A) Dataverse calculated columns

B) Canvas app timers

C) Desktop flows

D) Power BI measures

Answer: A) Dataverse calculated columns

Explanation:

Dataverse calculated columns enable automatic computation of values based on other fields in the table. For tracking the duration a support ticket remains in each stage, a calculated column can subtract the timestamp of entering one stage from the timestamp of moving to the next stage to determine the elapsed time. These calculations occur at the database level, which ensures that results are consistent across all apps and interfaces accessing Dataverse, such as model-driven apps, canvas apps, and Power Pages. Since users do not need to manually input timestamps, data integrity is maintained, reducing errors and administrative workload. Calculated columns also update dynamically as underlying data changes, allowing for accurate real-time metrics. The results can be leveraged in dashboards, workflows, or reports, providing actionable insights without user intervention.

Canvas app timers operate only when an app is running and cannot track all records automatically. They depend on user interaction and cannot perform database-level calculations for multiple records efficiently.

Desktop flows automate tasks on a local machine but are unsuitable for real-time monitoring of Dataverse records or calculating stage durations. They cannot reliably track timestamps or integrate results across all users and applications.

Power BI measures can calculate stage durations for reporting purposes, but do not store computed results in Dataverse. They are designed for visualization and analytics, not operational automation or automatic field calculations.

Dataverse calculated columns are the correct solution because they provide automatic, accurate, and centralized tracking of stage durations without requiring manual input.

Question 177:

A company wants to automatically assign new service requests to a team based on the request type. The assignment should happen without user intervention. What solution should they implement?

A) Power Automate cloud flow

B) Canvas app button

C) Model-driven form rule

D) Scheduled cloud flow

Answer: A) Power Automate cloud flow

Explanation:

Power Automate cloud flows can be triggered automatically when a Dataverse record is created. By evaluating the request type, the flow can assign the new service request to the appropriate team or user automatically. This automation ensures that requests are routed efficiently, consistently, and according to business rules without manual intervention. The flow can incorporate conditional logic, escalate requests when necessary, and send notifications to assigned users. Operating at the database level ensures that the assignment process is applied consistently across all apps and interfaces that access Dataverse. Automated flows improve operational efficiency and reduce errors in manual assignments.

Canvas app buttons require a user to manually trigger an action within an app, making them unsuitable for automated assignment processes.

Model-driven form rules enforce field behavior and validation within a form, but cannot perform automatic assignment across multiple records without user interaction.

Scheduled cloud flows run at predetermined intervals, which may delay assignments, making them unsuitable for real-time request routing.

Power Automate cloud flows are the correct solution because they provide automated, real-time, and conditional record assignments.

Question 178:

A company wants to allow external partners to submit incident reports securely online without requiring Power Apps licenses. The submitted data must be stored in Dataverse and trigger automated workflows. Which platform should they use?

A) Power Pages

B) Canvas apps

C) Desktop flows

D) Model-driven form rules

Answer: A) Power Pages

Explanation:

Power Pages allows the creation of secure, external-facing web portals that connect directly to Dataverse. External partners can submit incident reports through authenticated forms, and data is stored in Dataverse for subsequent processing. Role-based access ensures that only authorized users can submit or view records. The portal can trigger automated workflows via Power Automate, such as notifications, approvals, or task assignments. Power Pages eliminates the need for external users to have Power Apps licenses while maintaining secure data entry and integration with internal systems. Low-code customization allows rapid deployment and responsive design, ensuring usability across devices.

Canvas apps are designed for internal users and require licensing for external sharing. They are not suitable for secure, public-facing portals.

Desktop flows automate tasks on local computers and cannot provide web interfaces for external submissions or secure authentication.

Model-driven form rules enforce behavior within specific internal forms but do not create external portals or support secure submissions for partners.

Power Pages is the correct solution because it enables secure, authenticated, and integrated external submissions directly into Dataverse.

Question 179:

A company wants to enforce that certain Dataverse fields cannot be edited after a record reaches the “Approved” stage. The restriction must apply across all apps. Which feature should they configure?

A) Field-level security

B) Canvas app visibility rules

C) Model-driven form rules

D) Business process flow stages

Answer: A) Field-level security

Explanation:

Field-level security in Dataverse allows administrators to define which users can read, update, or delete specific fields, applying the rules at the database level. Once configured, these restrictions are enforced across all apps, portals, and APIs. For records that have reached the “Approved” stage, the system can prevent unauthorized modifications to critical fields, maintaining data integrity and compliance. Security roles can be customized to grant exceptions for specific users, such as administrators, while standard users are restricted. This approach is consistent, centralized, and does not depend on the interface used to access Dataverse.

Canvas app visibility rules can hide fields or make them read-only in a specific app, but they do not enforce security across other apps, portals, or APIs. Users could still modify the fields through alternative access points.

Model-driven form rules only enforce behavior in specific forms and cannot prevent edits at the database level. They are limited to form-level validation and cannot provide organization-wide security.

Business process flow stages guide users through workflow steps, but cannot enforce field-level security or prevent updates from other apps or APIs.

Field-level security is the correct solution because it enforces consistent, database-level protection for sensitive fields across all interfaces.

Question 180:

A company wants to send real-time notifications to managers when high-priority cases are created in Dataverse, including details and the current owner. Which tool should they implement?

A) Power Automate cloud flow

B) Canvas app button

C) Desktop flow

D) Model-driven form rule

Answer: A) Power Automate cloud flow

Explanation:

Power Automate cloud flows can trigger automatically when specific conditions are met in Dataverse, such as the creation of a high-priority case. The flow can collect necessary details, including the current owner, case description, and priority level, and send notifications via email or Microsoft Teams in real-time. Cloud flows operate at the database level, ensuring that notifications are delivered consistently regardless of the app or interface used to create the record. Conditional logic can handle different scenarios, multiple recipients, or escalation paths. Automated flows reduce manual effort, improve response times, and ensure critical cases are promptly addressed.

Canvas app buttons require user interaction and cannot trigger notifications automatically based on database events.

Desktop flows automate tasks on a local machine but cannot monitor real-time record creation or deliver automated notifications.

Model-driven form rules enforce behavior or validation in specific forms but cannot trigger external notifications automatically.

Power Automate cloud flows are the correct solution because they provide automated, real-time, and condition-based notifications integrated with Dataverse.