Amazon AWS Certified Data Engineer - Associate DEA-C01 Practice Test 111
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.
Question 1101
An encrypted bucket's new objects use an unexpected key after a partner upload bypasses the intended client settings. An incorrect proposal is: Send production data to an unencrypted public bucket as a debugging workaround. What operational defect would the misguided change introduce?
- The concrete failure is that the presence of an accurate job timestamp automatically created unauthorized database credentials.
- The concrete failure is that inspecting an existing Athena query plan itself deleted every production table.
- 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 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. The safer implementation is to require appropriate S3 server-side encryption and verify default or bucket policy key conditions for new objects.
Incorrect Answers
A: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.
B:Inspecting an existing Athena query plan itself deleted every production table. 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: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.
Question 1102
An encrypted bucket's new objects use an unexpected key after a partner upload bypasses the intended client settings. The observed failure is: Assuming a bucket's name implies the required KMS key can leave writes using unintended encryption. What focused remediation preserves the intended data contract?
- The supported recovery step is to ignore upload metadata because downstream Athena queries succeed.
- The supported recovery step is to enforce and inspect the correct key on a test upload while denying writes with a disallowed configuration.
- The supported recovery step is to send production data to an unencrypted public bucket as a debugging workaround.
- The supported recovery step is to assume every SSE-S3 object uses a specific customer managed KMS key.
Explanation
Correct Answer
B:This addresses the observed S3 server-side encryption default and bucket enforcement failure while preserving the required contract. Recheck putObject encryption headers, bucket default encryption, object KMS key ARN, policy decision and readback.
Incorrect Answers
A: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.
C: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.
D: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.
Question 1103
A Glue job connects to an RDS source with TLS disabled although the data transport policy requires encryption. Which controlled service choice should the engineer make to meet this requirement?
- Disable database certificate validation permanently to resolve a hostname error.
- Configure TLS-capable JDBC and managed encrypted transfer with server certificate verification and appropriate protocol.
- Assume S3 SSE-KMS automatically encrypts an unrelated source-side JDBC socket.
- Use plaintext FTP over the internet because downstream storage is encrypted.
Explanation
Correct Answer
B:Validate with jDBC SSL connection parameters, certificate chain, TLS negotiation, transfer endpoint and network trace. This directly addresses TLS for JDBC and data movement paths.
Incorrect Answers
A:Encrypting S3 target objects does not protect unencrypted bytes before they reach AWS storage. This does not meet TLS for JDBC and data movement paths.
C:Assume S3 SSE-KMS automatically encrypts an unrelated source-side JDBC socket. Encryption at rest and encryption in transit protect different stages of data movement. Inspect jDBC SSL connection parameters, certificate chain, TLS negotiation, transfer endpoint and network trace.
D:Encrypting S3 target objects does not protect unencrypted bytes before they reach AWS storage. The appropriate action is to configure TLS-capable JDBC and managed encrypted transfer with server certificate verification and appropriate protocol.
Question 1104
A Glue job connects to an RDS source with TLS disabled although the data transport policy requires encryption. Which metrics or records most directly prove the required behavior?
- A resource ARN alone without any current data-plane observation.
- A dashboard color with no source event or data row evidence.
- JDBC SSL connection parameters, certificate chain, TLS negotiation, transfer endpoint and network trace.
- A browser screenshot from another AWS account and time period.
Explanation
Correct Answer
C:These observations directly test TLS for JDBC and data movement paths. Encryption at rest and encryption in transit protect different stages of data movement.
Incorrect Answers
A:A resource ARN alone without any current data-plane observation. This is not sufficient evidence for TLS for JDBC and data movement paths. Check jDBC SSL connection parameters, certificate chain, TLS negotiation, transfer endpoint and network trace. Encryption at rest and encryption in transit protect different stages of data movement.
B:A dashboard color with no source event or data row evidence. This is not sufficient evidence for TLS for JDBC and data movement paths. Check jDBC SSL connection parameters, certificate chain, TLS negotiation, transfer endpoint and network trace. Encryption at rest and encryption in transit protect different stages of data movement.
D:A browser screenshot from another AWS account and time period. This is not sufficient evidence for TLS for JDBC and data movement paths. Check jDBC SSL connection parameters, certificate chain, TLS negotiation, transfer endpoint and network trace. Encryption at rest and encryption in transit protect different stages of data movement.
Question 1105
A Glue job connects to an RDS source with TLS disabled although the data transport policy requires encryption. Why does the correct approach fit this workflow boundary?
- An S3 bucket prefix guarantees exactly-once multi-service transactions without an output commit.
- A CloudWatch metric label is equivalent to a successful target table data-quality validation.
- Every AWS managed service uses the same consistency, retry and query-processing semantics.
- Encryption at rest and encryption in transit protect different stages of data movement.
Explanation
Correct Answer
D:Implement by choosing to configure TLS-capable JDBC and managed encrypted transfer with server certificate verification and appropriate protocol.
Incorrect Answers
A:An S3 bucket prefix guarantees exactly-once multi-service transactions without an output commit. That generalization conflicts with TLS for JDBC and data movement paths. Instead encryption at rest and encryption in transit protect different stages of data movement. Check jDBC SSL connection parameters, certificate chain, TLS negotiation, transfer endpoint and network trace.
B:A CloudWatch metric label is equivalent to a successful target table data-quality validation. That generalization conflicts with TLS for JDBC and data movement paths. Instead encryption at rest and encryption in transit protect different stages of data movement. Check jDBC SSL connection parameters, certificate chain, TLS negotiation, transfer endpoint and network trace.
C:Every AWS managed service uses the same consistency, retry and query-processing semantics. That generalization conflicts with TLS for JDBC and data movement paths. Instead encryption at rest and encryption in transit protect different stages of data movement. Check jDBC SSL connection parameters, certificate chain, TLS negotiation, transfer endpoint and network trace.
Question 1106
A Glue job connects to an RDS source with TLS disabled although the data transport policy requires encryption. An incorrect proposal is: Disable database certificate validation permanently to resolve a hostname error. What operational defect would the misguided change introduce?
- The presence of an accurate job timestamp automatically created unauthorized database credentials.
- Inspecting an existing Athena query plan itself deleted every production table.
- Encrypting S3 target objects does not protect unencrypted bytes before they reach AWS storage.
- The dashboard theme independently caused an unrelated source database failure.
Explanation
Correct Answer
C:This is why the incorrect shortcut does not meet TLS for JDBC and data movement paths. Encryption at rest and encryption in transit protect different stages of data movement.
Incorrect Answers
A:The presence of an accurate job timestamp automatically created unauthorized database credentials. That unrelated assertion does not explain the actual TLS for JDBC and data movement paths risk. The relevant failure is that encrypting S3 target objects does not protect unencrypted bytes before they reach AWS storage. Check jDBC SSL connection parameters, certificate chain, TLS negotiation, transfer endpoint and network trace.
B:Inspecting an existing Athena query plan itself deleted every production table. That unrelated assertion does not explain the actual TLS for JDBC and data movement paths risk. The relevant failure is that encrypting S3 target objects does not protect unencrypted bytes before they reach AWS storage. Check jDBC SSL connection parameters, certificate chain, TLS negotiation, transfer endpoint and network trace.
D:The dashboard theme independently caused an unrelated source database failure. That unrelated assertion does not explain the actual TLS for JDBC and data movement paths risk. The relevant failure is that encrypting S3 target objects does not protect unencrypted bytes before they reach AWS storage. Check jDBC SSL connection parameters, certificate chain, TLS negotiation, transfer endpoint and network trace.
Question 1107
A Glue job connects to an RDS source with TLS disabled although the data transport policy requires encryption. The observed failure is: Encrypting S3 target objects does not protect unencrypted bytes before they reach AWS storage. What focused remediation preserves the intended data contract?
- Assume S3 SSE-KMS automatically encrypts an unrelated source-side JDBC socket.
- Use plaintext FTP over the internet because downstream storage is encrypted.
- Disable database certificate validation permanently to resolve a hostname error.
- Enable and verify appropriate TLS or SFTP and reject connections with an untrusted certificate.
Explanation
Correct Answer
D:This addresses the observed TLS for JDBC and data movement paths failure while preserving the required contract. Encryption at rest and encryption in transit protect different stages of data movement.
Incorrect Answers
A:Assume S3 SSE-KMS automatically encrypts an unrelated source-side JDBC socket. Encrypting S3 target objects does not protect unencrypted bytes before they reach AWS storage. Instead enable and verify appropriate TLS or SFTP and reject connections with an untrusted certificate.
B:Use plaintext FTP over the internet because downstream storage is encrypted. Encrypting S3 target objects does not protect unencrypted bytes before they reach AWS storage. Instead enable and verify appropriate TLS or SFTP and reject connections with an untrusted certificate.
C:Disable database certificate validation permanently to resolve a hostname error. Encrypting S3 target objects does not protect unencrypted bytes before they reach AWS storage. Instead enable and verify appropriate TLS or SFTP and reject connections with an untrusted certificate.
Question 1108
A file-transfer partner uses unencrypted FTP and an ETL stage stores sensitive payloads in transit. What architecture action addresses the stated source-to-target behavior?
- In this operational case, assume S3 SSE-KMS automatically encrypts an unrelated source-side JDBC socket.
- In this operational case, use plaintext FTP over the internet because downstream storage is encrypted.
- In this operational case, configure TLS-capable JDBC and managed encrypted transfer with server certificate verification and appropriate protocol.
- In this operational case, disable database certificate validation permanently to resolve a hostname error.
Explanation
Correct Answer
C:Validate with jDBC SSL connection parameters, certificate chain, TLS negotiation, transfer endpoint and network trace. Encryption at rest and encryption in transit protect different stages of data movement.
Incorrect Answers
A:Assume S3 SSE-KMS automatically encrypts an unrelated source-side JDBC socket. Encryption at rest and encryption in transit protect different stages of data movement. Inspect jDBC SSL connection parameters, certificate chain, TLS negotiation, transfer endpoint and network trace.
B:Encrypting S3 target objects does not protect unencrypted bytes before they reach AWS storage. Use plaintext FTP over the internet because downstream storage is encrypted.
D:This does not meet TLS for JDBC and data movement paths.
Question 1109
A file-transfer partner uses unencrypted FTP and an ETL stage stores sensitive payloads in transit. What validation evidence distinguishes a correct implementation from a dashboard-only change?
- The relevant validation evidence is a successful ping to an unrelated service that did not process the data.
- The relevant validation evidence is a resource ARN alone without any current data-plane observation.
- The relevant validation evidence is a dashboard color with no source event or data row evidence.
- The relevant validation evidence is jDBC SSL connection parameters, certificate chain, TLS negotiation, transfer endpoint and network trace.
Explanation
Correct Answer
D:These observations directly test TLS for JDBC and data movement paths. In this specific operating situation, a file-transfer partner uses unencrypted FTP and an ETL stage stores sensitive payloads in transit.
Incorrect Answers
A:A successful ping to an unrelated service that did not process the data. This is not sufficient evidence for TLS for JDBC and data movement paths. Check jDBC SSL connection parameters, certificate chain, TLS negotiation, transfer endpoint and network trace. Encryption at rest and encryption in transit protect different stages of data movement.
B:A resource ARN alone without any current data-plane observation. This is not sufficient evidence for TLS for JDBC and data movement paths. Check jDBC SSL connection parameters, certificate chain, TLS negotiation, transfer endpoint and network trace. Encryption at rest and encryption in transit protect different stages of data movement.
C:A dashboard color with no source event or data row evidence. This is not sufficient evidence for TLS for JDBC and data movement paths. Check jDBC SSL connection parameters, certificate chain, TLS negotiation, transfer endpoint and network trace. Encryption at rest and encryption in transit protect different stages of data movement.
Question 1110
A file-transfer partner uses unencrypted FTP and an ETL stage stores sensitive payloads in transit. An incorrect proposal is: Disable database certificate validation permanently to resolve a hostname error. What issue should reviewers anticipate if the shortcut is adopted?
- The concrete failure is that the dashboard theme independently caused an unrelated source database failure.
- The concrete failure is that reading a healthy CloudWatch log automatically erased every earlier record.
- The concrete failure is that encrypting S3 target objects does not protect unencrypted bytes before they reach AWS storage.
- The concrete failure is that inspecting an existing Athena query plan itself deleted every production table.
Explanation
Correct Answer
C:This is why the incorrect shortcut does not meet TLS for JDBC and data movement paths. The safer implementation is to configure TLS-capable JDBC and managed encrypted transfer with server certificate verification and appropriate protocol.
Incorrect Answers
A:The dashboard theme independently caused an unrelated source database failure. That unrelated assertion does not explain the actual TLS for JDBC and data movement paths risk. The relevant failure is that encrypting S3 target objects does not protect unencrypted bytes before they reach AWS storage. Check jDBC SSL connection parameters, certificate chain, TLS negotiation, transfer endpoint and network trace.
B:Reading a healthy CloudWatch log automatically erased every earlier record. That unrelated assertion does not explain the actual TLS for JDBC and data movement paths risk. The relevant failure is that encrypting S3 target objects does not protect unencrypted bytes before they reach AWS storage. Check jDBC SSL connection parameters, certificate chain, TLS negotiation, transfer endpoint and network trace.
D:Inspecting an existing Athena query plan itself deleted every production table. That unrelated assertion does not explain the actual TLS for JDBC and data movement paths risk. The relevant failure is that encrypting S3 target objects does not protect unencrypted bytes before they reach AWS storage. Check jDBC SSL connection parameters, certificate chain, TLS negotiation, transfer endpoint and network trace.