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

Box 1: Custom connector

While Azure Logic Apps, Microsoft Power Automate, and Microsoft Power Apps offer over 325+ connectors to connect to Microsoft and non-Microsoft services, you may want to communicate with services that aren't available as prebuilt connectors.

Box 2: Microsoft Dataverse

The Microsoft Dataverse connector provides several triggers to start your flows and many actions that you can use to create or update data in Dataverse while your flows run. You can use Dataverse actions even if your flows don't use a trigger from the Dataverse connector.

Use the Microsoft Dataverse connector to create cloud flows that start when data changes in Dataverse tables and custom messages.

Reference: https://docs.microsoft.com/en-us/connectors/custom-connectors/ https://docs.microsoft.com/en-us/powerautomate/dataverse/overview

Box 1: Azure Data Lake

A data warehouse is a centralized repository of integrated data from one or more disparate sources. Data warehouses store current and historical data and are used for reporting and analysis of the data.

Incorrect Answers:

Dataverse is not a database.

Box 2: Microsoft Teams integration object

You can use the Teams integration object to easily find and access the Teams integration features and use the improved usability of expressions while integrating your canvas app with Teams. You can get a Teams theme inside a canvas app, and you can filter data depending on the team or channel context.

Reference:

https://docs.microsoft.com/en-us/azure/architecture/data-guide/relational-data/data-warehousing

https://docs.microsoft.com/en-us/powerapps/teams/use-teams-integration-object

Box 1: For each activity.. Cascade None: Do nothing

Note:

Cascade All: Perform the action on all referencing table records associated with the referenced table record. Cascade Active: Perform the action on all active referencing table records associated with the referenced table record. Box 2: Create Power BI reports using the Microsoft Dataverse connector

Use the Dataverse connector in DirectQuery mode: Connects directly to the data in Dataverse. Use this mode for real-time data retrieval.

Reference:

https://docs.microsoft.com/en-us/powerapps/developer/data-platform/configure-entity-relationship-cascading-behavior https://docs.microsoft.com/en-us/powerapps/maker/data-platform/data-platform-powerbi-connector

Box 1: Owner team

Owner team: An owner team owns records and has security roles assigned to the team. A user's privileges can come from their individual security roles, those of the teams that they're part of or the ones they inherit. A team has full access rights on the records that the team owns. Team members are added manually to the owner team.

Box 2: Access team

Access team: An access team doesn't own records and doesn't have security roles assigned to the team. The team members have privileges defined by their individual security roles and by roles from the teams they're members of. These members share records with an access team, and the team is granted access rights to the records. Access rights include Read, Write, and Append. Box 3: Owner team

Reference: https://docs.microsoft.com/en-us/power-platform/admin/manage-teams

References: https://docs.microsoft.com/en-us/powerapps/developer/data-platform/field-security-entities

Box 1: 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.

Box 2: Non-business

DLP policies enforce rules for which connectors can be used together by classifying connectors as either Business or Non- Business.

Box 3: Blocked

Sometimes you might want to block the usage of certain connectors altogether by classifying them as Blocked. Data policy group Business blocked

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

Box 1: Reduce usage of near real-time workflows

A real-time workflow can be converted to asynchronous workflow and back to real-time.

Box 2: Convert all Dynamics 365 workflows to Power Automate cloud flows.

Workflows are limited to Microsoft Dynamics 365/CRM application only.

Power Automate can span across multiple web-based services or applications at the same time. Dynamics 365 CRM Workflows can be converted to Power Automate flows.

Reference: https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/developer/create-real-time- workflows https://rajeevpentyala.com/2019/12/11/d365-switching-from-workflow-to-microsoft-power-automate-flow/

Box 1: Disable duplicate detection

Duplicate detection has rules for sending emails.

Box 2: Disable all workflows, plug-ins, and Power Platform admin center

Box 3: Disable auditing

Auditing affects the size of the log file.

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

B: We need is a source for exchange rates. There are some published connectors, but you also use a free service called Exchange Rates API, which are based on the European Central Bank, and create a custom connection. Now that we have our custom connector defined and have a way to request the latest exchange rates, the next step is to create a Power Automate flow that will update all of currencies setup in our Dataverse environment. Dataverse is a multicurrency system, in which each record can be associated with its own currency. This currency is called the transaction currency. The multicurrency features enable users to perform financial transactions like opportunities, quotes, orders, and invoices in multiple currencies. This feature also provides a currency choice to the end user when a financial transaction occurs.

Reference:

https://readyxrm.blog/2021/03/10/updating-currency-exchange-rates-in-dataverse/