Correct Answer: C

Reference: https://community.dynamics.com/365/b/dynamics365apps/posts/kb-understanding-dynamics-365-field-s-searchable-property

Correct Answer: B

Manage access to apps by using security roles.

You can choose what users see and access from the My Apps page or the Customer Engagement home page by giving app access to specific security roles. Users will have access to apps based on the security roles they're assigned to.

1.

Go to Settings > My Apps.

2.

In the lower-right corner of the app tile you want to manage access for, select More options (...), and then select Manage Roles.

3.

Enter the following in the Manage Roles dialog box: a) App URL Suffix b) Roles c) Select Save.

4.

Refresh the My Apps page.

5.

Go to the Apps Being Edited view, and publish the app again. https://docs.microsoft.com/en-us/dynamics365/customer-engagement/customize/manage-access-apps-security-roles

Correct Answer: A

Correct Answer: A

The personal app can be shared in the team!

Correct Answer: C

Column-level security is available for the default columns on most out-of-box tables, custom columns, and custom columns on custom tables. Column-level security is managed by the security profiles. To implement column-level security, a

system administrator performs the following tasks.

Enable column security on one or more columns for a given table.

Associate one more existing security profiles, or create one or more new security profiles to grant the appropriate access to specific users or teams.

A security profile determines the following:

Permissions to the secure columns

Users and teams assigned access

A security profile can be configured to grant user or team members the following permissions at the column level:

Read. Read-only access to the column's data.

Create. Users or teams in this profile can add data to this column when creating a row.

Update. Users or teams in this profile can update the column's data after it has been created.

A combination of these three permissions can be configured to determine the user privileges for a specific data column.

Reference: https://learn.microsoft.com/en-us/power-platform/admin/field-level-security

Correct Answer: B

Correct Solution: Create a flow that has an Update a row action.

Note: Actions that real-time workflow processes can perform

Real-time workflow processes can perform the actions listed in the following table.

*

Update Row. You can update the row that the real-time workflow is running on, any of the rows linked to that row in an N:1 relationship, or any rows created by earlier steps.

*

Etc.

Reference: https://learn.microsoft.com/en-us/power-apps/maker/data-platform/configure-workflow-steps

Correct Answer:

Correct Answer:

Box 1: Assign users to a security role.

Users in the accounting department must be able to create a bot for frequently asked questions.

Create a bot in an existing environment where you don't have access

To create a bot in an environment where you don't have access, you'll need to be a system administrator or contact the system administrator. You then need to complete the following:

Create a bot in the environment (this step will install the necessary Power Virtual Agents solutions).

Assign the security role of "bot author" to you in the environment.

You can then return to the Power Virtual Agents portal and create a bot in the environment.

Incorrect:

*

System Administrator role Too powerful.

The users must not be able to change environment parameters in the Microsoft Power Platform environment.

*

Share the bot with a security group. So that users can use the bot.

Box 2: Share the bot with a security group.

The support desk users must be able to use the bot.

Share your bot with other users

You can share your bots with others to grant them special permissions. There are two different sharing methods:

Grant security groups, or your whole organization, permission to chat with the bot.

Invite users to collaborate on your bot project. Collaborators always have permission to chat with the bot.

Reference: https://learn.microsoft.com/en-us/power-virtual-agents/environments-first-run-experience https://learn.microsoft.com/en-us/power-virtual-agents/admin-share-bots

Correct Answer:

Correct Answer:

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.