A company requires a plug-in that makes multiple requests to an external web service. The plug-in must not time out when the web service has issues or is slow to respond.
You need to create the plug-in.
What should you do?
A. Assign the IOrganizationService object to a member variable.
B. Register the plug-in to run synchronously.
C. Register the plug-in step once for each web service request.
D. Set the HTTP connection KeepAlive property to false.
Show Answer
Correct Answer: D
Explanation: Dataverse plug-ins that call external web services can time out due to persistent HTTP connections being reused against slow or unstable hosts. Microsoft explicitly recommends setting the HTTP KeepAlive property to false when interacting with external services from plug-ins to avoid hangs and timeouts. The other options do not address the root cause of external call timeouts.
Question 65
Case study -
This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section.
To start the case study -
To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question.
Background -
Northwind Traders uses Microsoft Dynamics 365 Sales to manage its sales process. To better understand its customers, Northwind Traders invests in a team of researchers who gather data from multiple sources. The company stores the data it collects in a Microsoft Azure SQL Database. The company plans to use the data to enrich account records and make the sales team more effective.
Current environment -
Environment -
• The company has three Microsoft Power Platform environments with Dynamics 365 Sales installed. The environments are named development, test, and production.
• Each environment has an application user that can be used for integrations.
• The company must use solutions to perform all customization and configuration deployment.
Data -
• Researchers are responsible for creating account records.
• Researchers have permissions on the Account table to create records, read all records, and update records they own.
• A synchronous plug-in runs when an account record is created and could reassign the record to a different user.
• Users must access data as themselves to enforce security and audit changes.
• A column named new_dataid is added to the Account table. The column uniquely identifies which data it should receive.
• Researchers have researched only the top 20 percent of account records.
Web API -
• The company creates an Azure Function to run a RESTful .NET Web API.
• Data can be retrieved by placing a GET request to the URL https://dataservice-[ENVIRONMENTNAME].azurewebsites.net/enrich/[DATAID].
• [ENVIRONMENTNAME] is the name of the Microsoft Power Platform environment that requests the data.
• [DATAID] is the new_dataid column in the Account table.
• The Web API response will return a 200 response plus data if the DataId is found. Otherwise, a 404 response is returned.
• Developers plan to create a custom connector from the Web API to make it accessible from Microsoft Power Platform.
Requirements -
Custom connector -
• The Web API definition used to create the custom connector must be generated based on a low-code technology.
• The URL used by the custom connector must incorporate the current environment name without hardcoding values.
• Errors generated by the custom connector must not cause downstream processes to fail.
• Text descriptions and field placeholder text that describe the use of the custom connector must appear for non-developers.
Process -
• All account records must be updated with data from the Web API once automatically.
• Only account records that contain a DataId should be updated by the Web API.
• Researchers must create Power Automate flows to specify data analysis priority.
• The researchers require a process that repurposes a set of identical steps of parameterized Microsoft Dataverse queries from a Power Automate flow for use in other flows that have different parameters. The researchers want to avoid recreating the steps manually each time they create a flow to save time and avoid errors.
Issues -
• A tester attempts to connect to the production instance of the Web API with a DataId that should return data. The tester receives an error stating that the remote name could not be resolved.
• A missing component causes an error to occur when importing the solution that contains the Power Automate flow to update account records in a test environment.
You need to determine the cause of the 404 error when connecting to the production instance of the Web API.
What do you identify?
A. The web service lacks data for the record.
B. An authentication error occurred.
C. The request timed-out.
D. The host name in the URL is missing a valid value.
Show Answer
Correct Answer: D
Explanation: The error reported is that the remote name could not be resolved, which indicates a DNS or URL resolution problem, not an application-level 404 from the API. In this case, the Web API URL depends on the environment name (dataservice-[ENVIRONMENTNAME].azurewebsites.net). If the production environment name is missing or incorrect, the host name cannot be resolved, causing the connection failure. A true 404 due to missing data would require the host to resolve successfully first.
Question 66
Case study -
This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section.
To start the case study -
To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question.
Background -
Northwind Traders uses Microsoft Dynamics 365 Sales to manage its sales process. To better understand its customers, Northwind Traders invests in a team of researchers who gather data from multiple sources. The company stores the data it collects in a Microsoft Azure SQL Database. The company plans to use the data to enrich account records and make the sales team more effective.
Current environment -
Environment -
• The company has three Microsoft Power Platform environments with Dynamics 365 Sales installed. The environments are named development, test, and production.
• Each environment has an application user that can be used for integrations.
• The company must use solutions to perform all customization and configuration deployment.
Data -
• Researchers are responsible for creating account records.
• Researchers have permissions on the Account table to create records, read all records, and update records they own.
• A synchronous plug-in runs when an account record is created and could reassign the record to a different user.
• Users must access data as themselves to enforce security and audit changes.
• A column named new_dataid is added to the Account table. The column uniquely identifies which data it should receive.
• Researchers have researched only the top 20 percent of account records.
Web API -
• The company creates an Azure Function to run a RESTful .NET Web API.
• Data can be retrieved by placing a GET request to the URL https://dataservice-[ENVIRONMENTNAME].azurewebsites.net/enrich/[DATAID].
• [ENVIRONMENTNAME] is the name of the Microsoft Power Platform environment that requests the data.
• [DATAID] is the new_dataid column in the Account table.
• The Web API response will return a 200 response plus data if the DataId is found. Otherwise, a 404 response is returned.
• Developers plan to create a custom connector from the Web API to make it accessible from Microsoft Power Platform.
Requirements -
Custom connector -
• The Web API definition used to create the custom connector must be generated based on a low-code technology.
• The URL used by the custom connector must incorporate the current environment name without hardcoding values.
• Errors generated by the custom connector must not cause downstream processes to fail.
• Text descriptions and field placeholder text that describe the use of the custom connector must appear for non-developers.
Process -
• All account records must be updated with data from the Web API once automatically.
• Only account records that contain a DataId should be updated by the Web API.
• Researchers must create Power Automate flows to specify data analysis priority.
• The researchers require a process that repurposes a set of identical steps of parameterized Microsoft Dataverse queries from a Power Automate flow for use in other flows that have different parameters. The researchers want to avoid recreating the steps manually each time they create a flow to save time and avoid errors.
Issues -
• A tester attempts to connect to the production instance of the Web API with a DataId that should return data. The tester receives an error stating that the remote name could not be resolved.
• A missing component causes an error to occur when importing the solution that contains the Power Automate flow to update account records in a test environment.
You need to implement visual hints in the custom connector.
What should you do? Each correct answer presents a complete solution.
NOTE: Each correct selection is worth one point.
A. In the custom connector, update the name of the policy template.
B. Extend the Open API definition of the Web API for the EnvironmentName parameter.
C. Extend the Open API definition of the Web API for the DataId parameter.
D. In the custom connector, update the description for the DataId parameter.
Show Answer
Correct Answer: B, D
Explanation: Visual hints in a custom connector are provided through descriptions and metadata defined in the OpenAPI definition and connector configuration. Extending the OpenAPI definition for the EnvironmentName parameter allows clear guidance on how the environment-specific URL should be resolved dynamically, helping non-developers understand its purpose. Updating the description for the DataId parameter adds helpful placeholder text and explanations so users know when and how to supply it. Updating policy templates or the parameter schema itself does not address visual hints.
Question 67
HOTSPOT
-
Field technicians use a canvas app to update Microsoft Dataverse data. The app is designed to work when it is not connected to the internet.
The app requires a plug-in to apply business logic after records are updated. Unhandled exceptions must not prevent records from saving or syncing.
You need to register the plug-in step to apply the business logic.
Which values should you use for each plug-in step setting? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Show Answer
Correct Answer: Offline
PostOperation
Explanation: Offline deployment allows the plug-in to run when records are synced from an offline canvas app. PostOperation applies business logic after the record is saved; unhandled exceptions do not block the save or sync process.
Question 68
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than once correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
A company develops a new custom connector for a Microsoft Entra ID-protected Azure Function that was created as a single tenant app.
The custom connector must be moved to a production environment. The connector must be visible and accessible only to users in the tenant.
You need to deploy the custom connector.
Solution: Use the maker portal to export the custom connector. Then use the maker portal to import the connector into the production environment.
Does the solution meet the goal?
A. Yes
B. No
Show Answer
Correct Answer: B
Explanation: The solution does not meet the goal because a custom connector cannot be exported directly by itself from the maker portal. To move a custom connector between environments, it must first be added to a solution and then the solution is exported and imported. As stated, the proposed approach is not a valid deployment method, so it does not meet the requirement.
Question 69
You manage a Microsoft Power Automate cloud flow. The cloud flow queries Microsoft Dataverse data by using the List rows action.
You need to configure the cloud flow to process 10,000 records in a single run.
What should you do? Each correct answer presents a complete solution.
NOTE: Each correct selection is worth one point.
A. Set the row count parameter to 10,000.
B. Return the first 5,000 records and use the @odata.nextLink in the response to return the remaining records.
C. Create the query by using FetchXML and set the top parameter to 10,000.
D. Turn on pagination and set the threshold to 10,000.
Show Answer
Correct Answer: B, D
Explanation: The Dataverse List rows action returns a maximum of 5,000 rows per page. To process 10,000 records in a single flow run, you must either handle server-side paging via the @odata.nextLink to retrieve subsequent pages, or enable pagination in the action and set the threshold to 10,000 so Power Automate automatically retrieves multiple pages. Setting row count or FetchXML top to 10,000 is not supported because Dataverse limits results per page to 5,000.
Question 70
DRAG DROP
-
You are developing a Power Apps app for a company. The app will interact with the company's enterprise resource planning (ERP) system. The app allows users to create quotes for customers. You are creating a plug-in for the app.
The solution must meet the following requirements:
• Display an error message if there is no account associated with a quote and prevent changes to the quote.
• Synchronize quotes with the external ERP system.
You need configure the plug-in execution pipeline.
Which pipeline stages should you use? To answer, drag the appropriate pipeline stages to the correct requirements. Each pipeline stage may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.
Show Answer
Correct Answer: Display an error message if there is no account associated with a quote and prevent changes to the quote:
PreValidation
Synchronize quotes with the external ERP system:
PostOperation
Explanation: PreValidation runs before the core operation, allowing validation and cancellation with an error message. PostOperation runs after the transaction succeeds and is appropriate for external integrations such as ERP synchronization; MainOperation is not used for standard plug-ins.
Question 71
You are developing a Power Platform app.
The app must implement a two-way listener to an on-premises system by using Microsoft Azure Service Bus. You create an Azure Service Bus namespace and messaging entity. You must add the shared access policies.
You need to select the permissions for the messaging entity.
Which two permissions should you use? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.
A. System customizer
B. Listen
C. Read
D. Send
E. Manage
Show Answer
Correct Answer: B, D
Explanation: A two-way listener requires the app to both receive messages from and send messages to Azure Service Bus. The Listen permission allows the app to receive messages, while the Send permission allows it to send messages back. Read and Manage are not required for message exchange, and System customizer is unrelated.
Question 72
HOTSPOT
-
Case study
-
This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section.
To start the case study
-
To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question.
Background
-
Northwind Traders uses Microsoft Dynamics 365 Sales to manage its sales process. To better understand its customers, Northwind Traders invests in a team of researchers who gather data from multiple sources. The company stores the data it collects in a Microsoft Azure SQL Database. The company plans to use the data to enrich account records and make the sales team more effective.
Current environment
-
Environment
-
• The company has three Microsoft Power Platform environments with Dynamics 365 Sales installed. The environments are named development, test, and production.
• Each environment has an application user that can be used for integrations.
• The company must use solutions to perform all customization and configuration deployment.
Data
-
• Researchers are responsible for creating account records.
• Researchers have permissions on the Account table to create records, read all records, and update records they own.
• A synchronous plug-in runs when an account record is created and could reassign the record to a different user.
• Users must access data as themselves to enforce security and audit changes.
• A column named new_dataid is added to the Account table. The column uniquely identifies which data it should receive.
• Researchers have researched only the top 20 percent of account records.
Web API
-
• The company creates an Azure Function to run a RESTful .NET Web API.
• Data can be retrieved by placing a GET request to the URL https://dataservice-[ENVIRONMENTNAME].azurewebsites.net/enrich/[DATAID].
• [ENVIRONMENTNAME] is the name of the Microsoft Power Platform environment that requests the data.
• [DATAID] is the new_dataid column in the Account table.
• The Web API response will return a 200 response plus data if the DataId is found. Otherwise, a 404 response is returned.
• Developers plan to create a custom connector from the Web API to make it accessible from Microsoft Power Platform.
Requirements
-
Custom connector
-
• The Web API definition used to create the custom connector must be generated based on a low-code technology.
• The URL used by the custom connector must incorporate the current environment name without hardcoding values.
• Errors generated by the custom connector must not cause downstream processes to fail.
• Text descriptions and field placeholder text that describe the use of the custom connector must appear for non-developers.
Process
-
• All account records must be updated with data from the Web API once automatically.
• Only account records that contain a DataId should be updated by the Web API.
• Researchers must create Power Automate flows to specify data analysis priority.
• The researchers require a process that repurposes a set of identical steps of parameterized Microsoft Dataverse queries from a Power Automate flow for use in other flows that have different parameters. The researchers want to avoid recreating the steps manually each time they create a flow to save time and avoid errors.
Issues
-
• A tester attempts to connect to the production instance of the Web API with a DataId that should return data. The tester receives an error stating that the remote name could not be resolved.
• A missing component causes an error to occur when importing the solution that contains the Power Automate flow to update account records in a test environment.
You need to configure a Dataverse trigger and action in a Power Automate flow so researchers can update account records with data from the Web API even if they do not have edit privileges on the record.
What should you configure for each trigger and action requirement? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Show Answer
Correct Answer: Added or Modified
Service principal
Explanation: The flow should run when an account is created or updated to ensure enrichment occurs once and when the DataId is set. Updating rows must use a service principal so the flow can update records even when researchers do not have edit privileges, while still enforcing centralized security and auditability.
Question 73
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than once correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
A company develops a new custom connector for a Microsoft Entra ID-protected Azure Function that was created as a single tenant app.
The custom connector must be moved to a production environment. The connector must be visible and accessible only to users in the tenant.
You need to deploy the custom connector.
Solution: Publish the custom connector to AppSource.
Does the solution meet the goal?
A. Yes
B. No
Show Answer
Correct Answer: B
Explanation: Publishing a custom connector to AppSource makes it publicly discoverable (or at least broadly available) and is intended for marketplace distribution, not tenant‑restricted use. A single‑tenant, Entra ID–protected custom connector that must be visible only within one tenant should be deployed and shared within the tenant (e.g., via Power Platform environments and connector sharing), not published to AppSource.
$19
Get all 406 questions with detailed answers and explanations
Instant download HTML + PDF delivered the moment payment clears.
Secure Stripe checkout we never see or store your card details.
7-day refund if files are defective see our refund policy.