[Q35-Q50] Full PL-400 Practice Test and 317 unique questions with explanations waiting just for you!

Scenario: CustomerC requested additional information from the parts department through the customer survey and has not received a response one week later.
Imagine having a process where you want to give someone a couple of days to reply to an approval. If that someone doesn’t respond in time, you want to assign a new approval to another person or group of people. To achieve this you can set the timeout in the action settings.
Reference:
https://www.o365dude.com/2018/06/02/timeout-flow-approvals/
Topic 1, Adventure Works
Overview
This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section.
To start the case study
To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question.
Background
Current environment
Adventure Works Cycles wants to replace their paper-based bicycle manufacturing business with an efficient paperless solution. The company has one manufacturing plant in Seattle that produces bicycle parts, assembles bicycles, and distributes finished bicycles to the Pacific Northwest.
Adventure Works Cycles has a retail location that performs bicycle repair and warranty repair work. The company has six maintenance vans that repair bicycles at various events and residences.
Adventure Works Cycles recently deployed Dynamics 365 Finance and Dynamics 365 Manufacturing in a Microsoft-hosted environment for financials and manufacturing. The company plans to leverage the Microsoft Power Platform to migrate all of their distribution and retail workloads to Dynamics 365 Unified Operations.
The customer uses Dynamics 365 Sales. Dynamics 365 Customer Service and Dynamics 365 Field Service.
Retail store information
Adventure Works Cycle has one legal entity, four warehouses, and six field service technicians.
Warehouse counting is performed manually by using a counting journal. All warehouse boxes and items are barcoded.
The Adventure Works Cycles retail location performs bicycle inspections and performance tune-ups.
Technicians use paper forms to document the bicycle inspection performed before a tune-up and any additional work performed on the bicycle.
Adventure Works Cycles uses a Power Apps app for local bike fairs to attract new customers.
A canvas app is being developed to capture customer information when customers check in at the retail location. The app has the following features:
Customer selects yes or no if they are on the mailing list.
Customer selects the amount of times they have visited the store.
Customer selects the type of service needed.
The search result returns all last name records that match the search term.
Technology
Requirements
A plug-in for Dynamics 365 Sales automatically calculated the total billed time from all activities on a particular customer account, including sales representative visits, phone calls, email correspondence, and repair time compared with hours spent.
A shipping API displays shipping rates and tracking information on sales orders. The contract allows for 3,000 calls per month.
Ecommerce orders are processed in batch daily by using a manual import of sales orders in Dynamics 365 Finance.
Microsoft Teams is used for all collaboration.
All testing and problem diagnostics are performed in a copy of the production environment.
Customer satisfaction surveys are recorded with Microsoft Forms Pro. Survey replies from customers are sent to a generic mailbox.
Automation
A text message must be automatically sent to a customer to confirm an appointment and to notify when a technician is on route that includes their location.
Ecommerce sales orders must be integrated into Dynamics 365 Finance and then exported to Azure every night.
A text alert must be sent to employees scheduled to assist in the repair area of the retail store if the number of repair check-ins exceeds eight.
Submitted customer surveys must generate an email to the correct department. Approval and follow-up must occur within a week.
Reporting
The warehouse manager’s dashboard must contain warehouse counting variance information.
A warehouse manager needs to quickly view warehouse KPIs by using a mobile device.
Power BI must be used for reporting across the organization.
User experience
Warehouse counting must be performed by using a mobile app that scans barcodes on boxes.
All customer repairs must be tracked in the system no matter where they occur.
Qualified leads must be collected from local bike fairs.
Issues
Warehouse counting must be performed by using a mobile app that scans barcodes on boxes.
All customer repairs must be tracked in the system no matter where they occur.
Qualified leads must be collected from local bike fairs.
Internal
User1 reports receives an intermittent plug-in error when viewing the total bill customer time.
User2 reports that Azure consumption for API calls has increased significantly to 100 calls per minute in the last month.
User2 reports that sales orders have increased.
User5 receives the error message: ‘Endpoint unavailable’ during a test of the technician dispatch ISV solution.
The parts department manager who is the approver for the department is currently on sabbatical.
External
CustomerB reports that the check-in app returned only one search result for their last name, which is not the correct name.
Nine customers arrive in the repair area of the retail store, but no texts were sent to scheduled employees.
Customers report that the response time from the information email listed on the Adventure Works Cycles website is greater than five days.
CustomerC requested additional information from the parts department through the customer survey and has not received a response one week later.

Reference:
https://docs.microsoft.com/en-us/powerapps/developer/data-platform/user-team-entities
https://docs.microsoft.com/en-us/powerapps/maker/data-platform/create-edit-entity-relationships#types-of-table-relationships

Explanation

Box 1: Webhook
With Dataverse, you can send data about events that occur on the service to a web app by using webhooks. A webhook is a lightweight HTTP pattern for connecting web APIs and services with a publish-and-subscribe model. Webhook senders notify receivers about events by making requests to receiver endpoints with some information about the events.
Webhooks enable developers and ISVs to integrate Dataverse data with their own custom code hosted on external services.
Box 2: Azure Service Bus
Service Bus provides a secure and reliable communication channel between Dataverse runtime data and external, cloud-based line-of-business apps. This capability is especially useful in keeping disparate Dataverse systems or other Dataverse servers synchronized with business data changes.
Box 3: Azure Event hub
Azure Event Hubs is a big data streaming platform and event ingestion service. It can receive and process millions of events per second. Data sent to an event hub can be transformed and stored by using any real-time analytics provider or batching/storage adapters.
Note: The most popular approaches in Dataverse involve webhooks, Azure messaging (Service Bus, Event Hubs), Azure Logic Apps, or Power Automate.
Reference:
https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/why-cds-any-type-app

Reference:
https://docs.microsoft.com/en-us/powerapps/developer/common-data-service/webapi/use-web-api-actions

Reference:
https://docs.microsoft.com/en-us/powerapps/developer/data-platform/configure-entity-relationship-cascading-behavior

Explanation

Box 1: Power Automate
Ensure that notifications are sent to the sales team when a lead is added by using Slack Power Automate is a service that helps you create automated workflows between your favorite apps and services to synchronize files, get notifications, collect data, and more.
Box 2: Business rule
A trigger must be created that changes the Priority field to 1 in the Account record 10 days after an account record is created.
A field named Priority_Trigger must be created to trigger the Priority field.
Business rules provide a simple interface to implement and maintain fast-changing and commonly used rules.
Box 3: Business process flow
Ensure that leads have a review stage added to the sales process.
Use business process flows to define a set of steps for people to follow to take them to a desired outcome.
These steps provide a visual indicator that tells people where they are in the business process.
Reference:
https://docs.microsoft.com/en-us/power-automate/
https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/customize/create-business-rule
https://docs.microsoft.com/en-us/power-automate/business-process-flows-overview

Microsoft Dataverse supports integration with Azure.
For the Dataverse and Azure connection to work, there must be at least one solution in an Azure Service Bus solution account, where the solution contains one or more service endpoints.
For a queue endpoint contract, a listener doesn’t have to be actively listening.
Reference:
https://docs.microsoft.com/en-us/powerapps/developer/common-data-service/azure-integration

Two security models can be used for hierarchies, the Manager hierarchy and the Position hierarchy. The Position hierarchy allows data access across business units. If you are a financial organization, you may prefer the Manager hierarchy model, to prevent managers’ accessing data outside of their business units. However, if you are a part of a customer service organization and want the managers to access service cases handled in different business units, the Position hierarchy may work better for you.
Note: The hierarchy security model is an extension to the existing security models that use business units, security roles, sharing, and teams. It can be used in conjunction with all other existing security models. The hierarchy security offers a more granular access to records for an organization and helps to bring the maintenance costs down.
Reference:
https://docs.microsoft.com/en-us/power-platform/admin/hierarchy-security

Reference:
https://docs.microsoft.com/en-us/power-platform/admin/restrict-access-online-trusted-ip-rules
https://docs.microsoft.com/en-us/power-platform/admin/wp-data-loss-prevention
https://docs.microsoft.com/en-us/power-platform/admin/wp-data-loss-prevention
https://docs.microsoft.com/en-us/power-platform/admin/block-forwarded-email-from-power-automate
https://docs.microsoft.com/en-us/power-platform/admin/block-forwarded-email-from-power-automate

https://docs.microsoft.com/en-us/powerapps/developer/model-driven-apps/clientapi/reference/xrm-webapi/updaterecord

Reference:
https://us.hitachi-solutions.com/blog/dynamics-365-workflow-vs-microsoft-flow/

Reference:
https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/create-edit-entity-relationships

Reference:
https://docs.microsoft.com/en-us/powerapps/developer/common-data-service/tutorial-write-plug-in

If all the entities in external data source have an associated GUID primary key then we can implement the virtual entities for sure. For Reference: https://learn.microsoft.com/en-us/dynamics365/customerengagement/on-premises/developer/virtual-entities/get-started-ve?view=op-9-1

Configure OAuth2 provider settings for portals.
The OAuth 2.0 based external identity providers involve registering an “application” with a third-party service to obtain a “client ID” and “client secret” pair.
The supported providers are:
Microsoft Account
Twitter
Facebook
Google
LinkedIn
Yahoo
Reference:
https://docs.microsoft.com/en-us/powerapps/maker/portals/configure/configure-oauth2-settings

Reference:
https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/offline-apps