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: Add the custom connector to a managed solution, export the managed solution, and then import the managed solution into the production environment.Does the solution meet the goal?
Answer(s): B
You can't export managed solutions.Correct Solution: Use the maker portal to export the custom connector. Then use the maker portal to import the connector into the production environment.Export solutionsYou can manually export solutions. We recommend that you create an unmanaged solution to use for exporting your customizations, and then export your customizations periodically so that you have a backup in case anything happens. You can't export managed solutions or the Default Solution.Note: Solutions are used to transport apps and components from one environment to another or to apply a set of customizations to existing apps. A solution can contain one or more apps as well as other components such as site maps, tables, processes, web resources, choices, flows, and more.Solutions are the mechanism for implementing application lifecycle management (ALM) in Power Apps and other Power Platform products, such as Power Automate.Note 2: Create custom connectors in solutionsBy using solutions, you can move your custom connectors—along with canvas apps, flows, and Microsoft Dataverse customizations—in a single package. Solutions have the added benefit of managing your customizations in Azure DevOps and automating your CI/CD process.Steps0. Select the Solutions tab.1. Create a new solution or open an existing unmanaged solution.2. Select New > Automation > Custom connector.3. A new tab opens, where you create a new custom connector.4. When you've finished, select Save.5. Close the browser tab. You'll see the new custom connector listed within your solution.*-> 6. To migrate the custom connector and any other customizations, export your solution, and then import it to the target environment.
https://learn.microsoft.com/en-us/connectors/custom-connectors/customconnectorssolutionshttps://learn.microsoft.com/en-us/power-apps/maker/data-platform/solutions-overviewhttps://learn.microsoft.com/en-us/power-apps/maker/data-platform/export-solutions
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?
You export, not publish, solutions.Correct Solution: Use the maker portal to export the custom connector. Then use the maker portal to import the connector into the production environment.Export solutionsYou can manually export solutions. We recommend that you create an unmanaged solution to use for exporting your customizations, and then export your customizations periodically so that you have a backup in case anything happens. You can't export managed solutions or the Default Solution.Note: Solutions are used to transport apps and components from one environment to another or to apply a set of customizations to existing apps. A solution can contain one or more apps as well as other components such as site maps, tables, processes, web resources, choices, flows, and more.Solutions are the mechanism for implementing application lifecycle management (ALM) in Power Apps and other Power Platform products, such as Power Automate.Note 2: Create custom connectors in solutionsBy using solutions, you can move your custom connectors—along with canvas apps, flows, and Microsoft Dataverse customizations—in a single package. Solutions have the added benefit of managing your customizations in Azure DevOps and automating your CI/CD process.Steps0. Select the Solutions tab.1. Create a new solution or open an existing unmanaged solution.2. Select New > Automation > Custom connector.3. A new tab opens, where you create a new custom connector.4. When you've finished, select Save.5. Close the browser tab. You'll see the new custom connector listed within your solution.*-> 6. To migrate the custom connector and any other customizations, export your solution, and then import it to the target environment.
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?
Answer(s): A
Correct Solution: Use the maker portal to export the custom connector. Then use the maker portal to import the connector into the production environment.Export solutionsYou can manually export solutions. We recommend that you create an unmanaged solution to use for exporting your customizations, and then export your customizations periodically so that you have a backup in case anything happens. You can't export managed solutions or the Default Solution.Note: Solutions are used to transport apps and components from one environment to another or to apply a set of customizations to existing apps. A solution can contain one or more apps as well as other components such as site maps, tables, processes, web resources, choices, flows, and more.Solutions are the mechanism for implementing application lifecycle management (ALM) in Power Apps and other Power Platform products, such as Power Automate.Note 2: Create custom connectors in solutionsBy using solutions, you can move your custom connectors—along with canvas apps, flows, and Microsoft Dataverse customizations—in a single package. Solutions have the added benefit of managing your customizations in Azure DevOps and automating your CI/CD process.Steps0. Select the Solutions tab.1. Create a new solution or open an existing unmanaged solution.2. Select New > Automation > Custom connector.3. A new tab opens, where you create a new custom connector.4. When you've finished, select Save.5. Close the browser tab. You'll see the new custom connector listed within your solution.*-> 6. To migrate the custom connector and any other customizations, export your solution, and then import it to the target environment.
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 Postman to export the custom connector. Then use Postman to import the connector into the production environment.Does the solution meet the goal?
Postman is a useful tool for testing and exploring an API. In this case, we can capture all of our interactions as a collection that we can export as a file and then use this file to create a custom connector. The Postman website provides an in-depth walkthrough of creating a collection which is available here.Correct Solution: Use the maker portal to export the custom connector. Then use the maker portal to import the connector into the production environment.Export solutionsYou can manually export solutions. We recommend that you create an unmanaged solution to use for exporting your customizations, and then export your customizations periodically so that you have a backup in case anything happens. You can't export managed solutions or the Default Solution.Note: Solutions are used to transport apps and components from one environment to another or to apply a set of customizations to existing apps. A solution can contain one or more apps as well as other components such as site maps, tables, processes, web resources, choices, flows, and more.Solutions are the mechanism for implementing application lifecycle management (ALM) in Power Apps and other Power Platform products, such as Power Automate.Note 2: Create custom connectors in solutionsBy using solutions, you can move your custom connectors—along with canvas apps, flows, and Microsoft Dataverse customizations—in a single package. Solutions have the added benefit of managing your customizations in Azure DevOps and automating your CI/CD process.Steps0. Select the Solutions tab.1. Create a new solution or open an existing unmanaged solution.2. Select New > Automation > Custom connector.3. A new tab opens, where you create a new custom connector.4. When you've finished, select Save.5. Close the browser tab. You'll see the new custom connector listed within your solution.*-> 6. To migrate the custom connector and any other customizations, export your solution, and then import it to the target environment.
A company uses Microsoft Dataverse rollup fields to calculate insurance exposure and risk profiles for customers.Users report that the system does not update values for the rollup fields when new insurance policies are written.You need to recalculate the value of the rollup fields immediately after a policy is created.What should you do?
Post your Comments and Discuss Microsoft PL-400 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the PL-400 content, but please register or login to continue.