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

Exam AWS Certified SysOps Administrator - Associate All Questions

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

Exam AWS Certified SysOps Administrator - Associate topic 1 question 238 discussion

Exam question from Amazon's AWS Certified SysOps Administrator - Associate
Question #: 238
Topic #: 1
[All AWS Certified SysOps Administrator - Associate Questions]

A SysOps administrator is testing an application that is hosted on five Amazon EC2 instances. The instances run in an Auto Scaling group behind an Application Load Balancer (ALB). High CPU utilization during load testing is causing the Auto Scaling group to scale out. The SysOps administrator must troubleshoot to find the root cause of the high CPU utilization before the Auto Scaling group scales out.

Which action should the SysOps administrator take to meet these requirements?

  • A. Enable instance scale-in protection.
  • B. Place the instance into the Standby state.
  • C. Remove the listener from the ALB.
  • D. Suspend the Launch and Terminate process types.
Show Suggested Answer Hide Answer
Suggested Answer: D 🗳️
by Deeezz at Feb. 8, 2023, 11:46 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
Vivec
Highly Voted 1 year, 7 months ago
Selected Answer: D
Placing the instance into the Standby state (answer B) would remove the instance from the ALB target group, which would prevent it from receiving traffic. The answer is D, because you need Suspend the Launch and Terminate process so that you can troubleshoot to find the root cause of the high CPU utilization before the Auto Scaling group scales out.
upvoted 6 times
vn_thanhtung
1 year, 7 months ago
I think ans is B. https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-suspend-resume-processes.html
upvoted 1 times
vn_thanhtung
1 year, 7 months ago
Answer is D, my bad
upvoted 1 times
...
...
...
Gomer
Highly Voted 1 year, 6 months ago
Selected Answer: D
Answer is D per the URL, and here is the command I derived from researching tis # Suspend ALB Launch and Terminate processes to inhibit scale-in/scale-out while debugging root cause of high CPU utilization aws autoscaling suspend-processes --auto-scaling-group-name my-asg --scaling-processes Launch Terminate https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-suspend-resume-processes.html
upvoted 5 times
...
tsangckl
Most Recent 4 months, 4 weeks ago
Selected Answer: B
B. Place the instance into the Standby state. Placing an instance into the Standby state removes it from the Auto Scaling group without terminating it, allowing the administrator to investigate the issue without affecting the group’s scaling processes1. This action helps in isolating the instance and performing a detailed investigation to identify the root cause of the high CPU utilization.
upvoted 1 times
...
TareDHakim
9 months, 4 weeks ago
Selected Answer: D
The goal is to "find the root cause of the high CPU utilization before the Auto Scaling group scales out" meaning we need to suspend the scaling events. "D"
upvoted 2 times
...
Mila28
11 months, 2 weeks ago
Selected Answer: B
troubleshooting only is posible with b
upvoted 1 times
...
Christina666
1 year, 3 months ago
Selected Answer: B
Option B (Place the instance into the Standby state) is the correct option for troubleshooting the high CPU utilization issue. By placing the instance in the Standby state, it will be removed from the load balancer's target group temporarily, and new traffic will not be routed to it. This will allow the SysOps administrator to investigate the high CPU utilization without interference from incoming requests. The other instances in the Auto Scaling group will continue to serve traffic, and the Auto Scaling group will not scale out based on the high CPU utilization of the affected instance.
upvoted 2 times
Christina666
1 year, 3 months ago
Option D (Suspend the Launch and Terminate process types) is not the correct option either. Suspending the Launch and Terminate process types will prevent the Auto Scaling group from launching new instances and terminating instances, but it won't address the root cause of the high CPU utilization on the existing instances. In conclusion, to troubleshoot the high CPU utilization issue before the Auto Scaling group scales out, the SysOps administrator should place the affected instance into the Standby state. This will allow for investigation and analysis of the high CPU utilization without affecting the traffic flow to other instances in the Auto Scaling group.
upvoted 1 times
xSohox
1 year, 2 months ago
The point here is that CPU is high during the LOAD TESTING and the app is working via ALB. So if you put instance to Standby mode it will stop receiving the traffic from ALB and you wouldn't be able to investigate the problem. So I would vote for D here.
upvoted 4 times
...
...
...
noahsark
1 year, 6 months ago
Selected Answer: D
Suspend the Launch and Terminate process types. You might want to do this, for example, so that you can investigate a configuration issue that is causing the process to fail, or to prevent Amazon EC2 Auto Scaling from marking instances unhealthy and replacing them while you are making changes to your Auto Scaling group. https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-suspend-resume-processes.html
upvoted 1 times
...
braveheart22
1 year, 7 months ago
B is the answer because- Terminate—Removes instances from the Auto Scaling group when the group scales in, or when Amazon EC2 Auto Scaling chooses to terminate instances for other reasons, such as when an instance is terminated for exceeding its maximum lifetime duration or failing a health check. https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-suspend-resume-processes.html
upvoted 1 times
...
Vivec
1 year, 7 months ago
Selected Answer: D
Ddddddd
upvoted 2 times
...
littlecleo
1 year, 8 months ago
Selected Answer: B
You can put an instance that is in the InService state into the Standby state, update or troubleshoot the instance, and then return the instance to service. Instances that are on standby are still part of the Auto Scaling group, but they do not actively handle load balancer traffic. reference: https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-enter-exit-standby.html
upvoted 3 times
...
Deeezz
1 year, 8 months ago
Selected Answer: D
you have to suspend the launch and termination of instances in order to troubleshoot the issues.
upvoted 4 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