What is a common way to extend Power Platform Pipelines for enhanced agent lifecycle management?

By using the Pipeline Designer to add new deployment stages

By installing a third-party plugin from AppSource

By adding pre- and post-deployment steps using Power Automate flows

By modifying the pipeline's source code in GitHub

You are developing an agent in Copilot Studio that uses an environment variable to store a connection string. The agent will be deployed to a test and a production environment. How should you reference the environment variable in the agent's logic?

Use a global variable that is set in the agent's startup trigger.

Hard-code the connection string in the agent and change it before each deployment.

Store the connection string in a text file and read it at runtime.

Use the environment variable name directly in the agent's code or expressions.

Your agent solution uses an environment variable for an API key. You need to deploy the solution to a new environment, but the API key must not be visible to makers in the target environment. What should you do?

Share the API key with all makers and rely on their discretion.

Use a connection reference instead of an environment variable for the API key.

Store the API key in the agent's code and obscure it with a custom function.

Mark the environment variable as secret and set its value during import.

Where in Copilot Studio do you create a new solution for managing agents?

In the 'Channels' tab of the agent's settings

In the 'Analytics' section of Copilot Studio

In the 'Solutions' area of the Power Apps portal

In the 'Publish' pane of the agent editor

What is the primary benefit of using environment variables in a solution?

They increase the runtime performance of the agent

They reduce the number of components in a solution

They automatically encrypt sensitive data in the solution

They allow you to change configuration values when moving the solution to another environment

Microsoft Certified:AI Agent Builder Associate

Domain 3Objective 2

Implement Application Lifecycle Management (ALM) for Agents in Copilot Studio AB-620 Practice Questions (Page 3)

Part of the Test and manage agents domain, which accounts for 20–25% of the AB-620 exam. Microsoft does not publish an official question count, but from its 120-minute exam (~50–80 total, ~10–20 in this domain), expect 5–10 from this objective — we provide 34 practice questions to prepare you well beyond it. (estimate)

34questions here

7free pages

6concepts

20–25%of the exam

Questions 11–15

11foundation · easy
What is a common way to extend Power Platform Pipelines for enhanced agent lifecycle management?
Select an answer first
12application · medium
You are developing an agent in Copilot Studio that uses an environment variable to store a connection string. The agent will be deployed to a test and a production environment. How should you reference the environment variable in the agent's logic?
Select an answer first
13expert · hard
Your agent solution uses an environment variable for an API key. You need to deploy the solution to a new environment, but the API key must not be visible to makers in the target environment. What should you do?
Select an answer first
14foundation · easy
Where in Copilot Studio do you create a new solution for managing agents?
Select an answer first
15foundation · easy
What is the primary benefit of using environment variables in a solution?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to AB-620

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Microsoft. “AB-620” is a trademark of its owner, used for identification only.