Exam PL-600 topic 3 question 13 discussion

CD This happens a lot. People have custom configuration data and when going in between environments they dont create the same data You can in fact use the import wizard to also set the GUID, so when people say you cannot you can. So this one is straight forward for me

The requirement is to "update" the existing data that has problems with "record identifiers" - it is not clear what records they are talking about. So, option D is crossed of the list for me as I would not use a data import to update existing data. Option C is used for configurations not data. Options A, B are definitely plausible tools References: https://www.infostrat.com/post/how-to-update-existing-records-with-dynamics-365-import-wizard

They are asking about data syncing between different environments.

It is definitely CD

In my opinion CD is the best answer. The issue lies in "record identifiers" not being the same in all environments. This refers to the GUID of the records. "Update the reference data" is misleading, because you cannot update the GUID of an existing record, you can only create a new record. Power Automate and Logic Apps work the same. In both you cannot set the GUID of a record with the Dataverse connector, which is needed here. You could trigger a dataflow, but nothing suggests, that such a setup is in place. With the CMT and Import Wizard you can import data and set the GUID of records. Azure Data Factory does not seem to fit, because it is a big data integration tool. Seems a bit much to change some reference data.

both flows and logic apps are mainly working the same in this case, if you need to update data across environments in one step not per environment which would take a lot of time only A and B would be able to do it

C. Configuration Migration tool and D. Import Data Wizard are two possible ways to update the reference data across all environments. The Configuration Migration tool can be used to move configuration data between environments, including reference data related to car colors, car types, and car models. This tool enables you to export configuration data from one environment and import it into another environment. This can help to ensure that the reference data is consistent across all environments. The Import Data Wizard is another option to update the reference data across all environments. This tool allows you to import data from a file into Common Data Service, which can then be used in your solution. You can use the Import Data Wizard to import the reference data related to car colors, car types, and car models into each environment. This can help to ensure that the reference data is consistent across all environments.

A. Power Automate flows (Correct): Power Automate can be used to create flows that automate tasks across different services and environments, including synchronizing reference data between environments. C. Configuration Migration tool (Correct): The Configuration Migration tool allows for the export of data from one environment and import into another, ensuring consistency across environments. This makes it a suitable choice for updating reference data across environments.

Again one of those questions: Last sentence asks to update data, so only A and B are suitable.

It is definitely CD.

What is the correct answer?

So the question can be rephrased as: what is the recommended tool to transfer reference data between environments keeping the unique identifiers. The correct answers are A, B, C and E because all this tools are able to move data from one place to another keeping the same unique ID. For me CE make the most sense, never saw a reference data moved by Power Automate in my life. Anybody can tell me why nobody is voting for Data Factory? It's a recommended tool for move data between to/from dataverse in the cloud, we can argue if it's not overkill, but to be honest building Logic app is for me bigger overkill than creating super basic Data Factory flow which can be reused

CD for a single update on records

CD Better Suited

This is about a 1-time correction. I see no reason to build neither flow now logic app.

How would you import unique identifiers with the import wizard? Configuration Migration can do that, but is not suitable for updating transactional data - i.e. the references in the account table. I believe the answers are correct.

I agree with C and D.