Reference:
https://docs.microsoft.com/en-us/microsoft-365/community/power-automate-vs-logic-apps
https://docs.microsoft.com/en-us/power-automate/replace-workflows-with-flows

Explanation

Box 1: Set the test environment security group to TestSG and assign test users the app security role.
PowerApps apps use role-based security for sharing. The fundamental concept in role-based security is that a security role contains privileges that define a set of actions that can be performed within the app. All app users must be assigned to one or more predefined or custom roles.
Box 2: Assign the manager the app security role.
Box 3: Set the production environment security group to TestSG
Box 4: Add all users in the department to the TestSG security group.
Reference:
https://docs.microsoft.com/en-us/powerapps/maker/model-driven-apps/share-model-driven-app

Explanation


Box 1: Custom self-service portal for both employers and job candidates If you select an environment that contains customer engagement, you can create the following portals:
* Customer self-service portal: A customer self-service portal enables customers to access self-service
* knowledge, support resources, view the progress of their cases, and provide feedback.
* Partner portal: A partner portal allows every organization with resellers, distributors, suppliers, or partners to have real-time access to every stage of shared activities.
* Employee self-service portal: An employee self-service portal creates an efficient and well-informed workforce by streamlining common tasks and empowering every employee with a definitive source of knowledge.
Box 2: Model-driven app with push notifications
Compared to canvas apps, model-driven apps in PowerApps are based on underlying data - specifically, the data stored in Common Data Service (CDS).
Box 3: Webform with target set to the job custom entity
Box 4: Configure a value for the Execute Workflow on Redeeming Contact option only.
Execute Workflow on Redeeming Contact: A workflow process to be executed when the invite is redeemed.
The workflow will be passed the redeeming contact as the primary entity.
Box 5: Configure the value for the Assigned to Account option only.
Assign to Account: An account record to be associated as the redeeming contact's parent customer when the invite is redeemed.
Reference:
https://docs.microsoft.com/en-us/powerapps/maker/portals/portal-templates
https://global.hitachi-solutions.com/blog/canvas-vs-model-driven-apps
https://docs.microsoft.com/en-us/powerapps/maker/portals/configure/invite-contacts#invitation-attributes

A: When you import a managed solution, all component changes will be brought into the environment in a published state.
B: You can apply patches to either managed or unmanaged solutions and include only changes to entities and related entity assets. Patches do not contain any non-customized system components or relationships that it dependents upon because these components already exist in the deployed-to organization. At some point in your development cycle, you can roll up all the patches into a new solution version to replace the original solution that the patches were created from.
Reference:
https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/import-update-export-solutions
https://docs.microsoft.com/en-us/power-platform/alm/create-patches-simplify-solution-updates Create and configure Power Apps Testlet 1 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 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
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.

Reference:
https://docs.microsoft.com/en-us/power-platform/admin/environments-overview
https://crmbook.powerobjects.com/system-administration/business-administration/security-roles/