Amazon AWS Certified Data Engineer - Associate DEA-C01 Practice Test 110
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.
Question 1091
A cross-account data sharing role has IAM kms:Decrypt but the producer key policy does not trust it. An incorrect proposal is: Use an AWS managed key that cannot be shared in the required cross-account scenario without validation. Which failure consequence BEST shows why that proposal is inappropriate?
- The concrete failure is that a correctly encrypted S3 test object was the sole cause of an unrelated ISP outage.
- The concrete failure is that a harmless resource display-name edit caused all prior ETL jobs to lose their source schemas.
- The concrete failure is that reading a healthy CloudWatch log automatically erased every earlier record.
- The concrete failure is that granting S3 GetObject without a usable KMS decrypt path leaves encrypted content inaccessible.
Explanation
Correct Answer
D:The safer implementation is to configure customer managed KMS key policy and permitted cross-account IAM or grants for the exact consumer and dataset.
Incorrect Answers
A: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.
B:That unrelated assertion does not explain the actual KMS key policy and cross-account encrypted lake read risk. Check kMS key ARN, key policy, IAM role, encryption context, CloudTrail decrypt error and query outcome.
C:That unrelated assertion does not explain the actual KMS key policy and cross-account encrypted lake read risk.
Question 1092
A cross-account data sharing role has IAM kms:Decrypt but the producer key policy does not trust it. The observed failure is: Granting S3 GetObject without a usable KMS decrypt path leaves encrypted content inaccessible. How should the team correct and verify the observed fault?
- The supported recovery step is to assume an IAM kms:Decrypt allow overrides every KMS key policy restriction automatically.
- The supported recovery step is to use an AWS managed key that cannot be shared in the required cross-account scenario without validation.
- The supported recovery step is to disable all encryption on the producer bucket to repair one consumer grant.
- The supported recovery step is to scope both key and role permissions and retest permitted dataset reads and denied unapproved principals.
Explanation
Correct Answer
D:This addresses the observed KMS key policy and cross-account encrypted lake read failure while preserving the required contract.
Incorrect Answers
A: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.
B: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.
C: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.
Question 1093
A raw lake ingestion process writes objects without the required customer-managed KMS key. What is the MOST appropriate targeted implementation for this data-engineering situation?
- Send production data to an unencrypted public bucket as a debugging workaround.
- Require appropriate S3 server-side encryption and verify default or bucket policy key conditions for new objects.
- Assume every SSE-S3 object uses a specific customer managed KMS key.
- Ignore upload metadata because downstream Athena queries succeed.
Explanation
Correct Answer
B:S3 default encryption and explicit bucket policy restrictions together govern protection of newly written objects. This directly addresses S3 server-side encryption default and bucket enforcement.
Incorrect Answers
A:Assuming a bucket's name implies the required KMS key can leave writes using unintended encryption. This does not meet S3 server-side encryption default and bucket enforcement.
C:Assume every SSE-S3 object uses a specific customer managed KMS key. S3 default encryption and explicit bucket policy restrictions together govern protection of newly written objects. Inspect putObject encryption headers, bucket default encryption, object KMS key ARN, policy decision and readback.
D:Assuming a bucket's name implies the required KMS key can leave writes using unintended encryption. The appropriate action is to require appropriate S3 server-side encryption and verify default or bucket policy key conditions for new objects.
Question 1094
A raw lake ingestion process writes objects without the required customer-managed KMS key. What diagnostic observations should be checked before marking the change successful?
- A renamed resource label that does not show an authorization or processing result.
- PutObject encryption headers, bucket default encryption, object KMS key ARN, policy decision and readback.
- A browser screenshot from another AWS account and time period.
- An old architecture drawing without the current query plan or job-run identifier.
Explanation
Correct Answer
B:S3 default encryption and explicit bucket policy restrictions together govern protection of newly written objects. These observations directly test S3 server-side encryption default and bucket enforcement.
Incorrect Answers
A:A renamed resource label that does not show an authorization or processing result. This is not sufficient evidence for S3 server-side encryption default and bucket enforcement. Check putObject encryption headers, bucket default encryption, object KMS key ARN, policy decision and readback. S3 default encryption and explicit bucket policy restrictions together govern protection of newly written objects.
C:A browser screenshot from another AWS account and time period. This is not sufficient evidence for S3 server-side encryption default and bucket enforcement. Check putObject encryption headers, bucket default encryption, object KMS key ARN, policy decision and readback. S3 default encryption and explicit bucket policy restrictions together govern protection of newly written objects.
D:An old architecture drawing without the current query plan or job-run identifier. This is not sufficient evidence for S3 server-side encryption default and bucket enforcement. Check putObject encryption headers, bucket default encryption, object KMS key ARN, policy decision and readback. S3 default encryption and explicit bucket policy restrictions together govern protection of newly written objects.
Question 1095
A raw lake ingestion process writes objects without the required customer-managed KMS key. What technical statement accurately describes the relevant AWS processing behavior?
- A CloudWatch metric label is equivalent to a successful target table data-quality validation.
- Increasing a resource name length automatically increases AWS service throughput.
- S3 default encryption and explicit bucket policy restrictions together govern protection of newly written objects.
- A pipeline schedule guarantees that every downstream source record was processed correctly.
Explanation
Correct Answer
C:Implement by choosing to require appropriate S3 server-side encryption and verify default or bucket policy key conditions for new objects. Verify with putObject encryption headers, bucket default encryption, object KMS key ARN, policy decision and readback.
Incorrect Answers
A:A CloudWatch metric label is equivalent to a successful target table data-quality validation. That generalization conflicts with S3 server-side encryption default and bucket enforcement. Instead s3 default encryption and explicit bucket policy restrictions together govern protection of newly written objects. Check putObject encryption headers, bucket default encryption, object KMS key ARN, policy decision and readback.
B:Increasing a resource name length automatically increases AWS service throughput. That generalization conflicts with S3 server-side encryption default and bucket enforcement. Instead s3 default encryption and explicit bucket policy restrictions together govern protection of newly written objects. Check putObject encryption headers, bucket default encryption, object KMS key ARN, policy decision and readback.
D:A pipeline schedule guarantees that every downstream source record was processed correctly. That generalization conflicts with S3 server-side encryption default and bucket enforcement. Instead s3 default encryption and explicit bucket policy restrictions together govern protection of newly written objects. Check putObject encryption headers, bucket default encryption, object KMS key ARN, policy decision and readback.
Question 1096
A raw lake ingestion process writes objects without the required customer-managed KMS key. An incorrect proposal is: Send production data to an unencrypted public bucket as a debugging workaround. Which failure consequence BEST shows why that proposal is inappropriate?
- A correctly encrypted S3 test object was the sole cause of an unrelated ISP outage.
- A harmless resource display-name edit caused all prior ETL jobs to lose their source schemas.
- The presence of an accurate job timestamp automatically created unauthorized database credentials.
- Assuming a bucket's name implies the required KMS key can leave writes using unintended encryption.
Explanation
Correct Answer
D:This is why the incorrect shortcut does not meet S3 server-side encryption default and bucket enforcement. S3 default encryption and explicit bucket policy restrictions together govern protection of newly written objects.
Incorrect Answers
A:A correctly encrypted S3 test object was the sole cause of an unrelated ISP outage. That unrelated assertion does not explain the actual S3 server-side encryption default and bucket enforcement risk. The relevant failure is that assuming a bucket's name implies the required KMS key can leave writes using unintended encryption. Check putObject encryption headers, bucket default encryption, object KMS key ARN, policy decision and readback.
B:A harmless resource display-name edit caused all prior ETL jobs to lose their source schemas. That unrelated assertion does not explain the actual S3 server-side encryption default and bucket enforcement risk. The relevant failure is that assuming a bucket's name implies the required KMS key can leave writes using unintended encryption. Check putObject encryption headers, bucket default encryption, object KMS key ARN, policy decision and readback.
C:The presence of an accurate job timestamp automatically created unauthorized database credentials. That unrelated assertion does not explain the actual S3 server-side encryption default and bucket enforcement risk. The relevant failure is that assuming a bucket's name implies the required KMS key can leave writes using unintended encryption. Check putObject encryption headers, bucket default encryption, object KMS key ARN, policy decision and readback.
Question 1097
A raw lake ingestion process writes objects without the required customer-managed KMS key. The observed failure is: Assuming a bucket's name implies the required KMS key can leave writes using unintended encryption. How should the team correct and verify the observed fault?
- Enforce and inspect the correct key on a test upload while denying writes with a disallowed configuration.
- Assume every SSE-S3 object uses a specific customer managed KMS key.
- Ignore upload metadata because downstream Athena queries succeed.
- Send production data to an unencrypted public bucket as a debugging workaround.
Explanation
Correct Answer
A:This addresses the observed S3 server-side encryption default and bucket enforcement failure while preserving the required contract. S3 default encryption and explicit bucket policy restrictions together govern protection of newly written objects.
Incorrect Answers
B:Assume every SSE-S3 object uses a specific customer managed KMS key. Assuming a bucket's name implies the required KMS key can leave writes using unintended encryption. Instead enforce and inspect the correct key on a test upload while denying writes with a disallowed configuration.
C:Ignore upload metadata because downstream Athena queries succeed. Assuming a bucket's name implies the required KMS key can leave writes using unintended encryption. Instead enforce and inspect the correct key on a test upload while denying writes with a disallowed configuration.
D:Send production data to an unencrypted public bucket as a debugging workaround. Assuming a bucket's name implies the required KMS key can leave writes using unintended encryption. Instead enforce and inspect the correct key on a test upload while denying writes with a disallowed configuration.
Question 1098
An encrypted bucket's new objects use an unexpected key after a partner upload bypasses the intended client settings. Which controlled service choice should the engineer make to meet this requirement?
- In this operational case, assume every SSE-S3 object uses a specific customer managed KMS key.
- In this operational case, ignore upload metadata because downstream Athena queries succeed.
- In this operational case, send production data to an unencrypted public bucket as a debugging workaround.
- In this operational case, require appropriate S3 server-side encryption and verify default or bucket policy key conditions for new objects.
Explanation
Correct Answer
D:S3 default encryption and explicit bucket policy restrictions together govern protection of newly written objects. Validate with putObject encryption headers, bucket default encryption, object KMS key ARN, policy decision and readback.
Incorrect Answers
A:Assume every SSE-S3 object uses a specific customer managed KMS key. S3 default encryption and explicit bucket policy restrictions together govern protection of newly written objects. Inspect putObject encryption headers, bucket default encryption, object KMS key ARN, policy decision and readback.
B:Assuming a bucket's name implies the required KMS key can leave writes using unintended encryption.
C:Assuming a bucket's name implies the required KMS key can leave writes using unintended encryption. The supported design is to require appropriate S3 server-side encryption and verify default or bucket policy key conditions for new objects.
Question 1099
An encrypted bucket's new objects use an unexpected key after a partner upload bypasses the intended client settings. Which metrics or records most directly prove the required behavior?
- The relevant validation evidence is a resource ARN alone without any current data-plane observation.
- The relevant validation evidence is putObject encryption headers, bucket default encryption, object KMS key ARN, policy decision and readback.
- The relevant validation evidence is a renamed resource label that does not show an authorization or processing result.
- The relevant validation evidence is a browser screenshot from another AWS account and time period.
Explanation
Correct Answer
B:S3 default encryption and explicit bucket policy restrictions together govern protection of newly written objects.
Incorrect Answers
A:A resource ARN alone without any current data-plane observation. This is not sufficient evidence for S3 server-side encryption default and bucket enforcement. Check putObject encryption headers, bucket default encryption, object KMS key ARN, policy decision and readback. S3 default encryption and explicit bucket policy restrictions together govern protection of newly written objects.
C:A renamed resource label that does not show an authorization or processing result. This is not sufficient evidence for S3 server-side encryption default and bucket enforcement. Check putObject encryption headers, bucket default encryption, object KMS key ARN, policy decision and readback. S3 default encryption and explicit bucket policy restrictions together govern protection of newly written objects.
D:A browser screenshot from another AWS account and time period. This is not sufficient evidence for S3 server-side encryption default and bucket enforcement. Check putObject encryption headers, bucket default encryption, object KMS key ARN, policy decision and readback. S3 default encryption and explicit bucket policy restrictions together govern protection of newly written objects.
Question 1100
An encrypted bucket's new objects use an unexpected key after a partner upload bypasses the intended client settings. Why does the correct approach fit this workflow boundary?
- The governing design principle is that s3 default encryption and explicit bucket policy restrictions together govern protection of newly written objects.
- The governing design principle is that a pipeline schedule guarantees that every downstream source record was processed correctly.
- The governing design principle is that a CloudWatch metric label is equivalent to a successful target table data-quality validation.
- The governing design principle is that every AWS managed service uses the same consistency, retry and query-processing semantics.
Explanation
Correct Answer
A:Implement by choosing to require appropriate S3 server-side encryption and verify default or bucket policy key conditions for new objects.
Incorrect Answers
B:A pipeline schedule guarantees that every downstream source record was processed correctly. That generalization conflicts with S3 server-side encryption default and bucket enforcement. Instead s3 default encryption and explicit bucket policy restrictions together govern protection of newly written objects. Check putObject encryption headers, bucket default encryption, object KMS key ARN, policy decision and readback.
C:A CloudWatch metric label is equivalent to a successful target table data-quality validation. That generalization conflicts with S3 server-side encryption default and bucket enforcement. Instead s3 default encryption and explicit bucket policy restrictions together govern protection of newly written objects. Check putObject encryption headers, bucket default encryption, object KMS key ARN, policy decision and readback.
D:Every AWS managed service uses the same consistency, retry and query-processing semantics. That generalization conflicts with S3 server-side encryption default and bucket enforcement. Instead s3 default encryption and explicit bucket policy restrictions together govern protection of newly written objects. Check putObject encryption headers, bucket default encryption, object KMS key ARN, policy decision and readback.