Courseiva

CCNA Data Protection Questions

52 questions · Data Protection · All types, answers revealed

1
MCQhard

A large-scale data lake on S3 contains billions of small objects encrypted with AWS KMS. The security team is concerned about the high cost of KMS API calls and the potential for hitting KMS request rate limits. Which solution should they implement to reduce costs and increase performance?

A.Switch from using Customer Managed Keys (CMKs) to AWS Managed Keys (aws/s3), as managed keys have higher request limits and lower costs.
B.Enable S3 Bucket Keys for the buckets to reduce the request traffic from S3 to AWS KMS.
C.Implement an Amazon CloudFront distribution in front of the S3 bucket and enable 'Origin Request Caching' for KMS metadata.
D.Use S3 Batch Operations to re-encrypt all objects with SSE-S3 (AES-256) instead of SSE-KMS.
AnswerB

S3 Bucket Keys are designed specifically for this scenario. By decreasing the frequency of requests from S3 to KMS, they reduce the cost of encryption by up to 99% and help avoid throttling. This is highly effective for data lakes where a massive number of objects are frequently accessed or uploaded.

Why this answer

S3 Bucket Keys reduce the number of requests to AWS KMS by generating a bucket-level key that is used to derive unique data keys for objects, thereby lowering KMS API call costs and avoiding request rate limits. This is the recommended solution for large-scale data lakes with many small objects encrypted with SSE-KMS.

Exam trap

SCS-C03 often tests the misconception that switching to AWS Managed Keys reduces costs or increases limits, but the correct solution is S3 Bucket Keys to minimize KMS calls.

How to eliminate wrong answers

Option A is wrong because AWS Managed Keys (aws/s3) do not have higher request limits or lower costs compared to Customer Managed Keys; they are also not recommended for fine-grained control. Option C is wrong because CloudFront does not cache KMS metadata; it caches content, and 'Origin Request Caching' for KMS metadata is not a feature. Option D is wrong because re-encrypting with SSE-S3 removes KMS-based encryption, which may violate security requirements; it also does not reduce KMS costs but eliminates them, which is not the goal if KMS is required.

2
MCQmedium

An organization wants to rotate their KMS customer-managed keys every 90 days. What is the most effective way to implement this?

A.Modify the KMS key's rotation policy to 90 days.
B.Use an AWS Lambda function to trigger the rotation of the KMS key backing material.
C.Perform manual key rotation by creating a new key every 90 days.
D.Use AWS Secrets Manager to rotate the KMS key every 90 days.
AnswerC

Since automatic rotation is fixed at 365 days, manual rotation is the only way to satisfy a 90-day requirement. This involves creating a new KMS key, updating application references, and retaining the previous key for decryption of legacy data, ensuring compliance with internal security policies.

Why this answer

AWS KMS automatic rotation occurs every 365 days and cannot be configured for a 90-day interval. To meet a 90-day requirement, the organization must perform manual rotation. This involves creating a new key, updating the application's key ID configuration (or using an alias), and keeping the old key active only for decrypting existing data, which is a standard procedure for strict compliance.

Exam trap

Examinees often assume AWS KMS automatic key rotation can be customized to intervals shorter than one year, such as 90 days, forgetting that AWS automatically rotates keys strictly every 365 days.

3
MCQhard

A financial institution requires that all data stored in S3 buckets be immutable for five years to comply with regulatory requirements. They also need to ensure that even the root user cannot delete the data or shorten the retention period. Which configuration should the security engineer implement?

A.Enable S3 Versioning and implement an S3 Lifecycle policy to transition objects to Glacier Deep Archive with a five-year expiration rule.
B.Enable S3 Object Lock on the bucket and set a Default Retention period of five years using Governance mode.
C.Enable S3 Object Lock on the bucket and set a Default Retention period of five years using Compliance mode.
D.Apply a Bucket Policy with a Deny effect on the s3:DeleteObject action for all principals, including a condition that checks the current date.
AnswerC

Compliance mode ensures that an object cannot be deleted or its retention settings modified by any user, including the AWS account root user. This mode is specifically designed for environments where strict data integrity and non-rewriteable, non-erasable storage are required for a fixed period to satisfy legal mandates.

Why this answer

S3 Object Lock in Compliance mode provides the strongest immutability guarantee by preventing any user, including the root user, from deleting objects or reducing the retention period. This is essential for meeting strict regulatory requirements like SEC Rule 17a-4. Using Compliance mode ensures that the protection remains absolute throughout the entire specified duration.

Exam trap

Candidates often select Governance mode instead of Compliance mode, mistakenly believing Governance mode prevents root users from deleting objects or altering retention periods when it actually allows privileged users to bypass restrictions.

4
Multi-Selecthard

A security architect is designing a cross-account data sharing solution. Account A owns a KMS Customer Managed Key (CMK) that must be used by an IAM role in Account B to decrypt S3 objects. Which TWO steps are required to enable this cross-account access?

Select 2 answers
A.Modify the KMS key policy in Account A to grant the IAM role in Account B permission to use the key.
B.Attach an IAM policy to the role in Account B that allows the 'kms:Decrypt' action on the Key ARN in Account A.
C.Create a VPC Peering connection between Account A and Account B to allow KMS traffic.
D.Configure the IAM role in Account B to assume a role in Account A that has KMS permissions.
E.Enable 'KMS Multi-Region' support on the key in Account A to allow it to be seen by Account B.
AnswersA, B

The key policy is the primary gatekeeper for a KMS key. For cross-account access, the key policy in the owning account must explicitly allow the external account (or a specific principal in that account) to perform cryptographic operations. Without this explicit grant, AWS identity-based policies in Account B will have no effect.

Why this answer

Option A is correct because KMS key policies are the primary resource-based authorization mechanism for a CMK, and cross-account use of a key requires the key policy in Account A to explicitly grant the external IAM role in Account B permission to use the key (e.g., kms:Decrypt). Option B is also correct because, in addition to the key policy, the identity-based IAM policy attached to the role in Account B must allow the kms:Decrypt action on the specific key ARN in Account A; both the key policy and the caller's IAM policy must permit the action for cross-account KMS access to succeed. Option C is incorrect because KMS is a regional AWS service accessed via AWS API endpoints, not through VPC peering, so a VPC Peering connection is irrelevant to KMS authorization.

Option D is incorrect because the role in Account B does not need to assume a role in Account A; the cross-account access is granted directly through the key policy and the role's IAM policy. Option E is incorrect because KMS Multi-Region keys replicate keys across Regions for disaster recovery and latency, not to make a key visible or usable by another account.

Exam trap

SCS-C03 often tests the misconception that modifying only the key policy or only the IAM policy is sufficient for cross-account KMS access, when both are required.

5
MCQmedium

A security engineer manages a workload where an Amazon EC2 instance retrieves secrets from AWS Secrets Manager at startup. The instance's IAM role has a policy granting secretsmanager:GetSecretValue on the secret ARN, but the application still receives an AccessDeniedException. CloudTrail shows the call was made with a valid role session. Which condition should the engineer check FIRST to resolve the failure?

A.The S3 bucket policy on the bucket that stores the secret payload.
B.The KMS key policy on the customer managed key used to encrypt the secret.
C.The resource-based policy on the EC2 instance profile.
D.The VPC endpoint policy attached to the interface endpoint for Secrets Manager.
AnswerB

Secrets Manager encrypts secret values with a KMS key. Even with GetSecretValue allowed, the role must also have kms:Decrypt on the key, and the key policy must permit the role. A restrictive key policy or missing kms:Decrypt in the identity policy produces AccessDeniedException on the Secrets Manager call, making this the most likely first check.

Why this answer

Secrets Manager protects secret values with AWS KMS. Retrieving a secret requires both secretsmanager:GetSecretValue on the secret and kms:Decrypt on the encrypting key, with the key policy also allowing the principal. Because the role session was valid and CloudTrail recorded the attempt, the most probable cause is a KMS authorization gap, not a networking or S3 issue.

Exam trap

The trap here is assuming that an identity policy granting GetSecretValue is sufficient, while ignoring the separate KMS Decrypt authorization that Secrets Manager requires.

6
MCQmedium

A company is implementing a new internal web application and needs to use SSL/TLS certificates. Due to regulatory requirements, the certificates must be issued by a private Certificate Authority (CA) managed by the company, rather than a public CA. Which AWS service should be used to meet this requirement?

A.AWS Private Certificate Authority (AWS Private CA)
B.AWS Certificate Manager (ACM) with public certificates.
C.AWS CloudHSM to store and manage the private keys of the web application.
D.AWS Secrets Manager to store and rotate the SSL/TLS certificates.
AnswerA

AWS Private CA is the correct service for managing a private CA hierarchy. It allows you to issue and revoke certificates that are trusted within your organization but not by the public internet. It integrates with ACM, making it easy to deploy these private certificates to resources like Load Balancers.

Why this answer

AWS Private Certificate Authority (AWS Private CA) is a managed service that allows organizations to create and manage private CAs and issue private SSL/TLS certificates. It is designed exactly for internal use cases where certificates must be issued by a company-controlled CA rather than a public one. It integrates with ACM to issue and renew private certificates for internal resources.

Exam trap

SCS-C03 often tests the distinction between ACM public certificates and AWS Private CA — candidates may assume ACM can issue private certificates, but ACM alone only issues public certificates; private issuance requires AWS Private CA.

How to eliminate wrong answers

Option B is wrong because ACM public certificates are issued by Amazon's public CA and cannot be used for private, internally managed CA requirements. Option C is wrong because CloudHSM stores and manages cryptographic keys but does not issue or manage certificates; it is a key management appliance, not a CA. Option D is wrong because Secrets Manager stores and rotates secrets, not SSL/TLS certificates, and does not provide CA functionality.

7
MCQhard

A security engineer is designing encryption for a DynamoDB table that stores regulated data. The requirements state that the encryption key must be rotated automatically every year, that the security team must be able to audit key usage, and that the key must be usable only by the specific DynamoDB table and the security team's automation role. The team also wants to minimize the risk of accidental key deletion. Which combination of actions should the engineer take?

A.Create a customer managed key in AWS KMS, set the key policy to allow only the DynamoDB table and the automation role, enable automatic key rotation, and configure CloudTrail to log KMS events.
B.Create a customer managed key with a key policy that allows only the DynamoDB table and automation role, and rely on AWS to rotate the key automatically without configuring rotation.
C.Create a customer managed key, enable automatic rotation, and grant kms:* to the account root in the key policy to simplify administration.
D.Use the default AWS owned key for DynamoDB and enable CloudTrail management events.
AnswerA

A customer managed key supports automatic annual rotation, a restrictive key policy that limits usage to the table and the automation role, and CloudTrail logging of KMS API calls for auditing. This combination meets the rotation, least-privilege, and audit requirements. To reduce deletion risk, the team can also restrict kms:ScheduleKeyDeletion in the key policy and use a CloudWatch alarm on the ScheduleKeyDeletion event.

Why this answer

A customer managed key in AWS KMS provides the controls needed: opt-in automatic annual rotation, a key policy that restricts usage to the DynamoDB table and the automation role, and CloudTrail logging of KMS operations for auditing. Deletion risk is reduced by restricting kms:ScheduleKeyDeletion and monitoring for deletion events. AWS owned keys and root-permissive key policies do not meet the auditing and least-privilege requirements.

Exam trap

The trap here is assuming that customer managed keys rotate automatically by default, when rotation must be explicitly enabled.

8
MCQhard

A security engineer needs to identify and protect Personally Identifiable Information (PII) stored in thousands of S3 buckets across multiple AWS accounts. The solution must provide a centralized dashboard and use machine learning to classify data. Which service is best suited for this task?

A.Amazon Macie
B.Amazon GuardDuty
C.AWS Glue DataBrew
D.AWS Security Hub
AnswerA

Amazon Macie is specifically designed for S3 data discovery and classification. It uses machine learning to identify sensitive data like credit card numbers or names. Macie integrates with AWS Organizations, allowing a security hub account to manage discovery jobs across thousands of buckets and accounts from a single centralized dashboard.

Why this answer

Amazon Macie is a fully managed data security and data privacy service that uses machine learning and pattern matching to discover and protect sensitive data in Amazon S3. Macie automatically provides an inventory of S3 buckets and can be configured to scan objects for PII, providing a centralized view of data risks.

Exam trap

Candidates often suggest AWS Config or GuardDuty. While these provide security monitoring, Amazon Macie is the only service specifically built for machine-learning-driven discovery and classification of sensitive PII in S3.

9
MCQmedium

An organization is using AWS Secrets Manager to store database credentials. The security policy requires that these credentials be rotated every 30 days. The database is hosted on Amazon RDS. What is the most secure and automated way to implement this requirement?

A.Enable rotation in Secrets Manager and use a provided Lambda template to update the RDS credentials.
B.Use an Amazon EventBridge rule to trigger a manual password reset on the RDS instance every 30 days.
C.Store the credentials in an S3 bucket with versioning and use a Lifecycle policy to rotate the files.
D.Configure the RDS instance to automatically pull new credentials from Secrets Manager using IAM roles.
AnswerA

Using the built-in Secrets Manager rotation feature with a Lambda function is the AWS-recommended approach. The Lambda function handles the multi-step rotation process, which includes creating a new secret version, updating the database password, and testing the new credentials before finalizing the rotation to prevent application downtime.

Why this answer

AWS Secrets Manager natively supports automatic rotation of RDS database credentials by invoking a Lambda rotation function on a schedule (e.g., every 30 days). The provided Lambda templates for RDS (MySQL, PostgreSQL, Aurora, etc.) handle the password change on the database and update the secret value atomically, so applications always fetch valid credentials. This is the only option that delivers fully automated, secure rotation without manual intervention or insecure storage.

Exam trap

SCS-C03 often tests the misconception that RDS can natively pull credentials from Secrets Manager or that S3 lifecycle policies can rotate secrets — candidates must remember that rotation is driven by a Lambda function invoked by Secrets Manager, not by the database or storage layer.

How to eliminate wrong answers

Option B is wrong because EventBridge can trigger a Lambda, but 'manual password reset' implies human intervention and does not update the secret in Secrets Manager, breaking the automation and consistency of credentials. Option C is wrong because S3 versioning and lifecycle policies manage object versions, not credential rotation — they cannot change the RDS master password or update the secret value. Option D is wrong because RDS instances do not have a built-in mechanism to pull credentials from Secrets Manager; the application or rotation Lambda must retrieve them, and RDS has no IAM role-based credential pull feature.

10
Multi-Selectmedium

A security engineer is configuring encryption for a new Amazon RDS for PostgreSQL database. The database must be encrypted at rest using AWS KMS, and the engineer wants to ensure that the encryption key is rotated automatically every year. The engineer also needs to grant a specific IAM role permission to decrypt the database snapshots. Which two actions should the engineer take to meet these requirements? (Choose two.)

Select 2 answers
A.Attach an IAM policy to the role that allows kms:Decrypt on all KMS keys.
B.Enable automatic rotation on the AWS managed key used by RDS.
C.Create a customer managed KMS key with automatic key rotation enabled.
D.Use the default AWS managed key for RDS to encrypt the database.
E.Modify the KMS key policy to allow the specific IAM role to use the key for decryption.
AnswersC, E

To have automatic key rotation every year, you must use a customer managed KMS key and enable rotation. AWS managed keys are rotated automatically every three years, not yearly, and you cannot change their rotation schedule. A customer managed key allows you to enable annual rotation. This key can then be used to encrypt the RDS database. Thus, this action is necessary to meet the yearly rotation requirement.

Why this answer

To achieve annual automatic key rotation, a customer managed KMS key must be created with rotation enabled. AWS managed keys rotate every three years and cannot be customized. To grant a specific IAM role decryption permission for RDS snapshots, the KMS key policy must explicitly allow that role to use the key for decryption.

An IAM policy alone is insufficient without the key policy grant. Thus, the two correct actions are creating a customer managed key with rotation and modifying the key policy to allow the role.

Exam trap

The trap here is assuming that AWS managed keys can be configured for yearly rotation or that an IAM policy alone can grant decryption access without a key policy.

11
Multi-Selecthard

A security team must protect data in transit for workloads running on AWS. They need to enforce TLS for connections to an Application Load Balancer and to an Amazon RDS for PostgreSQL instance, and they want to verify that only strong cipher suites are used. Which TWO actions will BEST meet these requirements? (Choose two.)

Select 2 answers
A.Attach an AWS WAF web ACL to the Application Load Balancer and create a rule that blocks requests without the HTTPS scheme.
B.Create an RDS parameter group with rds.force_ssl set to 1 and apply it to the PostgreSQL instance.
C.Enable Amazon GuardDuty RDS Protection and remediate findings that indicate unencrypted database connections.
D.Configure the Application Load Balancer HTTPS listener to use a security policy that specifies the minimum TLS version and allowed cipher suites.
E.Enable AWS Certificate Manager to issue a private certificate and attach it to the RDS instance to force TLS.
AnswersB, D

For RDS for PostgreSQL, the rds.force_ssl parameter, when set to 1 in a parameter group and applied, requires SSL/TLS for connections to the instance and rejects non-SSL connections. This enforces encryption in transit for database clients and is the standard mechanism to require TLS on RDS PostgreSQL, meeting the in-transit protection requirement.

Why this answer

Enforcing TLS on the Application Load Balancer is done by choosing an HTTPS listener security policy with a minimum TLS version and strong cipher suites. Enforcing TLS on RDS for PostgreSQL is done by setting rds.force_ssl to 1 in the parameter group. Together these controls protect data in transit and restrict weak protocols and ciphers for both the load balancer and the database.

Exam trap

The trap here is assuming that a layer 7 service such as AWS WAF or a detection service such as GuardDuty can enforce TLS versions and cipher suites for a load balancer or database.

12
MCQeasy

A company needs to store sensitive data in Amazon S3. The security policy requires that the data be encrypted at rest using server-side encryption with AWS KMS (SSE-KMS) and that the encryption key be managed by the company. Which AWS service should the company use to create and manage the encryption key?

A.AWS Secrets Manager
B.AWS CloudHSM
C.AWS Certificate Manager (ACM)
D.AWS Key Management Service (AWS KMS)
AnswerD

AWS KMS is the service designed to create and manage encryption keys used for data at rest encryption across AWS services, including S3. With KMS, the company can create customer managed keys, control their policies, and use them for SSE-KMS. This meets the requirement for customer-managed encryption keys.

Why this answer

AWS Key Management Service (AWS KMS) is the correct service for creating and managing customer managed keys used for server-side encryption with AWS KMS (SSE-KMS) in Amazon S3. KMS allows fine-grained access control and key rotation, meeting the requirement for company-managed encryption keys.

Exam trap

The trap here is confusing services that use encryption (like Secrets Manager or ACM) with the service that actually manages encryption keys (KMS).

13
Multi-Selecthard

A database team needs to migrate an unencrypted Amazon RDS for MySQL DB instance to an encrypted instance using a specific KMS Customer Managed Key (CMK). Which THREE steps are required to complete this migration?

Select 3 answers
A.Take a snapshot of the unencrypted RDS DB instance.
B.Use the RDS console or CLI to copy the unencrypted snapshot to a new snapshot, enabling encryption and selecting the CMK.
C.Restore a new RDS DB instance from the encrypted snapshot.
D.Modify the existing RDS DB instance and enable the 'StorageEncrypted' parameter while specifying the KMS key ARN.
E.Enable the 'AutoMinorVersionUpgrade' feature to allow RDS to automatically apply encryption during the next maintenance window.
AnswersA, B, C

The migration process begins by capturing the current state of the unencrypted database. Snapshots are the standard way to move data in RDS. Since you cannot enable encryption on an existing running instance, the snapshot serves as the source data for the subsequent encryption and restoration steps.

Why this answer

Option A is correct because you must first create a snapshot of the existing unencrypted RDS for MySQL DB instance, since encryption cannot be applied in place and the snapshot serves as the source for the encrypted copy. Option B is correct because copying the unencrypted snapshot with encryption enabled (via the RDS console or CLI, e.g., aws rds copy-db-snapshot with --kms-key-id) produces a new encrypted snapshot tied to the specified KMS Customer Managed Key. Option C is correct because the final step is restoring a new DB instance from that encrypted snapshot, which yields an encrypted instance using the chosen CMK.

Option D is incorrect because the StorageEncrypted parameter cannot be enabled on an existing unencrypted RDS instance via ModifyDBInstance; encryption at rest can only be applied at creation or by restoring from an encrypted snapshot. Option E is incorrect because AutoMinorVersionUpgrade only controls automatic minor engine version patching and has nothing to do with enabling storage encryption.

Exam trap

SCS-C03 often tests the misconception that you can enable encryption on an existing RDS instance via ModifyDBInstance — candidates pick option D because it sounds like the 'least disruptive' fix, but RDS encryption is immutable after creation.

14
MCQhard

A security engineer is configuring an Amazon RDS for PostgreSQL database that must encrypt data at rest with a customer managed AWS KMS key. The engineer also needs to ensure that snapshots of the database are encrypted with the same key. Which action should the engineer take?

A.Create the RDS instance without encryption, then modify it to enable encryption using the customer managed key.
B.Enable encryption on the RDS instance using the default AWS managed key aws/rds, then create manual snapshots encrypted with a customer managed key.
C.Enable encryption on the RDS instance at creation time using the customer managed key, and enable encryption on automated backups.
D.Enable encryption on the RDS instance at creation time using the customer managed key; snapshots will automatically be encrypted with the same key.
AnswerD

When you create an RDS instance with encryption enabled using a customer managed KMS key, all automated backups, manual snapshots, read replicas, and logs are encrypted with the same key. This satisfies the requirement without additional configuration. The engineer simply needs to select the customer managed key during instance creation.

Why this answer

Encryption must be enabled at RDS instance creation. When using a customer managed KMS key, all associated snapshots and backups are automatically encrypted with that same key. There is no need to separately configure snapshot encryption, and you cannot enable encryption on an existing unencrypted instance.

Exam trap

The trap here is thinking that snapshot encryption can be configured independently or that an unencrypted RDS instance can be encrypted after creation, when in fact encryption is set at creation and inherited by snapshots.

15
MCQmedium

A company uses AWS Secrets Manager to store database credentials for an application running on Amazon EC2. The security team wants to ensure that the credentials are automatically rotated every 30 days and that the application can retrieve them securely. The application uses an IAM role attached to the EC2 instance. Which configuration should the security engineer implement?

A.Use AWS Systems Manager Parameter Store with a SecureString parameter and enable automatic rotation via a Lambda function.
B.Enable automatic rotation for the secret with a 30-day schedule, and embed the secret ARN in the application code to retrieve it using the AWS CLI.
C.Enable automatic rotation for the secret with a 30-day rotation schedule, and attach an IAM policy to the EC2 role allowing secretsmanager:GetSecretValue for the secret.
D.Store the credentials in an encrypted S3 object and configure the application to download and decrypt them using the EC2 role.
AnswerC

Enabling automatic rotation with a 30-day schedule meets the rotation requirement. Attaching an IAM policy to the EC2 role allows the application to retrieve the secret securely using the role's temporary credentials. This is the standard and secure method for accessing Secrets Manager from EC2.

Why this answer

Secrets Manager supports automatic rotation on a schedule. Attaching an IAM policy to the EC2 instance role grants the application permission to retrieve the secret using temporary credentials. This provides secure, automated rotation and access without embedding credentials in code.

Exam trap

The trap here is considering Parameter Store or S3 as equivalent, when Secrets Manager natively provides scheduled rotation and secure retrieval via IAM roles.

16
MCQeasy

Which AWS feature can be used to monitor and detect accidental exposure of S3 buckets to the public?

A.AWS Trusted Advisor
B.AWS Config
C.Amazon GuardDuty
D.AWS CloudTrail
AnswerB

AWS Config provides continuous monitoring of resource configurations. By enabling rules that check for S3 public access, you can identify and potentially auto-remediate buckets that become public. This provides a robust detective control that is essential for maintaining compliance and preventing accidental data exposure.

Why this answer

AWS Config continuously records resource configurations and evaluates them against rules, so you can deploy a managed rule like s3-bucket-public-read-prohibited or s3-bucket-public-write-prohibited to detect and alert on buckets that become publicly accessible. Config's configuration history and compliance dashboard make it the right tool for detecting accidental public exposure over time.

Exam trap

SCS-C03 often tests the confusion between CloudTrail (API activity logging) and AWS Config (configuration state and compliance) — candidates pick CloudTrail because it 'logs changes' but miss that Config evaluates the resulting configuration.

How to eliminate wrong answers

Option A is wrong because AWS Trusted Advisor provides best-practice checks (including an S3 bucket permissions check) but it is advisory, runs periodically, and is not a continuous configuration-compliance engine with remediation hooks. Option C is wrong because Amazon GuardDuty is a threat-detection service that analyzes CloudTrail, VPC Flow Logs, and DNS logs for malicious activity — it does not evaluate S3 bucket ACLs or policies for public exposure. Option D is wrong because AWS CloudTrail records API activity (who did what), not the resulting configuration state — it can show that a bucket policy was changed, but it does not evaluate whether the bucket is now public.

17
MCQmedium

An organization needs to store compliance records in Amazon S3. The records must not be deleted or overwritten by any user, including the root user, for a period of five years. Which S3 feature provides this level of data protection?

A.S3 Object Lock in Compliance mode.
B.S3 Object Lock in Governance mode.
C.S3 Bucket Policies with an explicit Deny for 's3:DeleteObject'.
D.Amazon S3 Glacier with a Vault Lock policy.
AnswerA

S3 Object Lock in Compliance mode is specifically designed for strict regulatory requirements. It ensures that an object cannot be deleted or modified by anyone during the retention period. Even the root user is blocked from bypassing the lock, making it the ideal choice for long-term immutable storage.

Why this answer

S3 Object Lock provides a 'Write Once Read Many' (WORM) model. In 'Compliance mode', an object version cannot be overwritten or deleted by any user, including the root user in your AWS account. This is the strongest form of protection for data that must be preserved for regulatory or legal reasons.

Exam trap

Candidates often confuse Governance mode with Compliance mode. Governance mode allows users with specific permissions (s3:BypassGovernanceRetention) to delete objects, whereas Compliance mode prevents even the root user from deleting objects.

18
MCQmedium

A security engineer must protect a set of credentials that an on-premises application uses to call AWS APIs. The credentials must be rotated automatically every 90 days, and the application must not store long-term access keys on disk. The on-premises server can reach AWS over the internet but cannot use an IAM role because it is not an EC2 instance. Which solution meets these requirements?

A.Create an IAM user with programmatic access and store the access key in AWS Secrets Manager with a 90-day rotation schedule.
B.Create an IAM user and enable multi-factor authentication, then store the access key and MFA seed in AWS Systems Manager Parameter Store.
C.Use AWS Security Token Service AssumeRoleWithSAML from the on-premises server by configuring it as a SAML identity provider.
D.Deploy AWS IAM Roles Anywhere and configure the on-premises server to obtain temporary credentials using an X.509 certificate issued by a trusted certificate authority.
AnswerD

IAM Roles Anywhere lets workloads outside AWS assume an IAM role by presenting an X.509 certificate from a trust anchor, returning temporary credentials with a configurable session duration. No long-term access keys are stored on the server, and the credentials expire automatically. By setting the role session duration appropriately, the application can obtain fresh credentials before expiry, meeting the rotation and no-long-term-key requirements.

Why this answer

IAM Roles Anywhere is designed for workloads outside AWS, such as on-premises servers, to assume an IAM role using X.509 certificates and receive temporary credentials. This avoids storing long-term access keys and allows credential rotation through session expiry and renewal. IAM users with stored access keys, MFA-protected users, and SAML federation do not meet the no-long-term-key and automatic-rotation requirements for this server workload.

Exam trap

The trap here is assuming that storing an IAM user access key in Secrets Manager with rotation eliminates long-term credentials, when the underlying IAM user key is still long-lived.

19
MCQmedium

A security engineer is tasked with implementing a rotation strategy for a Customer Managed Key (CMK) in AWS KMS that is used to encrypt sensitive financial records. The organization requires that the rotation happens automatically and that historical data remains accessible without manual intervention. Which approach meets these requirements while minimizing operational overhead?

A.Enable automatic key rotation for the CMK, which will generate new key material every year.
B.Create a new CMK every year and update the application configuration to use the new Key ARN.
C.Schedule a Lambda function to perform manual rotation by updating the key alias every 90 days.
D.Enable automatic rotation and configure the key to delete old key material after 365 days.
AnswerA

Automatic key rotation is a managed feature that generates new backing material for the KMS key every year. It is the most efficient method because it requires no manual updates to the key policy, aliases, or application code, while ensuring that all previously encrypted data remains fully accessible for decryption.

Why this answer

Enabling automatic key rotation for the CMK meets the requirement for automatic rotation without manual intervention. AWS KMS automatically rotates the key material every year (or a custom period if specified) while retaining old key material for decryption, ensuring historical data remains accessible. This minimizes operational overhead.

The other options require manual steps or are not supported.

Exam trap

The trap is thinking that old key material can be deleted or that manual rotation via Lambda is equivalent to automatic rotation; candidates might forget that automatic rotation retains old key material for decryption.

How to eliminate wrong answers

Option B is wrong because creating a new CMK every year and updating the application configuration requires manual intervention and does not automatically keep historical data accessible without re-encryption. Option C is wrong because scheduling a Lambda function to perform manual rotation by updating the alias is not automatic rotation of key material; it is a manual process and may not properly rotate the key material. Option D is wrong because AWS KMS does not allow deletion of old key material after 365 days; key material is retained indefinitely for decryption, and you cannot configure automatic deletion of old key material.

20
MCQeasy

A company stores sensitive data in an Amazon S3 bucket. The security team wants to ensure that all data is encrypted in transit when accessed over the internet. They also want to enforce that only encrypted connections are allowed. Which action should they take?

A.Attach a bucket policy that denies requests where aws:SecureTransport is false.
B.Enable versioning and MFA delete on the bucket.
C.Configure the bucket to use only S3 Transfer Acceleration.
D.Enable default encryption on the S3 bucket using SSE-S3.
AnswerA

A bucket policy with a condition denying requests when aws:SecureTransport is false enforces that all access to the bucket must use HTTPS (TLS). This ensures data is encrypted in transit. The condition key aws:SecureTransport is set to true for HTTPS requests and false for HTTP. By denying false, the bucket rejects any unencrypted connections. This is the standard method to enforce encryption in transit for S3.

Why this answer

To enforce encryption in transit for an S3 bucket, a bucket policy must deny requests when aws:SecureTransport is false. This condition ensures that only HTTPS (TLS) connections are allowed, rejecting any unencrypted HTTP access. Default encryption, Transfer Acceleration, and versioning do not enforce encryption in transit.

The bucket policy with the aws:SecureTransport condition is the correct and standard solution.

Exam trap

The trap here is confusing encryption at rest (default encryption) with encryption in transit (TLS enforcement).

21
MCQmedium

A company is setting up a private Public Key Infrastructure (PKI) on AWS to issue certificates for internal microservices. They need to ensure that the private keys of the CA are protected by a FIPS 140-2 Level 3 validated Hardware Security Module (HSM). Which service should they use?

A.AWS Certificate Manager (ACM) with a public certificate request.
B.AWS Private CA.
C.AWS CloudHSM with a custom-built OpenSSL CA on EC2.
D.AWS Key Management Service (KMS) with an asymmetric key pair.
AnswerB

AWS Private CA is designed specifically for creating private CA hierarchies. It uses managed HSMs that are FIPS 140-2 Level 3 validated to protect the CA's private keys. This service allows you to issue and revoke certificates for internal resources securely while offloading the HSM management to AWS.

Why this answer

AWS Private CA is a managed private certificate authority service that uses a FIPS 140-2 Level 3 validated HSM to protect the CA private key. It is designed for internal PKI use cases such as issuing certificates for microservices, and it integrates with ACM for certificate issuance. The service meets the requirement for HSM-backed key protection without the operational overhead of managing an HSM yourself.

Exam trap

SCS-C03 often tests the distinction between AWS Private CA and CloudHSM: candidates may think they need to build their own CA on CloudHSM to get FIPS 140-2 Level 3, but AWS Private CA already provides that level of protection as a managed service.

How to eliminate wrong answers

Option A is wrong because ACM public certificates are for public-facing endpoints and do not provide a private CA with HSM-backed key protection. Option C is wrong because while CloudHSM provides FIPS 140-2 Level 3 validated HSMs, building a custom CA on EC2 with OpenSSL is not a managed service and adds significant operational complexity. Option D is wrong because KMS asymmetric keys are not FIPS 140-2 Level 3 validated for CA private key storage; KMS HSMs are validated at Level 2 (though some features are Level 3, the service as a whole is not designed for private CA use).

22
MCQmedium

A company needs to encrypt data at rest for an Amazon Aurora database. They want to ensure that they maintain full control over the KMS key used for encryption. What is the correct approach?

A.Enable storage encryption during the Aurora cluster creation using a customer-managed key.
B.Enable encryption using the default AWS-managed key for Aurora.
C.Use AWS CloudHSM to manage the encryption keys for the Aurora database.
D.Enable TDE (Transparent Data Encryption) in the Aurora parameter group.
AnswerA

Selecting a customer-managed key during the creation of an Aurora cluster ensures the data is encrypted at rest and that the owner retains full control over the key's policy and lifecycle. This meets the requirement for both encryption and administrative control over the underlying cryptographic material.

Why this answer

Using a customer-managed KMS key (CMK) is the correct way to maintain full control. AWS-managed keys do not allow users to modify the key policy or rotation settings. By creating a CMK, the security team can define the key policy, enabling them to audit access, rotate the key on a specific schedule, and grant cross-account permissions as needed for their data protection requirements.

Exam trap

Candidates might mistakenly believe that AWS-managed keys provide the same level of control as customer-managed keys, or they might confuse Aurora's native KMS integration with legacy TDE options found in traditional RDS engines like SQL Server or Oracle.

23
MCQeasy

A company wants to ensure that all new Amazon EBS volumes created in their account are automatically encrypted, regardless of whether the developer specifies encryption during the volume creation process. Which AWS feature should be used?

A.Enable 'EBS encryption by default' in the EC2 dashboard for each specific AWS region.
B.Create an IAM policy that denies the 'ec2:CreateVolume' action if the 'Encrypted' parameter is false.
C.Use an AWS Config rule to automatically delete any EBS volume that is found to be unencrypted.
D.Configure an S3 Bucket Policy to only allow encrypted EBS snapshots to be uploaded.
AnswerA

EBS encryption by default is a regional setting that, once enabled, automatically encrypts all new volumes and snapshots using a specified KMS key. This is the most effective way to enforce encryption at rest for block storage without requiring developers to change their existing workflows or deployment scripts.

Why this answer

The 'EBS encryption by default' feature, when enabled in a region, automatically encrypts all new EBS volumes created in that region, regardless of whether encryption is specified during creation. This is the simplest and most direct way to enforce encryption for all new volumes.

Exam trap

The trap is confusing reactive measures (like AWS Config rules) with proactive enforcement (like encryption by default), or assuming that IAM policies can enforce encryption automatically rather than just denying unencrypted requests.

How to eliminate wrong answers

Option B is wrong because an IAM policy denying 'ec2:CreateVolume' when 'Encrypted' is false would prevent volume creation entirely, not automatically encrypt them. Option C is wrong because an AWS Config rule can detect and remediate unencrypted volumes, but it is reactive and may delete volumes, causing data loss; it does not automatically encrypt new volumes. Option D is wrong because S3 bucket policies apply to S3, not EBS volumes, and are irrelevant to EBS encryption.

24
MCQmedium

An IAM policy is attached to an application role to allow decryption of S3 objects. However, the application still receives an 'Access Denied' error. What is the most likely cause?

A.The resource in the IAM policy must be the specific ARN of the KMS key.
B.The KMS key policy does not grant the role permission to use the key.
C.The KMS key is in a different AWS region than the S3 bucket.
D.The application is missing the 'kms:GenerateDataKey' permission in its policy.
AnswerB

KMS requires both an IAM policy and a key policy to grant access. Even if the IAM policy is correct, if the key policy lacks an explicit 'Allow' for the application role, KMS will reject the request. The key policy acts as the definitive trust policy for the key.

Why this answer

Even if an IAM policy grants decryption permissions, the KMS key policy must also allow the role to use the key. KMS key policies are resource-based policies that are required for access, and if they do not explicitly grant permission, access is denied. This is the most likely cause of the 'Access Denied' error.

Exam trap

SCS-C03 often tests the misconception that IAM policies alone are sufficient for KMS access, but KMS key policies must also grant permission.

How to eliminate wrong answers

Option A is wrong because the resource in the IAM policy can be a wildcard or specific ARN; it does not have to be the specific ARN of the KMS key, though it must match the key. Option C is wrong because KMS keys are regional, but if the S3 bucket and key are in the same region, this is not an issue; cross-region access is possible with grants but not the primary cause here. Option D is wrong because 'kms:GenerateDataKey' is for encryption, not decryption; for decryption, 'kms:Decrypt' is needed.

25
MCQhard

A security engineer is designing a solution to protect sensitive data in an Amazon S3 bucket. The data must be encrypted at rest with a customer managed key, and the encryption key must be stored in a hardware security module (HSM) that the company controls. The company also requires the ability to audit all key usage. Which solution meets these requirements?

A.Use S3 client-side encryption with a key stored in AWS CloudHSM, and enable S3 server access logging.
B.Configure S3 default encryption with an AWS KMS key in a custom key store backed by AWS CloudHSM, and enable CloudTrail logging for KMS.
C.Use S3 server-side encryption with customer-provided keys (SSE-C) and store the keys in AWS Secrets Manager.
D.Use S3 default encryption with an AWS KMS customer managed key, and enable CloudTrail logging for KMS.
AnswerB

Using a KMS custom key store backed by AWS CloudHSM stores the key material in an HSM cluster that the company controls. S3 default encryption with this key encrypts data at rest. CloudTrail logs KMS key usage, providing auditing. This meets all requirements: customer-managed key, company-controlled HSM, and auditability.

Why this answer

A KMS custom key store backed by AWS CloudHSM allows the company to control the HSM that stores the key material. Using this key for S3 default encryption encrypts data at rest. CloudTrail logs KMS key usage, providing the required audit trail.

This solution meets the HSM control and auditing requirements.

Exam trap

The trap here is assuming that standard AWS KMS keys or SSE-C provide company-controlled HSM storage, when only a custom key store with CloudHSM meets that requirement.

26
MCQmedium

A security engineer is designing encryption for a new Amazon DynamoDB table that stores healthcare records. Compliance requires that the data be encrypted at rest using a key that the company can rotate on demand and whose usage can be independently audited and revoked. The team wants minimal application changes. Which approach BEST meets these requirements?

A.Attach an IAM policy that denies unencrypted PutItem calls and enable default encryption on the table.
B.Enable client-side encryption in the application using a key stored in AWS Secrets Manager before writing items to DynamoDB.
C.Configure the table to use a customer managed key in AWS KMS for encryption at rest.
D.Rely on the default DynamoDB encryption at rest, which uses an AWS owned key managed entirely by AWS.
AnswerC

DynamoDB supports specifying a customer managed key in AWS KMS as the encryption key for a table. This gives the company control over key rotation, key policy, auditing through CloudTrail, and the ability to disable or revoke the key, meeting the compliance requirements with no application code changes because DynamoDB transparently encrypts and decrypts items.

Why this answer

Using a customer managed key in AWS KMS for the DynamoDB table gives the organization control over rotation, key policy, auditing, and revocation while DynamoDB handles encryption transparently. The default AWS owned key does not provide customer-controlled rotation or independent auditing, and client-side approaches add application changes without meeting the key management requirements.

Exam trap

The trap here is assuming that DynamoDB's default encryption at rest with an AWS owned key satisfies compliance requirements for customer-controlled rotation and auditing.

27
MCQhard

An organization wants to encrypt all existing and future EBS volumes in their account using a Customer Managed Key (CMK). They have several unencrypted EBS snapshots from previous years. What is the most efficient way to ensure all new volumes created from these snapshots are encrypted with the CMK?

A.Manually copy each unencrypted snapshot and select the CMK to create an encrypted version of the snapshot before launching a volume.
B.Enable EBS encryption by default for the AWS Region and specify the Customer Managed Key as the default encryption key.
C.Create an IAM policy that denies the ec2:CreateVolume action if the 'Encrypted' parameter is set to false and attach it to all users.
D.Use AWS Config to detect unencrypted EBS volumes and trigger an AWS Systems Manager Automation document to stop and encrypt them.
AnswerA

While copying snapshots to encrypt them works, it is a manual and operationally intensive process, especially for a large number of snapshots. It does not provide a global safeguard for future volumes that might be created by users who forget to follow this manual step during their deployment process.

Why this answer

Copying an unencrypted snapshot with the CMK selected as the encryption key produces a new encrypted snapshot; any volume launched from that encrypted snapshot is automatically encrypted with the same CMK. This is the only method that retroactively encrypts existing snapshot data, since EBS encryption by default only applies to newly created volumes and does not transform existing unencrypted snapshots.

Exam trap

SCS-C03 often tests the misconception that 'EBS encryption by default' retroactively encrypts existing snapshots or volumes — it only applies to newly created resources, so pre-existing unencrypted snapshots must be copied with encryption explicitly.

How to eliminate wrong answers

Option B is wrong because enabling EBS encryption by default only affects newly created volumes and snapshots going forward — it does not encrypt pre-existing unencrypted snapshots, so volumes restored from them remain unencrypted. Option C is wrong because an IAM deny on ec2:CreateVolume with Encrypted=false blocks creation of unencrypted volumes but does not encrypt the existing snapshots or allow volumes to be created from them with encryption. Option D is wrong because AWS Config remediation via SSM Automation cannot encrypt an in-use EBS volume in place — EBS volumes cannot be encrypted after creation; you must create an encrypted copy from a snapshot.

28
MCQeasy

A security engineer needs to ensure that data stored in an Amazon DynamoDB table is encrypted at rest using a customer managed AWS KMS key. The table is already created and contains data. What should the engineer do?

A.Enable encryption on the existing table using the AWS Management Console; DynamoDB will automatically re-encrypt the data with the customer managed key.
B.Create a new DynamoDB table with encryption using the customer managed key and migrate the data.
C.Use AWS KMS to create a grant that allows DynamoDB to use the customer managed key for the existing table.
D.Modify the DynamoDB table to enable encryption with the customer managed key.
AnswerB

DynamoDB encryption at rest is always on, but to use a customer managed KMS key, you must specify it when creating the table. Existing tables cannot be modified to change the key. Therefore, the engineer must create a new table with the desired key and migrate the data from the old table.

Why this answer

DynamoDB encryption at rest is always enabled, but the key type is chosen at table creation. To use a customer managed KMS key, you must create a new table with that key and migrate the data, as existing tables cannot be modified to change their encryption key.

Exam trap

The trap here is assuming that DynamoDB tables can be modified to change encryption keys, similar to some other services, when in fact the key is immutable after creation.

29
MCQmedium

A security engineer needs to provide a third-party audit team in Account B access to S3 objects in Account A. The objects are encrypted with a Customer Managed Key (CMK) in Account A. What combination of permissions is required to allow the auditors to download and decrypt the objects?

A.Grant the Account B role S3 permissions in Account A's bucket policy and update the KMS key policy in Account A to include the Account B role ARN in the 'Principal' element with kms:Decrypt permissions.
B.Attach an IAM policy to the Account B role allowing kms:Decrypt on all resources and update the Account A S3 bucket policy to allow public access to the encrypted objects.
C.Use an S3 Access Point in Account A to grant access to Account B and enable the 'KMS PassThrough' flag on the Access Point configuration to manage decryption.
D.Create a cross-account IAM role in Account A that the auditors assume, then grant that role permissions to the S3 bucket only, as S3 handles KMS decryption automatically for assumed roles.
AnswerA

Providing cross-account access requires the resource-based policy of the KMS key to trust the external entity. By adding the Account B role to the KMS key policy and granting S3 bucket access, you satisfy both the storage and cryptographic requirements needed to retrieve and read the encrypted data securely.

Why this answer

To access cross-account encrypted objects, the KMS key policy in Account A must grant the external principal (Account B's role) permission to use the key. Simply adding the role ARN to the Principal element is not enough; the key policy must explicitly allow the 'kms:Decrypt' action for that principal. Additionally, the IAM policy in Account B must also grant the 'kms:Decrypt' permission to the role, as KMS permissions are evaluated against both the key policy and the IAM policy.

Exam trap

Candidates often forget that KMS permissions are evaluated against both the key policy and the IAM policy, or they assume that S3 bucket access automatically grants KMS decryption rights.

30
MCQmedium

A security engineer is designing a solution to protect a 2 TB Amazon RDS for PostgreSQL database that contains regulated cardholder data. The database must be encrypted at rest, and the security team must be able to audit every time the encryption key is used to decrypt the underlying storage. The team also wants the ability to immediately revoke access to the data by disabling the key if a breach is suspected. Which approach should the engineer take?

A.Enable RDS encryption at rest using the default AWS managed key aws/rds.
B.Enable RDS encryption at rest using a customer managed key, and enable RDS Performance Insights to record key usage.
C.Enable RDS encryption at rest using the default AWS managed key, then enable IAM database authentication on the DB instance.
D.Create a customer managed key in AWS KMS, enable RDS encryption at rest with that key, and monitor key usage with AWS CloudTrail and KMS key policies.
AnswerD

With a customer managed key, the security team controls the key policy, can define who may use the key for Decrypt and GenerateDataKey operations, and can audit every use through CloudTrail data events for KMS. The team can also disable the key or schedule deletion to revoke access quickly, satisfying the immediate-revocation requirement. RDS supports customer managed keys for encryption at rest on supported engines, so this design meets all stated needs.

Why this answer

A customer managed key in AWS KMS gives the security team control over the key policy, the ability to audit every cryptographic operation through CloudTrail, and the ability to disable the key to revoke access immediately. The AWS managed key aws/rds provides encryption but not customer-controlled policies, rotation, or revocation. IAM database authentication and Performance Insights address authentication and performance, not key auditing or revocation.

Exam trap

The trap here is assuming that enabling encryption at rest with the default AWS managed key provides the same audit and revocation control as a customer managed key.

31
MCQmedium

Which service should be used to protect sensitive data from being exfiltrated via API calls to unauthorized services?

A.AWS WAF
B.VPC Endpoint Policies
C.AWS CloudTrail
D.AWS Shield
AnswerB

VPC Endpoint Policies are attached to VPC endpoints and allow you to define which AWS service actions are permitted. This is a highly effective way to prevent unauthorized data exfiltration by ensuring that only approved AWS services can be accessed from within your VPC.

Why this answer

VPC endpoints, specifically Interface Endpoints (powered by AWS PrivateLink), allow you to restrict traffic to specific AWS services. By using a VPC Endpoint Policy, you can restrict API calls to only those services you explicitly authorize. This provides a robust preventative control that stops data from being sent to unauthorized accounts or services, even if an identity is compromised.

Exam trap

Test-takers frequently choose security groups or network ACLs instead of VPC endpoint policies when trying to restrict API calls to specific external services, confusing network-level packet filtering with application-level API access control.

32
Multi-Selecthard

An organization uses AWS Secrets Manager to store database credentials. Which THREE actions are recommended to secure access to these secrets?

Select 3 answers
A.Attach an IAM policy that allows 'secretsmanager:GetSecretValue' to all users.
B.Use a customer-managed KMS key to encrypt the secrets stored in Secrets Manager.
C.Configure automatic rotation for the secrets using an AWS Lambda function.
D.Store the secret value in plain text within the application's configuration file.
E.Restrict access to the secret using resource-based policies on the secret itself.
AnswersB, C, E

Using a customer-managed KMS key allows for granular control over who can decrypt the secret. It provides audit logs through CloudTrail and allows the security team to define specific key usage policies, adding an extra layer of protection beyond the standard IAM permissions provided by Secrets Manager.

Why this answer

Option B is correct because Secrets Manager encrypts secrets at rest, and using a customer-managed KMS key gives you control over the key policy, rotation, and audit trail via CloudTrail, which is a recommended security practice over relying solely on the default AWS-managed key. Option C is correct because configuring automatic rotation with an AWS Lambda rotation function limits the lifetime of credentials, so compromised or leaked secrets become useless quickly, reducing the blast radius of exposure. Option E is correct because resource-based policies attached directly to the secret allow you to grant least-privilege access to specific principals and enforce conditions (such as requiring MFA or specific VPC endpoints), which is a recommended way to tightly control who can call secretsmanager:GetSecretValue.

Option A is not recommended because granting secretsmanager:GetSecretValue to all users violates least privilege and would expose credentials broadly. Option D is not recommended because storing secret values in plain text in an application configuration file defeats the purpose of Secrets Manager and risks credential leakage through source control or filesystem access.

Exam trap

SCS-C03 often tests the misconception that broad IAM policies or plaintext storage are acceptable, but the key is to use encryption, rotation, and resource-based policies for least privilege.

33
MCQhard

A security engineer must ensure that objects in an S3 bucket are encrypted with a specific AWS KMS key and that uploads using any other encryption method are rejected. The engineer wants a policy-based control that evaluates the encryption parameters on every PutObject request. Which approach should the engineer implement?

A.Create an S3 Lifecycle rule that re-encrypts non-compliant objects after upload
B.Enable default bucket encryption with SSE-KMS and rely on it to override request headers
C.Configure S3 Object Lock in compliance mode on the bucket
D.Attach a bucket policy that denies s3:PutObject unless the request includes the required s3:x-amz-server-side-encryption and s3:x-amz-server-side-encryption-aws-kms-key-id conditions
AnswerD

A bucket policy with StringEquals conditions on the encryption headers forces every PutObject to declare the approved algorithm and KMS key ARN. Requests that omit the headers or specify a different key fail the condition and are denied, providing the policy-based enforcement the engineer needs.

Why this answer

A bucket policy that denies PutObject unless the request carries the approved server-side encryption algorithm and KMS key ID conditions enforces the requirement at request time. Default encryption, Object Lock, and lifecycle rules either allow alternative encryption headers or address entirely different concerns such as immutability and storage transitions.

Exam trap

The trap here is assuming default bucket encryption prevents uploads with other keys, when it only applies to requests that omit encryption headers.

34
Multi-Selectmedium

Which THREE of the following are valid methods for securing data in transit for AWS services?

Select 3 answers
A.Enforce HTTPS/TLS for all communication to and from AWS services.
B.Use VPC endpoints to keep traffic within the AWS private network.
C.Store data in an S3 bucket with 'Block Public Access' enabled.
D.Use AWS Site-to-Site VPN to encrypt traffic between on-premises and VPC.
E.Enable S3 Object Lock to prevent object deletion.
AnswersA, B, D

Using TLS ensures that data in transit is encrypted, preventing unauthorized actors from eavesdropping on the traffic. This is the fundamental requirement for data protection in transit and is supported by virtually all AWS services, which should be configured to reject non-encrypted connections.

Why this answer

Securing data in transit involves ensuring that communications are encrypted using secure protocols like TLS. Using VPC endpoints ensures that traffic between VPC resources and AWS services stays within the AWS network, preventing traversal over the public internet. AWS Site-to-Site VPN provides an encrypted tunnel for traffic between on-premises networks and AWS.

Options C and E relate to data at rest and data integrity/retention, not data in transit.

Exam trap

Candidates often confuse data-at-rest security controls (like S3 Block Public Access or Object Lock) with data-in-transit security controls.

35
MCQmedium

A security engineer at a healthcare company needs to protect data stored in an Amazon S3 bucket. Compliance requires that all objects be encrypted at rest using a customer managed AWS KMS key, and that the encryption key be automatically rotated every year. The engineer creates a new KMS key with automatic rotation enabled. Which of the following must the engineer do to ensure that all new objects uploaded to the bucket are encrypted with this KMS key?

A.Use AWS CloudTrail to log all S3 API calls and configure an Amazon EventBridge rule to trigger a Lambda function that encrypts objects after upload.
B.Create an S3 bucket policy that denies uploads unless the request includes the x-amz-server-side-encryption header with the KMS key ID.
C.Enable default encryption on the S3 bucket using SSE-KMS with the customer managed key.
D.Enable versioning on the bucket and configure replication to another bucket that uses the KMS key.
AnswerC

Configuring the bucket's default encryption to use SSE-KMS with the specified customer managed key ensures that all new objects are automatically encrypted with that key upon upload. This satisfies the requirement without requiring changes to client applications. The key's automatic rotation setting applies to the key material itself, not to the encryption configuration, so enabling default encryption is the correct step.

Why this answer

To ensure all new objects are encrypted with a specific AWS KMS customer managed key, the most direct and effective method is to set the S3 bucket's default encryption to use SSE-KMS with that key. This automatically applies the encryption to all objects uploaded without requiring client-side changes. The KMS key's rotation setting is separate and does not affect the default encryption configuration.

Exam trap

The trap here is assuming that enabling automatic key rotation on a KMS key also applies that key as the default encryption for S3 buckets.

36
MCQmedium

A security engineer is configuring server-side encryption for a new Amazon S3 bucket that stores regulated healthcare data. Compliance requires that the organization control the rotation of the encryption keys and be able to audit every use of those keys through AWS CloudTrail. The keys must not be shared with any other AWS account. Which encryption configuration should the engineer choose?

A.SSE-KMS with the AWS managed key aws/s3
B.SSE-KMS with a customer managed key in AWS KMS
C.Client-side encryption with an AWS KMS key before uploading objects
D.SSE-S3 with default bucket encryption enabled
AnswerB

A customer managed key in AWS KMS gives the organization full control over the key policy, rotation configuration, and enable/disable state. Every cryptographic operation is logged to CloudTrail as a KMS event, satisfying the audit requirement, and the key is scoped to the account, so no other AWS account can use it without an explicit grant.

Why this answer

The requirement for organizational control of rotation plus CloudTrail auditing of every key use maps directly to SSE-KMS backed by a customer managed key. AWS managed keys and SSE-S3 do not let the customer define rotation or key policy, and client-side encryption is an application-level approach rather than the requested bucket-level server-side configuration.

Exam trap

The trap here is assuming that any KMS-based encryption satisfies the rotation-control requirement, when only a customer managed key lets the organization define and audit rotation.

37
MCQeasy

A company stores application logs in an Amazon S3 bucket. A security policy requires that all objects in the bucket be encrypted at rest, and that the company retain control over the encryption keys and be able to audit key usage. The logs are written by an application that does not currently perform client-side encryption. Which S3 configuration should the security engineer implement to meet these requirements with the least operational overhead?

A.Configure the bucket to use server-side encryption with AWS KMS keys (SSE-KMS) using a customer managed key.
B.Enable default bucket encryption using SSE-S3 and enable S3 access logging to record key usage.
C.Configure the bucket to use server-side encryption with Amazon S3 managed keys (SSE-S3).
D.Configure the bucket to use server-side encryption with customer-provided keys (SSE-C).
AnswerA

SSE-KMS with a customer managed key encrypts every object at rest without requiring the application to change, because S3 performs the encryption on write. The customer controls the key policy, can audit every Encrypt and Decrypt operation through CloudTrail, and can rotate or disable the key. This meets the encryption, control, and audit requirements with no application changes, which is the least operational overhead.

Why this answer

SSE-KMS with a customer managed key lets S3 encrypt objects at rest automatically while the customer retains control of the key policy, rotation, and auditing. The application does not need to change because encryption happens on the service side. SSE-S3 and SSE-C either remove customer key control or require application changes and external key management, and S3 access logging does not capture key usage.

Exam trap

The trap here is confusing S3 access logging, which records object-level API calls, with KMS auditing, which records key usage.

38
MCQhard

A security engineer is building a solution to store backup files in Amazon S3 Glacier Deep Archive. Compliance requires that the data be encrypted at rest with a key the company controls, that the key be used only for this purpose, and that the encryption key material never leave AWS KMS. The backups are written by an application using the AWS SDK. Which approach BEST satisfies these requirements?

A.Use SSE-S3 with Amazon S3 managed keys and enable versioning on the bucket.
B.Use SSE-KMS with a dedicated customer managed key in AWS KMS and grant the application role kms:GenerateDataKey and kms:Decrypt.
C.Use client-side encryption with a customer provided key stored in AWS Secrets Manager, and upload the encrypted objects to S3 Glacier Deep Archive.
D.Use SSE-C with a customer provided key that the application supplies on every request, and store the key in an encrypted Amazon EBS volume.
AnswerB

SSE-KMS with a dedicated customer managed key gives the company control over the key, its policy, and its usage, and the key material remains in AWS KMS hardware security modules. Granting the application role kms:GenerateDataKey and kms:Decrypt allows S3 to encrypt and decrypt objects on the application's behalf, meeting all requirements for controlled, dedicated encryption.

Why this answer

SSE-KMS with a dedicated customer managed key keeps key material inside AWS KMS hardware security modules, gives the company control over key policy and usage, and supports a key dedicated to this backup purpose. Granting the application role kms:GenerateDataKey and kms:Decrypt enables S3 to encrypt and decrypt objects transparently, satisfying the compliance requirements.

Exam trap

The trap here is assuming that SSE-C or client-side encryption with a key in Secrets Manager keeps key material within AWS KMS, when those approaches require the customer to manage the key material outside KMS.

39
MCQmedium

A company stores configuration files containing database credentials in AWS Systems Manager Parameter Store. A security engineer must ensure the values are encrypted with a key the company controls and that any attempt to decrypt the values is recorded for audit. Which action should the engineer take?

A.Store the credentials in an S3 bucket with SSE-KMS and grant the application s3:GetObject
B.Create the parameters as SecureString using a customer managed KMS key and enable CloudTrail logging for KMS
C.Create the parameters as SecureString using the default aws/ssm KMS key and enable S3 server access logging
D.Create the parameters as String type and rely on IAM policies to restrict read access
AnswerB

SecureString parameters are encrypted with a KMS key, and specifying a customer managed key gives the company control over the key policy and rotation. Every Decrypt call made by Parameter Store is recorded as a KMS event in CloudTrail, satisfying the audit requirement for decryption attempts.

Why this answer

SecureString parameters encrypted with a customer managed KMS key meet the control requirement, and CloudTrail captures every KMS Decrypt call made when the parameter is retrieved. Plaintext String parameters, the AWS managed aws/ssm key, and relocating secrets to S3 all fail at least one of the stated control or audit requirements.

Exam trap

The trap here is assuming SecureString alone is sufficient, when the default aws/ssm key gives no customer control over the key policy or rotation.

40
Multi-Selectmedium

A company needs to protect sensitive data stored in Amazon S3 from unauthorized access. The security team wants to implement additional layers of protection beyond basic IAM policies. Which two AWS features can be used to restrict access to S3 objects based on specific conditions such as source IP address and require encryption in transit? (Choose two.)

Select 2 answers
A.Amazon S3 Inventory reports.
B.S3 Access Points with a policy that restricts access to a VPC endpoint.
C.S3 bucket policies with conditions like aws:SourceIp and aws:SecureTransport.
D.S3 Object Lock in compliance mode.
E.AWS Identity and Access Management (IAM) policies with conditions like aws:SourceIp and aws:SecureTransport.
AnswersC, E

S3 bucket policies can include condition keys such as aws:SourceIp to restrict access to specific IP ranges and aws:SecureTransport to deny requests that are not over HTTPS. These conditions provide fine-grained control and are evaluated for every request, effectively enforcing network and transport security requirements.

Why this answer

Both S3 bucket policies and IAM policies support condition keys like aws:SourceIp and aws:SecureTransport to restrict access based on network origin and require encryption in transit. These policies can be used together to enforce defense in depth. The other options do not provide the specific condition-based access restrictions required.

Exam trap

The trap here is confusing features that provide network isolation or immutability with those that enforce transport and IP conditions; only policies with condition keys directly restrict access based on those criteria.

41
Multi-Selecthard

A company wants to migrate an unencrypted Amazon Redshift cluster to an encrypted cluster using a KMS Customer Managed Key (CMK). The data must be protected during and after the migration. Which TWO steps are necessary to complete this process?

Select 2 answers
A.Create a manual snapshot of the existing unencrypted Redshift cluster.
B.Restore the snapshot into a new Redshift cluster and specify the KMS key for encryption.
C.Use the 'Modify Cluster' command to enable encryption on the live Redshift cluster.
D.Enable 'Encryption by Default' in the Redshift console to automatically migrate the data.
E.Attach a KMS key policy to the unencrypted cluster to encrypt the data in place.
AnswersA, B

The first step in migrating an unencrypted Redshift cluster is to create a snapshot. This snapshot contains all the data from the cluster and serves as the source for the new encrypted cluster. Redshift snapshots are stored in S3 and are the primary mechanism for cluster recovery and migration.

Why this answer

Option A is correct because Redshift cannot encrypt an existing unencrypted cluster in place, so the migration must begin by creating a manual snapshot of the existing unencrypted cluster, which captures the data for the subsequent encrypted restore. Option B is correct because restoring that snapshot into a new Redshift cluster is the supported mechanism to produce an encrypted cluster, and during the restore you specify the KMS Customer Managed Key (CMK) so the new cluster's data and snapshots are encrypted at rest. Option C is incorrect because the Modify Cluster command cannot enable encryption on a live unencrypted Redshift cluster; encryption status is fixed at cluster creation/restore time.

Option D is incorrect because 'Encryption by Default' only affects newly created clusters and does not migrate or encrypt an existing unencrypted cluster's data. Option E is incorrect because attaching a KMS key policy to an unencrypted cluster does not encrypt data in place; KMS key policies govern key usage, not retroactive cluster encryption.

Exam trap

SCS-C03 often tests the misconception that you can enable encryption on an existing Redshift cluster, but you must snapshot and restore to a new encrypted cluster.

42
MCQeasy

A developer must grant an application running on Amazon EC2 access to an Amazon DynamoDB table. The application needs read and write access. The security team requires that credentials never be stored on the instance and that access be scoped to the specific table. Which approach meets these requirements?

A.Attach an IAM role to the EC2 instance profile with a policy allowing the required DynamoDB actions on the table ARN.
B.Create an IAM user and embed the access key in the application configuration file encrypted with AWS KMS.
C.Use AWS Secrets Manager to store an IAM user's access key and configure automatic rotation every 30 days.
D.Store an IAM user's access key in AWS Systems Manager Parameter Store as a SecureString and retrieve it at runtime.
AnswerA

An IAM role attached through an instance profile delivers temporary credentials to the instance via the instance metadata service, so no long-term keys are stored. The role's identity policy can be scoped to the specific table ARN with only the needed DynamoDB actions, satisfying both the no-stored-credentials and least-privilege requirements.

Why this answer

Attaching an IAM role to the EC2 instance profile is the standard, secure way to grant AWS service access to EC2 workloads. The instance retrieves temporary credentials automatically, so no long-term keys are stored, and the role policy can be scoped to the exact table ARN and actions. This satisfies both the credential-handling and least-privilege requirements.

Exam trap

The trap here is treating encrypted or rotated long-term access keys as equivalent to temporary role credentials, when the requirement is that no credentials be stored on the instance.

43
MCQmedium

Refer to the exhibit. This policy is attached to a KMS Customer Managed Key (CMK) in Account 111122223333. What is the effect of the 'root' principal being granted 'kms:*' permissions in this key policy?

A.It allows the account's IAM policies to further define and grant permissions to the key.
B.It restricts all KMS operations to only be performed by the account's root user.
C.It automatically grants every IAM user in the account full access to the KMS key.
D.It makes the KMS key public and allows any AWS account to use it for encryption.
AnswerA

By granting the account's root principal access to the key, you enable IAM policies within that account to be effective. Without this delegation in the key policy, IAM policies that attempt to grant KMS permissions would be ignored, as the key policy must first permit the account to manage access.

Why this answer

In a KMS key policy, granting the root principal 'kms:*' does not automatically give all IAM users access. Instead, it enables IAM policies in the account to grant permissions to the key. This is because the key policy must delegate permissions to the account for IAM to be able to allow access.

Without this delegation, IAM policies alone cannot grant access to the key.

Exam trap

The trap is thinking that granting root 'kms:*' gives all users access or restricts to root only. The correct interpretation is that it enables IAM policies to grant access, which is a delegation mechanism.

How to eliminate wrong answers

Option B is wrong because it does not restrict operations to only the root user; the root principal is not a user but the account itself, and the permission allows IAM to grant access to others. Option C is wrong because it does not automatically grant every IAM user full access; IAM policies must still explicitly allow it. Option D is wrong because it does not make the key public; cross-account access requires explicit grants in both the key policy and the external account's IAM policy.

44
MCQhard

Refer to the exhibit. A security engineer has applied the provided bucket policy to an S3 bucket containing sensitive financial data. What is the primary security outcome of this policy configuration?

A.It forces all users to use MFA-protected API calls when accessing the bucket.
B.It ensures all data stored in the bucket is encrypted using SSE-S3.
C.It explicitly denies any request to the bucket that does not use the HTTPS protocol.
D.It prevents the bucket from being accessed from any IP address outside of the corporate VPC.
AnswerC

The policy uses a Deny statement combined with a condition that checks if SecureTransport is false (meaning HTTP was used). In AWS policy evaluation, an explicit Deny always overrides any Allow. Therefore, any request made over standard HTTP will be rejected regardless of other permissions the user might have.

Why this answer

The bucket policy in the exhibit contains a Deny statement with a condition 'aws:SecureTransport: false', which explicitly rejects any request made over plain HTTP. This is the standard AWS pattern for enforcing encryption in transit to S3. Because it is a Deny, it overrides any Allow in IAM or the bucket policy, guaranteeing that only TLS-protected requests succeed.

Exam trap

SCS-C03 often tests whether candidates can distinguish encryption in transit (SecureTransport) from encryption at rest (SSE) and from MFA enforcement — the exhibit shows only the SecureTransport condition, so any answer mentioning SSE or MFA is a distractor.

How to eliminate wrong answers

Option A is wrong because MFA enforcement requires the 'aws:MultiFactorAuthAge' or 'aws:MultiFactorAuthPresent' condition keys, which are not present in a SecureTransport policy. Option B is wrong because SSE-S3 encryption at rest is configured via bucket default encryption or object headers, not via a bucket policy condition on transport. Option D is wrong because VPC/IP restrictions require 'aws:SourceVpce' or 'aws:SourceIp' conditions, which are unrelated to the SecureTransport check.

45
Multi-Selectmedium

A company wants to centralize the management of backups for Amazon EBS volumes, RDS databases, and EFS file systems across multiple AWS regions. They need to ensure that backups are encrypted and can be restored in a different region. Which TWO steps should be taken?

Select 2 answers
A.Use AWS Backup to create a central backup plan and enable cross-region copy.
B.Configure a KMS Customer Managed Key (CMK) in the destination region for the backup vault.
C.Enable EBS Multi-Region Replication for all volumes needing backup.
D.Use S3 Cross-Region Replication (CRR) to move the backup files between regions.
E.Create a single global KMS key to be used across all AWS regions for backup encryption.
AnswersA, B

AWS Backup allows you to define backup plans that specify how often to back up resources and how long to retain them. The cross-region copy feature within the backup plan automates the transfer of backups to a different AWS region, providing a robust disaster recovery solution for the company's data.

Why this answer

Option A is correct because AWS Backup is the centralized, policy-based service that natively supports EBS volumes, RDS databases, and EFS file systems, and its backup plans can include cross-region copy rules to replicate recovery points into another region. Option B is correct because when copying backups to a destination region, the backup vault in that region must be encrypted with a KMS key that exists in that same region, so a Customer Managed Key must be created there (AWS KMS keys are regional and cannot be used outside their region). Option C is wrong because EBS Multi-Attach/Multi-Region Replication is not a backup mechanism and does not cover RDS or EFS.

Option D is wrong because S3 Cross-Region Replication only replicates S3 objects, not AWS Backup recovery points for EBS, RDS, or EFS. Option E is wrong because KMS keys are region-specific; there is no single global KMS key that can be used across all AWS regions.

Exam trap

SCS-C03 often tests the misconception that a single global KMS key or S3 CRR can be used for cross-region backups, but the key is that KMS keys are regional and AWS Backup with cross-region copy requires a destination-region CMK.

46
MCQmedium

A company needs to share an encrypted EBS volume snapshot with a partner's AWS account. The snapshot is encrypted with a customer-managed KMS key. What must the company do to enable this sharing?

A.Copy the snapshot to an unencrypted state, then share the unencrypted snapshot.
B.Share the snapshot and update the KMS key policy to permit usage by the partner.
C.Export the snapshot to an S3 bucket and provide the partner with the S3 URL.
D.Use AWS DataSync to copy the volume data directly to the partner account.
AnswerB

Sharing the snapshot makes it visible to the partner, but they cannot decrypt it without access to the key. Updating the KMS key policy allows the partner's IAM entities to use the key for cryptographic operations, which is required to successfully restore or use the shared encrypted snapshot.

Why this answer

Sharing encrypted snapshots requires sharing both the snapshot and the associated KMS key. Because the partner account cannot use the owner's KMS key directly, the key policy must be modified to allow the partner account to use the key for decryption. This ensures the partner can access the encrypted data while maintaining the security of the encryption process through AWS KMS.

Exam trap

Candidates often think sharing an encrypted EBS snapshot is sufficient on its own, forgetting that the underlying customer-managed KMS key policy must also explicitly grant decryption permissions to the partner account.

47
MCQmedium

A healthcare company stores patient records in an Amazon S3 bucket. A security engineer must ensure that all data uploaded to the bucket is encrypted with a customer managed AWS KMS key and that the key is automatically rotated every year. Which configuration should the engineer implement?

A.Enable default encryption on the S3 bucket using SSE-S3.
B.Enable default encryption on the S3 bucket using SSE-KMS with a customer managed key and enable automatic key rotation on the key.
C.Enable default encryption on the S3 bucket using SSE-KMS with the AWS managed key aws/s3.
D.Enable default encryption on the S3 bucket using SSE-C with a customer-provided key stored in AWS Secrets Manager.
AnswerB

This configuration uses a customer managed KMS key, satisfying the requirement for customer control, and enables automatic annual rotation of the key material. SSE-KMS with a customer managed key provides the necessary encryption and key management capabilities, including rotation, which aligns with the compliance need.

Why this answer

Default bucket encryption with SSE-KMS and a customer managed key ensures all new objects are encrypted with that key. Enabling automatic key rotation on the customer managed key satisfies the annual rotation requirement. The other options either use keys not customer managed or do not support the required rotation, making them unsuitable.

Exam trap

The trap here is assuming that SSE-S3 or the AWS managed key aws/s3 provides customer managed key rotation, when actually only a customer managed KMS key supports configurable automatic rotation.

48
MCQhard

A company uses AWS Secrets Manager to store database credentials. A security engineer needs to ensure that the secrets are encrypted with a customer managed AWS KMS key and that the key is automatically rotated every year. The engineer creates a new secret and specifies a customer managed key. What else must the engineer do to meet the rotation requirement?

A.Enable automatic key rotation on the customer managed KMS key with a rotation period of 365 days.
B.Configure the secret to use the AWS managed key aws/secretsmanager and enable automatic rotation on that key.
C.Create a KMS grant that allows Secrets Manager to rotate the customer managed key every 365 days.
D.Enable automatic rotation on the secret with a rotation interval of 365 days.
AnswerA

The requirement is for the KMS key to be automatically rotated every year. This is achieved by enabling automatic key rotation on the customer managed KMS key and setting the rotation period to 365 days. AWS KMS supports automatic rotation for customer managed keys with a configurable period, which meets the compliance need.

Why this answer

To meet the requirement, the engineer must enable automatic rotation on the customer managed KMS key and set the rotation period to 365 days. This rotates the key material annually. Secret rotation is separate and does not rotate the encryption key.

Exam trap

The trap here is confusing secret rotation with KMS key rotation; they are independent features, and the question specifically requires the KMS key to be rotated annually.

49
MCQmedium

A security engineer is designing a solution to protect data at rest in an Amazon S3 bucket. The bucket must use a customer managed key in AWS KMS, and the team wants every new object encrypted with that key without relying on clients to set encryption headers. What is the MOST reliable configuration?

A.Enable S3 Block Public Access and require clients to pass the x-amz-server-side-encryption header with the customer managed key ARN.
B.Create an S3 Object Lambda access point that rewrites object metadata to apply the customer managed key on read.
C.Use an AWS Lambda function triggered by S3 events to copy each new object and re-encrypt it with the customer managed key after upload.
D.Configure default bucket encryption with SSE-KMS and the customer managed key, and enforce it with a bucket policy that denies PutObject requests that do not include the correct encryption headers.
AnswerD

Default bucket encryption applies SSE-KMS with the chosen key to objects that do not specify encryption, and a bucket policy denying unencrypted or wrong-key uploads ensures clients cannot bypass the setting. Together they guarantee that every new object is encrypted with the customer managed key, regardless of client behavior.

Why this answer

Default bucket encryption with SSE-KMS and the customer managed key encrypts new objects automatically, and a bucket policy that denies PutObject requests lacking the required encryption headers prevents clients from bypassing the configuration. This combination enforces encryption at write time and guarantees that all new objects use the specified key without depending on client behavior.

Exam trap

The trap here is assuming that default bucket encryption alone prevents noncompliant uploads, when a client can still specify a different encryption method unless a policy denies it.

50
MCQhard

An application in Account A needs to decrypt S3 objects in Account B using a KMS key in Account B. What is the minimal configuration required?

A.Only update the IAM policy in Account A to allow 'kms:Decrypt'.
B.Only update the KMS key policy in Account B to allow the role from Account A.
C.Update the IAM policy in Account A and the KMS key policy in Account B.
D.Create an IAM user in Account B and provide credentials to the application.
AnswerC

This dual-policy configuration is required for cross-account access. The key policy grants permission to the external account's role, and the IAM policy ensures the role has permission to exercise that grant. This combination follows the principle of least privilege while enabling necessary cross-account functionality.

Why this answer

To enable cross-account access, the KMS key policy in Account B must explicitly permit the IAM role in Account A to perform 'kms:Decrypt'. Furthermore, the IAM role in Account A must also have an IAM policy granting it the permission to perform 'kms:Decrypt' on the specific KMS key ARN in Account B. Both policies must be present; if either is missing, the operation will fail.

Exam trap

Examinees often configure only the KMS key policy in the target account and forget that the calling principal's IAM role must also have explicit permissions to use the external KMS key.

51
MCQmedium

A security engineer needs to ensure that data stored in an Amazon S3 bucket is encrypted at rest and that the encryption keys are automatically rotated every year. The engineer decides to use server-side encryption with AWS KMS (SSE-KMS) and creates a new customer managed key. What should the engineer do next to meet the key rotation requirement?

A.Use an AWS managed key instead of a customer managed key, as AWS managed keys are automatically rotated every year.
B.Enable automatic key rotation on the customer managed key.
C.Configure a lifecycle policy on the S3 bucket to re-encrypt objects with a new key every year.
D.Manually rotate the key by creating a new customer managed key and updating the S3 bucket to use the new key.
AnswerB

AWS KMS customer managed keys support automatic key rotation, which can be enabled to rotate the backing key material annually. This meets the requirement for automatic yearly rotation. The key rotation is transparent to applications and does not change the key ARN or require re-encryption of existing data.

Why this answer

To meet the requirement for automatic yearly rotation of a customer managed KMS key, the engineer should enable automatic key rotation on that key. AWS KMS supports this feature, which rotates the key material annually without changing the key ID or requiring application changes.

Exam trap

The trap here is thinking that AWS managed keys are the only ones with automatic rotation, or that manual rotation is necessary for customer managed keys.

52
MCQmedium

A company stores sensitive documents in an Amazon S3 bucket encrypted with SSE-KMS using a customer managed key. A security engineer must ensure that only principals in a specific AWS account can decrypt the objects, and that the S3 service can still use the key on behalf of authorized requests. The bucket policy already restricts access to the account. What should the engineer do to meet the key access requirement?

A.Edit the KMS key policy to allow the S3 service principal to use the key and to allow the specific account's principals to decrypt.
B.Enable S3 Block Public Access on the bucket and rely on IAM policies attached to the account's roles.
C.Add a statement to the S3 bucket policy that allows kms:Decrypt for the specific account principals.
D.Create a new customer managed key in the same account and set the key's alias to match the bucket name.
AnswerA

For SSE-KMS, the KMS key policy must grant the S3 service principal permission to use the key for encryption and decryption so S3 can perform cryptographic operations, and it must allow the intended account principals to decrypt. The bucket policy alone cannot grant KMS permissions, so the key policy is the correct place to enforce who can use the key.

Why this answer

SSE-KMS encryption requires that the KMS key policy grant the S3 service principal permission to use the key and grant the intended account principals permission to decrypt. Bucket policies govern S3 operations and cannot grant KMS permissions, and Block Public Access or alias changes do not establish the necessary key access controls for the specified account.

Exam trap

The trap here is believing that an S3 bucket policy can grant AWS KMS permissions such as kms:Decrypt, when KMS access is governed by the key policy and IAM.

Ready to test yourself?

Try a timed practice session using only Data Protection questions.