SOA-C02 Reviews Questions

"Network Load Balancer is optimized to handle sudden and volatile traffic patterns while using a single static IP address per Availability Zone." https://aws.amazon.com/elasticloadbalancing/network-load-balancer/

For an application that must scale to millions of requests per second and requires a single static IP address for each Availability Zone, a Network Load Balancer (NLB) is the most suitable option. NLBs are designed for high-performance, low-latency networking, and they support static IP addresses for each Availability Zone, making it ideal for volatile traffic patterns. Option D is the correct choice. AWS provides extensive documentation on NLB capabilities and configurations that suit these requirements AWS Network Load Balancer.

https://aws.amazon.com/premiumsupport/knowledge-center/ec2-ri-consolidated-billing/

RI discounts apply to accounts in an organization's consolidated billing family depending upon whether RI sharing is turned on or off for the accounts. By default, RI sharing for all accounts in an organization is turned on. The management account of an organization can change this setting by turning off RI sharing for an account. The capacity reservation for an RI applies only to the account the RI was purchased on, no matter whether RI sharing is turned on or off.

To enforce compliance with tagging policies in real-time:

AWS Config Setup: Implement an AWS Config rule to continuously monitor and evaluate EC2 instances for compliance with the tagging requirements. The required-tags managed rule can be configured to specifically check for the presence of a 'department' tag.

Automatic Remediation: Configure AWS Config to automatically execute the AWS-TerminateEC2Instance Systems Manager Automation document as a remediation action. This runbook will terminate any EC2 instance identified as noncompliant due to missing required tags.

Operational Efficiency: This setup allows for the enforcement of company tagging policies automatically and in near real-time, reducing the manual overhead of monitoring and ensuring compliance.

This method provides an efficient and effective solution to ensure that all EC2 instances meet the company's tagging requirements and that any noncompliant instances are dealt with promptly.

Weighted routing in Route 53 allows you to direct a percentage of traffic to different resources by configuring specific weights. For this requirement, you can:

Weighted Routing Policy: This is the most suitable approach for gradually rolling out a new version by controlling traffic distribution.

Weight Configuration: Setting a weight of 80 for the original resource and 20 for the new resource ensures that 80% of the traffic continues to go to the existing version, while 20% is directed to the new version.

Other routing policies, such as failover and multivalue answer, are not intended for traffic distribution based on percentage; they serve different use cases.