Amazon AWS Certified Data Engineer - Associate DEA-C01 Practice Test 101
Question 1000
A cross-account ETL job requires temporary permissions to a curated S3 dataset without sharing producer account keys. Which evidence would BEST verify that the intended pipeline outcome occurred?
- 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 trust policy principal, role permission policy, STS identity, expiry and CloudTrail access events.
- The relevant validation evidence is an old architecture drawing without the current query plan or job-run identifier.
Explanation
Correct Answer
C:IAM roles can supply temporary credentials for supported AWS workloads while trust and permission policies serve different checks.
Incorrect Answers
A:A renamed resource label that does not show an authorization or processing result. This is not sufficient evidence for IAM execution roles and STS temporary credentials for ETL. Check trust policy principal, role permission policy, STS identity, expiry and CloudTrail access events. IAM roles can supply temporary credentials for supported AWS workloads while trust and permission policies serve different checks.
B:A successful ping to an unrelated service that did not process the data. This is not sufficient evidence for IAM execution roles and STS temporary credentials for ETL. Check trust policy principal, role permission policy, STS identity, expiry and CloudTrail access events. IAM roles can supply temporary credentials for supported AWS workloads while trust and permission policies serve different checks.
D:An old architecture drawing without the current query plan or job-run identifier. This is not sufficient evidence for IAM execution roles and STS temporary credentials for ETL. Check trust policy principal, role permission policy, STS identity, expiry and CloudTrail access events. IAM roles can supply temporary credentials for supported AWS workloads while trust and permission policies serve different checks.
Question 1001
A cross-account ETL job requires temporary permissions to a curated S3 dataset without sharing producer account keys. Which underlying AWS service principle BEST explains the recommended approach?
- The governing design principle is that iAM roles can supply temporary credentials for supported AWS workloads while trust and permission policies serve different checks.
- 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.
Explanation
Correct Answer
A:This is the relevant technical mechanism for IAM execution roles and STS temporary credentials for ETL. Verify with trust policy principal, role permission policy, STS identity, expiry and CloudTrail access events.
Incorrect Answers
B:A successful IAM login means every analytics dataset is readable and correctly transformed. That generalization conflicts with IAM execution roles and STS temporary credentials for ETL. Instead iAM roles can supply temporary credentials for supported AWS workloads while trust and permission policies serve different checks. Check trust policy principal, role permission policy, STS identity, expiry and CloudTrail access events.
C:Increasing a resource name length automatically increases AWS service throughput. That generalization conflicts with IAM execution roles and STS temporary credentials for ETL. Instead iAM roles can supply temporary credentials for supported AWS workloads while trust and permission policies serve different checks. Check trust policy principal, role permission policy, STS identity, expiry and CloudTrail access events.
D:A pipeline schedule guarantees that every downstream source record was processed correctly. That generalization conflicts with IAM execution roles and STS temporary credentials for ETL. Instead iAM roles can supply temporary credentials for supported AWS workloads while trust and permission policies serve different checks. Check trust policy principal, role permission policy, STS identity, expiry and CloudTrail access events.
Question 1002
A cross-account ETL job requires temporary permissions to a curated S3 dataset without sharing producer account keys. An incorrect proposal is: Copy the producer administrator's long-lived access key into the consumer job. 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 embedding permanent keys in source code creates avoidable credential compromise and rotation risk.
- 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 IAM execution roles and STS temporary credentials for ETL. The safer implementation is to assign least-privilege IAM execution roles with supported STS assume-role trust and short-lived credentials.
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 IAM execution roles and STS temporary credentials for ETL risk. The relevant failure is that embedding permanent keys in source code creates avoidable credential compromise and rotation risk. Check trust policy principal, role permission policy, STS identity, expiry and CloudTrail access events.
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 IAM execution roles and STS temporary credentials for ETL risk. The relevant failure is that embedding permanent keys in source code creates avoidable credential compromise and rotation risk. Check trust policy principal, role permission policy, STS identity, expiry and CloudTrail access events.
D:Reading a healthy CloudWatch log automatically erased every earlier record. That unrelated assertion does not explain the actual IAM execution roles and STS temporary credentials for ETL risk. The relevant failure is that embedding permanent keys in source code creates avoidable credential compromise and rotation risk. Check trust policy principal, role permission policy, STS identity, expiry and CloudTrail access events.
Question 1003
A cross-account ETL job requires temporary permissions to a curated S3 dataset without sharing producer account keys. The observed failure is: Embedding permanent keys in source code creates avoidable credential compromise and rotation risk. Which recovery action BEST restores the required data-processing state?
- The supported recovery step is to replace keys with scoped roles and test allowed S3 reads and denied unrelated bucket access.
- The supported recovery step is to grant sts:AssumeRole on a principal without verifying the target role trust policy.
- The supported recovery step is to copy the producer administrator's long-lived access key into the consumer job.
- The supported recovery step is to assume a role permission policy alone lets every AWS account assume it.
Explanation
Correct Answer
A:This addresses the observed IAM execution roles and STS temporary credentials for ETL failure while preserving the required contract. Recheck trust policy principal, role permission policy, STS identity, expiry and CloudTrail access events.
Incorrect Answers
B:Grant sts:AssumeRole on a principal without verifying the target role trust policy. Embedding permanent keys in source code creates avoidable credential compromise and rotation risk. Instead replace keys with scoped roles and test allowed S3 reads and denied unrelated bucket access.
C:Copy the producer administrator's long-lived access key into the consumer job. Embedding permanent keys in source code creates avoidable credential compromise and rotation risk. Instead replace keys with scoped roles and test allowed S3 reads and denied unrelated bucket access.
D:Assume a role permission policy alone lets every AWS account assume it. Embedding permanent keys in source code creates avoidable credential compromise and rotation risk. Instead replace keys with scoped roles and test allowed S3 reads and denied unrelated bucket access.
Question 1004
A data warehouse ingestion service fails after a database password changes while its Glue job still uses an old hardcoded password. Which AWS design or configuration BEST satisfies the stated processing requirement?
- Put the database password into a public CloudFormation template parameter default.
- Store and rotate database credentials in Secrets Manager with authorized runtime retrieval and tested rotation behavior.
- Assume updating a secret value instantly changes every cached client connection.
- Disable all credential rotations because the first client used an old password.
Explanation
Correct Answer
B:Secrets Manager can maintain rotating credentials but applications must fetch valid versions and the database change must succeed. This directly addresses Secrets Manager database credential rotation and consumers.
Incorrect Answers
A:A successfully scheduled rotation without verified consumer retrieval can break ETL authentication. This does not meet Secrets Manager database credential rotation and consumers.
C:That option would assume updating a secret value instantly changes every cached client connection, but it addresses a different concern. Secrets Manager can maintain rotating credentials but applications must fetch valid versions and the database change must succeed.
D:A successfully scheduled rotation without verified consumer retrieval can break ETL authentication. The appropriate action is to store and rotate database credentials in Secrets Manager with authorized runtime retrieval and tested rotation behavior.
Question 1005
A data warehouse ingestion service fails after a database password changes while its Glue job still uses an old hardcoded password. Which evidence would BEST verify that the intended pipeline outcome occurred?
- A renamed resource label that does not show an authorization or processing result.
- A browser screenshot from another AWS account and time period.
- Secret version stages, rotation Lambda status, database login result, application cache TTL and CloudTrail reads.
- An old architecture drawing without the current query plan or job-run identifier.
Explanation
Correct Answer
C:Secrets Manager can maintain rotating credentials but applications must fetch valid versions and the database change must succeed. These observations directly test Secrets Manager database credential rotation and consumers.
Incorrect Answers
A:A renamed resource label that does not show an authorization or processing result. This is not sufficient evidence for Secrets Manager database credential rotation and consumers. Check secret version stages, rotation Lambda status, database login result, application cache TTL and CloudTrail reads. Secrets Manager can maintain rotating credentials but applications must fetch valid versions and the database change must succeed.
B:A browser screenshot from another AWS account and time period. This is not sufficient evidence for Secrets Manager database credential rotation and consumers. Check secret version stages, rotation Lambda status, database login result, application cache TTL and CloudTrail reads. Secrets Manager can maintain rotating credentials but applications must fetch valid versions and the database change must succeed.
D:An old architecture drawing without the current query plan or job-run identifier. This is not sufficient evidence for Secrets Manager database credential rotation and consumers. Check secret version stages, rotation Lambda status, database login result, application cache TTL and CloudTrail reads. Secrets Manager can maintain rotating credentials but applications must fetch valid versions and the database change must succeed.
Question 1006
A data warehouse ingestion service fails after a database password changes while its Glue job still uses an old hardcoded password. Which underlying AWS service principle BEST explains the recommended approach?
- A CloudWatch metric label is equivalent to a successful target table data-quality validation.
- Increasing a resource name length automatically increases AWS service throughput.
- A pipeline schedule guarantees that every downstream source record was processed correctly.
- Secrets Manager can maintain rotating credentials but applications must fetch valid versions and the database change must succeed.
Explanation
Correct Answer
D:Implement by choosing to store and rotate database credentials in Secrets Manager with authorized runtime retrieval and tested rotation behavior. This is the relevant technical mechanism for Secrets Manager database credential rotation and consumers.
Incorrect Answers
A:A CloudWatch metric label is equivalent to a successful target table data-quality validation. That generalization conflicts with Secrets Manager database credential rotation and consumers. Instead secrets Manager can maintain rotating credentials but applications must fetch valid versions and the database change must succeed. Check secret version stages, rotation Lambda status, database login result, application cache TTL and CloudTrail reads.
B:Increasing a resource name length automatically increases AWS service throughput. That generalization conflicts with Secrets Manager database credential rotation and consumers. Instead secrets Manager can maintain rotating credentials but applications must fetch valid versions and the database change must succeed. Check secret version stages, rotation Lambda status, database login result, application cache TTL and CloudTrail reads.
C:A pipeline schedule guarantees that every downstream source record was processed correctly. That generalization conflicts with Secrets Manager database credential rotation and consumers. Instead secrets Manager can maintain rotating credentials but applications must fetch valid versions and the database change must succeed. Check secret version stages, rotation Lambda status, database login result, application cache TTL and CloudTrail reads.
Question 1007
A data warehouse ingestion service fails after a database password changes while its Glue job still uses an old hardcoded password. An incorrect proposal is: Put the database password into a public CloudFormation template parameter default. What material risk would follow from the proposed incorrect shortcut?
- 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.
- A successfully scheduled rotation without verified consumer retrieval can break ETL authentication.
Explanation
Correct Answer
D:This is why the incorrect shortcut does not meet Secrets Manager database credential rotation and consumers.
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 Secrets Manager database credential rotation and consumers risk. The relevant failure is that a successfully scheduled rotation without verified consumer retrieval can break ETL authentication. Check secret version stages, rotation Lambda status, database login result, application cache TTL and CloudTrail reads.
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 Secrets Manager database credential rotation and consumers risk. The relevant failure is that a successfully scheduled rotation without verified consumer retrieval can break ETL authentication. Check secret version stages, rotation Lambda status, database login result, application cache TTL and CloudTrail reads.
C:The presence of an accurate job timestamp automatically created unauthorized database credentials. That unrelated assertion does not explain the actual Secrets Manager database credential rotation and consumers risk. The relevant failure is that a successfully scheduled rotation without verified consumer retrieval can break ETL authentication. Check secret version stages, rotation Lambda status, database login result, application cache TTL and CloudTrail reads.
Question 1008
A data warehouse ingestion service fails after a database password changes while its Glue job still uses an old hardcoded password. The observed failure is: A successfully scheduled rotation without verified consumer retrieval can break ETL authentication. Which recovery action BEST restores the required data-processing state?
- Assume updating a secret value instantly changes every cached client connection.
- Disable all credential rotations because the first client used an old password.
- Repair rotation or cache refresh and test a valid new credential and rejected retired credential.
- Put the database password into a public CloudFormation template parameter default.
Explanation
Correct Answer
C:This addresses the observed Secrets Manager database credential rotation and consumers failure while preserving the required contract. Secrets Manager can maintain rotating credentials but applications must fetch valid versions and the database change must succeed.
Incorrect Answers
A:Assume updating a secret value instantly changes every cached client connection. A successfully scheduled rotation without verified consumer retrieval can break ETL authentication. Instead repair rotation or cache refresh and test a valid new credential and rejected retired credential.
B:Disable all credential rotations because the first client used an old password. A successfully scheduled rotation without verified consumer retrieval can break ETL authentication. Instead repair rotation or cache refresh and test a valid new credential and rejected retired credential.
D:Put the database password into a public CloudFormation template parameter default. A successfully scheduled rotation without verified consumer retrieval can break ETL authentication. Instead repair rotation or cache refresh and test a valid new credential and rejected retired credential.
Question 1009
A team needs automatic credential rotation with a controlled consumer retrieval path for a private RDS instance. What is the MOST appropriate targeted implementation for this data-engineering situation?
- In this operational case, assume updating a secret value instantly changes every cached client connection.
- In this operational case, store and rotate database credentials in Secrets Manager with authorized runtime retrieval and tested rotation behavior.
- In this operational case, disable all credential rotations because the first client used an old password.
- In this operational case, put the database password into a public CloudFormation template parameter default.
Explanation
Correct Answer
B:Secrets Manager can maintain rotating credentials but applications must fetch valid versions and the database change must succeed. Validate with secret version stages, rotation Lambda status, database login result, application cache TTL and CloudTrail reads.
Incorrect Answers
A:Assume updating a secret value instantly changes every cached client connection. Secrets Manager can maintain rotating credentials but applications must fetch valid versions and the database change must succeed. Inspect secret version stages, rotation Lambda status, database login result, application cache TTL and CloudTrail reads.
C:A successfully scheduled rotation without verified consumer retrieval can break ETL authentication. Disable all credential rotations because the first client used an old password.
D:A successfully scheduled rotation without verified consumer retrieval can break ETL authentication. The supported design is to store and rotate database credentials in Secrets Manager with authorized runtime retrieval and tested rotation behavior.
Question 1010
A team needs automatic credential rotation with a controlled consumer retrieval path for a private RDS instance. What diagnostic observations should be checked before marking the change successful?
- 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 secret version stages, rotation Lambda status, database login result, application cache TTL and CloudTrail reads.
- The relevant validation evidence is a browser screenshot from another AWS account and time period.
Explanation
Correct Answer
C:Secrets Manager can maintain rotating credentials but applications must fetch valid versions and the database change must succeed.
Incorrect Answers
A:A resource ARN alone without any current data-plane observation. This is not sufficient evidence for Secrets Manager database credential rotation and consumers. Check secret version stages, rotation Lambda status, database login result, application cache TTL and CloudTrail reads. Secrets Manager can maintain rotating credentials but applications must fetch valid versions and the database change must succeed.
B:A renamed resource label that does not show an authorization or processing result. This is not sufficient evidence for Secrets Manager database credential rotation and consumers. Check secret version stages, rotation Lambda status, database login result, application cache TTL and CloudTrail reads. Secrets Manager can maintain rotating credentials but applications must fetch valid versions and the database change must succeed.
D:A browser screenshot from another AWS account and time period. This is not sufficient evidence for Secrets Manager database credential rotation and consumers. Check secret version stages, rotation Lambda status, database login result, application cache TTL and CloudTrail reads. Secrets Manager can maintain rotating credentials but applications must fetch valid versions and the database change must succeed.