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

Exam AWS-SysOps All Questions

View all questions & answers for the AWS-SysOps exam
Go to Exam

Exam AWS-SysOps topic 1 question 3 discussion

Exam question from Amazon's AWS-SysOps
Question #: 3
Topic #: 1
[All AWS-SysOps Questions]

You have started a new job and are reviewing your company's infrastructure on AWS You notice one web application where they have an Elastic Load Balancer
(&B) in front of web instances in an Auto Scaling Group When you check the metrics for the ELB in CloudWatch you see four healthy instances in Availability Zone
(AZ) A and zero in AZ B There are zero unhealthy instances.
What do you need to fix to balance the instances across AZs?

  • A. Set the ELB to only be attached to another AZ
  • B. Make sure Auto Scaling is configured to launch in both AZs
  • C. Make sure your AMI is available in both AZs
  • D. Make sure the maximum size of the Auto Scaling Group is greater than 4
Show Suggested Answer Hide Answer
Suggested Answer: B 🗳️
by karmaah at Oct. 29, 2019, 1:50 a.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
RicardoD
Highly Voted 3 years, 9 months ago
B Is the answer The only way the ASG can spin up instances in another AZ is if it is allowed to do so. Option A may call you attention but it will not solve the problem as just being able to route traffic to another AZ, will not force the ASG to span EC2 in another AZ
upvoted 5 times
...
Inslution
Most Recent 4 months, 3 weeks ago
Selected Answer: B
B. Make sure Auto Scaling is configured to launch in both AZs
upvoted 1 times
...
MeisterNickey
6 months ago
Selected Answer: B
AMI is not restricted based on AZ
upvoted 1 times
...
AWSArt
3 years, 9 months ago
definitely B. I think ELB being mentioned is a red herring to throw you off. in this case having no unhealthy instances, but all stacked in one AZ, means the ASG is probably set to spin up only in that on AZ.
upvoted 1 times
...
walthor
3 years, 9 months ago
The Correct Answer is B. It's a best practice that Amazon Auto Scaling Groups (ASGs) span across multiple Availability Zones (AZs) within an AWS region to expand the availability of your auto-scaled applications.
upvoted 2 times
...
nicat
3 years, 10 months ago
Ans - B
upvoted 1 times
...
awscertified
3 years, 10 months ago
B. Make sure Auto Scaling is configured to launch in both AZs
upvoted 3 times
...
twxl
3 years, 10 months ago
Not A. 'only be attached to another AZ' would not work as 'balance' fix across AZ's reqd. Not C. AMI's are available to all AZ's in same region Not D. Will be set to at least 4. Q does not required more - just balance across AZ's B- best option
upvoted 4 times
...
karmaah
3 years, 10 months ago
Requirement is on Both Zones. Even C relates, it does not fit the exact situation. so agree the default ans.
upvoted 3 times
Ka
3 years, 10 months ago
AMI is region base, so it will be available on both AZ
upvoted 4 times
...
Suresh_bk201
3 years, 10 months ago
Only volumes are AZ dependant if I'm right
upvoted 1 times
AWS_Noob
3 years, 10 months ago
Yip, you would need to create a snapshot and migrate a EBS volume to a different AZ
upvoted 3 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