Examkin

Question

Difficulty: MediumAWS Trusted Advisor Cost Optimization Checks

A company runs a set of non-production workloads on Amazon EC2 instances that are automatically stopped outside of business hours to reduce expenses. Despite the instances being stopped, the company's monthly bill continues to show persistent hourly charges for public IPv4 addresses. A SysOps administrator needs to identify the source of these charges and prevent them in the future.

Which AWS Trusted Advisor Cost Optimization check should the administrator review to locate these specific resources, and what is the billing reason for the ongoing charges?

  1. A
    Low Utilization Amazon EC2 Instances; AWS charges for Elastic IP addresses on stopped instances unless detailed monitoring is enabled to track and report the resource state with 1-minute granularity.
  2. Unassociated Elastic IP Addresses; AWS charges an hourly fee for Elastic IP addresses that are allocated to the account but are not associated with a running EC2 instance or an active network interface.Answer
  3. C
    Underutilized Amazon EBS Volumes; AWS charges a recurring fee for Elastic IP addresses unless they are identified using cost allocation tags that have been activated in the billing console.
  4. D
    Idle Load Balancers; AWS charges for Elastic IP addresses unless a static AWS Budget alert is configured to detect these un-forecasted charges and release the resources.

Answer

The Unassociated Elastic IP Addresses check in AWS Trusted Advisor should be reviewed. AWS charges an hourly fee for Elastic IP addresses that are allocated to the account but are not associated with a running EC2 instance or an active network interface.
The correct option correctly identifies the 'Unassociated Elastic IP Addresses' check in AWS Trusted Advisor and states the correct billing policy. When an EC2 instance is stopped, the associated Elastic IP address becomes unassociated. AWS charges an hourly fee for allocated Elastic IP addresses that are not associated with a running instance or an active network interface, aiming to optimize the usage of the public IPv4 address space.

Step-by-Step Solution

1
Analyze the scenario where stopped EC2 instances still result in hourly public IPv4 charges.
Identify that the charges are caused by Elastic IP (EIP) addresses remaining allocated to the account while the associated EC2 instances are stopped.
When an EC2 instance is stopped, any associated Elastic IP address is no longer associated with a running instance, triggering AWS's idle EIP billing policy.
2
Select the appropriate AWS Trusted Advisor Cost Optimization check designed to detect these resources.
Determine that the 'Unassociated Elastic IP Addresses' check flags allocated EIPs that are not linked to a running instance or active network interface.
This specific check is built to help administrators find and release unused Elastic IP addresses to eliminate unnecessary costs.
3
Verify the billing mechanics of Elastic IP addresses.
Confirm that AWS charges a small hourly fee for allocated but unassociated Elastic IP addresses to encourage efficient public IPv4 address utilization.
Understanding the billing rule explains why stopping the instance without releasing the EIP results in ongoing charges.

Key Concept

AWS Trusted Advisor Unassociated Elastic IP Addresses Cost Check
Estimated Time:1m 30s
Rate this question

Topics

AWS Trusted Advisor Cost Optimization Checks

More questions from this topic