Ends in
00
days
00
hrs
00
mins
00
secs
SHOP NOW

💝 Valentine's Sale! Get 30% OFF Any Reviewer. Use coupon code: PASSION-4-CLOUD & 10% OFF Store Credits/Gift Cards

Find answers, ask questions, and connect with our
community around the world.

Home Forums AWS AWS Certified Solutions Architect Associate Understanding ASG behaviour Reply To: Understanding ASG behaviour

  • JR-TutorialsDojo

    Administrator
    January 27, 2025 at 10:46 am

    Hello anthill5060,

    Thank you for sharing your insights on this topic.

    Your point about right-sizing and dynamic scaling is crucial, and it’s always good practice to consider these aspects when designing architectures. However, given the constraints of this specific question, we had to choose the best option among the provided ones.

    Since the scenario requires a minimum of two instances to manage regular traffic, you should always have at least two instances running, even in the event of an Availability Zone (AZ) outage. To achieve this, you can use an Auto Scaling Group to automatically distribute your compute resources across two or more Availability Zones. It is important to set the minimum capacity to four instances and the maximum capacity to six instances. With two instances running in each AZ, your system will maintain at least two operational instances, even if one AZ fails.

    The given question focuses on the need for zero downtime and strong fault tolerance. In this context, configuring the Auto Scaling Group (ASG) with at least four instances across two Availability Zones (AZs) more effectively meets these requirements than other options.

    Let us know if you need further assistance.

    Regards,
    JR @ Tutorials Dojo

Skip to content