Amazon AWS Certified Data Engineer - Associate DEA-C01 Practice Test 112
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.
Question 1111
A file-transfer partner uses unencrypted FTP and an ETL stage stores sensitive payloads in transit. The observed failure is: Encrypting S3 target objects does not protect unencrypted bytes before they reach AWS storage. Which response repairs the underlying problem without unnecessary privilege or data loss?
- The supported recovery step is to use plaintext FTP over the internet because downstream storage is encrypted.
- The supported recovery step is to disable database certificate validation permanently to resolve a hostname error.
- The supported recovery step is to assume S3 SSE-KMS automatically encrypts an unrelated source-side JDBC socket.
- The supported recovery step is to 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. Recheck jDBC SSL connection parameters, certificate chain, TLS negotiation, transfer endpoint and network trace.
Incorrect Answers
A: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.
B: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.
C: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.
Question 1112
An analytics dataset contains personal identity numbers that ordinary reporting users must not see. What architecture action addresses the stated source-to-target behavior?
- Assume a column named secret is automatically masked in every database query.
- Copy production PII unchanged into open development datasets for convenience.
- Apply supported masking, pseudonymization or tokenization as required with separation of sensitive mapping secrets.
- Store reversible token mappings in the same public analytics table as the tokens.
Explanation
Correct Answer
C:Validate with source and derived field sample, masking policy, re-identification access, data lineage and negative query test. Masking replaces or obscures sensitive values while controlled reversible tokenization needs separately protected mappings.
Incorrect Answers
A:Hashing predictable identifiers without salt or access controls may permit re-identification and leak sensitive information. This does not meet Sensitive field masking and tokenization in curated data.
B:Copy production PII unchanged into open development datasets for convenience. Masking replaces or obscures sensitive values while controlled reversible tokenization needs separately protected mappings. Inspect source and derived field sample, masking policy, re-identification access, data lineage and negative query test.
D:Hashing predictable identifiers without salt or access controls may permit re-identification and leak sensitive information. The appropriate action is to apply supported masking, pseudonymization or tokenization as required with separation of sensitive mapping secrets.
Question 1113
An analytics dataset contains personal identity numbers that ordinary reporting users must not see. What validation evidence distinguishes a correct implementation from a dashboard-only change?
- 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.
- Source and derived field sample, masking policy, re-identification access, data lineage and negative query test.
Explanation
Correct Answer
D:Masking replaces or obscures sensitive values while controlled reversible tokenization needs separately protected mappings. These observations directly test Sensitive field masking and tokenization in curated data.
Incorrect Answers
A:A successful ping to an unrelated service that did not process the data. This is not sufficient evidence for Sensitive field masking and tokenization in curated data. Check source and derived field sample, masking policy, re-identification access, data lineage and negative query test. Masking replaces or obscures sensitive values while controlled reversible tokenization needs separately protected mappings.
B:An old architecture drawing without the current query plan or job-run identifier. This is not sufficient evidence for Sensitive field masking and tokenization in curated data. Check source and derived field sample, masking policy, re-identification access, data lineage and negative query test. Masking replaces or obscures sensitive values while controlled reversible tokenization needs separately protected mappings.
C:A dashboard color with no source event or data row evidence. This is not sufficient evidence for Sensitive field masking and tokenization in curated data. Check source and derived field sample, masking policy, re-identification access, data lineage and negative query test. Masking replaces or obscures sensitive values while controlled reversible tokenization needs separately protected mappings.
Question 1114
An analytics dataset contains personal identity numbers that ordinary reporting users must not see. Which design principle is consistent with the stated data-processing contract?
- Increasing a resource name length automatically increases AWS service throughput.
- Masking replaces or obscures sensitive values while controlled reversible tokenization needs separately protected mappings.
- An S3 bucket prefix guarantees exactly-once multi-service transactions without an output commit.
- A successful IAM login means every analytics dataset is readable and correctly transformed.
Explanation
Correct Answer
B:This is the relevant technical mechanism for Sensitive field masking and tokenization in curated data. Implement by choosing to apply supported masking, pseudonymization or tokenization as required with separation of sensitive mapping secrets.
Incorrect Answers
A:Increasing a resource name length automatically increases AWS service throughput. That generalization conflicts with Sensitive field masking and tokenization in curated data. Instead masking replaces or obscures sensitive values while controlled reversible tokenization needs separately protected mappings. Check source and derived field sample, masking policy, re-identification access, data lineage and negative query test.
C:An S3 bucket prefix guarantees exactly-once multi-service transactions without an output commit. That generalization conflicts with Sensitive field masking and tokenization in curated data. Instead masking replaces or obscures sensitive values while controlled reversible tokenization needs separately protected mappings. Check source and derived field sample, masking policy, re-identification access, data lineage and negative query test.
D:A successful IAM login means every analytics dataset is readable and correctly transformed. That generalization conflicts with Sensitive field masking and tokenization in curated data. Instead masking replaces or obscures sensitive values while controlled reversible tokenization needs separately protected mappings. Check source and derived field sample, masking policy, re-identification access, data lineage and negative query test.
Question 1115
An analytics dataset contains personal identity numbers that ordinary reporting users must not see. An incorrect proposal is: Assume a column named secret is automatically masked in every database query. What issue should reviewers anticipate if the shortcut is adopted?
- The dashboard theme independently caused an unrelated source database failure.
- Hashing predictable identifiers without salt or access controls may permit re-identification and leak sensitive information.
- 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
B:This is why the incorrect shortcut does not meet Sensitive field masking and tokenization in curated data. Masking replaces or obscures sensitive values while controlled reversible tokenization needs separately protected mappings.
Incorrect Answers
A:The dashboard theme independently caused an unrelated source database failure. That unrelated assertion does not explain the actual Sensitive field masking and tokenization in curated data risk. The relevant failure is that hashing predictable identifiers without salt or access controls may permit re-identification and leak sensitive information. Check source and derived field sample, masking policy, re-identification access, data lineage and negative query test.
C:Reading a healthy CloudWatch log automatically erased every earlier record. That unrelated assertion does not explain the actual Sensitive field masking and tokenization in curated data risk. The relevant failure is that hashing predictable identifiers without salt or access controls may permit re-identification and leak sensitive information. Check source and derived field sample, masking policy, re-identification access, data lineage and negative query test.
D:A correctly encrypted S3 test object was the sole cause of an unrelated ISP outage. That unrelated assertion does not explain the actual Sensitive field masking and tokenization in curated data risk. The relevant failure is that hashing predictable identifiers without salt or access controls may permit re-identification and leak sensitive information. Check source and derived field sample, masking policy, re-identification access, data lineage and negative query test.
Question 1116
An analytics dataset contains personal identity numbers that ordinary reporting users must not see. The observed failure is: Hashing predictable identifiers without salt or access controls may permit re-identification and leak sensitive information. Which response repairs the underlying problem without unnecessary privilege or data loss?
- Copy production PII unchanged into open development datasets for convenience.
- Enforce and test field-level redaction and ensure authorized reconstruction is constrained where needed.
- Store reversible token mappings in the same public analytics table as the tokens.
- Assume a column named secret is automatically masked in every database query.
Explanation
Correct Answer
B:This addresses the observed Sensitive field masking and tokenization in curated data failure while preserving the required contract. Masking replaces or obscures sensitive values while controlled reversible tokenization needs separately protected mappings.
Incorrect Answers
A:Copy production PII unchanged into open development datasets for convenience. Hashing predictable identifiers without salt or access controls may permit re-identification and leak sensitive information. Instead enforce and test field-level redaction and ensure authorized reconstruction is constrained where needed.
C:Store reversible token mappings in the same public analytics table as the tokens. Hashing predictable identifiers without salt or access controls may permit re-identification and leak sensitive information. Instead enforce and test field-level redaction and ensure authorized reconstruction is constrained where needed.
D:Assume a column named secret is automatically masked in every database query. Hashing predictable identifiers without salt or access controls may permit re-identification and leak sensitive information. Instead enforce and test field-level redaction and ensure authorized reconstruction is constrained where needed.
Question 1117
A test environment copies real production PII without redaction and violates privacy policy. Which AWS design or configuration BEST satisfies the stated processing requirement?
- In this operational case, copy production PII unchanged into open development datasets for convenience.
- In this operational case, store reversible token mappings in the same public analytics table as the tokens.
- In this operational case, apply supported masking, pseudonymization or tokenization as required with separation of sensitive mapping secrets.
- In this operational case, assume a column named secret is automatically masked in every database query.
Explanation
Correct Answer
C:Validate with source and derived field sample, masking policy, re-identification access, data lineage and negative query test. This directly addresses Sensitive field masking and tokenization in curated data.
Incorrect Answers
A:Copy production PII unchanged into open development datasets for convenience. Masking replaces or obscures sensitive values while controlled reversible tokenization needs separately protected mappings. Inspect source and derived field sample, masking policy, re-identification access, data lineage and negative query test.
B:Hashing predictable identifiers without salt or access controls may permit re-identification and leak sensitive information.
D:Hashing predictable identifiers without salt or access controls may permit re-identification and leak sensitive information. The supported design is to apply supported masking, pseudonymization or tokenization as required with separation of sensitive mapping secrets.
Question 1118
A test environment copies real production PII without redaction and violates privacy policy. Which evidence would BEST verify that the intended pipeline outcome occurred?
- The relevant validation evidence is source and derived field sample, masking policy, re-identification access, data lineage and negative query test.
- The relevant validation evidence is a renamed resource label that does not show an authorization or processing result.
- 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
A:Masking replaces or obscures sensitive values while controlled reversible tokenization needs separately protected mappings.
Incorrect Answers
B:A renamed resource label that does not show an authorization or processing result. This is not sufficient evidence for Sensitive field masking and tokenization in curated data. Check source and derived field sample, masking policy, re-identification access, data lineage and negative query test. Masking replaces or obscures sensitive values while controlled reversible tokenization needs separately protected mappings.
C:A successful ping to an unrelated service that did not process the data. This is not sufficient evidence for Sensitive field masking and tokenization in curated data. Check source and derived field sample, masking policy, re-identification access, data lineage and negative query test. Masking replaces or obscures sensitive values while controlled reversible tokenization needs separately protected mappings.
D:An old architecture drawing without the current query plan or job-run identifier. This is not sufficient evidence for Sensitive field masking and tokenization in curated data. Check source and derived field sample, masking policy, re-identification access, data lineage and negative query test. Masking replaces or obscures sensitive values while controlled reversible tokenization needs separately protected mappings.
Question 1119
A test environment copies real production PII without redaction and violates privacy policy. Which underlying AWS service principle BEST explains the recommended approach?
- 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 masking replaces or obscures sensitive values while controlled reversible tokenization needs separately protected mappings.
- The governing design principle is that a pipeline schedule guarantees that every downstream source record was processed correctly.
Explanation
Correct Answer
C:This is the relevant technical mechanism for Sensitive field masking and tokenization in curated data. Verify with source and derived field sample, masking policy, re-identification access, data lineage and negative query test.
Incorrect Answers
A:A successful IAM login means every analytics dataset is readable and correctly transformed. That generalization conflicts with Sensitive field masking and tokenization in curated data. Instead masking replaces or obscures sensitive values while controlled reversible tokenization needs separately protected mappings. Check source and derived field sample, masking policy, re-identification access, data lineage and negative query test.
B:Increasing a resource name length automatically increases AWS service throughput. That generalization conflicts with Sensitive field masking and tokenization in curated data. Instead masking replaces or obscures sensitive values while controlled reversible tokenization needs separately protected mappings. Check source and derived field sample, masking policy, re-identification access, data lineage and negative query test.
D:A pipeline schedule guarantees that every downstream source record was processed correctly. That generalization conflicts with Sensitive field masking and tokenization in curated data. Instead masking replaces or obscures sensitive values while controlled reversible tokenization needs separately protected mappings. Check source and derived field sample, masking policy, re-identification access, data lineage and negative query test.
Question 1120
A test environment copies real production PII without redaction and violates privacy policy. An incorrect proposal is: Assume a column named secret is automatically masked in every database query. What material risk would follow from the proposed incorrect shortcut?
- 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 hashing predictable identifiers without salt or access controls may permit re-identification and leak sensitive information.
- The concrete failure is that reading a healthy CloudWatch log automatically erased every earlier record.
Explanation
Correct Answer
C:This is why the incorrect shortcut does not meet Sensitive field masking and tokenization in curated data. The safer implementation is to apply supported masking, pseudonymization or tokenization as required with separation of sensitive mapping secrets.
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 Sensitive field masking and tokenization in curated data risk. The relevant failure is that hashing predictable identifiers without salt or access controls may permit re-identification and leak sensitive information. Check source and derived field sample, masking policy, re-identification access, data lineage and negative query test.
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 Sensitive field masking and tokenization in curated data risk. The relevant failure is that hashing predictable identifiers without salt or access controls may permit re-identification and leak sensitive information. Check source and derived field sample, masking policy, re-identification access, data lineage and negative query test.
D:Reading a healthy CloudWatch log automatically erased every earlier record. That unrelated assertion does not explain the actual Sensitive field masking and tokenization in curated data risk. The relevant failure is that hashing predictable identifiers without salt or access controls may permit re-identification and leak sensitive information. Check source and derived field sample, masking policy, re-identification access, data lineage and negative query test.