Exam PL-600 topic 1 question 16 discussion

Note that Microsoft 365 Multi-Geo is not designed for performance optimization, it is designed to meet data residency requirements. https://docs.microsoft.com/en-us/microsoft-365/enterprise/microsoft-365-multi-geo?view=o365-worldwide My answers would be: 1 - Single instance: use Microsoft Azure Traffic Manager where needed. Reason: You can't actively collaborate on anything with multiple instances and replication. You need a single repository of data. 2 - Multiple instances in different regions with data replication Reason: Customers data is different, so multiple instances are not a problem. You can replicate data when needed and use it any instance for reporting. 3 - Multiple instances in different regions; Power BI for Reporting Separated data and functionality don't need data replication at all. Power BI is capable of aggregate data from multiple sources.

The 3rd question should be： The multi-tenant

1 - Single instance: use Microsoft Azure Traffic Manager where needed. 2 - Multiple instances in different regions; Power BI for Reporting . 3 - Multiple instances in different regions; Power BI for Reporting

It was on 07/24/23 exam

A Power Platform instance is a Database and this can only be allocated to one region. Therefore, single multi geo instance is excluded as it does not exist in Power Platform. There can be multiple environments with one instance/database per environment. So I would select the single instance - Azure Traffic Manager option by process of elimination. Multi instances and PBI for the second solution. Multi Tenant is a very expensive option but available nonetheless as an option for multinational organisations that require it. Multi Tenant specifically allows for separate functionality so I would recommend that for the last solution.

Multi Geo seems more applicable to the company than Azure Traffic Manager. Multi Geo would cater for the company's users who operate in multi-regions at the same time. They would get good performance because the instance is in each of their regions (no latency). Whereas a 'single instance with Azure Traffic Manager' would mean that some of the users will not have the platform in their region to start with. They would not get as good performance to start with and they would need to wait for Azure Traffic Manager to distribute traffic to a closer regions. So single multi-geo seems like the positive approach to start with. Give them an instance in their region to start with.

Eliminate Single multi-geo instance from all answers. Instance can only be in one region, and Muilt-geo only applies to Customer Insights. Eliminate Multi-tenant from all instances. Requirements do not align with this, not necessary. This leaves two options to select from for each question. Question 1: SIngle instance; use traffic manager. Single instance required for collaboration. Traffic manager will only help if there are azure functions utilized. Question 2: Multiple instances in different regions; Power BI reporting. Data can be separated in dataverse but brought together in Power BI for reporting. Same apps and solutions deployed across instances to maintain same functionality. Question 3: Multiple instances in different regions; Power BI for Reporting. Data can be separated in dataverse but brought together in Power BI for reporting. Functionality can be customized to the instance.

1)D, Azure Traffic Manager is load balancer, wouldn't help. need single instance 2) and 3) C, each region has different customers, data replicate doesn't help

1) Single Multi-Geo Instance. Yes, you need a single repository of data, but using Azure Traffic Manager makes literally no sense. It would just route people from different regions to different instances; but you only have one anyway; not to mention it does nothing to improve customization performance. 2) Multiple instances in different regions + power BI. 3) Multiple instances in different regions + power BI.

My answers would be: D-C-B

1 - Single instance: use Microsoft Azure Traffic Manager where needed. 2 - Multiple instances in different regions; Power BI for Reporting 3 - Multiple instances in different regions; Power BI for Reporting

1) Single instance; use MS azure Traffic Manage where needed – Division actively collaborates on customers Using MS traffic manager to improve the performance. 2) Single multi-geo instance – Regions have separate customers but use the same functionality and need global reporting Because of separate customers but same functionality, can use Geo-based Business Unit to handle this situation. 3) Multiple instances in different regions; Power BI for reporting – Regions have separate functionality and customers but global reporting on data Key point here is SEPERATE functionality AND customers, have to develop separate functionalities in respective instance, but can use PBI with the data sets from the instances to issue global reporting. In addition, here not select Multi Tenant, because it cannot global reporting.

1 - A. Single instance; use Microsoft Azure Traffic Manager where needed (Azure Traffic Manager is a DNS-based traffic load balancer, so will not hurt) Multi tenant and Multi instance will force you to sync data between environments and it was clearly pointed that divisions collaborate. Single multi-geo instance there is no multi-geo instance for power platform. https://www.microsoftpartnercommunity.com/t5/KUMPPANIFOORUMI-General/Dynamics-365-Multi-geo-tenant/m-p/36214 Regards, MiTu

In reading through all the documentation, I'm going with 1) Single instance; use Microsoft Azure Traffic Manager where needed and 2) & 3) Multiple instances in different regions; Power BI for Reporting

this was present today

3. Data and functionality are different so they are not dependent. Multiple instances with PBI would be the answer.

This question was there on 20/Feb/2022.