TA-002-P · Question #208
Your manager has instructed you to start using terraform for the entire infra provisioning of the application stack. There are 4 environments ?DEV , QA , UAT , and PROD. The application team has…
The correct answer is A. Completely separate the working directories , keep one for each environment . For each. In particular, organizations commonly want to create a strong separation between multiple deployments of the same infrastructure serving different development stages (e.g. staging vs. production) or different internal teams. In this case, the backend used for each deployment…
Question
Your manager has instructed you to start using terraform for the entire infra provisioning of the application stack. There are 4 environments ?DEV , QA , UAT , and PROD. The application team has asked for complete segregation between these environments including the backend , state , and also configurations ,since there will be unique resources in different environments . What is the possible way to structure the terraform code to facilitate that.
Options
- ACompletely separate the working directories , keep one for each environment . For each
- BCompletely separate the working directories , keep one for each environment . For each
- CImplement terraform workspaces , and map each environment with one workspace.
- DEnable remote backend storage . Configure 4 different backend storages , one for each
How the community answered
(36 responses)- A75% (27)
- B3% (1)
- C6% (2)
- D17% (6)
Explanation
In particular, organizations commonly want to create a strong separation between multiple deployments of the same infrastructure serving different development stages (e.g. staging vs. production) or different internal teams. In this case, the backend used for each deployment often belongs to that deployment, with different credentials and access controls. Named workspaces are not a suitable isolation mechanism for this scenario.
Topics
Community Discussion
No community discussion yet for this question.