Your team Is excited about the use of AWS because now they have access to programmable Infrastructure”
You have been asked to manage your AWS infrastructure In a manner similar to the way you might manage
application code You want to be able to deploy exact copies of different versions of your infrastructure, stage
changes into different environments, revert back to previous versions, and identify what versions are running
at any particular time (development test QA . production).
Which approach addresses this requirement?
A.
Use cost allocation reports and AWS Opsworks to deploy and manage your infrastructure.
B.
Use AWS CloudWatch metrics and alerts along with resource tagging to deploy and manage your
infrastructure.
C.
Use AWS Beanstalk and a version control system like GIT to deploy and manage your infrastructure.
D.
Use AWS CloudFormation and a version control system like GIT to deploy and manage your infrastructure.
Explanation:
http://aws.amazon.com/opsworks/faqs/
Answer: D
– Answer A: does not provide versioning
– Answer B: does not provide versioning
– Answer C: Beanstalk provide version control over your application (not infrastructure)
Thx, Frank
2
0
Exactly!
0
0
Frank you are good!
0
0
Cloudwatch doesn’t address the question at all. The answer would be C or D and I would lean towards D using CloudFormation.
0
0
The Answer should be ‘A’, Opsware does support versioning.
http://aws.amazon.com/opsworks/faqs/
ref:
Q: What is AWS OpsWorks?
Q: What elements of my application can I control when using AWS OpsWorks?
&
Q: What software versioning and revision control systems does AWS OpsWorks support?
AWS OpsWorks can retrieve the code you want to deploy from common version control systems like Git and Subversion as well as HTTP and private or public S3 bundles. For example, you can deploy a specific version of your application by adding the version or branch from your Git repository into your OpsWorks app definition. You can also use Chef recipes to deploy your apps from anywhere you like using rsync or scp.
0
1
I chose D
Extract from what is AWS CloudFormation: (http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/Welcome.html)
Easily Control and Track Changes to Your Infrastructure
In some cases, you might have underlying resources that you want to upgrade incrementally. For example, you might change to a higher performing instance type in your Auto Scaling launch configuration so that you can reduce the maximum number of instances in your Auto Scaling group. If problems occur after you complete the update, you might need to roll back your infrastructure to the original settings. To do this manually, you not only have to remember which resources were changed, you also have to know what the original settings were.
When you provision your infrastructure with AWS CloudFormation, the AWS CloudFormation template describes exactly what resources are provisioned and their settings. Because these templates are text files, you simply track differences in your templates to track changes to your infrastructure, similar to the way developers control revisions to source code. For example, you can use a version control system with your templates so that you know exactly what changes were made, who made them, and when. If at any point you need to reverse changes to your infrastructure, you can use a previous version of your template.
0
0
I will go with D.
https://aws.amazon.com/opsworks/faqs/
0
1
Tricky question as opsworks does support versioning as does cloud formation. Not sure what cost optimization reports have to do with versioning. So i’ll go with D.
0
0
D, CLOUDFORMATION
1
0
D
0
0
Answer is D,
The question requires versioning for infrastructure, not include of application (opswork)
0
0
d
0
0
D – Cloud Formation for multiple infrastructure versions.
A is wrong, Chef can go fetch versions from Github or Subversion, and is a configuration management tool
B is wrong , use CloudWatch to track resource allocations via high/low watermarks and alarms
C is wrong, Elastic Beanstalk runs a single version of your application.
0
0
https://aws.amazon.com/opsworks/chefautomate/faqs/
OpsWorks for Chef Automate automatically performs updates for new Chef minor versions. OpsWorks for Chef Automate does not perform major platform version updates automatically (for example, a major new platform version such as Chef Automate 13) because these updates might include backward-incompatible changes and require additional testing. In these cases, you must manually initiate the update.
Answer is D
0
0
D
0
0
D
0
0
Correct answer is D
0
0
D
0
0