Microsoft PL-600 Practice Test - Questions Answers, Page 2

Box 1: Contact

With Contact scope, a signed-in user in the role for which the permission record is defined will have the rights granted by that permission only for records that are related to that user's contact record via a defined relationship.

Box 2: Account

With Account Scope, a signed-in user in the role for which the permission record is defined will have the rights granted by that permission only for records that are related to that user's parent account record via a defined relationship.

This scope means that the entity list will only show the records of the selected entity that are associated to the user's parent account. For example, if an entity permission allows Read access to Lead entity with the Account scope, the user having this permission can view all the leads of only the parent account of the user.

Incorrect Answers:

Self Scope allows you to define the rights a user has to their own Contact (Identity) record. Users can use entity forms or web forms to make changes to their own Contact record linked with their profile.

Parental scope: In this most complex case, permissions are granted for an entity that is a relationship away from an entity for which an Entity Permission record has already been defined. This permission is actually a child record of the parent entity permission.

Reference:

https://docs.microsoft.com/en-us/powerapps/maker/portals/configure/assign-entity-permissions

Reference:

Box 1: One-to-many relationship

Each educator can have 0, 1, or many qualifications

Box 2: One-to-many relationship

Each educator can be the primary educator for 0, 1 or many cources.

Box 3: Many-to-many relationship that uses a custom table.

Note: N:N (Many-to-Many): A table relationship that depends on a special Relationship table, sometimes called an Intersect table, so that many rows of one table can be related to many rows of another table.

Reference:

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

Box 1: Data loss prevention policy

Data loss prevention (DLP) policies enforce rules for which connectors can be used together by classifying connectors as either Business or Non-Business. If you put a connector in the Business group, it can only be used with other connectors from that group in any given app or flow. Sometimes you might want to block the usage of certain connectors altogether by classifying them as Blocked. Box 2: Security group

If your company has multiple Microsoft Dataverse environments, you can use security groups to control which licensed users can be a member of a particular environment.

Reference:

https://docs.microsoft.com/en-us/power-platform/admin/wp-data-loss-prevention

https://docs.microsoft.com/en-us/power-platform/admin/control-user-access

Box 1: Microsoft Power Automate, Microsoft Dataverse connector, and Microsoft 365 Outlook connector Use Microsoft Dataverse as the data source.

While Power Automate is a robust tool with ever-expanding capabilities, it also handles simple tasks with grace. A universal business need for many organizations is the ability to automate email notifications based on certain criteria: an opportunity is won, send an email to the sales manager; a case is closed, send an email to the customer; a work order is completed, send an email to the customer. Power Automate can easily accommodate this using the Microsoft 365 Outlook connector.

Box 2: Microsoft Power Automate, Power Bi data alerts, and Microsoft 365 connector

Data alerts in the Power BI service: Set alerts to notify you when data in your dashboards changes beyond limits you set.

Box 3: Microsoft Power Automate, Power BI, Power Apps, and Microsoft Dataverse connector

Reference:

https://www.velosio.com/blog/2021/01/27/tracking-emails-the-right-way-with-power-automate/

https://docs.microsoft.com/en-us/power-bi/create-reports/service-set-data-alerts

Box 1: Increase multithreading and/or batch size settings

Box 2: Ensure you are loading data in a specific order.

Load the base tables in the hierarchies first.

Box 1: Use Virtual tables

A virtual entity is a custom entity in Dynamics 365 Customer Engagement (on-premises) that has fields containing data from an external data source. Virtual entities appear in your app to users as regular entity records, but contain data that is sourced from an external database, such as an Azure SQL Database. Records based on virtual entities are available in all clients including custom clients developed using the Dynamics 365 Customer Engagement Web Services.

Box 2: Use Dynamics 365 Web API.

Dynamics 365 Web Services API: Many times, straight database-to-database integrations aren’t a possibility. In these cases, the development of a solution may depend on utilization of the Dynamics 365 Customer Engagement web services API (Application Programming Interface).

Reference:

https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/customize/create-edit-virtual-entities

Box 1: Define the data type and format for each column

Increase the data type size of the column.

Box 2: Define and implement duplicate detection rules

Reference:

https://docs.microsoft.com/en-us/power-platform/admin/set-up-duplicate-detection-rules-keep-data-clean

Box 1: Field security profile

Record-level permissions are granted at the entity level, but you may have certain fields associated with an entity that contain data that is more sensitive than the other fields. For these situations, you use field-level security to control access to specific fields.

Field-level security is available for the default fields on most out-of-box entities, custom fields, and custom fields on custom entities. Field-level security is managed by the security profiles.

Box 2: Compliancy policy

Compliance policy settings – Tenant-wide settings that are like a built-in compliance policy that every device receives. Compliance policy settings set a baseline for how compliance policy works in your Intune environment, including whether devices that haven’t received any device compliance policies are compliant or noncompliant.

Note: Mobile device management (MDM) solutions like Intune can help protect organizational data by requiring users and devices to meet some requirements. In Intune, this feature is called compliance policies.

Compliance policies in Intune:

Define the rules and settings that users and devices must meet to be compliant.

Include actions that apply to devices that are noncompliant. Actions for noncompliance can alert users to the conditions of noncompliance and safeguard data on noncompliant devices. Can be combined with Conditional Access, which can then block users and devices that don't meet the rules.

Reference:

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

https://docs.microsoft.com/en-us/mem/intune/protect/device-compliance-get-started

A: How to View Auditing Log Details?

System administrators can see activities for the entities that are enabled for audit logging. To view the audit logs:

Go to Settings > System >Auditing.

Choose Audit Summary View.

Under Audit Summary View, you will see the list of audit entries

B: You can view details about solution operations from the Solutions area of Power Apps. An operation can be a solution import, export, or uninstall. The solution history displays information such as solution version, solution publisher, type of operation, operation start and end time, and operation status.

D: Trace log records are written to the PluginTraceLog Table. Writing of these records is controlled by the trace settings mentioned in Enable trace logging.

This data can be found in model-driven applications by navigating to Settings and choosing the Plug-in Trace Log tile.

Reference:

https://www.sherweb.com/blog/dynamics-365/audits-dynamics-365/

https://docs.microsoft.com/en-us/powerapps/developer/data-platform/logging-tracing