Which factors affect costs in the AWS Cloud?

AWS costs are affected by compute resources while they are running or otherwise allocated according to their pricing model. AWS documentation explains that compute is commonly billed by the second or hour from launch until the resource is stopped or terminated. Outbound data transfer can also generate charges, depending on the service, destination, Region, monthly allowance, and transfer pattern. Therefore, options D and E are correct. Data transfer into AWS is generally provided without charge, although customers should always verify the pricing rules for the specific service and architecture. Merely creating an unused Lambda function normally does not produce execution charges because Lambda is primarily billed for requests and processing duration. Charges could arise from related resources or optional features, but the function count alone is not the general cost factor described. Similarly, Amazon S3 pricing is based on components such as stored data, requests, retrievals, management features, and data transfer rather than simply the number of configured general-purpose buckets. The foundational pricing principle is pay for resources consumed, including active compute and chargeable outbound transfer, subject to service-specific pricing and free allowances.