This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
You plan the environments for an agent that makers promote from development to test and production by using Power Platform pipelines. Which plan meets the pipeline requirements?
Use the development environment as the pipeline host, so the team maintains one fewer environment.
Create a separate production type environment as the pipeline host, and make the test and production environments managed environments.
Build the agent in the default environment, because every licensed user already has the environment maker role there.
You plan to create an agent on the GitHub Copilot harness and promote it through test and production in a custom solution. What should you do?
Save the agent first, and then select the custom solution in the Solution field before the first deployment.
Create the agent in a sandbox environment, and export its solution as unmanaged for the test environment.
Create the custom solution and its publisher first, and then select that solution in the Solution field on the Agent details tab before you save the agent.
An agent's flow reads a SharePoint list. The test and production environments each use their own site, their own list, and their own account. How should you configure the solution so the same package works in both environments?
Add a connection reference for the SharePoint connection and data source environment variables for the site and the list, and then supply the values for each environment during deployment.
Add a connection reference only, because the connection records the site and the list that the flow uses.
Store the account credentials, site, and list as Text environment variables, and set their current values in development before you export.
Production deployments of an agent solution must run under a nonuser identity and wait for approval. Makers have no access to the production environment. Which configuration meets these requirements?
Assign makers the System Administrator role in production, so the pipeline can run each deployment as the requesting maker after approval.
Turn on Pre-export step required on the production stage, and approve requests in a flow before the pipeline exports the solution.
Turn on Is delegated deployment with a service principal on the production stage, add the service principal as an application user in the host and the target environment, and approve requests through a flow that starts from OnApprovalStarted.
A pipeline deploys an agent solution to production. In production, the agent doesn't send telemetry to Azure Application Insights and doesn't use the web channel security settings configured in development. What explains this behavior?
The pipeline deployed the solution as unmanaged, and unmanaged solutions don't carry channel or telemetry settings.
Application Insights and web channel security settings aren't solution-aware, so they need to be configured in production after deployment.
The deployment didn't supply values for the solution's environment variables.
You must answer all questions before checking your work.
Was this page helpful?
Need help with this topic?
Want to try using Ask Learn to clarify or guide you through this topic?