Exam PL-600 topic 1 question 1 discussion

I would say BDE instead of ADE. In the documentation of Dual Write it says: business applications from Microsoft. Being the key word Microsoft, and here we have a third-party application, so we will need the appropiate connectors to its data (and if there aren't any in the market, then we have to build them via a Custom one)

BDE "Power Apps app and a third-party application" Steps that make sense 1) Custom connector to read/write to the 3rd party app Data 2) Power Automate cloud flow to execute the automation 3) CDS Connector to read/write to the Power App Data A) Does not contribute to the steps needed for this solution. Additionally - Dual-write is an out-of-box infrastructure that provides near-real-time interaction between customer engagement apps and Finance and Operations apps. (Not 3rd party apps) https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/dual-write/dual-write-overview

B. Custom connector A custom connector allows you to connect the Power Apps app to the third-party application's API and define the necessary operations (like creating and updating leads). D. Power Automate cloud flow Power Automate cloud flows can handle automated processes, such as creating or updating leads in the Power Apps app when changes occur in the third-party application. E. Dataverse connector If the Power Apps app uses Dataverse for storing leads, the Dataverse connector can facilitate interactions between the Power Apps app and other systems, including the third-party application.

Dual write is only for integration within D365 FO and dataflow can be used to copy data but Power Automate flow will be good option as it will be on demand not bulk copy

the right answer is BDE

for third party solutions we can use custom connector to integrate. Power Automate to do CRUD operations. Dataverse connector to update power apps data

To achieve the goal of integrating the Power Apps app and the third-party application, the following options can be used: A. Custom Connector: A custom connector in Power Apps can be used to connect to the third-party application's API and enable the integration between the two apps. D. Power Automate cloud flow: Power Automate cloud flow can be used to automate the process of creating a lead in the Power Apps app when a user creates a lead in the third-party application, and updating leads in the Power Apps app when a user updates a lead in the third-party application. E. Dataverse connector: The Power Apps app can be integrated with the third-party application by using the Dataverse connector, which enables the two apps to exchange data. This will allow the management of all leads through the Power Apps app. These options together can provide a comprehensive solution to meet the client's requirements of integrating the two separate apps for managing sales leads.

Bde its better

BDE are the correct answers

Has anyone renewed PL-600 if yes please reply on this i need some help

BDE, as Dual Write is dedicated for D365FO.

Need to create a custom connector that uses the exposed API

The question is around the third party app: Data flow & Odata connects ISV solutions, We need customAPI if the connector is not meeting the need, We need P.Automate flow to manage BPF. CDS is used only when you are connecting CDM DB with Canvas. Your BPF is running in CDS env, our ISV is running outside, you are connecting using Dflow/Odata or Custom API. This is what makes sense to me. Other answers are just to distract you

BDE is the correct choice. A: Dual write is not appropriate in this use case. " Dual-write is an out-of-box infrastructure that provides near-real-time interaction between customer engagement apps and Finance and Operations apps." It's clearly needed a Custom connector not a Finance and Ops connector which is needed here.

Custom Connector should be used. You can create an API with Azure functions for example and then go back to your Power Platform and create the Custom Connector

This is correct.

custom connector for third-party app