nerdexam
Amazon

SAP-C02 · Question #523

A company has millions of objects in an Amazon S3 bucket. The objects are in the S3 Standard storage class. All the S3 objects are accessed frequently. The number of users and applications that…

The correct answer is B. Create a new S3 bucket that has server-side encryption with Amazon S3 managed keys (SSE-. This option switches the encryption method from using AWS Key Management Service (AWS KMS) to using server-side encryption with S3 managed keys (SSE-S3). This change can significantly reduce costs because AWS KMS charges per API request, while SSE-S3 does not have additional…

Submitted by omar99· Mar 6, 2026Continuous Improvement for Existing Solutions

Question

A company has millions of objects in an Amazon S3 bucket. The objects are in the S3 Standard storage class. All the S3 objects are accessed frequently. The number of users and applications that access the objects is increasing rapidly. The objects are encrypted with server-side encryption with AWS KMS keys (SSE-KMS). A solutions architect reviews the company's monthly AWS invoice and notices that AWS KMS costs are increasing because of the high number of requests from Amazon S3. The solutions architect needs to optimize costs with minimal changes to the application. Which solution will meet these requirements with the LEAST operational overhead?

Options

  • ACreate a new S3 bucket that has server-side encryption with customer-provided keys (SSE-C) as
  • BCreate a new S3 bucket that has server-side encryption with Amazon S3 managed keys (SSE-
  • CUse AWS CloudHSM to store the encryption keys. Create a new S3 bucket. Use S3 Batch
  • DUse the S3 Intelligent-Tiering storage class for the S3 bucket. Create an S3 Intelligent-Tiering

How the community answered

(58 responses)
  • A
    14% (8)
  • B
    74% (43)
  • C
    9% (5)
  • D
    3% (2)

Explanation

This option switches the encryption method from using AWS Key Management Service (AWS KMS) to using server-side encryption with S3 managed keys (SSE-S3). This change can significantly reduce costs because AWS KMS charges per API request, while SSE-S3 does not have additional charges per API request beyond the S3 usage.

Community Discussion

No community discussion yet for this question.

Full SAP-C02 Practice