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.)

ALM for agents that call external systems depends on separating configuration from logic. Storing environment-specific values such as the SharePoint site URL and SQL API base URL in solution environment variables, and referencing those variables from the agent/flow configuration, is correct because 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. Including connection references in the solution and re-establishing/mapping connections for the target environment during or after import/pipeline deployment is correct because connection references abstract connector connections; each environment needs valid connections mapped for the deploying identity/service principal. Hard-coding the Production SharePoint URL in every topic Message node so Test always points at Production data is wrong because it bypasses environment isolation and risks Test traffic hitting Production systems. Deleting connection references before export so the target environment creates anonymous connections automatically is wrong because removing connection references breaks clean deployment and does not create secure anonymous connections by design. Exam tip: Environment variables plus connection references are the twin pillars of multi-environment Copilot Studio ALM.