ExamTopics Logo
Mail Us[email protected]
Menu
Amazon Discussions
exam questions

Exam AWS Certified Solutions Architect - Professional SAP-C02 All Questions

View all questions & answers for the AWS Certified Solutions Architect - Professional SAP-C02 exam
Go to Exam

Exam AWS Certified Solutions Architect - Professional SAP-C02 topic 1 question 461 discussion

Exam question from Amazon's AWS Certified Solutions Architect - Professional SAP-C02
Question #: 461
Topic #: 1
[All AWS Certified Solutions Architect - Professional SAP-C02 Questions]

A company needs to migrate its website from an on-premises data center to AWS. The website consists of a load balancer, a content management system (CMS) that runs on a Linux operating system, and a MySQL database.

The CMS requires persistent NFS-compatible storage for a file system. The new solution on AWS must be able to scale from 2 Amazon EC2 instances to 30 EC2 instances in response to unpredictable traffic increases. The new solution also must require no changes to the website and must prevent data loss.

Which solution will meet these requirements?

  • A. Create an Amazon Elastic File System (Amazon EFS) file system. Deploy the CMS to AWS Elastic Beanstalk with an Application Load Balancer and an Auto Scaling group. Use .ebextensions to mount the EFS file system to the EC2 instances. Create an Amazon Aurora MySQL database that is separate from the Elastic Beanstalk environment.
  • B. Create an Amazon Elastic Block Store (Amazon EBS) Multi-Attach volume. Deploy the CMS to AWS Elastic Beanstalk with a Network Load Balancer and an Auto Scaling group. Use .ebextensions to mount the EBS volume to the EC2 instances. Create an Amazon RDS for MySQL database in the Elastic Beanstalk environment.
  • C. Create an Amazon Elastic File System (Amazon EFS) file system. Create a launch template and an Auto Scaling group to launch EC2 instances to support the CMS. Create a Network Load Balancer to distribute traffic. Create an Amazon Aurora MySQL database. Use an EC2 Auto Scaling scale-in lifecycle hook to mount the EFS file system to the EC2 instances.
  • D. Create an Amazon Elastic Block Store (Amazon EBS) Multi-Attach volume. Create a launch template and an Auto Scaling group to launch EC2 instances to support the CMS. Create an Application Load Balancer to distribute traffic. Create an Amazon ElastiCache for Redis cluster to support the MySQL database. Use EC2 user data to attach the EBS volume to the EC2 instances.
Show Suggested Answer Hide Answer
Suggested Answer: A 🗳️
by CMMC at March 19, 2024, 1:59 p.m.
Disclaimers:
  • - ExamTopics website is not related to, affiliated with, endorsed or authorized by Amazon.
  • - Trademarks, certification & product names are used for reference only and belong to Amazon.

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
Submit Cancel
AzureDP900
5 months, 3 weeks ago
Option A involves creating an Amazon Elastic File System (Amazon EFS) file system, which provides a highly available and scalable file system that can be accessed by multiple EC2 instances. Deploying the CMS to AWS Elastic Beanstalk with an Application Load Balancer and an Auto Scaling group will allow the website to scale from 2 EC2 instances to 30 EC2 instances in response to unpredictable traffic increases, meeting the first requirement. The use of EFS ensures that the file system is preserved across instance replacements or terminations during scale-in operations, preventing data loss.
upvoted 1 times
...
spencer_sharp
1 year, 1 month ago
Selected Answer: A
C is wrong because lifehook cannot mount EFS
upvoted 4 times
...
VerRi
1 year, 1 month ago
Selected Answer: A
B and D are out because NFS->EFS C scale-in lifecycle hook to mount the EFS?????
upvoted 2 times
...
yog927
1 year, 1 month ago
Selected Answer: A
A is correct
upvoted 1 times
...
pangchn
1 year, 1 month ago
Selected Answer: A
A EBS is out first. For C, the NLB is weired but couldn't say its wrong. The scale-in policy to mount EFS is wrong, since mounting task should happens during scale-out process.
upvoted 3 times
...
lasithasilva709
1 year, 1 month ago
Selected Answer: A
B and D are out because Amazon EBS is not NFS-compatible C is out because scale-in lifecycle hook triggers when the instance is about to terminate - no point of mounting the EFS file system here References: https://docs.aws.amazon.com/autoscaling/ec2/userguide/lifecycle-hooks.html
upvoted 2 times
...
ahmadraufsyahputra
1 year, 1 month ago
A because I think Network Load Balancer is not the answer for this case
upvoted 2 times
...
Dgix
1 year, 1 month ago
Selected Answer: A
B and D are out because of EBS Multi-Attach volumes not working across AZs and have a max number of 16 instances in one zone. A is the correct answer because of no code changes (yes!). C is not optimal because of the NLB which isn't optimal as it doesn't support HTTP/HTTPS as such, working on the TCP level and doesn't do path-based routing. Also, having to set up autoscaling explicitly adds overhead. Therefore, A.
upvoted 1 times
...
CMMC
1 year, 1 month ago
Selected Answer: C
Change to #C since #A could involve website changes
upvoted 1 times
...
CMMC
1 year, 1 month ago
Selected Answer: A
EFS for persistent storage, Beanstalk for deploying with ALB and auto-scaling
upvoted 1 times
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
exam
Someone Bought Contributor Access for:
SY0-701
London, 1 minute ago