A county IT team runs the same automation code against lab and production network controllers. How should credentials be handled?
Select an answer to reveal the explanation.
Short Explanation
Lab and prod controllers are different buildings—different keys on different keyrings in the vault. Inject the matching secret for the environment you target. One password in git or prod tokens in lab is how a test script paints the live city.
Full Explanation
Multi-controller automation should retrieve environment-specific credentials from a secrets vault or equivalent secure store so lab mistakes cannot authenticate to production with the same secret. Hard-coding, cross-environment token reuse, and committing secrets defeat separation of duties and audit controls.