What is the root cause?

The AP team monitors the shared mailbox to confirm that the customer has paid the invoice.

Requirements

Functional requirements

• Large volume orders must be processed before other orders.

• Invoices must be cross-checked with received items against packing slip for shipments.

• The finance team must be able to analyze patterns in transactional data to conduct fraud prevention activities.

• You must automate the process of entering data about incoming orders into SMSApp.

• The solution must follow the principle of least privilege.

Purchase Order Quantity flow

• You must create an unmanaged solution to update purchase order details in SMSApp. The flow must use a manual trigger.

• Members of Accounts Payable team will be testers for the solution. They must be able to access

the Purchase Order Quantity flow.

Flow for processing invoice data

• You must create a flow to monitor the AP mailbox. When an invoice arrives as an attachment in the inbox, the flow must automatically process the invoice data by using a form processing model. The flow must cross-check the received items against the packing slip.

• You must use different Accounts Payable email addresses for development user acceptance testing (UAT), and production environments.

• You must use an environment variable to represent the Accounts Payable mailbox for the environment in use.

• You must be able to use the environment variable across multiple cloud flows, a custom connector, and a canvas app.

Technical requirements

• Users must only be allowed to connect to and access systems that are required for the employee to perform required job tasks.

• All automation flows must be either co-owned or shared between staff.

• All employees must be able to access the new environment to build personal productivity automations.

• You must distribute the workload for desktop flows to optimize productivity.

Monitor flows

• All data extracted from Invoices should be stored in a custom Dataverse entity. Only employees who are part of Finance role should be able to edit all Invoice data but must be prevented from creating or deleting one.

Issues

Invoice data

All users report that they can see and modify invoice data.

New environment

•The IT department creates a new environment. A user creates a cloud flow named FlowA in the environment that triggers a desktop flow. A user reports that the cloud flow does not trigger the desktop flow to run.

• Microsoft Dataverse is not provisioned in the new environment. You attempt to create a Desktop flow in the default environment but receive a Dataverse error message and cannot proceed.

Data entry automation flow

An administrator runs a new desktop flow in the development environment to automate data entry into SMSApp. The flow automatically reverts to a suspended state.

Order fulfillment flow

You must automate the customer communication process by using an unattended desktop flow. The flow must check the fulfillment status of each active order in SMSApp. If an order is fulfilled, the flow must send the customer an email that includes tracking information for their order.

You need to identify the cause for the SMSApp data entry issue.

What is the root cause?
A . The DLP policy that contains the desktop flow connector was deleted.
B . The default policy group is set to Blocked.
C . The desktop flow was not shared with the finance clerk.
D . The Power Automate Management connector is assigned to the Business category.

View Answer

Answer: B

Explanation:

According to the scenario, the SMSApp data entry issue occurred after a DLP policy change that excluded the development environment from its scope. This means that any desktop flow that uses connectors in the development environment will be blocked by the DLP policy1. Therefore, the root cause of the issue is option D.