Your company needs to automate 3 layers of a large cloud deployment. You want to be able to track this deployment’s
evolution as it changes over time, and carefully control any alterations. What is a good way to automate a stack to meet
these requirements?
A.
Use OpsWorks Stacks with three layers to model the layering in your stack.
B.
Use CloudFormation Nested Stack Templates, with three child stacks to represent the three logical layers of your cloud.
C.
Use AWS Config to declare a configuration set that AWS should roll out to your cloud.
D.
Use Elastic Beanstalk Linked Applications, passing the important DNS entires between layers using the metadata interface.
Explanation:
Only CloudFormation allows source controlled, declarative templates as the basis for stack automation. Nested Stacks
help achieve clean separation of layers while simultaneously providing a method to control all layers at once when needed.
https://blogs.aws.amazon.com/application-management/post/Tx1T9JYQOS8AB9I/Use-Nested-Stacks-to-CreateReusable-Templates-and-Support-Role-Specialization
B.
Using Cloud formation nested stack best fits here.
1
1
” able to track this deployment’s evolution as it changes over time, and carefully control any alterations” – this sounds like Config. The wording of C is bad – Config tracks but not Control (you have to control by tracking).
So B – CloudFormation could be a better answer – CloudFormation – does not Track – you can version and track that way.
So answer should be B + C. But they want only 1. So who knows- maybe B.
0
0
B is best fits.
0
1
B is the right answer, we can track the changes with versioning control, lets say in git or so.
0
1