Amazon AWS Certified Data Engineer - Associate DEA-C01 Practice Test 107
Question 1060
A new Redshift role has USAGE on a schema yet cannot query a table because SELECT was never granted. Why does the correct approach fit this workflow boundary?
- 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 database schema visibility and permission to read or modify specific table objects are separate controls.
- 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.
Explanation
Correct Answer
B:Implement by choosing to configure database roles with explicit schema and table privileges according to the access requirement. Verify with redshift role membership, schema USAGE, table SELECT, denied DDL and query audit.
Incorrect Answers
A:A successful IAM login means every analytics dataset is readable and correctly transformed. That generalization conflicts with Redshift database roles and schema grants. Instead database schema visibility and permission to read or modify specific table objects are separate controls. Check redshift role membership, schema USAGE, table SELECT, denied DDL and query audit.
C:Increasing a resource name length automatically increases AWS service throughput. That generalization conflicts with Redshift database roles and schema grants. Instead database schema visibility and permission to read or modify specific table objects are separate controls. Check redshift role membership, schema USAGE, table SELECT, denied DDL and query audit.
D:A pipeline schedule guarantees that every downstream source record was processed correctly. That generalization conflicts with Redshift database roles and schema grants. Instead database schema visibility and permission to read or modify specific table objects are separate controls. Check redshift role membership, schema USAGE, table SELECT, denied DDL and query audit.
Question 1061
A new Redshift role has USAGE on a schema yet cannot query a table because SELECT was never granted. An incorrect proposal is: Assume USAGE on schema automatically allows modifying every table. What operational defect would the misguided change introduce?
- 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 granting broad SUPERUSER privileges to fix one SELECT failure violates least privilege.
- 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.
Explanation
Correct Answer
B:This is why the incorrect shortcut does not meet Redshift database roles and schema grants. The safer implementation is to configure database roles with explicit schema and table privileges according to the access requirement.
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 Redshift database roles and schema grants risk. The relevant failure is that granting broad SUPERUSER privileges to fix one SELECT failure violates least privilege. Check redshift role membership, schema USAGE, table SELECT, denied DDL and query audit.
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 Redshift database roles and schema grants risk. The relevant failure is that granting broad SUPERUSER privileges to fix one SELECT failure violates least privilege. Check redshift role membership, schema USAGE, table SELECT, denied DDL and query audit.
D:Reading a healthy CloudWatch log automatically erased every earlier record. That unrelated assertion does not explain the actual Redshift database roles and schema grants risk. The relevant failure is that granting broad SUPERUSER privileges to fix one SELECT failure violates least privilege. Check redshift role membership, schema USAGE, table SELECT, denied DDL and query audit.
Question 1062
A new Redshift role has USAGE on a schema yet cannot query a table because SELECT was never granted. The observed failure is: Granting broad SUPERUSER privileges to fix one SELECT failure violates least privilege. What focused remediation preserves the intended data contract?
- The supported recovery step is to disable audit logging to avoid recording access-denied requests.
- The supported recovery step is to grant the minimum role permissions and test an intended read and a denied DDL or cross-schema query.
- The supported recovery step is to assume USAGE on schema automatically allows modifying every table.
- The supported recovery step is to give all dashboard viewers full Redshift superuser access.
Explanation
Correct Answer
B:This addresses the observed Redshift database roles and schema grants failure while preserving the required contract. Recheck redshift role membership, schema USAGE, table SELECT, denied DDL and query audit.
Incorrect Answers
A:Disable audit logging to avoid recording access-denied requests. Granting broad SUPERUSER privileges to fix one SELECT failure violates least privilege. Instead grant the minimum role permissions and test an intended read and a denied DDL or cross-schema query.
C:Assume USAGE on schema automatically allows modifying every table. Granting broad SUPERUSER privileges to fix one SELECT failure violates least privilege. Instead grant the minimum role permissions and test an intended read and a denied DDL or cross-schema query.
D:Give all dashboard viewers full Redshift superuser access. Granting broad SUPERUSER privileges to fix one SELECT failure violates least privilege. Instead grant the minimum role permissions and test an intended read and a denied DDL or cross-schema query.
Question 1063
A growing lake has hundreds of tables that need consistent access by confidentiality classification. Which controlled service choice should the engineer make to meet this requirement?
- Assume an S3 object tag automatically grants all Lake Formation table permissions.
- Use Lake Formation LF-Tags and tag-based policy grants that map governed classifications to eligible principal roles.
- Make all tables public rather than checking LF-Tag expressions.
- Copy a permissive grant to every new table without classification review.
Explanation
Correct Answer
B:Validate with lF-Tag key/value, table tag assignment, principal LF permissions and allowed or denied query. This directly addresses Lake Formation LF tags and attribute-based grants.
Incorrect Answers
A:A wrong or missing classification tag can produce unintended access or loss of required permissions. This does not meet Lake Formation LF tags and attribute-based grants.
C:LF-Tags support attribute-based governance without repeating every individual table grant. Inspect lF-Tag key/value, table tag assignment, principal LF permissions and allowed or denied query.
D:A wrong or missing classification tag can produce unintended access or loss of required permissions. The appropriate action is to use Lake Formation LF-Tags and tag-based policy grants that map governed classifications to eligible principal roles.
Question 1064
A growing lake has hundreds of tables that need consistent access by confidentiality classification. Which metrics or records most directly prove the required behavior?
- LF-Tag key/value, table tag assignment, principal LF permissions and allowed or denied query.
- A renamed resource label that does not show an authorization or processing result.
- 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
A:These observations directly test Lake Formation LF tags and attribute-based grants. LF-Tags support attribute-based governance without repeating every individual table grant.
Incorrect Answers
B:A renamed resource label that does not show an authorization or processing result. This is not sufficient evidence for Lake Formation LF tags and attribute-based grants. Check lF-Tag key/value, table tag assignment, principal LF permissions and allowed or denied query. LF-Tags support attribute-based governance without repeating every individual table grant.
C:A browser screenshot from another AWS account and time period. This is not sufficient evidence for Lake Formation LF tags and attribute-based grants. Check lF-Tag key/value, table tag assignment, principal LF permissions and allowed or denied query. LF-Tags support attribute-based governance without repeating every individual table grant.
D:An old architecture drawing without the current query plan or job-run identifier. This is not sufficient evidence for Lake Formation LF tags and attribute-based grants. Check lF-Tag key/value, table tag assignment, principal LF permissions and allowed or denied query. LF-Tags support attribute-based governance without repeating every individual table grant.
Question 1065
A growing lake has hundreds of tables that need consistent access by confidentiality classification. Why does the correct approach fit this workflow boundary?
- A CloudWatch metric label is equivalent to a successful target table data-quality validation.
- Increasing a resource name length automatically increases AWS service throughput.
- LF-Tags support attribute-based governance without repeating every individual table grant.
- A pipeline schedule guarantees that every downstream source record was processed correctly.
Explanation
Correct Answer
C:Implement by choosing to use Lake Formation LF-Tags and tag-based policy grants that map governed classifications to eligible principal roles. This is the relevant technical mechanism for Lake Formation LF tags and attribute-based grants.
Incorrect Answers
A:A CloudWatch metric label is equivalent to a successful target table data-quality validation. That generalization conflicts with Lake Formation LF tags and attribute-based grants. Instead lF-Tags support attribute-based governance without repeating every individual table grant. Check lF-Tag key/value, table tag assignment, principal LF permissions and allowed or denied query.
B:Increasing a resource name length automatically increases AWS service throughput. That generalization conflicts with Lake Formation LF tags and attribute-based grants. Instead lF-Tags support attribute-based governance without repeating every individual table grant. Check lF-Tag key/value, table tag assignment, principal LF permissions and allowed or denied query.
D:A pipeline schedule guarantees that every downstream source record was processed correctly. That generalization conflicts with Lake Formation LF tags and attribute-based grants. Instead lF-Tags support attribute-based governance without repeating every individual table grant. Check lF-Tag key/value, table tag assignment, principal LF permissions and allowed or denied query.
Question 1066
A growing lake has hundreds of tables that need consistent access by confidentiality classification. An incorrect proposal is: Assume an S3 object tag automatically grants all Lake Formation table permissions. What operational defect would the misguided change introduce?
- A wrong or missing classification tag can produce unintended access or loss of required permissions.
- 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.
Explanation
Correct Answer
A:This is why the incorrect shortcut does not meet Lake Formation LF tags and attribute-based grants. LF-Tags support attribute-based governance without repeating every individual table grant.
Incorrect Answers
B:A correctly encrypted S3 test object was the sole cause of an unrelated ISP outage. That unrelated assertion does not explain the actual Lake Formation LF tags and attribute-based grants risk. The relevant failure is that a wrong or missing classification tag can produce unintended access or loss of required permissions. Check lF-Tag key/value, table tag assignment, principal LF permissions and allowed or denied query.
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 Lake Formation LF tags and attribute-based grants risk. The relevant failure is that a wrong or missing classification tag can produce unintended access or loss of required permissions. Check lF-Tag key/value, table tag assignment, principal LF permissions and allowed or denied query.
D:The presence of an accurate job timestamp automatically created unauthorized database credentials. That unrelated assertion does not explain the actual Lake Formation LF tags and attribute-based grants risk. The relevant failure is that a wrong or missing classification tag can produce unintended access or loss of required permissions. Check lF-Tag key/value, table tag assignment, principal LF permissions and allowed or denied query.
Question 1067
A growing lake has hundreds of tables that need consistent access by confidentiality classification. The observed failure is: A wrong or missing classification tag can produce unintended access or loss of required permissions. What focused remediation preserves the intended data contract?
- Make all tables public rather than checking LF-Tag expressions.
- Review tag assignment and test allowed and forbidden tables for a role before production rollout.
- Copy a permissive grant to every new table without classification review.
- Assume an S3 object tag automatically grants all Lake Formation table permissions.
Explanation
Correct Answer
B:This addresses the observed Lake Formation LF tags and attribute-based grants failure while preserving the required contract. LF-Tags support attribute-based governance without repeating every individual table grant.
Incorrect Answers
A:Make all tables public rather than checking LF-Tag expressions. A wrong or missing classification tag can produce unintended access or loss of required permissions. Instead review tag assignment and test allowed and forbidden tables for a role before production rollout.
C:Copy a permissive grant to every new table without classification review. A wrong or missing classification tag can produce unintended access or loss of required permissions. Instead review tag assignment and test allowed and forbidden tables for a role before production rollout.
D:Assume an S3 object tag automatically grants all Lake Formation table permissions. A wrong or missing classification tag can produce unintended access or loss of required permissions. Instead review tag assignment and test allowed and forbidden tables for a role before production rollout.
Question 1068
A new table marked restricted is mistakenly shared because grants were individually copied from public tables. What architecture action addresses the stated source-to-target behavior?
- In this operational case, make all tables public rather than checking LF-Tag expressions.
- In this operational case, copy a permissive grant to every new table without classification review.
- In this operational case, assume an S3 object tag automatically grants all Lake Formation table permissions.
- In this operational case, use Lake Formation LF-Tags and tag-based policy grants that map governed classifications to eligible principal roles.
Explanation
Correct Answer
D:Validate with lF-Tag key/value, table tag assignment, principal LF permissions and allowed or denied query. LF-Tags support attribute-based governance without repeating every individual table grant.
Incorrect Answers
A:LF-Tags support attribute-based governance without repeating every individual table grant. Make all tables public rather than checking LF-Tag expressions.
B:A wrong or missing classification tag can produce unintended access or loss of required permissions. Copy a permissive grant to every new table without classification review.
C:A wrong or missing classification tag can produce unintended access or loss of required permissions. The supported design is to use Lake Formation LF-Tags and tag-based policy grants that map governed classifications to eligible principal roles.
Question 1069
A new table marked restricted is mistakenly shared because grants were individually copied from public tables. What validation evidence distinguishes a correct implementation from a dashboard-only change?
- The relevant validation evidence is a resource ARN alone without any current data-plane observation.
- The relevant validation evidence is a renamed resource label that does not show an authorization or processing result.
- The relevant validation evidence is lF-Tag key/value, table tag assignment, principal LF permissions and allowed or denied query.
- The relevant validation evidence is a browser screenshot from another AWS account and time period.
Explanation
Correct Answer
C:These observations directly test Lake Formation LF tags and attribute-based grants. In this specific operating situation, a new table marked restricted is mistakenly shared because grants were individually copied from public tables.
Incorrect Answers
A:A resource ARN alone without any current data-plane observation. This is not sufficient evidence for Lake Formation LF tags and attribute-based grants. Check lF-Tag key/value, table tag assignment, principal LF permissions and allowed or denied query. LF-Tags support attribute-based governance without repeating every individual table grant.
B:A renamed resource label that does not show an authorization or processing result. This is not sufficient evidence for Lake Formation LF tags and attribute-based grants. Check lF-Tag key/value, table tag assignment, principal LF permissions and allowed or denied query. LF-Tags support attribute-based governance without repeating every individual table grant.
D:A browser screenshot from another AWS account and time period. This is not sufficient evidence for Lake Formation LF tags and attribute-based grants. Check lF-Tag key/value, table tag assignment, principal LF permissions and allowed or denied query. LF-Tags support attribute-based governance without repeating every individual table grant.
Question 1070
A new table marked restricted is mistakenly shared because grants were individually copied from public tables. Which design principle is consistent with the stated data-processing contract?
- 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 lF-Tags support attribute-based governance without repeating every individual table grant.
- The governing design principle is that every AWS managed service uses the same consistency, retry and query-processing semantics.
Explanation
Correct Answer
C:Implement by choosing to use Lake Formation LF-Tags and tag-based policy grants that map governed classifications to eligible principal roles. Verify with lF-Tag key/value, table tag assignment, principal LF permissions and allowed or denied query.
Incorrect Answers
A:A pipeline schedule guarantees that every downstream source record was processed correctly. That generalization conflicts with Lake Formation LF tags and attribute-based grants. Instead lF-Tags support attribute-based governance without repeating every individual table grant. Check lF-Tag key/value, table tag assignment, principal LF permissions and allowed or denied query.
B:A CloudWatch metric label is equivalent to a successful target table data-quality validation. That generalization conflicts with Lake Formation LF tags and attribute-based grants. Instead lF-Tags support attribute-based governance without repeating every individual table grant. Check lF-Tag key/value, table tag assignment, principal LF permissions and allowed or denied query.
D:Every AWS managed service uses the same consistency, retry and query-processing semantics. That generalization conflicts with Lake Formation LF tags and attribute-based grants. Instead lF-Tags support attribute-based governance without repeating every individual table grant. Check lF-Tag key/value, table tag assignment, principal LF permissions and allowed or denied query.