Your team packages a Copilot Studio agent that calls a SharePoint knowledge site URL and a SQL API base URL that differ per environment. You also use a Power Automate flow with a SharePoint connection. Which TWO solution practices should you apply so Dev → Test → Prod promotion works cleanly? (Choose two.)
Select all correct answers, then click Submit.
Short Explanation and Infographic
Environment variables are labeled moving boxes for URLs and keys; connection references are the labeled power cords that must be plugged in again at each house. Hard-coding Prod URLs into Dev topics is how you accidentally stress Prod from Test.
Full explanation below image
Full Explanation
ALM for agents that call external systems depends on separating configuration from logic.
Option A is correct. Environment variables hold per-environment settings (URLs, keys via secret patterns, flags) so the same solution package can be configured differently in Test vs Prod.
Option B is correct. Connection references abstract connector connections; each environment needs valid connections mapped for the deploying identity/service principal.
Option C is wrong because hard-coding Production URLs into topics bypasses environment isolation and risks Test traffic hitting Production systems.
Option D is wrong because removing connection references breaks clean deployment and does not create secure anonymous connections by design.
Exam tip: Environment variables + connection references are the twin pillars of multi-environment Copilot Studio ALM.