Which factors affect costs in the AWS Cloud? (Select TWO.)

AWS cloud costs are fundamentally driven by a pay-as-you-go model. Two primary factors affecting costs are the consumption of compute resources and data transfer out of the AWS network. You are billed for compute services like Amazon EC2 instances or AWS Lambda functions only while they are actively running and processing workloads. Similarly, while data transfer into AWS is generally free, data transfer out from AWS services to the internet is a significant cost component, typically billed per gigabyte. These principles apply across the majority of AWS services and are core to understanding and managing cloud expenditure.

A: Unused AWS Lambda functions do not incur compute costs. Billing is based on the number of requests and the execution duration of the code.

B: The number of Amazon S3 buckets does not directly affect costs. S3 pricing is based on storage volume, requests, and data transfer, not the quantity of buckets.

C: Inbound data transfer from the internet to most AWS services is free. Therefore, it does not contribute to costs.

1. AWS Pricing Overview (Whitepaper)

Page 6

"Pay-as-you-go": This document outlines the core pricing model. It states

"Pay-as-you-go allows you to easily adapt to changing business needs without overcommitting budgets... For example

with compute services

like Amazon EC2 and AWS Lambda

you pay for the compute time that you use. With storage services

like Amazon S3 and Amazon EBS

you pay for the amount of data that you store." This supports option E.

2. Amazon EC2 Pricing Documentation: Under the "On-Demand" section

it is stated

"you pay for compute capacity by the hour or the second depending on which instances you run." This directly confirms that in-use compute resources generate costs (Option E).

3. AWS Website

"How AWS Pricing Works": In the section detailing the three fundamental drivers of cost

it explicitly lists "Compute" and "Data Transfer Out". It clarifies

"With AWS

data transfer in is free

but you will be charged for data transfer out. The price of data transfer out is tiered." This directly supports option D and refutes option C.

4. AWS Lambda Pricing Documentation: The pricing model is detailed as being based on two main components: "the number of requests for your functions and the duration... that your code executes." This confirms that unused functions (zero requests

zero duration) do not incur compute charges

refuting option A.

5. Amazon S3 Pricing Documentation: The pricing table for Amazon S3 clearly lists the cost components as Storage

Requests & data retrievals

Data transfer

and Management & analytics. The number of buckets is not listed as a pricing dimension

refuting option B.