An operations team wants to provision AWS resources in a non-interactive, repeatable way that can be saved in files and re-run from an automated build job, with no person clicking through a graphical interface. Which TWO methods of working with AWS support this scripted, repeatable approach? (Select TWO.)
- AThe AWS Command Line Interface, which issues service commands from a terminal that scripts can call and re-run. Correct
- BInfrastructure as code with AWS CloudFormation, which provisions resources from a declarative template file. Correct
- CThe AWS Management Console, which is a web interface where a person points and clicks to configure resources.
- DAmazon CloudWatch, which collects metrics and logs so teams can monitor how their running resources behave.
- EAWS Trusted Advisor, which inspects an account and recommends improvements to cost, security and performance.
Why A is correct: The AWS CLI runs commands from a terminal, so scripts can invoke and repeat them as part of an automated job.
Why B is correct: CloudFormation provisions resources from a saved template, giving the repeatable, file-driven approach the team wants.
Why C is wrong: The console is a manual graphical interface, so it does not give the scripted, re-runnable provisioning the team needs.
Why D is wrong: CloudWatch monitors resources after they exist and is not a method for provisioning them from scripts or files.
Why E is wrong: Trusted Advisor only advises on an existing account and cannot provision resources from a repeatable file or script.