Amazon AWS Certified Data Engineer - Associate DEA-C01 Practice Test 109
Question 1080
An S3 access point policy allows a principal but a KMS key policy still denies decrypting the objects. Which underlying AWS service principle BEST explains the recommended approach?
- The governing design principle is that every AWS managed service uses the same consistency, retry and query-processing semantics.
- The governing design principle is that access point policy and underlying bucket and encryption grants combine to determine practical object access.
- The governing design principle is that an S3 bucket prefix guarantees exactly-once multi-service transactions without an output commit.
- The governing design principle is that a successful IAM login means every analytics dataset is readable and correctly transformed.
Explanation
Correct Answer
B:This is the relevant technical mechanism for S3 Access Points prefix policy and cross-account authorization. Verify with access Point ARN, network origin, IAM principal, object prefix, KMS key policy and test read.
Incorrect Answers
A:Every AWS managed service uses the same consistency, retry and query-processing semantics. That generalization conflicts with S3 Access Points prefix policy and cross-account authorization. Instead access point policy and underlying bucket and encryption grants combine to determine practical object access. Check access Point ARN, network origin, IAM principal, object prefix, KMS key policy and test read.
C:An S3 bucket prefix guarantees exactly-once multi-service transactions without an output commit. That generalization conflicts with S3 Access Points prefix policy and cross-account authorization. Instead access point policy and underlying bucket and encryption grants combine to determine practical object access. Check access Point ARN, network origin, IAM principal, object prefix, KMS key policy and test read.
D:A successful IAM login means every analytics dataset is readable and correctly transformed. That generalization conflicts with S3 Access Points prefix policy and cross-account authorization. Instead access point policy and underlying bucket and encryption grants combine to determine practical object access. Check access Point ARN, network origin, IAM principal, object prefix, KMS key policy and test read.
Question 1081
An S3 access point policy allows a principal but a KMS key policy still denies decrypting the objects. An incorrect proposal is: Make the entire data lake bucket public to simplify cross-account access. What material risk would follow from the proposed incorrect shortcut?
- The concrete failure is that the dashboard theme independently caused an unrelated source database failure.
- The concrete failure is that a successful access point lookup cannot substitute for data key decrypt authorization.
- The concrete failure is that reading a healthy CloudWatch log automatically erased every earlier record.
- The concrete failure is that inspecting an existing Athena query plan itself deleted every production table.
Explanation
Correct Answer
B:Access point policy and underlying bucket and encryption grants combine to determine practical object access. The safer implementation is to configure S3 Access Point policy, bucket or account authorization and KMS cross-account grant for the bounded dataset.
Incorrect Answers
A:That unrelated assertion does not explain the actual S3 Access Points prefix policy and cross-account authorization risk.
C:That unrelated assertion does not explain the actual S3 Access Points prefix policy and cross-account authorization risk. Reading a healthy CloudWatch log automatically erased every earlier record.
D:That unrelated assertion does not explain the actual S3 Access Points prefix policy and cross-account authorization risk. Inspecting an existing Athena query plan itself deleted every production table.
Question 1082
An S3 access point policy allows a principal but a KMS key policy still denies decrypting the objects. The observed failure is: A successful access point lookup cannot substitute for data key decrypt authorization. Which recovery action BEST restores the required data-processing state?
- The supported recovery step is to correct layered grants and verify allowed prefix reads and forbidden unrelated objects.
- The supported recovery step is to remove all KMS key usage controls when only one partner needs decrypt.
- The supported recovery step is to make the entire data lake bucket public to simplify cross-account access.
- The supported recovery step is to assume an access point name grants implicit access to every S3 key.
Explanation
Correct Answer
A:This addresses the observed S3 Access Points prefix policy and cross-account authorization failure while preserving the required contract. Recheck access Point ARN, network origin, IAM principal, object prefix, KMS key policy and test read.
Incorrect Answers
B:Remove all KMS key usage controls when only one partner needs decrypt. A successful access point lookup cannot substitute for data key decrypt authorization. Instead correct layered grants and verify allowed prefix reads and forbidden unrelated objects.
C:Make the entire data lake bucket public to simplify cross-account access. A successful access point lookup cannot substitute for data key decrypt authorization. Instead correct layered grants and verify allowed prefix reads and forbidden unrelated objects.
D:Assume an access point name grants implicit access to every S3 key. A successful access point lookup cannot substitute for data key decrypt authorization. Instead correct layered grants and verify allowed prefix reads and forbidden unrelated objects.
Question 1083
An Athena consumer in one AWS account can list producer S3 objects but receives KMS AccessDenied when reading Parquet. Which AWS design or configuration BEST satisfies the stated processing requirement?
- Use an AWS managed key that cannot be shared in the required cross-account scenario without validation.
- Disable all encryption on the producer bucket to repair one consumer grant.
- Configure customer managed KMS key policy and permitted cross-account IAM or grants for the exact consumer and dataset.
- Assume an IAM kms:Decrypt allow overrides every KMS key policy restriction automatically.
Explanation
Correct Answer
C:Validate with kMS key ARN, key policy, IAM role, encryption context, CloudTrail decrypt error and query outcome.
Incorrect Answers
A:Granting S3 GetObject without a usable KMS decrypt path leaves encrypted content inaccessible. This does not meet KMS key policy and cross-account encrypted lake read.
B:Disable all encryption on the producer bucket to repair one consumer grant. Cross-account KMS use requires compatible key-side and principal-side authorization, not merely S3 object permission. Inspect kMS key ARN, key policy, IAM role, encryption context, CloudTrail decrypt error and query outcome.
D:Granting S3 GetObject without a usable KMS decrypt path leaves encrypted content inaccessible. The appropriate action is to configure customer managed KMS key policy and permitted cross-account IAM or grants for the exact consumer and dataset.
Question 1084
An Athena consumer in one AWS account can list producer S3 objects but receives KMS AccessDenied when reading Parquet. Which evidence would BEST verify that the intended pipeline outcome occurred?
- A successful ping to an unrelated service that did not process the data.
- An old architecture drawing without the current query plan or job-run identifier.
- A dashboard color with no source event or data row evidence.
- KMS key ARN, key policy, IAM role, encryption context, CloudTrail decrypt error and query outcome.
Explanation
Correct Answer
D:These observations directly test KMS key policy and cross-account encrypted lake read.
Incorrect Answers
A:A successful ping to an unrelated service that did not process the data. This is not sufficient evidence for KMS key policy and cross-account encrypted lake read. Check kMS key ARN, key policy, IAM role, encryption context, CloudTrail decrypt error and query outcome. Cross-account KMS use requires compatible key-side and principal-side authorization, not merely S3 object permission.
B:An old architecture drawing without the current query plan or job-run identifier. This is not sufficient evidence for KMS key policy and cross-account encrypted lake read. Check kMS key ARN, key policy, IAM role, encryption context, CloudTrail decrypt error and query outcome. Cross-account KMS use requires compatible key-side and principal-side authorization, not merely S3 object permission.
C:A dashboard color with no source event or data row evidence. This is not sufficient evidence for KMS key policy and cross-account encrypted lake read. Check kMS key ARN, key policy, IAM role, encryption context, CloudTrail decrypt error and query outcome. Cross-account KMS use requires compatible key-side and principal-side authorization, not merely S3 object permission.
Question 1085
An Athena consumer in one AWS account can list producer S3 objects but receives KMS AccessDenied when reading Parquet. Which underlying AWS service principle BEST explains the recommended approach?
- Increasing a resource name length automatically increases AWS service throughput.
- An S3 bucket prefix guarantees exactly-once multi-service transactions without an output commit.
- Cross-account KMS use requires compatible key-side and principal-side authorization, not merely S3 object permission.
- A successful IAM login means every analytics dataset is readable and correctly transformed.
Explanation
Correct Answer
C:Implement by choosing to configure customer managed KMS key policy and permitted cross-account IAM or grants for the exact consumer and dataset. This is the relevant technical mechanism for KMS key policy and cross-account encrypted lake read.
Incorrect Answers
A:Increasing a resource name length automatically increases AWS service throughput. That generalization conflicts with KMS key policy and cross-account encrypted lake read. Instead cross-account KMS use requires compatible key-side and principal-side authorization, not merely S3 object permission. Check kMS key ARN, key policy, IAM role, encryption context, CloudTrail decrypt error and query outcome.
B:An S3 bucket prefix guarantees exactly-once multi-service transactions without an output commit. That generalization conflicts with KMS key policy and cross-account encrypted lake read. Instead cross-account KMS use requires compatible key-side and principal-side authorization, not merely S3 object permission. Check kMS key ARN, key policy, IAM role, encryption context, CloudTrail decrypt error and query outcome.
D:A successful IAM login means every analytics dataset is readable and correctly transformed. That generalization conflicts with KMS key policy and cross-account encrypted lake read. Instead cross-account KMS use requires compatible key-side and principal-side authorization, not merely S3 object permission. Check kMS key ARN, key policy, IAM role, encryption context, CloudTrail decrypt error and query outcome.
Question 1086
An Athena consumer in one AWS account can list producer S3 objects but receives KMS AccessDenied when reading Parquet. An incorrect proposal is: Use an AWS managed key that cannot be shared in the required cross-account scenario without validation. What material risk would follow from the proposed incorrect shortcut?
- Granting S3 GetObject without a usable KMS decrypt path leaves encrypted content inaccessible.
- The dashboard theme independently caused an unrelated source database failure.
- Reading a healthy CloudWatch log automatically erased every earlier record.
- A correctly encrypted S3 test object was the sole cause of an unrelated ISP outage.
Explanation
Correct Answer
A:The safer implementation is to configure customer managed KMS key policy and permitted cross-account IAM or grants for the exact consumer and dataset. This is why the incorrect shortcut does not meet KMS key policy and cross-account encrypted lake read.
Incorrect Answers
B:The dashboard theme independently caused an unrelated source database failure. That unrelated assertion does not explain the actual KMS key policy and cross-account encrypted lake read risk. The relevant failure is that granting S3 GetObject without a usable KMS decrypt path leaves encrypted content inaccessible. Check kMS key ARN, key policy, IAM role, encryption context, CloudTrail decrypt error and query outcome.
C:Reading a healthy CloudWatch log automatically erased every earlier record. That unrelated assertion does not explain the actual KMS key policy and cross-account encrypted lake read risk. The relevant failure is that granting S3 GetObject without a usable KMS decrypt path leaves encrypted content inaccessible. Check kMS key ARN, key policy, IAM role, encryption context, CloudTrail decrypt error and query outcome.
D:A correctly encrypted S3 test object was the sole cause of an unrelated ISP outage. That unrelated assertion does not explain the actual KMS key policy and cross-account encrypted lake read risk. The relevant failure is that granting S3 GetObject without a usable KMS decrypt path leaves encrypted content inaccessible. Check kMS key ARN, key policy, IAM role, encryption context, CloudTrail decrypt error and query outcome.
Question 1087
An Athena consumer in one AWS account can list producer S3 objects but receives KMS AccessDenied when reading Parquet. The observed failure is: Granting S3 GetObject without a usable KMS decrypt path leaves encrypted content inaccessible. Which recovery action BEST restores the required data-processing state?
- Disable all encryption on the producer bucket to repair one consumer grant.
- Assume an IAM kms:Decrypt allow overrides every KMS key policy restriction automatically.
- Scope both key and role permissions and retest permitted dataset reads and denied unapproved principals.
- Use an AWS managed key that cannot be shared in the required cross-account scenario without validation.
Explanation
Correct Answer
C:This addresses the observed KMS key policy and cross-account encrypted lake read failure while preserving the required contract. Recheck kMS key ARN, key policy, IAM role, encryption context, CloudTrail decrypt error and query outcome.
Incorrect Answers
A:Disable all encryption on the producer bucket to repair one consumer grant. Granting S3 GetObject without a usable KMS decrypt path leaves encrypted content inaccessible. Instead scope both key and role permissions and retest permitted dataset reads and denied unapproved principals.
B:Assume an IAM kms:Decrypt allow overrides every KMS key policy restriction automatically. Granting S3 GetObject without a usable KMS decrypt path leaves encrypted content inaccessible. Instead scope both key and role permissions and retest permitted dataset reads and denied unapproved principals.
D:Use an AWS managed key that cannot be shared in the required cross-account scenario without validation. Granting S3 GetObject without a usable KMS decrypt path leaves encrypted content inaccessible. Instead scope both key and role permissions and retest permitted dataset reads and denied unapproved principals.
Question 1088
A cross-account data sharing role has IAM kms:Decrypt but the producer key policy does not trust it. What is the MOST appropriate targeted implementation for this data-engineering situation?
- In this operational case, disable all encryption on the producer bucket to repair one consumer grant.
- In this operational case, configure customer managed KMS key policy and permitted cross-account IAM or grants for the exact consumer and dataset.
- In this operational case, assume an IAM kms:Decrypt allow overrides every KMS key policy restriction automatically.
- In this operational case, use an AWS managed key that cannot be shared in the required cross-account scenario without validation.
Explanation
Correct Answer
B:This directly addresses KMS key policy and cross-account encrypted lake read.
Incorrect Answers
A:Disable all encryption on the producer bucket to repair one consumer grant. Cross-account KMS use requires compatible key-side and principal-side authorization, not merely S3 object permission. Inspect kMS key ARN, key policy, IAM role, encryption context, CloudTrail decrypt error and query outcome.
C:Granting S3 GetObject without a usable KMS decrypt path leaves encrypted content inaccessible.
D:Granting S3 GetObject without a usable KMS decrypt path leaves encrypted content inaccessible. The supported design is to configure customer managed KMS key policy and permitted cross-account IAM or grants for the exact consumer and dataset.
Question 1089
A cross-account data sharing role has IAM kms:Decrypt but the producer key policy does not trust it. What diagnostic observations should be checked before marking the change successful?
- The relevant validation evidence is a renamed resource label that does not show an authorization or processing result.
- The relevant validation evidence is kMS key ARN, key policy, IAM role, encryption context, CloudTrail decrypt error and query outcome.
- The relevant validation evidence is a successful ping to an unrelated service that did not process the data.
- The relevant validation evidence is an old architecture drawing without the current query plan or job-run identifier.
Explanation
Correct Answer
B:KMS key ARN, key policy, IAM role, encryption context, CloudTrail decrypt error and query outcome. These observations directly test KMS key policy and cross-account encrypted lake read. Cross-account KMS use requires compatible key-side and principal-side authorization, not merely S3 object permission.
Incorrect Answers
A:A renamed resource label that does not show an authorization or processing result. This is not sufficient evidence for KMS key policy and cross-account encrypted lake read. Check kMS key ARN, key policy, IAM role, encryption context, CloudTrail decrypt error and query outcome. Cross-account KMS use requires compatible key-side and principal-side authorization, not merely S3 object permission.
C:A successful ping to an unrelated service that did not process the data. This is not sufficient evidence for KMS key policy and cross-account encrypted lake read. Check kMS key ARN, key policy, IAM role, encryption context, CloudTrail decrypt error and query outcome. Cross-account KMS use requires compatible key-side and principal-side authorization, not merely S3 object permission.
D:An old architecture drawing without the current query plan or job-run identifier. This is not sufficient evidence for KMS key policy and cross-account encrypted lake read. Check kMS key ARN, key policy, IAM role, encryption context, CloudTrail decrypt error and query outcome. Cross-account KMS use requires compatible key-side and principal-side authorization, not merely S3 object permission.
Question 1090
A cross-account data sharing role has IAM kms:Decrypt but the producer key policy does not trust it. What technical statement accurately describes the relevant AWS processing behavior?
- The governing design principle is that a successful IAM login means every analytics dataset is readable and correctly transformed.
- The governing design principle is that increasing a resource name length automatically increases AWS service throughput.
- The governing design principle is that a pipeline schedule guarantees that every downstream source record was processed correctly.
- The governing design principle is that cross-account KMS use requires compatible key-side and principal-side authorization, not merely S3 object permission.
Explanation
Correct Answer
D:Implement by choosing to configure customer managed KMS key policy and permitted cross-account IAM or grants for the exact consumer and dataset. Verify with kMS key ARN, key policy, IAM role, encryption context, CloudTrail decrypt error and query outcome.
Incorrect Answers
A:A successful IAM login means every analytics dataset is readable and correctly transformed. That generalization conflicts with KMS key policy and cross-account encrypted lake read. Instead cross-account KMS use requires compatible key-side and principal-side authorization, not merely S3 object permission. Check kMS key ARN, key policy, IAM role, encryption context, CloudTrail decrypt error and query outcome.
B:Increasing a resource name length automatically increases AWS service throughput. That generalization conflicts with KMS key policy and cross-account encrypted lake read. Instead cross-account KMS use requires compatible key-side and principal-side authorization, not merely S3 object permission. Check kMS key ARN, key policy, IAM role, encryption context, CloudTrail decrypt error and query outcome.
C:A pipeline schedule guarantees that every downstream source record was processed correctly. That generalization conflicts with KMS key policy and cross-account encrypted lake read. Instead cross-account KMS use requires compatible key-side and principal-side authorization, not merely S3 object permission. Check kMS key ARN, key policy, IAM role, encryption context, CloudTrail decrypt error and query outcome.