Amazon AWS Certified Data Engineer - Associate DEA-C01 Practice Test 106
Question 1050
Two teams share one lake table while tenant-specific row filters must prevent cross-tenant disclosure. What diagnostic observations should be checked before marking the change successful?
- 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 lake Formation grants, data filter definition, Athena principal, permitted query projection and denied row test.
Explanation
Correct Answer
D:Lake Formation can govern access to cataloged tables and finer-grained data independent of SQL text preference.
Incorrect Answers
A:A successful ping to an unrelated service that did not process the data. This is not sufficient evidence for Lake Formation table column and row permissions. Check lake Formation grants, data filter definition, Athena principal, permitted query projection and denied row test. Lake Formation can govern access to cataloged tables and finer-grained data independent of SQL text preference.
B:A resource ARN alone without any current data-plane observation. This is not sufficient evidence for Lake Formation table column and row permissions. Check lake Formation grants, data filter definition, Athena principal, permitted query projection and denied row test. Lake Formation can govern access to cataloged tables and finer-grained data independent of SQL text preference.
C:A dashboard color with no source event or data row evidence. This is not sufficient evidence for Lake Formation table column and row permissions. Check lake Formation grants, data filter definition, Athena principal, permitted query projection and denied row test. Lake Formation can govern access to cataloged tables and finer-grained data independent of SQL text preference.
Question 1051
Two teams share one lake table while tenant-specific row filters must prevent cross-tenant disclosure. An incorrect proposal is: Grant SELECT on all tables and columns to all analysts to avoid one denial. Which failure consequence BEST shows why that proposal is inappropriate?
- 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 inspecting an existing Athena query plan itself deleted every production table.
- The concrete failure is that giving S3 read permission alone should not be treated as a complete governed-query authorization strategy.
Explanation
Correct Answer
D:Lake Formation can govern access to cataloged tables and finer-grained data independent of SQL text preference. This is why the incorrect shortcut does not meet Lake Formation table column and row permissions.
Incorrect Answers
A:That unrelated assertion does not explain the actual Lake Formation table column and row permissions risk. The relevant failure is that giving S3 read permission alone should not be treated as a complete governed-query authorization strategy.
B:That unrelated assertion does not explain the actual Lake Formation table column and row permissions risk. Check lake Formation grants, data filter definition, Athena principal, permitted query projection and denied row test.
C:That unrelated assertion does not explain the actual Lake Formation table column and row permissions risk.
Question 1052
Two teams share one lake table while tenant-specific row filters must prevent cross-tenant disclosure. The observed failure is: Giving S3 read permission alone should not be treated as a complete governed-query authorization strategy. How should the team correct and verify the observed fault?
- The supported recovery step is to use an S3 object tag as automatic row-level authorization in Athena.
- The supported recovery step is to grant SELECT on all tables and columns to all analysts to avoid one denial.
- The supported recovery step is to create a narrowly scoped data filter and test an allowed column, denied sensitive field and excluded tenant rows.
- The supported recovery step is to assume hiding a column in a dashboard removes storage-level access.
Explanation
Correct Answer
C:This addresses the observed Lake Formation table column and row permissions failure while preserving the required contract. Recheck lake Formation grants, data filter definition, Athena principal, permitted query projection and denied row test.
Incorrect Answers
A:Use an S3 object tag as automatic row-level authorization in Athena. Giving S3 read permission alone should not be treated as a complete governed-query authorization strategy. Instead create a narrowly scoped data filter and test an allowed column, denied sensitive field and excluded tenant rows.
B:Grant SELECT on all tables and columns to all analysts to avoid one denial. Giving S3 read permission alone should not be treated as a complete governed-query authorization strategy. Instead create a narrowly scoped data filter and test an allowed column, denied sensitive field and excluded tenant rows.
D:Assume hiding a column in a dashboard removes storage-level access. Giving S3 read permission alone should not be treated as a complete governed-query authorization strategy. Instead create a narrowly scoped data filter and test an allowed column, denied sensitive field and excluded tenant rows.
Question 1053
A reporting user needs SELECT on a curated schema but can currently modify production fact tables. What is the MOST appropriate targeted implementation for this data-engineering situation?
- Assume USAGE on schema automatically allows modifying every table.
- Give all dashboard viewers full Redshift superuser access.
- Configure database roles with explicit schema and table privileges according to the access requirement.
- Disable audit logging to avoid recording access-denied requests.
Explanation
Correct Answer
C:Database schema visibility and permission to read or modify specific table objects are separate controls. This directly addresses Redshift database roles and schema grants.
Incorrect Answers
A:Assume USAGE on schema automatically allows modifying every table. This does not meet Redshift database roles and schema grants. Granting broad SUPERUSER privileges to fix one SELECT failure violates least privilege. The supported design is to configure database roles with explicit schema and table privileges according to the access requirement.
B:Give all dashboard viewers full Redshift superuser access. Database schema visibility and permission to read or modify specific table objects are separate controls. Inspect redshift role membership, schema USAGE, table SELECT, denied DDL and query audit.
D:Disable audit logging to avoid recording access-denied requests. This leaves the relevant data-engineering requirement unresolved. Granting broad SUPERUSER privileges to fix one SELECT failure violates least privilege. The appropriate action is to configure database roles with explicit schema and table privileges according to the access requirement.
Question 1054
A reporting user needs SELECT on a curated schema but can currently modify production fact tables. What diagnostic observations should be checked before marking the change successful?
- Redshift role membership, schema USAGE, table SELECT, denied DDL and query audit.
- 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.
Explanation
Correct Answer
A:Database schema visibility and permission to read or modify specific table objects are separate controls. These observations directly test Redshift database roles and schema grants.
Incorrect Answers
B:A successful ping to an unrelated service that did not process the data. This is not sufficient evidence for Redshift database roles and schema grants. Check redshift role membership, schema USAGE, table SELECT, denied DDL and query audit. Database schema visibility and permission to read or modify specific table objects are separate controls.
C:An old architecture drawing without the current query plan or job-run identifier. This is not sufficient evidence for Redshift database roles and schema grants. Check redshift role membership, schema USAGE, table SELECT, denied DDL and query audit. Database schema visibility and permission to read or modify specific table objects are separate controls.
D:A dashboard color with no source event or data row evidence. This is not sufficient evidence for Redshift database roles and schema grants. Check redshift role membership, schema USAGE, table SELECT, denied DDL and query audit. Database schema visibility and permission to read or modify specific table objects are separate controls.
Question 1055
A reporting user needs SELECT on a curated schema but can currently modify production fact tables. What technical statement accurately describes the relevant AWS processing behavior?
- Increasing a resource name length automatically increases AWS service throughput.
- 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.
- Database schema visibility and permission to read or modify specific table objects are separate controls.
Explanation
Correct Answer
D:Implement by choosing to configure database roles with explicit schema and table privileges according to the access requirement. This is the relevant technical mechanism for Redshift database roles and schema grants.
Incorrect Answers
A: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.
B:An S3 bucket prefix guarantees exactly-once multi-service transactions without an output commit. 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: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.
Question 1056
A reporting user needs SELECT on a curated schema but can currently modify production fact tables. An incorrect proposal is: Assume USAGE on schema automatically allows modifying every table. Which failure consequence BEST shows why that proposal is inappropriate?
- The dashboard theme independently caused an unrelated source database failure.
- Granting broad SUPERUSER privileges to fix one SELECT failure violates least privilege.
- 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 Redshift database roles and schema grants. Database schema visibility and permission to read or modify specific table objects are separate controls.
Incorrect Answers
A:The dashboard theme independently caused an unrelated source database failure. 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: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.
D: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.
Question 1057
A reporting user needs SELECT on a curated schema but can currently modify production fact tables. The observed failure is: Granting broad SUPERUSER privileges to fix one SELECT failure violates least privilege. How should the team correct and verify the observed fault?
- Give all dashboard viewers full Redshift superuser access.
- Grant the minimum role permissions and test an intended read and a denied DDL or cross-schema query.
- Disable audit logging to avoid recording access-denied requests.
- Assume USAGE on schema automatically allows modifying every table.
Explanation
Correct Answer
B:This addresses the observed Redshift database roles and schema grants failure while preserving the required contract. Database schema visibility and permission to read or modify specific table objects are separate controls.
Incorrect Answers
A: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.
C: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.
D: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.
Question 1058
A new Redshift role has USAGE on a schema yet cannot query a table because SELECT was never granted. Which controlled service choice should the engineer make to meet this requirement?
- In this operational case, give all dashboard viewers full Redshift superuser access.
- In this operational case, disable audit logging to avoid recording access-denied requests.
- In this operational case, assume USAGE on schema automatically allows modifying every table.
- In this operational case, configure database roles with explicit schema and table privileges according to the access requirement.
Explanation
Correct Answer
D:Database schema visibility and permission to read or modify specific table objects are separate controls. Validate with redshift role membership, schema USAGE, table SELECT, denied DDL and query audit.
Incorrect Answers
A:Give all dashboard viewers full Redshift superuser access. Database schema visibility and permission to read or modify specific table objects are separate controls. Inspect redshift role membership, schema USAGE, table SELECT, denied DDL and query audit.
B:Disable audit logging to avoid recording access-denied requests. This leaves the relevant data-engineering requirement unresolved. Granting broad SUPERUSER privileges to fix one SELECT failure violates least privilege. The appropriate action is to configure database roles with explicit schema and table privileges according to the access requirement.
C:Assume USAGE on schema automatically allows modifying every table. This does not meet Redshift database roles and schema grants. Granting broad SUPERUSER privileges to fix one SELECT failure violates least privilege. The supported design is to configure database roles with explicit schema and table privileges according to the access requirement.
Question 1059
A new Redshift role has USAGE on a schema yet cannot query a table because SELECT was never granted. Which metrics or records most directly prove the required behavior?
- 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 redshift role membership, schema USAGE, table SELECT, denied DDL and query audit.
- The relevant validation evidence is an old architecture drawing without the current query plan or job-run identifier.
Explanation
Correct Answer
C:Database schema visibility and permission to read or modify specific table objects are separate controls.
Incorrect Answers
A:A renamed resource label that does not show an authorization or processing result. This is not sufficient evidence for Redshift database roles and schema grants. Check redshift role membership, schema USAGE, table SELECT, denied DDL and query audit. Database schema visibility and permission to read or modify specific table objects are separate controls.
B:A successful ping to an unrelated service that did not process the data. This is not sufficient evidence for Redshift database roles and schema grants. Check redshift role membership, schema USAGE, table SELECT, denied DDL and query audit. Database schema visibility and permission to read or modify specific table objects are separate controls.
D:An old architecture drawing without the current query plan or job-run identifier. This is not sufficient evidence for Redshift database roles and schema grants. Check redshift role membership, schema USAGE, table SELECT, denied DDL and query audit. Database schema visibility and permission to read or modify specific table objects are separate controls.
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.