Explanation/Reference:
Explanation:
With the Common Data Service connector, you can create Power Automate flows that are initiated by create and update events within Dataverse. Additionally, you can perform create, update, retrieve, and delete actions on records within Dataverse.
You can use scopes to determine if your flow runs if you create a new record, if a new record is created by a user within your business unit, or if a new record is created by any user in your organization.
Reference:
https://docs.microsoft.com/en-us/power-automate/connection-cds

Explanation
User5 receives the error message: 'Endpoint unavailable' during a test of the technician dispatch ISV solution.
When you choose to use a synchronous execution mode any failure will be reported back to the user of the application with an Endpoint unavailable error dialog informing the user that the webhook service endpoint may be configured incorrectly or is not available.
Reference:
https://docs.microsoft.com/en-us/powerapps/developer/common-data-service/use-webhooks
Topic 3, Contoso Pharmaceuticals
Case study
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 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 button to return to the question.
Background
Contoso Pharmaceuticals manufactures and sells drugs to retail and wholesale pharmacies, hospitals, and research facilities.
The company plans to implement Dynamics 365 Sales and Dynamics 365 Finance.
Current environment
* Contoso maintains a Microsoft Excel workbook that lists all drugs they supply.
* Pharmacies submit order requests through email.
* All information at customer locations is handwritten by customer representatives.
* Contoso uses Cerner, which is a medical industry application that uses a proprietary database.
* Some accounts are referrals from other pharmacies.
* Every pharmacy has its own Dynamics 365 Sales instance.
Requirements
General
Contoso wants to ensure that there is minimal custom code and custom connectors in the system.
Accounts
* Ensure that the names of the pharmacies are synced between the accounting and the customer management systems.
* Account numbers should be entered automatically into the pharmaceutical system that is in a Cerner database and kept in sync.
* When the account is entered into the system, extra fields must appear if the referral customer box is selected. If the box is not selected, the extra fields must not appear.
* 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.
* A field named Facility type field must be added in order to select whether a customer is a retail pharmacy, wholesale pharmacy, research facility, or hospital.
Users
* UserA must be able to create and publish Power Apps apps.
* UserB must be the owner of all the systems and be able to provide permissions and create all new environments.
* UserC must be able to create apps connected to the systems and update the security roles and entities.
* Pharmacy representatives must only be able to run the apps and access their own records.
* Access to the accounting Power Apps app must be restricted to accounting team members.
* End users must have minimum access to the required systems.
* Only supervisors must be able to view phone numbers in the Accounts form.
* Developers must be able to create new apps for all users.
* Sales users must only have access to their own records.
Reporting
Pharmacy orders must be displayed in four graphs as follows:
* Annual revenue over $100,000
* Annual revenues under $100,000
* Research facilities
* Hospitals
The graphs must be interactive, and users must be able to drill down on any dimension.
Customizations
* Ensure that notifications are sent to the sales team when a lead is added by using Slack.
* Ensure that leads have a review stage added to the sales process.
* Doctors must be manually added to a custom entity named Doctor if the doctor is not listed.
* Refill dates for customer prescriptions should be automatically determined and a notification should be sent to the customer.
* Fields for the doctor's name and phone number must be displayed in the customer record.
* The doctor entered on the customer's record must be validated against doctors that exist in the system.
* The new solution will be sold to other pharmacies for use. The application must not allow changes to be made.
* The solution must be error free so that when it is installed in other environments it does not cause issues.
* A custom mobile app must be created to allow salespeople to add or search by pharmacy name.
* Pharmacy records must be uniquely identified by pharmacy name, address, contact name, and phone number.
* When a pharmacy is added by using the mobile app, the phone number must be validated to be all digits.

By using a Dynamics 365 connector, you can create flows that initiate when an event occurs in Dynamics 365, or some other service, which then performs an action in Dynamics 365, or some other service.
Reference:
https://docs.microsoft.com/en-us/power-automate/connection-dynamics365
Topic 2, Bellows Sports
Current environment
Requirements
Bellow Sports tracks players and events in Microsoft Excel workbooks and uses email to communicate with players, partners, and prospective customers. The company uses a proprietary cloud-based accounting system.
The company relies on referrals from athletes for new business. Bellows uses a third-party marketing company to gather feedback and referrals from athletes. The third-party marketing company uploads a Microsoft Excel file containing lists of potential customers and players to the FTP site that Bellows Sports maintains.
Tournaments
Customer information is stored in the Accounts entity. Each tournament record must list the associated sales representative as the tournament owner. When team members create tournament records they must enter the start date for a tournament. The end date of the tournament must be automatically calculated.
Registration form
You must create a form to allow players to register for tournaments. The registration form must meet the following requirements:

Each division has tournaments that take place in specific locations. Users must be able to select the division for a tournament location.
Information about upcoming tournaments must be pre-located into the registration form when the registration form loads.
The form must include a custom button that sends an email confirmation to the player after the player registers.
The button must not be visible until after the form is saved.
Security
The company identifies the following job roles:

You must grant users the minimum permissions required to perform their job tasks.
Data automation
Customer name must be added to Dynamics 365 Finance automatically after it is entered.
You must produce a report that details the number of registrations for a day and send the report as a PDF to the management team.
You must implement mechanisms to handle all code-related errors.
When a customer record is updated, the system must look up the account number for the customer in the accounting system.
Referrals must be imported into the system as soon as they are available.
Issues
Apps
The captions for the New and Save buttons do not render properly on the form.
Interns can create apps but cannot interact with their own data.
Portal
The query for all registered users must return the data categorized by division. Queries must return only the Name and Sport fields. Queries return all fields. The query is as follows:

Solution checker issues
You run solution checker and observe Plug-in or workflow activity errors in the following code sets:

Code
The following code runs when the registration form loads. You must implement a mechanism to handle errors that occur in the code:

E: Before exporting an API, you must describe the API using an OpenAPI definition.
B: This OpenAPI definition contains information about what operations are available in an API and how the request and response data for the API should be structured. PowerApps and Microsoft Flow can create custom connectors for any OpenAPI 2.0 definition.
Reference:
https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/azure-functions/app-service-export-api-topowerapps-and-flow.md

Reference:
https://docs.microsoft.com/en-us/powerapps/developer/data-platform/use-change-tracking-synchronize-data-external-systems