Cost and Optimization

116 questions

All types116 Multiple choice60 Multiple select56

A SysOps Administrator is reviewing optimization opportunities for a memory-bound Lambda function that processes incoming file uploads. The administrator wants to use AWS Compute Optimizer to determine the most cost-effective memory configuration for the function without sacrificing performance. Currently, the Compute Optimizer console shows no recommendations for this Lambda function. Which of the following requirements must be met before AWS Compute Optimizer can generate memory size recommendations for the Lambda function?

The Lambda function must have been invoked at least 50 times over the past 14 days.

The Unified CloudWatch Agent must be deployed to the function's execution environment to publish memory utilization metrics.

AWS Cost Explorer must be configured with a cost anomaly detection monitor targeting the Lambda function's resource consumption.

The cost allocation tags applied to the Lambda function must be activated in the Billing Console to enable data ingestion.

Show answer & explanation

Answer: The Lambda function must have been invoked at least 50 times over the past 14 days.

Answer

The Lambda function must have been invoked at least 50 times over the past 14 days.

AWS Compute Optimizer natively analyzes the execution history of Lambda functions from CloudWatch Logs. To generate accurate memory recommendations, the service requires a minimum invocation history of at least 50 invocations over a 14-day lookback period.

Step-by-Step Solution

Identify the target resource and metric source for optimization.

The target is an AWS Lambda function, and Compute Optimizer analyzes its memory allocation natively using CloudWatch Logs metadata (such as memory used vs. memory configured in the REPORT lines).

Understanding where Compute Optimizer gathers metrics helps rule out options requiring additional agents or configuration.

Recall the minimum baseline data requirements for AWS Compute Optimizer.

Compute Optimizer needs a minimum history of 50 invocations over the last 14 days to build a baseline for recommending memory adjustments.

A minimum threshold ensures recommendations are statistically valid and accurate.

Key Concept

AWS Compute Optimizer requirements for AWS Lambda memory optimization

Question 2Question →

A SysOps Administrator is optimizing the performance and cost of a transactional database hosted on an Amazon EC2 instance. The database is currently backed by a $1\text{ TiB}$ Amazon EBS $\text{io2}$ volume configured with $10,000$ Provisioned IOPS. Over the past $14$ days, Amazon CloudWatch metrics indicate that the volume's IOPS utilization consistently peaks at $2,200$ IOPS, and throughput peaks at $150\text{ MiB/s}$ . AWS Compute Optimizer flags this volume as 'Overprovisioned'.

Which action should the administrator take to implement Compute Optimizer's recommendation and optimize costs without impacting application performance?

Modify the EBS volume in-place to change the volume type to gp3, configuring the volume with 3,000 IOPS and 150 MiB/s throughput.

Purchase an EC2 Instance Savings Plan to apply discounted rates to the EBS io2 volume while maintaining the current configuration.

Configure an AWS Budgets cost alert to trigger an automation that dynamically scales the provisioned IOPS of the io2 volume.

Activate cost allocation tags on the EBS volume in the AWS Billing Console to automatically apply the rightsizing configuration.

Show answer & explanation

Answer: Modify the EBS volume in-place to change the volume type to gp3, configuring the volume with 3,000 IOPS and 150 MiB/s throughput.

Answer

Modify the EBS volume in-place to change the volume type to gp3, configuring the volume with 3,000 IOPS and 150 MiB/s throughput.

Modifying the EBS volume in-place to change the volume type to gp3 with 3,000 IOPS and 150 MiB/s throughput is correct because it aligns with Compute Optimizer's recommendation. A gp3 volume offers 3,000 baseline IOPS and 125 MiB/s throughput for free. Increasing the throughput to 150 MiB/s satisfies the database's peak performance demands (2,200 IOPS and 150 MiB/s) while significantly reducing provisioned costs compared to the expensive io2 volume.

Step-by-Step Solution

Analyze the peak workload metrics from the past

14

days, identifying that the database requires a maximum of

2,200

IOPS and

150\text{ MiB/s}

throughput.

The requirements are within the capabilities of a gp3 volume, which offers

3,000

baseline IOPS and customizable throughput.

This establishes the minimum performance target needed to maintain database performance without overprovisioning.

Determine the optimal configuration for a gp3 volume to meet these metrics.

A gp3 volume configured with

3,000

baseline IOPS (included) and

150\text{ MiB/s}

throughput (

25\text{ MiB/s}

provisioned above the baseline

125\text{ MiB/s}

This configuration satisfies both the peak IOPS and peak throughput requirements while avoiding excess provisioned resources.

Perform an in-place EBS volume modification to change the volume type from io2 to gp3 with the determined settings.

The volume type is modified online without performance degradation or downtime.

EBS elastic volumes allow live modification of volume types, size, IOPS, and throughput.

Key Concept

AWS Compute Optimizer helps right-size EBS volumes by analyzing performance metrics and suggesting cost-effective alternatives like gp3 for overprovisioned io1/io2 volumes.

Question 3Question →

A company runs a memory-bound microservices application on Amazon EC2 instances. A SysOps Administrator notices that AWS Compute Optimizer is generating resource recommendations based only on CPU and network metrics, without factoring in memory utilization. Which of the following actions must the administrator take to ensure AWS Compute Optimizer includes memory metrics in its recommendations? (Select TWO.)

Select all that apply

Configure the unified CloudWatch agent on the EC2 instances to publish memory utilization metrics to the default CWAgent namespace.

Attach an IAM role to the EC2 instances that includes the CloudWatchAgentServerPolicy managed policy.

Enable CloudWatch detailed monitoring on the EC2 instances to decrease the metric collection interval to 1 minute.

Configure an AWS Budget with a custom optimization alert based on EC2 memory usage.

Create a VPC Gateway Endpoint for CloudWatch and associate it with the subnet route tables to allow the instances to send memory metrics.

Show answer & explanation

Answer: Configure the unified CloudWatch agent on the EC2 instances to publish memory utilization metrics to the default CWAgent namespace.; Attach an IAM role to the EC2 instances that includes the CloudWatchAgentServerPolicy managed policy.

Answer

Configure the unified CloudWatch agent on the EC2 instances to publish memory utilization metrics to the default CWAgent namespace, and attach an IAM role to the EC2 instances that includes the CloudWatchAgentServerPolicy managed policy.

To include memory metrics in AWS Compute Optimizer recommendations, the unified CloudWatch agent must be installed on the EC2 instances to capture OS-level memory utilization and publish it to the CWAgent namespace. Additionally, the EC2 instances must be authorized to write these metrics to CloudWatch, which requires attaching an IAM role with the CloudWatchAgentServerPolicy policy.

Step-by-Step Solution

Configure metric collection at the OS level.

The unified CloudWatch agent is installed and configured to send OS-level memory metrics (such as mem_used_percent) to the CWAgent namespace in CloudWatch.

By default, EC2 only reports hypervisor-level metrics like CPU and disk I/O. Memory is an OS-level metric that requires an agent to collect.

Grant the instances permission to write metrics.

An IAM role containing the CloudWatchAgentServerPolicy managed policy is attached to the EC2 instances.

The CloudWatch agent requires permissions to call the PutMetricData API to send metrics to CloudWatch.

Ensure Compute Optimizer reads the metrics.

Compute Optimizer detects the memory metrics under the CWAgent namespace and begins factoring them into recommendations.

Compute Optimizer is pre-configured to look for memory metrics specifically under the CWAgent namespace.

Key Concept

AWS Compute Optimizer memory metric requirements

Question 4Question →

A SysOps Administrator is managing resource optimization across a multi-account organization using AWS Organizations. The administrator notices that AWS Compute Optimizer is generating EC2 rightsizing recommendations based only on CPU and network metrics, failing to analyze memory utilization. Additionally, several member accounts are running gp2 EBS volumes that are overprovisioned for size just to achieve higher throughput. Which TWO actions should the SysOps Administrator take to resolve these issues?

Select all that apply

Deploy the Amazon CloudWatch agent to the EC2 instances in the member accounts to collect and report memory utilization metrics.

Enable CloudWatch detailed monitoring on the EC2 instances in the member accounts to expose memory metrics to AWS Compute Optimizer.

Modify the EBS volumes from gp2 to gp3 to allow independent scaling of throughput and size while reducing storage costs.

Configure AWS Budgets alerts to monitor EC2 memory utilization metrics and automatically downsize underutilized instances.

Purchase Compute Savings Plans to automatically implement rightsizing recommendations for the EC2 instances and EBS volumes.

Show answer & explanation

Answer: Deploy the Amazon CloudWatch agent to the EC2 instances in the member accounts to collect and report memory utilization metrics.; Modify the EBS volumes from gp2 to gp3 to allow independent scaling of throughput and size while reducing storage costs.

Answer

Deploy the Amazon CloudWatch agent to the EC2 instances in the member accounts to collect and report memory utilization metrics, and modify the EBS volumes from gp2 to gp3 to allow independent scaling of throughput and size while reducing storage costs.

Deploying the Amazon CloudWatch agent is correct because memory is an operating system-level metric that is not visible to the hypervisor. AWS Compute Optimizer requires the agent to be configured to receive these metrics. Modifying gp2 volumes to gp3 is correct because gp3 volumes decouple throughput and IOPS from storage capacity, enabling cost savings and rightsizing without overprovisioning storage size.

Step-by-Step Solution

Identify the cause of missing memory metrics in AWS Compute Optimizer.

Realize that memory metrics are OS-level metrics and require the Amazon CloudWatch agent to be installed on the EC2 instances.

AWS Compute Optimizer cannot access memory utilization metrics by default because they are not monitored at the hypervisor level.

Identify the optimization strategy for gp2 volumes overprovisioned for throughput.

Choose gp3 volumes as the target class, which allows independent provisioning of IOPS and throughput without scaling volume size.

Migrating to gp3 directly solves the issue of overprovisioning storage size solely to get higher throughput.

Key Concept

AWS Compute Optimizer rightsizing requirements and EBS volume performance optimization.

Question 5Question →

A company recently configured consolidated billing using AWS Organizations and completed the migration of several workloads. To track spending across departments, a SysOps Administrator used AWS CloudFormation to provision all resources with the `CostCenter` and `BusinessUnit` tag keys. However, when trying to create a monthly cost report in AWS Cost Explorer, the administrator finds that these tag keys are not available as filtering options. Which of the following steps must the SysOps Administrator take to resolve this issue and make these tags available in AWS Cost Explorer? (Select TWO.)

Select all that apply

Log in to the management account of the organization, open the Billing and Cost Management console, and activate the tag keys under Cost Allocation Tags.

Wait up to 24 hours after activation for the tag keys to become available as filters in AWS Cost Explorer.

Log in to each member account, open the Billing and Cost Management console, and activate the tag keys individually under Cost Allocation Tags.

Create a resource group in AWS Resource Groups using the tag keys to trigger automatic activation in AWS Cost Explorer.

Configure an AWS Config rule to automatically register and activate the tag keys in the Billing and Cost Management console.

Show answer & explanation

Answer: Log in to the management account of the organization, open the Billing and Cost Management console, and activate the tag keys under Cost Allocation Tags.; Wait up to 24 hours after activation for the tag keys to become available as filters in AWS Cost Explorer.

Answer

To resolve the issue, the administrator must log in to the management account of the organization, open the Billing and Cost Management console, and activate the tag keys under Cost Allocation Tags. Additionally, they must wait up to 24 hours for the activated tags to appear as filters in AWS Cost Explorer.

The correct answer requires performing tag activation from the management account because only the management (payer) account can enable user-defined cost allocation tags for consolidated billing. Furthermore, after activation, it takes up to 24 hours for AWS to update the metadata and populate the tag keys as filters in AWS Cost Explorer.

Step-by-Step Solution

Access the AWS Billing and Cost Management console using the organization's management account credentials.

The administrator accesses the centralized billing console where cost allocation tags are managed for the entire organization.

Only the management account can activate cost allocation tags for consolidated billing in AWS Organizations.

Navigate to the Cost Allocation Tags section, select the 'CostCenter' and 'BusinessUnit' keys under User-defined cost allocation tags, and click Activate.

The selected tags are marked for activation in the billing system.

By default, user-defined tags applied to AWS resources are inactive for cost allocation and must be explicitly activated.

Allow up to 24 hours for the activation to process and the keys to appear in Cost Explorer.

The active tags become available as filtering and grouping options in AWS Cost Explorer.

There is a standard processing delay of up to 24 hours for cost allocation tag updates to propagate to the billing reporting tools.

Key Concept

Cost Allocation Tags require central activation in the Billing and Cost Management console of the management account, followed by a propagation period before they can be used in cost reports.

Question 6Question →

A financial company is auditing its cloud expenditures across several member accounts within an AWS Organization. To track costs associated with a new data analysis project, a SysOps Administrator has written a Python script using AWS Systems Manager to apply a tag with the key `ProjectAnalysis` and value `DataLake` to all active Amazon EBS volumes. However, when the administrator logs into AWS Cost Explorer in the management account, the `ProjectAnalysis` tag is not available as a filtering option. Which action should the SysOps Administrator take to ensure the tag can be used to filter costs?

Access the AWS Billing and Cost Management console from the management account, navigate to Cost Allocation Tags, select the `ProjectAnalysis` tag, and click Activate.

Log into each member account individually, access the AWS Billing and Cost Management console, and activate the `ProjectAnalysis` tag within each account.

Create an AWS Organizations Tag Policy with compliance rules for the `ProjectAnalysis` key, which automatically registers the tag for cost allocation.

Modify the Python script to include the `aws:TagKeys` condition inside an IAM Service Control Policy (SCP) to force automatic activation of the tag.

Show answer & explanation

Answer: Access the AWS Billing and Cost Management console from the management account, navigate to Cost Allocation Tags, select the `ProjectAnalysis` tag, and click Activate.

Answer

Access the AWS Billing and Cost Management console from the management account, navigate to Cost Allocation Tags, select the `ProjectAnalysis` tag, and click Activate.

The correct answer is to access the AWS Billing and Cost Management console from the management account, navigate to Cost Allocation Tags, select the `ProjectAnalysis` tag, and click Activate. In AWS Organizations with consolidated billing, user-defined cost allocation tags must be centrally activated by the management (payer) account. Once activated, AWS begins to track costs associated with these tags, allowing them to appear as filters in AWS Cost Explorer.

Step-by-Step Solution

Access is granted to organization-wide billing configurations.

Only the management account has the authority to activate cost allocation tags for consolidated billing across all linked member accounts.

Navigate to the AWS Billing and Cost Management console, select 'Cost Allocation Tags' from the navigation pane, locate the user-defined tag key `ProjectAnalysis`, select it, and click 'Activate'.

The tag is marked as active for cost allocation.

User-defined tags applied to AWS resources do not automatically function as cost allocation tags. They must be manually activated to begin appearing in billing reports and Cost Explorer.

Wait for the active tag to propagate to Cost Explorer, which typically takes up to 24 hours.

The `ProjectAnalysis` tag becomes available as a filter and grouping category in Cost Explorer.

Activation triggers AWS to begin tracking the cost data for resources bearing that tag key from that point forward.

Key Concept

Activation of Cost Allocation Tags in AWS Organizations

Question 7Question →

A company operates a dynamic application environment that exhibits highly variable and un-forecastable daily resource utilization. A SysOps administrator must implement a cost-monitoring solution capable of identifying sudden, unexpected cost anomalies in near-real-time. When an anomaly is detected with a cost impact exceeding a specific threshold, the solution must automatically execute an AWS Systems Manager (SSM) Automation runbook to stop the offending resources. Which solution should the SysOps administrator implement to meet these requirements?

Create an AWS Budget with a daily cost limit that matches the baseline. Configure a budget action to execute the AWS Systems Manager Automation runbook when the actual cost exceeds the threshold by a static limit.

Configure an AWS Cost Anomaly Detection monitor. Create an alert subscription in AWS Cost Anomaly Detection and select the AWS Systems Manager Automation runbook as the direct notification target.

Configure an AWS Cost Anomaly Detection monitor. Create an Amazon EventBridge rule that matches AWS Cost Anomaly Detection alert events and targets the AWS Systems Manager Automation runbook.

Apply a custom billing tag to all application resources. Configure an AWS Cost Anomaly Detection monitor filtered by this tag. Create an Amazon EventBridge rule to route anomaly events to the Systems Manager Automation runbook, without activating the tag in the AWS Billing Console.

Show answer & explanation

Answer: Configure an AWS Cost Anomaly Detection monitor. Create an Amazon EventBridge rule that matches AWS Cost Anomaly Detection alert events and targets the AWS Systems Manager Automation runbook.

Answer

Configure an AWS Cost Anomaly Detection monitor. Create an Amazon EventBridge rule that matches AWS Cost Anomaly Detection alert events and targets the AWS Systems Manager Automation runbook.

The correct solution involves configuring an AWS Cost Anomaly Detection monitor to leverage machine learning, which dynamically adjusts baselines for un-forecastable daily usage patterns. Because AWS Cost Anomaly Detection automatically publishes anomaly events to Amazon EventBridge, creating an EventBridge rule that filters for these alerts and targets an AWS Systems Manager Automation runbook allows the system to execute remediations automatically when the cost anomaly exceeds the designated threshold.

Step-by-Step Solution

Choose the correct monitoring service for variable workloads.

AWS Cost Anomaly Detection is selected instead of AWS Budgets.

AWS Cost Anomaly Detection uses machine learning to dynamically model baseline spend, which is necessary to avoid false alarms on un-forecastable daily usage patterns.

Establish the resource scope and tag configuration.

Ensure any custom resource tags used for cost categorization are activated as Cost Allocation Tags in the AWS Billing Console.

Unactivated tags will not propagate to cost and billing services, rendering any tag-based cost monitors non-functional.

Configure the automated remediation pathway.

Create an Amazon EventBridge rule that triggers on AWS Cost Anomaly Detection events and sets the Systems Manager Automation runbook as the target.

AWS Cost Anomaly Detection subscriptions do not natively support executing Systems Manager Automation runbooks, necessitating EventBridge to route the anomaly alerts to the target runbook.

Key Concept

AWS Cost Anomaly Detection integration with EventBridge for automated remediation of variable workloads

Question 8Question →

A company wants to identify and receive alerts for unexpected, machine-learning-detected spikes in spending related specifically to resources tagged with `CostCenter: Marketing`. The SysOps administrator must ensure that these alerts are sent to the finance team using an existing Amazon SNS topic. Which two actions must the SysOps administrator perform to meet these requirements? (Select two.)

Select all that apply

Create a Cost Anomaly Monitor in AWS Cost Anomaly Detection, choosing the Tag monitor type and specifying the CostCenter tag key with the Marketing value.

Create an Alert Subscription in AWS Cost Anomaly Detection, link it to the tag monitor, define the alerting threshold, and select the Amazon SNS topic.

Create an AWS Budget for the CostCenter tag key, filter by the Marketing value, and configure email alerts when actual costs exceed 100% of the budget.

Create an Amazon EventBridge rule that triggers when AWS CloudTrail logs a Cost Explorer API call, and target the Amazon SNS topic.

Configure an Amazon CloudWatch Billing Alarm for the EstimatedCharges metric, add a search expression to filter by the CostCenter tag, and associate the SNS topic.

Show answer & explanation

Answer: Create a Cost Anomaly Monitor in AWS Cost Anomaly Detection, choosing the Tag monitor type and specifying the CostCenter tag key with the Marketing value.; Create an Alert Subscription in AWS Cost Anomaly Detection, link it to the tag monitor, define the alerting threshold, and select the Amazon SNS topic.

Answer

The correct actions are to create a Cost Anomaly Monitor using the Tag monitor type with the specific cost allocation tag, and to create an Alert Subscription linked to that monitor targeting the Amazon SNS topic.

To detect machine-learning-based anomalies on specific tagged resources, a Tag monitor must be created in AWS Cost Anomaly Detection. To receive alerts from this monitor, an Alert Subscription must be configured and associated with the monitor and an SNS topic.

Step-by-Step Solution

Create a cost monitor in AWS Cost Anomaly Detection.

The monitor will evaluate AWS spend data using machine learning to detect anomalies.

The Tag monitor type allows filtering anomalies specifically for resources tagged with CostCenter: Marketing.

Create an alert subscription in AWS Cost Anomaly Detection.

A subscription is established that connects the monitor to the SNS topic.

The subscription determines which anomalies trigger alerts and routes them to the correct notification target.

Key Concept

AWS Cost Anomaly Detection uses machine learning to monitor cost data, using Cost Anomaly Monitors to detect issues and Alert Subscriptions to route alerts.

Question 9Question →

A company stores daily database backup files in an Amazon S3 Standard bucket. Each backup file is approximately $10\text{ GB}$ . The backups are frequently accessed during the first $30$ days after upload. After $30$ days, access is rare, but the database team must be able to retrieve any backup within $15$ minutes if a restore is needed. The backups must be retained for a total of $90$ days before being permanently deleted.

A SysOps administrator is configuring an Amazon S3 Lifecycle policy to automate this process at the lowest cost.

Which TWO configurations should the administrator include in the S3 Lifecycle policy?

Select all that apply

Transition objects from S3 Standard to S3 Glacier Instant Retrieval after

30

days

Configure an expiration action to permanently delete the objects after

90

days

Transition objects from S3 Standard to S3 Standard-IA after

15

days

Transition objects from S3 Standard to S3 Standard-IA after

30

days, and then to S3 Glacier Flexible Retrieval after

45

days

Transition objects from S3 Standard to S3 Glacier Flexible Retrieval after

30

days, and then to S3 Standard-IA after

60

days

Show answer & explanation

Answer: Transition objects from S3 Standard to S3 Glacier Instant Retrieval after $30$ days; Configure an expiration action to permanently delete the objects after $90$ days

Answer

The correct configurations are transitioning objects from S3 Standard to S3 Glacier Instant Retrieval after

30

days, and configuring an expiration action to permanently delete the objects after

90

days.

Transitioning objects from S3 Standard to S3 Glacier Instant Retrieval after

30

days is a valid and cost-effective configuration because S3 Glacier Instant Retrieval offers millisecond retrieval times, satisfying the

15

-minute restore requirement, while significantly reducing storage costs. Additionally, configuring an expiration action to permanently delete objects after

90

days ensures compliance with the company's retention policy without retaining data longer than necessary.

Step-by-Step Solution

Analyze the access pattern and retrieval requirements to identify the appropriate storage classes.

Frequently accessed for the first

30

days (requires S3 Standard), rarely accessed thereafter but must be retrievable within

15

minutes (requires S3 Glacier Instant Retrieval, which offers millisecond access, rather than S3 Glacier Flexible Retrieval which defaults to

3-5

hours standard retrieval).

S3 Glacier Instant Retrieval provides cost-optimized archive storage while maintaining instant retrieval performance.

Evaluate S3 Lifecycle transition constraints for the proposed rules.

Transitioning from S3 Standard to S3 Glacier Instant Retrieval at day

30

is valid. Transitioning to Standard-IA at day

15

or moving from Standard-IA to another class before

30

days (e.g., day

45

after transitioning at day

30

) is invalid and violates S3 transition limits.

Ensures that all configured lifecycle rules comply with Amazon S3 validation constraints.

Verify retention and expiration rules.

Configure an expiration rule to permanently delete objects after

90

days.

This satisfies the requirement to retain files for exactly

90

days.

Key Concept

Amazon S3 Storage Class and Lifecycle Optimization

Question 10Question →

A company uploads system telemetry archives to an Amazon S3 Standard bucket. The logs must be accessed frequently with millisecond latency for the first $30$ days. After $30$ days, the logs are accessed occasionally but still require millisecond access. After $90$ days from upload, the logs are rarely accessed, but if a retrieval request is made, the logs must be available within $3$ to $5$ hours. The logs must be kept for a total of $360$ days before deletion.

Which two lifecycle transitions should a SysOps administrator configure to meet these requirements in the most cost-effective manner? (Select TWO.)

Select all that apply

Transition objects from S3 Standard to S3 Standard-Infrequent Access (S3 Standard-IA) after

30

days.

Transition objects from S3 Standard-IA to S3 Glacier Flexible Retrieval after

90

days.

Transition objects from S3 Standard to S3 Standard-Infrequent Access (S3 Standard-IA) after

15

days.

Transition objects from S3 Standard-IA to S3 Glacier Deep Archive after

90

days.

Transition objects from S3 Glacier Flexible Retrieval to S3 Standard-IA after

360

days.

Show answer & explanation

Answer: Transition objects from S3 Standard to S3 Standard-Infrequent Access (S3 Standard-IA) after $30$ days.; Transition objects from S3 Standard-IA to S3 Glacier Flexible Retrieval after $90$ days.

Answer

Transitioning objects from S3 Standard to S3 Standard-Infrequent Access (S3 Standard-IA) after

30

days, and transitioning objects from S3 Standard-IA to S3 Glacier Flexible Retrieval after

90

days.

The correct configuration transitions objects from S3 Standard to S3 Standard-Infrequent Access (S3 Standard-IA) after

30

days, and then to S3 Glacier Flexible Retrieval after

90

days. S3 Standard-IA provides millisecond latency for the occasional access required between days

30

and

90

, satisfying the

30

-day minimum limit. S3 Glacier Flexible Retrieval provides standard retrievals in

3

5

hours, meeting the recovery time requirement at a highly optimized cost.

Step-by-Step Solution

Analyze the access frequency, latency, and retrieval time requirements for each phase of the lifecycle.

Identified that the

30

-to-

90

-day phase requires millisecond access and occasional use, while the post-

90

-day phase requires retrieval within

3

5

hours.

This establishes the target S3 storage classes (S3 Standard-IA and S3 Glacier Flexible Retrieval).

Verify S3 Standard-IA transition constraints.

Transitioning to S3 Standard-IA after

30

days is valid because S3 Lifecycle rules require objects to reside in S3 Standard for at least

30

days before transitioning.

Ensures compliance with S3 minimum storage duration limits.

Verify S3 Glacier Flexible Retrieval transition constraints from S3 Standard-IA.

Transitioning to S3 Glacier Flexible Retrieval at day

90

(after

60

days in S3 Standard-IA) is valid because the objects have met the

30

-day minimum storage duration of S3 Standard-IA.

Confirms the transition sequence is valid and satisfies the

3

5

hours retrieval requirement.

Key Concept

Amazon S3 Lifecycle transition rules and minimum storage duration constraints for cost optimization.

Question 11Question →

A company manages a multi-account environment using AWS Organizations with consolidated billing enabled. The environment consists of the following workloads:

* Account A: Runs a steady-state web application on Amazon EC2 $c5.xlarge$ instances in the $us-east-1$ region.
* Account B: Runs microservices on AWS Fargate and AWS Lambda.
* Account C: Runs dynamic development environments on Amazon EC2 $m5.large$ instances in the $us-west-2$ region.

The SysOps administrator must implement a cost optimization strategy that provides the highest flexibility, covers all of these compute resources, and allows any unused discount capacity from one account to automatically apply to other accounts' eligible workloads.

Which purchasing strategy meets these requirements most cost-effectively?

Purchase regional Convertible Reserved Instances for both

c5.xlarge

us-east-1

and

m5.large

us-west-2

in the management account.

Purchase a Compute Savings Plan in the management account, ensuring that billing discount sharing is enabled for all member accounts.

Purchase an EC2 Instance Savings Plan for the

c5

and

m5

instance families in the management account.

Purchase a Compute Savings Plan in Account B and disable Billing discount sharing in the AWS Organizations console.

Show answer & explanation

Answer: Purchase a Compute Savings Plan in the management account, ensuring that billing discount sharing is enabled for all member accounts.

Answer

Purchase a Compute Savings Plan in the management account, ensuring that billing discount sharing is enabled for all member accounts.

Purchasing a Compute Savings Plan in the management account with billing discount sharing enabled is the most cost-effective and flexible solution. Compute Savings Plans automatically apply to EC2 instances regardless of instance family, size, OS, or region, and also cover AWS Fargate and AWS Lambda across all consolidated accounts in the AWS Organization.

Step-by-Step Solution

Analyze the workloads and compute types across the accounts.

Workloads include EC2 instances of different families (

c5

m5

) across multiple regions (

us-east-1

us-west-2

), Fargate container tasks, and Lambda functions.

Identifying all compute services and regions helps determine which commitment models are eligible to cover the entire fleet.

Compare the discount scope of Reserved Instances (RIs) vs. Savings Plans.

RIs only cover EC2/RDS and do not cover Fargate or Lambda. EC2 Instance Savings Plans are restricted to a single instance family in a single region. Compute Savings Plans cover EC2, Fargate, and Lambda globally across all regions.

Determining the correct discount type ensures maximum coverage and flexibility for a heterogeneous environment.

Evaluate the AWS Organizations sharing requirements.

By default, Savings Plans purchased in the management account or any member account apply to the consolidated billing family. Disabling sharing blocks this behavior.

Ensuring discount sharing is enabled allows unused commitments in one account to automatically apply to eligible workloads in other accounts.

Key Concept

Compute Savings Plans vs. EC2 Instance Savings Plans and RI coverage scope within AWS Organizations

Question 12Question →

A company manages a multi-account organization with consolidated billing. The SysOps administrator is tasked with optimizing cost for the following workloads:

Account	Workload Type	Instance/Service	Region	Pattern
Development	Dynamic	EC2 (`t3`, `m5`, `c5`) & Fargate	Multiple Regions	Frequently changes families and regions
Production	Steady-state	EC2 (`c6g.xlarge`)	`us-east-1`	Runs 24/7, expected to remain unchanged for 12 months

Which purchasing strategy provides the maximum cost savings while meeting the operational flexibility requirements of both environments?

Purchase a Compute Savings Plan to cover the development workloads, and an EC2 Instance Savings Plan for the production c6g instances in us-east-1.

Purchase an EC2 Instance Savings Plan to cover both the development and production workloads, as it offers the highest discount rate.

Purchase a Compute Savings Plan to cover all workloads across both the development and production accounts.

Purchase Standard Reserved Instances to cover the EC2 instances in both accounts, and a Compute Savings Plan for the Fargate tasks.

Show answer & explanation

Answer: Purchase a Compute Savings Plan to cover the development workloads, and an EC2 Instance Savings Plan for the production c6g instances in us-east-1.

Answer

Purchase a Compute Savings Plan to cover the development workloads, and an EC2 Instance Savings Plan for the production c6g instances in us-east-1.

The correct strategy combines a Compute Savings Plan and an EC2 Instance Savings Plan. Compute Savings Plans provide the flexibility required for the development account's dynamic workloads, as they apply across all instance families, regions, and Fargate tasks. Meanwhile, the EC2 Instance Savings Plan offers higher discount rates (similar to Standard RIs) for the steady-state production EC2 instances, which are restricted to a single instance family (c6g) in a single region (us-east-1).

Step-by-Step Solution

Analyze the development workloads requirements.

Requires coverage for AWS Fargate and EC2 instances that frequently change instance families (t3, m5, c5) and AWS Regions.

Only Compute Savings Plans offer the necessary flexibility to cover Fargate and automatically apply across different instance families and regions.

Analyze the production workloads requirements.

Requires coverage for a steady-state EC2 workload running on c6g.xlarge instances in us-east-1 for 12 months.

Since the workload is locked to one family and one region, it qualifies for an EC2 Instance Savings Plan, which offers higher savings than a Compute Savings Plan.

Combine commitments under Consolidated Billing.

A combined strategy using Compute Savings Plans for development and EC2 Instance Savings Plans for production.

This maximizes cost optimization by utilizing the highest possible discounts for the steady-state workload while maintaining flexibility where needed.

Key Concept

Selecting the optimal AWS Savings Plans based on workload flexibility and steady-state characteristics.

Estimated Time:2m 0s

Question 13Question →

A company manages a multi-account environment using AWS Organizations with consolidated billing. The workloads are distributed as follows:
- The production account runs a steady-state fleet of Amazon EC2 m6i.large instances.
- The staging account runs microservices on Amazon ECS with AWS Fargate.
- The analytics account runs batch processing using AWS Lambda functions.

The SysOps administrator must implement a cost optimization strategy that achieves the maximum possible savings across Fargate, Lambda, and EC2 workloads while allowing the EC2 instance families to be changed in the future. Which of the following actions should the SysOps administrator take to meet these requirements? (Select TWO.)

Select all that apply

Purchase a Compute Savings Plan to cover the Fargate, Lambda, and EC2 workloads.

Ensure that Savings Plan sharing is enabled in the billing preferences of the Organizations management account.

Purchase an EC2 Instance Savings Plan for the m6i instance family to cover both the EC2 instances and the Fargate tasks.

Purchase Standard Reserved Instances at the management account level to cover the Lambda functions.

Purchase Regional Reserved Instances for the Fargate tasks to cover their steady-state run time.

Show answer & explanation

Answer: Purchase a Compute Savings Plan to cover the Fargate, Lambda, and EC2 workloads.; Ensure that Savings Plan sharing is enabled in the billing preferences of the Organizations management account.

Answer

Purchase a Compute Savings Plan to cover all three workloads, and ensure that Savings Plan sharing is enabled in the Organizations billing preferences.

The correct options are to purchase a Compute Savings Plan and ensure Savings Plan sharing is enabled. Compute Savings Plans are the only commitment discount type that covers Amazon EC2, AWS Fargate, and AWS Lambda simultaneously. Enabling sharing across AWS Organizations ensures that the commitment applies to workloads running in the staging and analytics member accounts, maximizing overall savings.

Step-by-Step Solution

Analyze the workload requirements and resource types.

Identify that the workloads span EC2 instances, AWS Fargate, and AWS Lambda across different accounts in an AWS Organization.

Understanding the resource mix determines which Savings Plans or Reserved Instances are eligible.

Evaluate the eligibility of each service for commitment-based discounts.

Confirm that Compute Savings Plans cover EC2, Fargate, and Lambda, whereas EC2 Instance Savings Plans and Reserved Instances do not apply to Fargate or Lambda.

This narrows down the eligible purchase options to satisfy the requirement of covering all three workloads.

Select the correct Savings Plan type that supports flexibility.

Choose a Compute Savings Plan because it allows changing EC2 instance families in the future, unlike standard Reserved Instances or EC2 Instance Savings Plans which limit flexibility.

The scenario requires maintaining the ability to change EC2 instance families.

Configure the organization-wide sharing of the Savings Plan benefits.

Ensure that Savings Plan sharing is active in the management account's preferences so that the staging and analytics accounts can utilize the purchased commitment.

By default, consolidated billing shares benefits, but if sharing is disabled, the member accounts running Fargate and Lambda will not receive the discounted rates.

Key Concept

Compute Savings Plans offer the greatest flexibility and automatically apply across EC2, Fargate, and Lambda, even across multiple accounts in an AWS Organization when sharing is enabled.

Question 14Question →

A company runs a data processing application in a single AWS account. The application uses a fleet of Amazon EC2 instances in an Auto Scaling group that dynamically scales between $5$ and $20$ `c6i.large` instances depending on queue depth. The application also invokes AWS Lambda functions to perform lightweight pre-processing on incoming data. Additionally, a single `db.r6g.large` Amazon RDS for PostgreSQL database runs continuously to store processing metadata. The company wants to minimize costs over the next year with a commitment plan, while retaining the flexibility to change EC2 instance families in the future if needed. Which combination of purchases should the SysOps administrator make to achieve the maximum cost optimization? (Select TWO.)

Select all that apply

Purchase a Compute Savings Plan to cover the baseline usage of the EC2 instances and the AWS Lambda functions.

Purchase a

1

-year Reserved Instance for the db.r6g.large RDS database instance.

Purchase an EC2 Instance Savings Plan to cover the EC2 instances and the AWS Lambda functions.

Purchase a Compute Savings Plan that covers the EC2 instances and the db.r6g.large RDS database instance.

Purchase a single

1

-year Regional Reserved Instance to cover both the EC2 Auto Scaling group and the RDS database instance.

Show answer & explanation

Answer: Purchase a Compute Savings Plan to cover the baseline usage of the EC2 instances and the AWS Lambda functions.; Purchase a $1$ -year Reserved Instance for the db.r6g.large RDS database instance.

Answer

Purchase a Compute Savings Plan to cover the baseline usage of the EC2 instances and the AWS Lambda functions, and purchase a 1-year Reserved Instance for the db.r6g.large RDS database instance.

The correct strategy involves purchasing a Compute Savings Plan to cover the EC2 instances and AWS Lambda functions, as Compute Savings Plans apply to both services and allow changes to instance families. In addition, a 1-year Reserved Instance must be purchased for the db.r6g.large RDS database because Savings Plans do not support Amazon RDS.

Step-by-Step Solution

Analyze the workload components and find which components can be grouped under a single Savings Plan type.

The EC2 instances and AWS Lambda functions can both be covered under a Compute Savings Plan, which applies to EC2, Fargate, and Lambda usage.

This matches the requirement to cover the dynamically scaling EC2 fleet and the Lambda functions with flexibility to change instance families.

Determine the optimization option for the Amazon RDS database instance.

Amazon RDS does not support Savings Plans, so the only commitment-based discount mechanism available for RDS is a database Reserved Instance.

This requires purchasing an RDS Reserved Instance for the db.r6g.large database tier to reduce database costs.

Key Concept

Compute Savings Plans provide flexible coverage across EC2 and Lambda, whereas Amazon RDS requires database Reserved Instances as it is not covered by Savings Plans.

Question 15Question →

A SysOps team is tasked with reducing compute costs for a new serverless application. The application's architecture includes a mix of Amazon EC2 instances, AWS Fargate containers, and AWS Lambda functions across several AWS Regions. Which commitment-based pricing model should the SysOps team select to optimize costs with the greatest flexibility?

Convertible Reserved Instances

EC2 Instance Savings Plans

Compute Savings Plans

Standard Reserved Instances

Show answer & explanation

Answer: Compute Savings Plans

Answer

Compute Savings Plans are the most appropriate choice because they automatically apply to compute usage across Amazon EC2, AWS Fargate, and AWS Lambda, providing the maximum flexibility for the multi-service architecture.

Compute Savings Plans offer the greatest flexibility and automatically apply to compute usage across Amazon EC2, AWS Fargate, and AWS Lambda, regardless of region, instance family, size, operating system, or tenancy.

Step-by-Step Solution

Identify the compute resources in scope for cost optimization.

The architecture consists of EC2 instances, AWS Fargate containers, and AWS Lambda functions.

Understanding the resource types is necessary to select a pricing model that covers all of them.

Evaluate the coverage of available savings models.

Compute Savings Plans apply to EC2, Fargate, and Lambda. EC2 Instance Savings Plans and Reserved Instances (Convertible or Standard) apply only to EC2 instances.

Comparing coverage boundaries helps identify which models can apply to all the targeted resources.

Determine the pricing model that offers the greatest flexibility for this multi-service deployment.

Compute Savings Plans are selected.

They automatically apply to all three compute services across different regions and configurations without manual modification.

Key Concept

Compute Savings Plans automatically apply to EC2, Fargate, and Lambda usage across any AWS Region and configuration, making them the most flexible commitment option.

Question 16Question →

A company currently hosts a batch processing workload on a fleet of Amazon EC2 $c6g.2xlarge$ instances in the $us-east-1$ region. Over the next year, the company plans to modernize the workload by migrating $50\%$ of the processing to containerized tasks running on AWS Fargate in the same region, and upgrading the remaining EC2 instances to the newer $c7g.2xlarge$ instance family. Which commitment-based discount option should a SysOps administrator recommend to optimize costs for both the remaining EC2 instances and the Fargate tasks without requiring manual exchanges or interventions?

EC2 Instance Savings Plans for the c6g instance family

Compute Savings Plans

Convertible Reserved Instances for the c6g instance family

Standard Reserved Instances for the c6g instance family

Show answer & explanation

Answer: Compute Savings Plans

Answer

Compute Savings Plans

Compute Savings Plans provide the greatest flexibility. They automatically apply to compute usage across Amazon EC2, AWS Fargate, and AWS Lambda regardless of instance family, size, Availability Zone, region, OS, or tenancy. This ensures that as the company transitions their batch workloads from c6g instances on EC2 to a combination of c7g instances on EC2 and containerized tasks on Fargate, the discounts continue to apply seamlessly without requiring manual exchanges or interventions.

Step-by-Step Solution

Analyze the target architecture changes over the one-year period.

The target state consists of a mix of EC2 c7g instances and AWS Fargate tasks, representing changes in both EC2 instance families and compute service types.

Understanding the final architecture helps match the target workloads to the correct discount capabilities.

Evaluate the scope and flexibility of the available discount options.

Compute Savings Plans apply to EC2 instances (any family, size, or region) and AWS Fargate automatically. EC2 Instance Savings Plans and Reserved Instances do not support Fargate or require manual adjustments for instance family changes.

Selecting the most flexible discount model is necessary to avoid lock-in when workloads and instance types evolve.

Identify the option that applies automatically to both compute types without operational overhead.

Compute Savings Plans are selected as they require no manual modifications, exchanges, or interventions to cover both the upgraded EC2 instances and the Fargate tasks.

This meets the business goal of optimizing costs with minimal administrative overhead.

Key Concept

Compute Savings Plans offer the highest level of flexibility among AWS commitment-based discounts, automatically applying to EC2 instance usage across families, sizes, and regions, as well as AWS Fargate and AWS Lambda.

Estimated Time:1m 30s

Question 17Question →

A company manages a multi-account AWS environment using AWS Organizations with consolidated billing enabled. The environment has two member accounts:

* Account A (Production) runs a steady-state web application on Amazon EC2 $m6i.large$ instances and Amazon ECS on AWS Fargate.
* Account B (Testing) runs temporary development workloads using various EC2 instance families (such as $t3$ and $c6g$ ) that are frequently stopped, started, or terminated.

The company wants to optimize its compute costs. The SysOps administrator must ensure that the commitment discount is applied to both the Fargate tasks and the EC2 instances in Account A as a priority, and is not consumed by the fluctuating workloads in Account B.

Which strategy should the SysOps administrator implement to meet these requirements?

Purchase a Compute Savings Plan in Account A.

Purchase an EC2 Instance Savings Plan in Account A.

Purchase a Compute Savings Plan in the Management Account.

Purchase Regional Reserved Instances for

m6i

instances in Account A.

Show answer & explanation

Answer: Purchase a Compute Savings Plan in Account A.

Answer

Purchase a Compute Savings Plan in Account A.

Purchasing a Compute Savings Plan in Account A is correct because Compute Savings Plans apply to compute usage across Amazon EC2, AWS Fargate, and AWS Lambda. Additionally, in an AWS Organization with consolidated billing, Savings Plan discounts are applied first to the account that purchased the plan. Buying the plan in Account A ensures that Account A's steady-state EC2 and Fargate workloads receive the discount first, with any excess sharing to other accounts like Account B.

Step-by-Step Solution

Identify the compute resource types in the production workload.

Account A runs both Amazon EC2 instances and AWS Fargate tasks.

EC2 Instance Savings Plans and Reserved Instances only apply to EC2 instances, meaning Fargate usage would remain at On-Demand rates. A Compute Savings Plan is required to cover both services under a single commitment.

Determine the optimal account for purchasing the Savings Plan.

Purchase the Compute Savings Plan directly within Account A.

AWS billing consolidated billing logic applies Savings Plan discounts to the purchasing account's usage first. If purchased in the Management Account, the discount is distributed across the organization based on where it yields the highest discount, which could cause Account B's testing workloads to consume the commitment first.

Confirm sharing behavior for any excess commitment.

Enable Savings Plan sharing across the Organization.

Buying the plan in Account A prioritizes Account A's usage. If Account A has periods of lower usage, any excess commitment can still automatically scale to cover Account B's eligible workloads, maximizing the investment.

Key Concept

AWS Savings Plans application order and scope in consolidated billing environments.

Question 18Question →

A SysOps Administrator applied the tag key `CostCenter` to several Amazon EC2 instances and Amazon S3 buckets to track project expenditures. However, when analyzing costs, the `CostCenter` tag key does not appear as a filtering option in AWS Cost Explorer. Which two actions must the SysOps Administrator perform to resolve this issue and track costs by this tag? (Select TWO.)

Select all that apply

Activate the CostCenter tag in the AWS Billing and Cost Management console.

Wait up to 24 hours after activation for the tag to appear in AWS Cost Explorer.

Create an IAM policy that grants the Billing service permission to read resource tags on the S3 buckets and EC2 instances.

Enable resource tag synchronization in the AWS Cost Explorer settings.

Re-apply the tags in the AWS Organizations management account, because tags applied in member accounts cannot be used for cost allocation.

Show answer & explanation

Answer: Activate the CostCenter tag in the AWS Billing and Cost Management console.; Wait up to 24 hours after activation for the tag to appear in AWS Cost Explorer.

Answer

Activate the CostCenter tag in the AWS Billing and Cost Management console, and wait up to 24 hours for the activated tag to appear in AWS Cost Explorer.

To track costs using a custom resource tag, the tag must be activated in the AWS Billing and Cost Management console. Once activated, it can take up to 24 hours for AWS to update the billing dashboard and display the tag as a filter in AWS Cost Explorer.

Step-by-Step Solution

Access the AWS Billing and Cost Management console using credentials from the management account or an account with billing administration permissions.

The SysOps Administrator is authenticated and can manage billing-wide configurations.

Cost allocation tags must be activated from the Billing console, and in a multi-account environment, this is managed at the Organization payer/management account level.

Navigate to the Cost Allocation Tags page, search for the CostCenter tag key under the User-defined cost allocation tags tab, select it, and click Activate.

The tag is marked as active for cost allocation.

AWS does not automatically use standard resource tags for cost tracking; they must be explicitly activated to begin generating cost allocation metadata.

Allow up to 24 hours for the AWS Billing system to process the new tags and update Cost Explorer.

The CostCenter tag is indexed and becomes available as a filter and grouping dimension in AWS Cost Explorer.

AWS updates cost allocation tag data on a daily cycle, requiring a propagation period before the tags can be queried.

Key Concept

Standard resource tags applied to AWS resources do not automatically function as cost allocation tags. They must be explicitly activated within the AWS Billing and Cost Management console (typically in the management/payer account of an AWS Organization) before they can be used to filter or group costs in AWS Cost Explorer. Once activated, it can take up to 24 hours for the tags to be reflected in Cost Explorer.

Estimated Time:1m 30s

Question 19Question →

A SysOps Administrator is managing a multi-account AWS environment under a single organization in AWS Organizations. To track department spending, the administrator deploys a Tag Policy at the organization root that enforces the CostCenter tag on all Amazon EC2 instances. Several member accounts deploy new EC2 instances successfully, compliant with the policy. However, when the administrator runs a query in AWS Cost Explorer in the management account grouping by the CostCenter tag, all costs are grouped under the 'No tag key' category. What should the administrator do to ensure the cost data is properly categorized by the tag key in Cost Explorer?

Log in to the Billing and Cost Management console of the management account, navigate to Cost Allocation Tags, select the CostCenter tag, and click Activate.

Log in to the Billing and Cost Management console of each member account, navigate to Cost Allocation Tags, select the CostCenter tag, and click Activate.

Modify the Tag Policy at the organization root to set the 'CostAllocation' parameter to true for the CostCenter tag key.

Create an AWS Budgets rule in the management account targeting the CostCenter tag to trigger Cost Explorer to index the resource tags.

Show answer & explanation

Answer: Log in to the Billing and Cost Management console of the management account, navigate to Cost Allocation Tags, select the CostCenter tag, and click Activate.

Answer

Log in to the Billing and Cost Management console of the management account, navigate to Cost Allocation Tags, select the CostCenter tag, and click Activate.

The correct answer is to activate the tag in the management account. In AWS Organizations, billing features are consolidated under the management account. Newly created tags do not automatically become active for cost allocation; they must be manually activated in the Billing and Cost Management console of the management account before they appear in Cost Explorer.

Step-by-Step Solution

Identify where cost allocation tags are managed in a multi-account organization.

In AWS Organizations consolidated billing, cost allocation tags must be managed centrally from the management (payer) account.

Member accounts lack the permission to activate cost allocation tags for the organization's billing data.

Locate the Cost Allocation Tags settings within the management account.

Navigate to the Billing and Cost Management console and select the Cost Allocation Tags page.

This is the console section where resource tags are registered for billing reports.

Activate the user-defined tag key.

Select the CostCenter tag from the list of user-defined tags and click Activate.

Activating the tag key registers it so AWS can begin generating billing datasets grouped by that tag.

Key Concept

Activation of user-defined cost allocation tags in the management account of AWS Organizations is required before those tags are recognized and grouped in Cost Explorer.

Estimated Time:3m 0s

Question 20Question →

A company manages a multi-account environment using AWS Organizations with consolidated billing enabled. The SysOps administrator is reviewing the compute usage for the following workloads:

* Production Account: A steady-state fleet of $10$ Amazon EC2 $m7g.xlarge$ instances running $24/7$ in the $us-west-2$ Region, and a dynamically scaling web application running on Amazon ECS with AWS Fargate.
* Development Account: A fleet of $t4g.medium$ EC2 instances that are shut down outside of business hours, and various AWS Lambda functions for sporadic testing.

The company wants to implement a cost optimization strategy that maximizes savings while providing flexibility for the scaling and serverless workloads.

Which combination of actions should the SysOps administrator take to meet these requirements? (Select TWO.)

Select all that apply

Purchase an EC2 Instance Savings Plan in the production account for the

m7g

instance family in

us-west-2

Purchase a Compute Savings Plan in the management account to cover the AWS Fargate tasks and AWS Lambda functions.

Purchase an EC2 Instance Savings Plan to cover both the

m7g

instances and the AWS Fargate tasks in the production account.

Purchase regional Standard Reserved Instances to cover the AWS Lambda functions in the development account.

Purchase an EC2 Instance Savings Plan in the development account for the

t4g

instance family to cover the development instances.

Show answer & explanation

Answer: Purchase an EC2 Instance Savings Plan in the production account for the $m7g$ instance family in $us-west-2$ .; Purchase a Compute Savings Plan in the management account to cover the AWS Fargate tasks and AWS Lambda functions.

Answer

Purchasing an EC2 Instance Savings Plan for the m7g family in us-west-2 to cover the steady-state EC2 instances, and purchasing a Compute Savings Plan to cover the Fargate and Lambda workloads.

Purchasing an EC2 Instance Savings Plan for the m7g family in us-west-2 provides the highest discount for the 24/7 production EC2 instances. Purchasing a Compute Savings Plan provides the required flexibility to automatically cover the scaling AWS Fargate tasks and the sporadic AWS Lambda functions across any region or instance type.

Step-by-Step Solution

Analyze the workload characteristics of each account.

The production EC2 instances are steady-state (running 24/7) in a single region (us-west-2) and family (m7g). The Fargate and Lambda workloads are dynamic and serverless.

Identifying workload patterns helps determine whether to prioritize commitment flexibility or maximum savings rate.

Evaluate the scope of EC2 Instance Savings Plans.

EC2 Instance Savings Plans offer up to 72% discount and apply to a specific instance family in a specific region, which fits the production EC2 fleet perfectly but cannot cover Fargate or Lambda.

This matches the steady-state production EC2 fleet requirements for maximum cost optimization.

Evaluate the scope of Compute Savings Plans.

Compute Savings Plans offer up to 66% discount and apply automatically to EC2, Fargate, and Lambda across any region or instance family.

This covers the dynamically scaling Fargate tasks and sporadic Lambda functions where operational flexibility is required.

Key Concept

Selecting the optimal combination of Compute Savings Plans and EC2 Instance Savings Plans based on workload stability and compute service types.

Page 1 / 6Next

Cost and Optimization

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept