Free Practice Questions for Microsoft PL-200 Exam

Record the name of the QV team member who performed the work and the date completed.

Box 1: Connect by using the Dataverse connector from the desktop flow and retrieve the qualification data.

All information sent by clients for services is stored in Microsoft Dataverse with a model-driven app as the interface.

Qualification verification

The qualification table contains details about an individual school degree, professional qualifications, and other qualifications that must be verified.

A service request can have one or more Qualification records associated with it.

Record status is pending verification until the initial team member finishes, at which point the member changes the status to Complete.

When all qualification records related to a service request are verified either by manual or automated processes, the results are made available to ADatum Corporation’s client.

In the rare event that results are questioned, a new service request is created and verified independently of the previous work that took place.

Box 2: Send data from the desktop flow to a cloud flow to update the qualification record.

To complete a service request, users perform the following actions:

Send a templated email by using Microsoft Outlook to the client after all qualifications for a service request are checked.

Change the service request status to Completed. Currently, service requests do not indicate when all Qualification records are addressed.

A VP of sales requires a test environment to demonstrate to potential clients the security policies that are included in their initial offering.

Currently, testing the new QV functionality outside the development environment is not possible due to corporate security policies requiring the same security role across all environments.

Note: One of the security best practices in Dynamics 365 is to use the base security role as a baseline and apply that role to all Users. The base security role will include all the common/basic permissions that are required to have access to the system.

To set up the base security role for the first time

create a new empty security role.

add the minimum privileges required to access the system.

add the privileges required for the basic functionalities.

test the role with the test user account.

add the permissions to the entities that all users can access (e.g. reference data).

Internal IT reports that the solution import to the test environment failed because of missing dependencies related to the flow for completing service requests.

Flows with PowerApps steps

Flows that were created via Power Automate in the PowerApps menu or flows that have PowerApps steps added have a different issue then other Power Automate flows. As of the writing of this blog these flows are not able to be imported into another environment. This means that if you create flows with Power Apps steps within them you will need to recreate them in your destination environment.

Box 1: Set Table table to Qualification and Column filter to statuscode.

Box 2: Loop through related qualification records and complete if all are in Complete status.

The new process for completing a service request must automate the following:

Set the Service Request record status to Complete when work on all Qualification records is finished.

Send an email to the client with the results when the service request is completed. The email must list each qualification as either Valid or Not Valid, depending on the verification.

Box 1: Apply to each

You can use the Apply to each action to process a list of items periodically.

Box 2: Do until

The Do Until control in Power Automate is a loop that repeatedly forces an action until a certain condition becomes true.

Box 1: Assign records to a service account and add the team member doing the verification by using an access team.

When to use access teams

* The teams are dynamically formed and dissolved. This typically happens if the clear criteria for defining the teams, such as established territory, product, or volume aren’t provided.

* The team members require different access rights on the records. You can share a record with several access teams, each team providing different access rights on the record. For example, one team is granted the Read access right on the account and another team, the Read, Write and Share access rights on the same account.

* A unique set of users requires access to a single record without having an ownership of the record.

Box 2: Assign records to the QV team when the service request is completed.

Issues: More employees than are required can access individual client information and continue to have access after a service request is completed.

Management has decided to create a new qualification verification (QV) role to help ensure that clients get the most accurate results. This role examines completed work to ensure that nothing is missed.

• When users go on vacation, all their outstanding Service Request records are assigned to a substitute employee. The substitute employees are unable to see all the qualifications related to their service requests.

Box 1: Deploy a patch with the changes made from the current solution.

Scenario:

The Onsite Visit managed solution has a table that is not in the Verification Process Automation managed solution. This table must be upgraded prior to the go-live date without the other shared components.

Box 2: Deploy a full copy of the original solution using the upgrade option. Then, deploy the new solution by using the update option.

Scenario: All components required for the verification process must be included in a new solution.

Corporate security requires that deployments to non-development environments must be automated using service accounts.

Managed solutions are used to move customizations from the development environment to other higher-level environments. These solutions are created and maintained by the power users and provided to internal IT for deployment when they are ready.

Note:

Upgrade This is the default option and upgrades your solution to the latest version and rolls up all previous patches in one step. Any components associated to the previous solution version that are not in the newer solution version will be deleted. This is the recommended option as it will ensure that your resulting configuration state is consistent with the importing solution including removal of components that are no longer part of the solution.

Update This option replaces your solution with this version. Components that are not in the newer solution won't be deleted and will remain in the system. This option is not recommended as your destination environment will differ in configuration from your source environment and could cause issues that are difficult to reproduce and diagnose.