Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Amazon Exam SOA-C02 Topic 8 Question 88 Discussion

Actual exam question for Amazon's SOA-C02 exam
Question #: 88
Topic #: 8
[All SOA-C02 Questions]

A company uses AWS CloudFormation to manage a stack of Amazon EC2 instances on AWS. A SysOps administrator needs to keep the instances and all of the instances' data, even if someone deletes the stack.

Which solution will meet these requirements?

Show Suggested Answer Hide Answer
Suggested Answer: D

Amazon FSx provides a fully managed file system that is optimized for Windows-based workloads and can be used to create file shares that can be accessed both on premises and in the AWS Cloud. The file shares that are created in Amazon FSx are highly available and can be accessed with low latency. Additionally, Amazon FSx supports Windows-based authentication, making it easy to integrate with existing Windows user accounts.


Contribute your Thoughts:

Mitsue
1 months ago
I'm just picturing someone frantically trying to recover their instances after accidentally deleting the stack. Option D is the only way to avoid that nightmare scenario.
upvoted 0 times
...
Jesusa
1 months ago
Option D is the clear winner. Setting the DeletionPolicy to Retain is the only way to ensure the instances and their data survive a stack deletion. Gotta love those CloudFormation features!
upvoted 0 times
...
Lilli
1 months ago
Haha, I bet the person who wrote this question is a real prankster. They're probably just testing if we can spot the obvious solution!
upvoted 0 times
Lamonica
12 days ago
Use Amazon EBS volumes to store the data.
upvoted 0 times
...
Lashawn
14 days ago
Enable termination protection on the instances.
upvoted 0 times
...
Rosenda
17 days ago
Create an Amazon Machine Image (AMI) of the instances.
upvoted 0 times
...
...
Vincenza
2 months ago
Hmm, I'm not sure DLM or AWS Backup are the right solutions here. They're great for backups, but we need to make sure the instances themselves stick around even if the stack gets deleted.
upvoted 0 times
Melinda
4 days ago
C: Yeah, I agree with option D. That way the instances will stick around even if the stack is deleted.
upvoted 0 times
...
Maryann
7 days ago
B: I think that option D is the best choice. Set the DeletionPolicy attribute to Retain for the EC2 instance resource.
upvoted 0 times
...
Jolanda
1 months ago
A: Set the DeletionPolicy attribute to Snapshot for the EC2 instance resource in the CloudFormation template.
upvoted 0 times
...
...
Reita
2 months ago
That's a good point, Shoshana. Both options seem valid, but we should consider which one aligns better with the company's requirements.
upvoted 0 times
...
Leota
2 months ago
Option D is the way to go! Retaining the instances and their data is crucial, especially when someone tries to delete the stack. Deleting a stack doesn't have to mean losing everything.
upvoted 0 times
Kenda
16 days ago
D) Set the DeletionPolicy attribute to Retain for the EC2 instance resource in the CloudFormation template.
upvoted 0 times
...
Tomas
18 days ago
B) Automate backups by using Amazon Data Lifecycle Manager (Amazon DLM).
upvoted 0 times
...
Laurel
1 months ago
A) Set the DeletionPolicy attribute to Snapshot for the EC2 instance resource in the CloudFormation template.
upvoted 0 times
...
Rebeca
2 months ago
D) Set the DeletionPolicy attribute to Retain for the EC2 instance resource in the CloudFormation template.
upvoted 0 times
...
...
Shoshana
2 months ago
I disagree, I believe the answer is A. Setting the DeletionPolicy to Snapshot will create a snapshot of the instance, ensuring data persistence.
upvoted 0 times
...
Reita
3 months ago
I think the answer is D, because setting the DeletionPolicy to Retain will keep the instances and data even if the stack is deleted.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77