Amazon AWS Certified Developer - Associate DVA-C02 Practice Test 47
Question 460
An onboarding workflow invokes verification, account creation, and compensation with observable retries. Suppose the team omits the intended Step Functions orchestration safeguard. Which failure mode is the MOST direct risk of that omission?
- A producer hardcoded to one downstream endpoint cannot independently route new event types.
- Missing or incorrect event filter patterns cause unwanted work or dropped eligible records.
- A missing destination silently loses terminal failure context beyond default handling.
- A one-shot Lambda chain obscures per-step recovery and can exceed execution constraints.
Explanation
Correct Answer
D:A one-shot Lambda chain obscures per-step recovery and can exceed execution constraints. The planned prevention is to use AWS Step Functions to coordinate states, retries, catches, and compensating tasks explicitly; the most direct verification is that execution history shows state transitions, retries, and the branch taken after an error.
Incorrect Answers
A:That failure mechanism is associated with EventBridge event routing. The omitted Step Functions orchestration protection instead causes this problem: a one-shot Lambda chain obscures per-step recovery and can exceed execution constraints.
B:That failure mechanism is associated with Lambda event filtering. The omitted Step Functions orchestration protection instead causes this problem: a one-shot Lambda chain obscures per-step recovery and can exceed execution constraints.
C:That failure mechanism is associated with Lambda asynchronous failure destination. The omitted Step Functions orchestration protection instead causes this problem: a one-shot Lambda chain obscures per-step recovery and can exceed execution constraints.
Question 461
A consumer app needs password sign-in and standards-based tokens for its own users. Suppose the team omits the intended Cognito user pool authentication safeguard. Which failure mode is the MOST direct risk of that omission?
- Confusing a user pool with an identity pool leaves the app without the expected login and user-directory flow.
- Logging or returning raw records before masking exposes PII despite correct database encryption.
- Accepting a caller-supplied tenant key without validation enables cross-tenant record access.
- A correct permission policy without an allowed trust relationship cannot be assumed.
Explanation
Correct Answer
A:The planned prevention is to use an Amazon Cognito user pool as the user directory and authenticate users to obtain tokens; the most direct verification is that a successfully signed-in user receives correctly issued tokens whose signature, issuer, audience, and expiry validate.
Incorrect Answers
B:That failure mechanism is associated with PII response field masking. The omitted Cognito user pool authentication protection instead causes this problem: confusing a user pool with an identity pool leaves the app without the expected login and user-directory flow.
C:That failure mechanism is associated with multi-tenant DynamoDB row isolation. The omitted Cognito user pool authentication protection instead causes this problem: confusing a user pool with an identity pool leaves the app without the expected login and user-directory flow.
D:That failure mechanism is associated with IAM STS AssumeRole cross-account. The omitted Cognito user pool authentication protection instead causes this problem: confusing a user pool with an identity pool leaves the app without the expected login and user-directory flow.
Question 462
A full-text search endpoint is slow for broad wildcard queries despite healthy application instances. Suppose the team omits the intended OpenSearch query performance profiling safeguard. Which failure mode is the MOST direct risk of that omission?
- Ignoring a response-varying header can serve incorrect or sensitive content from cache.
- Scaling only the API tier does not correct an expensive OpenSearch query pattern.
- Leaving retention unlimited can accumulate unnecessary log storage and compliance exposure.
- A longer Lambda timeout alone does not prevent an earlier API Gateway integration timeout.
Explanation
Correct Answer
B:Scaling only the API tier does not correct an expensive OpenSearch query pattern. The planned prevention is to inspect query profiles, shard pressure, and index mappings before optimizing the search request; the most direct verification is that profile output identifies the costly query phase and a revised query reduces latency under representative load.
Incorrect Answers
A:That failure mechanism is associated with API response caching variation. The omitted OpenSearch query performance profiling protection instead causes this problem: scaling only the API tier does not correct an expensive OpenSearch query pattern.
C:That failure mechanism is associated with CloudWatch log retention. The omitted OpenSearch query performance profiling protection instead causes this problem: scaling only the API tier does not correct an expensive OpenSearch query pattern.
D:That failure mechanism is associated with API Gateway Lambda integration timeout. The omitted OpenSearch query performance profiling protection instead causes this problem: scaling only the API tier does not correct an expensive OpenSearch query pattern.
Question 463
A product API needs all purchases for a known customer ID and must avoid reading an entire table. Suppose the team omits the intended DynamoDB Query versus Scan safeguard. Which failure mode is the MOST direct risk of that omission?
- A one-shot Lambda chain obscures per-step recovery and can exceed execution constraints.
- Immediate unbounded retries amplify throttling and can repeat non-idempotent operations.
- Publishing access keys in client code exposes reusable credentials beyond one object operation.
- Using Scan for a predictable partition lookup wastes read capacity and creates latency.
Explanation
Correct Answer
D:Using Scan for a predictable partition lookup wastes read capacity and creates latency. The planned prevention is to use DynamoDB Query with the customer partition key and an appropriate sort-key condition; the most direct verification is that read capacity and response results are limited to the target key range rather than the whole table.
Incorrect Answers
A:That failure mechanism is associated with Step Functions orchestration. The omitted DynamoDB Query versus Scan protection instead causes this problem: using Scan for a predictable partition lookup wastes read capacity and creates latency.
B:That failure mechanism is associated with SDK adaptive retries. The omitted DynamoDB Query versus Scan protection instead causes this problem: using Scan for a predictable partition lookup wastes read capacity and creates latency.
C:That failure mechanism is associated with S3 presigned URLs. The omitted DynamoDB Query versus Scan protection instead causes this problem: using Scan for a predictable partition lookup wastes read capacity and creates latency.
Question 464
A developer accidentally commits an AWS access key to a feature branch that is reviewed before merge. Suppose the team omits the intended secret scanning in CI safeguard. Which failure mode is the MOST direct risk of that omission?
- Deleting the KMS key during rotation makes ciphertext inaccessible after deletion.
- Removing a secret from the latest file does not erase its exposure in repository history.
- Treating any valid JWT as permission to read arbitrary tenant IDs leaks cross-tenant data.
- Dumping secrets into CloudWatch Logs exposes credentials to log readers.
Explanation
Correct Answer
B:The planned prevention is to run automated secret scanning in CI and revoke exposed credentials instead of merely deleting one commit; the most direct verification is that a seeded test secret blocks the merge and revocation evidence confirms the exposed credential is unusable.
Incorrect Answers
A:That failure mechanism is associated with KMS rotation scope. The omitted secret scanning in CI protection instead causes this problem: removing a secret from the latest file does not erase its exposure in repository history.
C:That failure mechanism is associated with application tenant authorization. The omitted secret scanning in CI protection instead causes this problem: removing a secret from the latest file does not erase its exposure in repository history.
D:That failure mechanism is associated with Lambda environment secret leakage. The omitted secret scanning in CI protection instead causes this problem: removing a secret from the latest file does not erase its exposure in repository history.
Question 465
A server application calls DynamoDB with valid IAM access but manually constructed requests are rejected. Suppose the team omits the intended SigV4 authenticated SDK requests safeguard. Which failure mode is the MOST direct risk of that omission?
- A correct IAM token without database user setup or TLS configuration can still fail to connect.
- Manually reusing an old signature fails when headers, body, timestamps, or credentials change.
- A role allowed to GetObject but denied KMS Decrypt cannot read the plaintext.
- A backend-to-backend call can fail when identity access exists but a required resource policy denies the principal.
Explanation
Correct Answer
B:Manually reusing an old signature fails when headers, body, timestamps, or credentials change. The planned prevention is to use an AWS SDK with its default credential provider chain and SigV4 request signing; the most direct verification is that aPI requests carry valid signatures derived from current credentials and pass IAM authorization.
Incorrect Answers
A:That failure mechanism is associated with IAM authentication and TLS for RDS. The omitted SigV4 authenticated SDK requests protection instead causes this problem: manually reusing an old signature fails when headers, body, timestamps, or credentials change.
C:That failure mechanism is associated with S3 SSE-KMS access. The omitted SigV4 authenticated SDK requests protection instead causes this problem: manually reusing an old signature fails when headers, body, timestamps, or credentials change.
D:That failure mechanism is associated with service-to-service IAM authorization. The omitted SigV4 authenticated SDK requests protection instead causes this problem: manually reusing an old signature fails when headers, body, timestamps, or credentials change.
Question 466
An order API adds an optional field and must not break older mobile clients. Suppose the team omits the intended contract testing versioned API safeguard. Which failure mode is the MOST direct risk of that omission?
- Relying only on live third-party calls makes tests slow and nondeterministic.
- Sharing production tables with integration tests can corrupt real data.
- Manual configuration changes may be overwritten or missed by the next IaC deployment.
- Changing required response shapes without consumer tests can break callers after deployment.
Explanation
Correct Answer
D:Changing required response shapes without consumer tests can break callers after deployment. The planned prevention is to run consumer contract tests across supported API versions and stage new behavior before promotion; the most direct verification is that older client fixtures and the revised contract both pass against the candidate API stage.
Incorrect Answers
A:That failure mechanism is associated with API external dependency mocks. The omitted contract testing versioned API protection instead causes this problem: changing required response shapes without consumer tests can break callers after deployment.
B:That failure mechanism is associated with stage-isolated integration stack. The omitted contract testing versioned API protection instead causes this problem: changing required response shapes without consumer tests can break callers after deployment.
C:That failure mechanism is associated with infrastructure drift detection. The omitted contract testing versioned API protection instead causes this problem: changing required response shapes without consumer tests can break callers after deployment.
Question 467
A support platform emits typed ticket-updated events and several services need only selected event kinds. Suppose the team omits the intended EventBridge event routing safeguard. Which failure mode is the MOST direct risk of that omission?
- Missing or incorrect event filter patterns cause unwanted work or dropped eligible records.
- A producer hardcoded to one downstream endpoint cannot independently route new event types.
- An eventually consistent read may briefly return a stale value after a successful write.
- Duplicate deliveries bypass a stable deduplication check and cause the same side effect twice.
Explanation
Correct Answer
B:A producer hardcoded to one downstream endpoint cannot independently route new event types. The planned prevention is to put events on an EventBridge bus and create rules matching the required event patterns to targets; the most direct verification is that rule-matching events reach the intended targets while nonmatching event types do not.
Incorrect Answers
A:That failure mechanism is associated with Lambda event filtering. The omitted EventBridge event routing protection instead causes this problem: a producer hardcoded to one downstream endpoint cannot independently route new event types.
C:That failure mechanism is associated with DynamoDB strong read consistency. The omitted EventBridge event routing protection instead causes this problem: a producer hardcoded to one downstream endpoint cannot independently route new event types.
D:That failure mechanism is associated with idempotent event handling. The omitted EventBridge event routing protection instead causes this problem: a producer hardcoded to one downstream endpoint cannot independently route new event types.
Question 468
A Lambda SQS consumer must handle the Records envelope and malformed message bodies correctly. Suppose the team omits the intended SQS handler contract tests safeguard. Which failure mode is the MOST direct risk of that omission?
- Tests using only happy-path payloads miss error handling and event-shape incompatibilities.
- Changing required response shapes without consumer tests can break callers after deployment.
- Replacing all tasks in place can increase downtime or remove a quick rollback path.
- Testing a bare JSON object instead of an SQS event misses envelope parsing defects.
Explanation
Correct Answer
D:Testing a bare JSON object instead of an SQS event misses envelope parsing defects. The planned prevention is to build test events using realistic SQS Records metadata and verify handler output plus failure identifiers; the most direct verification is that contract tests prove valid records process once logically and only failed IDs are reported.
Incorrect Answers
A:That failure mechanism is associated with deployment test event generation. The omitted SQS handler contract tests protection instead causes this problem: testing a bare JSON object instead of an SQS event misses envelope parsing defects.
B:That failure mechanism is associated with contract testing versioned API. The omitted SQS handler contract tests protection instead causes this problem: testing a bare JSON object instead of an SQS event misses envelope parsing defects.
C:That failure mechanism is associated with CodeDeploy ECS blue-green. The omitted SQS handler contract tests protection instead causes this problem: testing a bare JSON object instead of an SQS event misses envelope parsing defects.
Question 469
A Lambda zip deployment fails at initialization with No module named requests. Suppose the team omits the intended Lambda deployment package dependencies safeguard. Which failure mode is the MOST direct risk of that omission?
- Hardcoding production resource names in a shared template can cause cross-environment collisions.
- A mutable latest tag can point to different image bytes on separate deployments.
- Missing or wrongly packaged dependencies cause runtime import failures before handler logic runs.
- Invoking the unqualified mutable $LATEST for production tests confuses tested and deployed revisions.
Explanation
Correct Answer
C:Missing or wrongly packaged dependencies cause runtime import failures before handler logic runs. The planned prevention is to build the deployment archive with runtime-compatible dependencies at the expected package paths; the most direct verification is that a deployment smoke test imports all required modules in the deployed Lambda runtime.
Incorrect Answers
A:That failure mechanism is associated with CloudFormation resource parameters. The omitted Lambda deployment package dependencies protection instead causes this problem: missing or wrongly packaged dependencies cause runtime import failures before handler logic runs.
B:That failure mechanism is associated with immutable container image tags. The omitted Lambda deployment package dependencies protection instead causes this problem: missing or wrongly packaged dependencies cause runtime import failures before handler logic runs.
D:That failure mechanism is associated with Lambda alias version testing. The omitted Lambda deployment package dependencies protection instead causes this problem: missing or wrongly packaged dependencies cause runtime import failures before handler logic runs.
Question 470
An API fanout causes thousands of concurrent calls to a downstream rate-limited billing system. Suppose the team omits the intended concurrency backpressure safeguard. Which failure mode is the MOST direct risk of that omission?
- Unbounded fanout can overwhelm a dependency even if the caller has ample compute capacity.
- Ignoring a response-varying header can serve incorrect or sensitive content from cache.
- Searching broad unstructured text without a request key obscures the relevant failure path.
- Debugging handler business code cannot fix a stack resource creation permission error.
Explanation
Correct Answer
A:Unbounded fanout can overwhelm a dependency even if the caller has ample compute capacity. The planned prevention is to limit parallelism and introduce queue-based backpressure with bounded retries and metrics; the most direct verification is that downstream 429 rates fall while queue depth and processing age remain within the service objective.
Incorrect Answers
B:That failure mechanism is associated with API response caching variation. The omitted concurrency backpressure protection instead causes this problem: unbounded fanout can overwhelm a dependency even if the caller has ample compute capacity.
C:That failure mechanism is associated with CloudWatch Logs Insights root cause. The omitted concurrency backpressure protection instead causes this problem: unbounded fanout can overwhelm a dependency even if the caller has ample compute capacity.
D:That failure mechanism is associated with failed CloudFormation deployment. The omitted concurrency backpressure protection instead causes this problem: unbounded fanout can overwhelm a dependency even if the caller has ample compute capacity.