Amazon AWS Certified Developer - Associate DVA-C02 Practice Test 24
Question 230
A shared SaaS table stores records for many tenants under tenant-prefixed partition keys. After implementing the planned multi-tenant DynamoDB row isolation change, which observation is the MOST direct proof that its specific requirement has been met?
- An approved role can decrypt the wrapped data key while an unauthorized role cannot.
- Authorized requests query only their tenant partition while cross-tenant requests are blocked.
- Secret-read API volume declines while newly rotated credentials are adopted within the specified refresh window.
- TLS handshakes present a valid chain and expected hostname before and after rotation.
Explanation
Correct Answer
B:Authorized requests query only their tenant partition while cross-tenant requests are blocked. This directly validates multi-tenant DynamoDB row isolation under the stated workload and confirms the intended AWS behavior: a tenant identifier from verified claims must control data scoping instead of untrusted request parameters.
Incorrect Answers
A:This observation tests KMS envelope encryption, rather than confirming multi-tenant DynamoDB row isolation. It does not by itself establish that authorized requests query only their tenant partition while cross-tenant requests are blocked.
C:This observation tests credential caching refresh, rather than confirming multi-tenant DynamoDB row isolation. It does not by itself establish that authorized requests query only their tenant partition while cross-tenant requests are blocked.
D:This observation tests TLS certificate rotation ACM, rather than confirming multi-tenant DynamoDB row isolation. It does not by itself establish that authorized requests query only their tenant partition while cross-tenant requests are blocked.
Question 231
A team needs to test v2 of an API while consumers still use the production stage. After implementing the planned API Gateway staging endpoints change, which observation is the MOST direct proof that its specific requirement has been met?
- Older client fixtures and the revised contract both pass against the candidate API stage.
- New instances become healthy and application checks pass before old capacity is retired.
- Peak /tmp usage remains within configured capacity during the largest supported input.
- Test requests route to the test deployment while production routes keep serving the previous version.
Explanation
Correct Answer
D:Test requests route to the test deployment while production routes keep serving the previous version. This directly validates API Gateway staging endpoints under the stated workload and confirms the intended AWS behavior: aPI Gateway stages provide deployment boundaries and can hold environment-specific settings.
Incorrect Answers
A:This observation tests contract testing versioned API, rather than confirming API Gateway staging endpoints. It does not by itself establish that test requests route to the test deployment while production routes keep serving the previous version.
B:This observation tests Elastic Beanstalk immutable update, rather than confirming API Gateway staging endpoints. It does not by itself establish that test requests route to the test deployment while production routes keep serving the previous version.
C:This observation tests Lambda ephemeral disk sizing, rather than confirming API Gateway staging endpoints. It does not by itself establish that test requests route to the test deployment while production routes keep serving the previous version.
Question 232
A search box must find phrases and relevance-ranked matches across an indexed document corpus. After implementing the planned OpenSearch full-text queries change, which observation is the MOST direct proof that its specific requirement has been met?
- Recorded integration requests contain the exact backend field names and values expected by the service.
- Read capacity and response results are limited to the target key range rather than the whole table.
- Search results return ranked text matches according to indexed tokens and query clauses.
- Retry telemetry shows spaced attempts with eventual success or a controlled terminal error.
Explanation
Correct Answer
C:Search results return ranked text matches according to indexed tokens and query clauses. This directly validates OpenSearch full-text queries under the stated workload and confirms the intended AWS behavior: full-text search uses analyzed inverted indexes rather than DynamoDB exact-key access.
Incorrect Answers
A:This observation tests API Gateway mapping templates, rather than confirming OpenSearch full-text queries. It does not by itself establish that search results return ranked text matches according to indexed tokens and query clauses.
B:This observation tests DynamoDB Query versus Scan, rather than confirming OpenSearch full-text queries. It does not by itself establish that search results return ranked text matches according to indexed tokens and query clauses.
D:This observation tests SDK adaptive retries, rather than confirming OpenSearch full-text queries. It does not by itself establish that search results return ranked text matches according to indexed tokens and query clauses.
Question 233
A SaaS API validates JWTs but must restrict reads to the tenant represented by the caller's verified claims. After implementing the planned application tenant authorization change, which observation is the MOST direct proof that its specific requirement has been met?
- Cross-tenant requests receive an authorization failure even with otherwise valid login tokens.
- The external role can use the approved KMS key while unrelated principals remain denied.
- A successfully signed-in user receives correctly issued tokens whose signature, issuer, audience, and expiry validate.
- Network captures and storage samples contain encrypted payloads before S3 receives them.
Explanation
Correct Answer
A:Cross-tenant requests receive an authorization failure even with otherwise valid login tokens. This directly validates application tenant authorization under the stated workload and confirms the intended AWS behavior: authentication proves a principal, whereas tenant-level authorization constrains which records it may access.
Incorrect Answers
B:This observation tests KMS key-policy cross-account, rather than confirming application tenant authorization. It does not by itself establish that cross-tenant requests receive an authorization failure even with otherwise valid login tokens.
C:This observation tests Cognito user pool authentication, rather than confirming application tenant authorization. It does not by itself establish that cross-tenant requests receive an authorization failure even with otherwise valid login tokens.
D:This observation tests client-side versus server-side encryption, rather than confirming application tenant authorization. It does not by itself establish that cross-tenant requests receive an authorization failure even with otherwise valid login tokens.
Question 234
A request crosses API Gateway and several Lambda-backed service calls but its latency cannot be attributed. After implementing the planned X-Ray trace propagation change, which observation is the MOST direct proof that its specific requirement has been met?
- A controlled threshold breach moves the alarm to ALARM and the subscribed channel receives a notification.
- A trace view shows related segments or subsegments with timing for the connected service path.
- The failed resource event includes a concrete status reason that matches the attempted operation.
- Telemetry separates initialization delay from handler time and shows improvement after the change.
Explanation
Correct Answer
B:A trace view shows related segments or subsegments with timing for the connected service path. This directly validates X-Ray trace propagation under the stated workload and confirms the intended AWS behavior: trace propagation links work across components; isolated logs alone cannot reconstruct spans reliably.
Incorrect Answers
A:This observation tests CloudWatch alarm notification, rather than confirming X-Ray trace propagation. It does not by itself establish that a trace view shows related segments or subsegments with timing for the connected service path.
C:This observation tests failed CloudFormation deployment, rather than confirming X-Ray trace propagation. It does not by itself establish that a trace view shows related segments or subsegments with timing for the connected service path.
D:This observation tests Lambda Init Duration diagnosis, rather than confirming X-Ray trace propagation. It does not by itself establish that a trace view shows related segments or subsegments with timing for the connected service path.
Question 235
Integration tests create temporary DynamoDB and SQS resources that must not touch live customer records. After implementing the planned stage-isolated integration stack change, which observation is the MOST direct proof that its specific requirement has been met?
- The running task image digest matches the tested build artifact after deployment and rollback.
- Integration tests use temporary resource ARNs and cleanup leaves production resources unchanged.
- Tests deterministically exercise success, timeout, and error handling without contacting the live partner.
- Drift results identify divergent supported properties and a later deployment restores intended state.
Explanation
Correct Answer
B:Integration tests use temporary resource ARNs and cleanup leaves production resources unchanged. This directly validates stage-isolated integration stack under the stated workload and confirms the intended AWS behavior: environment isolation prevents test mutations from affecting production state.
Incorrect Answers
A:This observation tests immutable container image tags, rather than confirming stage-isolated integration stack. It does not by itself establish that integration tests use temporary resource ARNs and cleanup leaves production resources unchanged.
C:This observation tests API external dependency mocks, rather than confirming stage-isolated integration stack. It does not by itself establish that integration tests use temporary resource ARNs and cleanup leaves production resources unchanged.
D:This observation tests infrastructure drift detection, rather than confirming stage-isolated integration stack. It does not by itself establish that integration tests use temporary resource ARNs and cleanup leaves production resources unchanged.
Question 236
A developer accidentally commits an AWS access key to a feature branch that is reviewed before merge. After implementing the planned secret scanning in CI change, which observation is the MOST direct proof that its specific requirement has been met?
- The client obtains a fresh access token and the protected API rejects an expired one.
- A seeded test secret blocks the merge and revocation evidence confirms the exposed credential is unusable.
- Requests from the intended endpoint succeed and other source contexts receive access denied.
- Requests from nonprivileged roles contain masked fields while approved roles get only permitted detail.
Explanation
Correct Answer
B:A seeded test secret blocks the merge and revocation evidence confirms the exposed credential is unusable. This directly validates secret scanning in CI under the stated workload and confirms the intended AWS behavior: secret scanning reduces accidental credential publication but exposed keys must be invalidated.
Incorrect Answers
A:This observation tests bearer token refresh and expiry, rather than confirming secret scanning in CI. It does not by itself establish that a seeded test secret blocks the merge and revocation evidence confirms the exposed credential is unusable.
C:This observation tests API Gateway resource policy, rather than confirming secret scanning in CI. It does not by itself establish that a seeded test secret blocks the merge and revocation evidence confirms the exposed credential is unusable.
D:This observation tests PII response field masking, rather than confirming secret scanning in CI. It does not by itself establish that a seeded test secret blocks the merge and revocation evidence confirms the exposed credential is unusable.
Question 237
A Lambda function update must route only 10 percent of traffic to a new version before full rollout. After implementing the planned CodeDeploy Lambda canary change, which observation is the MOST direct proof that its specific requirement has been met?
- The replacement task set passes health checks before traffic moves and the old target remains available for rollback.
- The correct environment retrieves its scoped configuration and a failed rollout can be rolled back.
- Alias routing starts at the selected small percentage and alarms can trigger rollback.
- Test requests route to the test deployment while production routes keep serving the previous version.
Explanation
Correct Answer
C:Alias routing starts at the selected small percentage and alarms can trigger rollback. This directly validates CodeDeploy Lambda canary under the stated workload and confirms the intended AWS behavior: canary deployment limits initial exposure by progressively shifting live traffic to a candidate version.
Incorrect Answers
A:This observation tests CodeDeploy ECS blue-green, rather than confirming CodeDeploy Lambda canary. It does not by itself establish that alias routing starts at the selected small percentage and alarms can trigger rollback.
B:This observation tests environment-specific AppConfig, rather than confirming CodeDeploy Lambda canary. It does not by itself establish that alias routing starts at the selected small percentage and alarms can trigger rollback.
D:This observation tests API Gateway staging endpoints, rather than confirming CodeDeploy Lambda canary. It does not by itself establish that alias routing starts at the selected small percentage and alarms can trigger rollback.
Question 238
An API fanout causes thousands of concurrent calls to a downstream rate-limited billing system. After implementing the planned concurrency backpressure change, which observation is the MOST direct proof that its specific requirement has been met?
- Only events matching the subscriber's policy reach its target while other topics of work are skipped.
- A controlled threshold breach moves the alarm to ALARM and the subscribed channel receives a notification.
- The query isolates timestamps and the exact error records associated with the failed request.
- Downstream 429 rates fall while queue depth and processing age remain within the service objective.
Explanation
Correct Answer
D:Downstream 429 rates fall while queue depth and processing age remain within the service objective. This directly validates concurrency backpressure under the stated workload and confirms the intended AWS behavior: concurrency controls must reflect downstream capacity rather than only upstream invocation volume.
Incorrect Answers
A:This observation tests SNS subscription filter policy, rather than confirming concurrency backpressure. It does not by itself establish that downstream 429 rates fall while queue depth and processing age remain within the service objective.
B:This observation tests CloudWatch alarm notification, rather than confirming concurrency backpressure. It does not by itself establish that downstream 429 rates fall while queue depth and processing age remain within the service objective.
C:This observation tests CloudWatch Logs Insights root cause, rather than confirming concurrency backpressure. It does not by itself establish that downstream 429 rates fall while queue depth and processing age remain within the service objective.
Question 239
An ECS container starts but should receive traffic only after its database connection pool is ready. After implementing the planned readiness versus liveness checks change, which observation is the MOST direct proof that its specific requirement has been met?
- The denied API event identifies the principal and missing permission or key-policy condition.
- End-to-end traces show the integration completes under the configured limit without gateway timeouts.
- Traffic reaches only ready tasks while a temporary dependency delay does not force needless process restarts.
- Old routine log events age out according to policy while newer diagnostic events stay queryable.
Explanation
Correct Answer
C:Traffic reaches only ready tasks while a temporary dependency delay does not force needless process restarts. This directly validates readiness versus liveness checks under the stated workload and confirms the intended AWS behavior: readiness controls whether a service should receive requests; liveness indicates whether the process needs restarting.
Incorrect Answers
A:This observation tests AccessDenied troubleshooting chain, rather than confirming readiness versus liveness checks. It does not by itself establish that traffic reaches only ready tasks while a temporary dependency delay does not force needless process restarts.
B:This observation tests API Gateway Lambda integration timeout, rather than confirming readiness versus liveness checks. It does not by itself establish that traffic reaches only ready tasks while a temporary dependency delay does not force needless process restarts.
D:This observation tests CloudWatch log retention, rather than confirming readiness versus liveness checks. It does not by itself establish that traffic reaches only ready tasks while a temporary dependency delay does not force needless process restarts.
Question 240
Two workers attempt to claim the same job and only one may transition it from PENDING to RUNNING. After implementing the planned DynamoDB conditional update change, which observation is the MOST direct proof that its specific requirement has been met?
- Each subscriber queue receives its own copy and an unavailable worker can process its backlog later.
- One competing write succeeds and the other receives a conditional-check failure.
- An expired item is denied by the app even when the physical DynamoDB item has not yet disappeared.
- CloudTrail or SDK results confirm the expected action succeeds while unrelated resources remain denied.
Explanation
Correct Answer
B:One competing write succeeds and the other receives a conditional-check failure. This directly validates DynamoDB conditional update under the stated workload and confirms the intended AWS behavior: conditional writes enforce state preconditions atomically during concurrent writes.
Incorrect Answers
A:This observation tests SNS fanout delivery, rather than confirming DynamoDB conditional update. It does not by itself establish that one competing write succeeds and the other receives a conditional-check failure.
C:This observation tests DynamoDB TTL expiry semantics, rather than confirming DynamoDB conditional update. It does not by itself establish that one competing write succeeds and the other receives a conditional-check failure.
D:This observation tests Lambda execution role least privilege, rather than confirming DynamoDB conditional update. It does not by itself establish that one competing write succeeds and the other receives a conditional-check failure.