AWS Certified Solutions Architect - Associate Practice Questions

AWS Certified Solutions Architect - Associate (SAA-C03) exam preparation

AWS Certified Solutions Architect - Associate practice questions in English: 180 questions with explanations. The mock exam has 65 questions and 130 minutes.

AWS Certified Solutions Architect - Associate free question 3 / 10 · Domain 1: Design Secure Architectures

S3 objects are encrypted with SSE-KMS using the AWS managed key (aws/s3). To let a team in another AWS account read them, the bucket policy allows reads by a role in that account, but reads from that account fail. Which fix matches the S3 and KMS pages?

  1. Allow decryption with the aws/s3 key in the other account's IAM policy, and leave the key policy as it is
  2. Re-encrypt the objects with an AWS owned KMS key, and leave the cross-account decrypt permission to AWS
  3. Re-encrypt with a customer managed KMS key, and allow the other account to decrypt in its key policy
  4. Add the other account to the key policy of aws/s3 and allow the other team's role to decrypt
Show the answer and explanation

Answer: C

Why this is correct
The S3 SSE-KMS page says that you cannot share objects encrypted with an AWS managed key across accounts, and that to share SSE-KMS data across accounts you must use a KMS customer managed key. The customer managed key's policy can allow access from other accounts. The KMS pages also say that with a customer managed key you can create and maintain key policies, IAM policies, and grants, and you can audit how the key is used in CloudTrail.

Why the other options are wrong
"Add the other account to the key policy of aws/s3 and allow the other team's role to decrypt" … You can view the key policy of an AWS managed key, but you cannot change it. The AWS service that created the key is the one that uses it for cryptographic operations.
"Re-encrypt the objects with an AWS owned KMS key, and leave the cross-account decrypt permission to AWS" … An AWS owned key is a key that an AWS service holds in its own account. You cannot view or change its policy or audit its use, and you cannot decide to share it across accounts.
"Allow decryption with the aws/s3 key in the other account's IAM policy, and leave the key policy as it is" … The S3 page says that objects encrypted with SSE-KMS under an AWS managed key cannot be shared across accounts. However the other account writes its IAM policy, it cannot read data encrypted with this key.

Three types of keys compared
Customer managed keys suit cases where you want control, AWS managed keys suit cases where you do not want to manage the key but want to see its use, and AWS owned keys suit cases where convenience is the priority. AWS managed keys have no monthly fee, while customer managed keys have a monthly fee and usage charges.

Go to the AWS Certified Solutions Architect - Associate practice app (10 free questions; purchase unlocks all questions)

See the full practice set