Microsoft Power Platform test (Intermediate)

Sample questions

5 sample questions from the Microsoft Power Platform test, with the answers. Samples are taken out of the live test, so you will not meet these when you sit it.

1. A data import operation from a CSV file to a Dataverse table failed. Which of the following is the most likely reason for the failure?

   1. Data import from a CSV file failed because the file was not mapped to the correct Dataverse table columns.
   2. Data import from a CSV file failed because the file was not stored in the correct folder in OneDrive.
   3. Data import from a CSV file failed because the file was not shared with the correct user.
   4. Data import from a CSV file failed because the file was not encrypted.

   Answer: A. Data import from a CSV file failed because the file was not mapped to the correct Dataverse table columns.

   When importing data into Dataverse from a CSV file, it is essential to map the CSV columns to the corresponding Dataverse table columns. If the mapping is incorrect or missing, the import will fail or result in incorrect data being inserted into the table. This is a common issue during data import and can be resolved by verifying the mapping between the CSV file and the Dataverse table.

2. You are designing a Dataverse solution for a company that tracks sales representatives and their assigned customer accounts. Each sales representative can be assigned to multiple customer accounts, and each customer account can have multiple sales representatives. What is the correct approach to model this relationship in Dataverse?

   1. Create a many-to-many relationship using an intersect table
   2. Add a lookup column to the Sales Representatives table pointing to the Customer Accounts table
   3. Use a virtual table to link Sales Representatives and Customer Accounts
   4. Create a one-to-many relationship with a lookup column in the Customer Accounts table pointing to the Sales Representatives table

   Answer: A. Create a many-to-many relationship using an intersect table

   When modeling a scenario where multiple sales representatives can be assigned to multiple customer accounts, a many-to-many relationship is required. This is achieved by creating an intersect table (also known as a junction table) that links the two tables. This table contains foreign keys to both the Sales Representatives and Customer Accounts tables, enabling the many-to-many relationship. Options 1, 2, and 3 are incorrect because they do not address the specific need for a many-to-many relationship, which requires the creation of an intersect table.

3. Which of the following best describes a calculated column in Dataverse?

   1. A formula column stores a fixed value that cannot be changed.
   2. A calculated column uses a formula to derive its value from other columns in the same table.
   3. A rollup column uses a formula to derive its value from other columns in the same table.
   4. A choice column uses a formula to derive its value from other columns in the same table.

   Answer: B. A calculated column uses a formula to derive its value from other columns in the same table.

   A calculated column in Dataverse derives its value using a formula based on other columns in the same table. A rollup column aggregates values from related records, a formula column performs calculations based on other columns (but is typically used in model-driven apps), and a choice column defines a set of predefined options for data entry.

4. What happens to a Power Automate flow if it reaches the default timeout period during execution?

   1. The flow will automatically restart from the beginning after the timeout period has been reached.
   2. The flow will time out after the default timeout period, and any actions that were in progress will be cancelled.
   3. The flow will continue executing even after the timeout period has been reached.
   4. The flow will pause execution until the timeout period is manually extended.

   Answer: B. The flow will time out after the default timeout period, and any actions that were in progress will be cancelled.

   If a Power Automate flow is running and the timeout period is reached, the flow will stop executing, and any actions that were in progress will be cancelled. This is a common mistake when designing flows, as it can lead to incomplete execution of tasks if the timeout is not properly configured or if the flow takes longer than expected to complete.

5. Which of the following statements best describes how Data Loss Prevention (DLP) policies work in the Power Platform?

   1. DLP policies are enforced at the user level and vary depending on individual user permissions.
   2. DLP policies enforce connector classification into Business, Non-business, and Blocked, and prevent mixing Business and Non-business connectors in the same app or flow.
   3. DLP policies apply to the data itself, not the connectors used in apps or flows.
   4. DLP policies are only enforced in production environments and do not apply to development or testing environments.

   Answer: B. DLP policies enforce connector classification into Business, Non-business, and Blocked, and prevent mixing Business and Non-business connectors in the same app or flow.

   Data Loss Prevention (DLP) policies in the Power Platform classify connectors into categories (Business, Non-business, Blocked) and enforce rules that prevent mixing Business and Non-business connectors in the same app or flow. This ensures compliance with organizational data governance standards. Option 1 is correct because it aligns with how DLP policies work. Option 2 is incorrect because DLP policies apply to connectors, not to the data itself. Option 3 is incorrect because DLP policies are not limited to production environments—they apply across all environments. Option 4 is incorrect because DLP policies are enforced at the tenant or environment level, not at the user level.