Amazon AWS Certified Developer - Associate DVA-C02 Practice Test 26
Question 250
A Kinesis-connected Lambda should process only IoT records with an alarm category to reduce unnecessary invocations. After implementing the planned Lambda event filtering change, which observation is the MOST direct proof that its specific requirement has been met?
- During a sustained fault, calls fail fast through the fallback and recover through controlled probes.
- Function concurrency metrics show the reserved limit applied and other functions retain available capacity.
- Matching records reach the handler and unrelated records do not produce application processing.
- No second delivery occurs during the normal work interval and a completed message is explicitly deleted.
Explanation
Correct Answer
C:Matching records reach the handler and unrelated records do not produce application processing. This directly validates Lambda event filtering under the stated workload and confirms the intended AWS behavior: event-source filtering applies selection before Lambda invokes the function for supported sources.
Incorrect Answers
A:This observation tests third-party circuit breaker, rather than confirming Lambda event filtering. It does not by itself establish that matching records reach the handler and unrelated records do not produce application processing.
B:This observation tests Lambda concurrency reservation, rather than confirming Lambda event filtering. It does not by itself establish that matching records reach the handler and unrelated records do not produce application processing.
D:This observation tests SQS visibility timeout, rather than confirming Lambda event filtering. It does not by itself establish that matching records reach the handler and unrelated records do not produce application processing.
Question 251
A serverless API experiences slow first requests after idle periods with large dependency packages. After implementing the planned Lambda Init Duration diagnosis change, which observation is the MOST direct proof that its specific requirement has been met?
- End-to-end traces show the integration completes under the configured limit without gateway timeouts.
- Comparative load tests show latency and billed cost at the chosen memory setting.
- Telemetry separates initialization delay from handler time and shows improvement after the change.
- A controlled threshold breach moves the alarm to ALARM and the subscribed channel receives a notification.
Explanation
Correct Answer
C:Telemetry separates initialization delay from handler time and shows improvement after the change. This directly validates Lambda Init Duration diagnosis under the stated workload and confirms the intended AWS behavior: lambda cold-start initialization is distinct from code execution duration.
Incorrect Answers
A:This observation tests API Gateway Lambda integration timeout, rather than confirming Lambda Init Duration diagnosis. It does not by itself establish that telemetry separates initialization delay from handler time and shows improvement after the change.
B:This observation tests Lambda duration versus memory tradeoff, rather than confirming Lambda Init Duration diagnosis. It does not by itself establish that telemetry separates initialization delay from handler time and shows improvement after the change.
D:This observation tests CloudWatch alarm notification, rather than confirming Lambda Init Duration diagnosis. It does not by itself establish that telemetry separates initialization delay from handler time and shows improvement after the change.
Question 252
A product catalog has repeated reads of slowly changing entries and the database is overloaded. After implementing the planned ElastiCache cache-aside change, which observation is the MOST direct proof that its specific requirement has been met?
- Malformed requests produce a client error before backend invocation while valid requests reach the integration.
- Retry telemetry shows spaced attempts with eventual success or a controlled terminal error.
- Cache hit-rate increases and backend read load falls while update invalidation keeps freshness within policy.
- Uploaded parts can be retried independently and the completed object is present only after completion.
Explanation
Correct Answer
C:Cache hit-rate increases and backend read load falls while update invalidation keeps freshness within policy. This directly validates ElastiCache cache-aside under the stated workload and confirms the intended AWS behavior: cache-aside populates on misses and requires an explicit freshness or invalidation strategy.
Incorrect Answers
A:This observation tests API Gateway request validation, rather than confirming ElastiCache cache-aside. It does not by itself establish that cache hit-rate increases and backend read load falls while update invalidation keeps freshness within policy.
B:This observation tests SDK adaptive retries, rather than confirming ElastiCache cache-aside. It does not by itself establish that cache hit-rate increases and backend read load falls while update invalidation keeps freshness within policy.
D:This observation tests S3 multipart upload recovery, rather than confirming ElastiCache cache-aside. It does not by itself establish that cache hit-rate increases and backend read load falls while update invalidation keeps freshness within policy.
Question 253
A Lambda function in a VPC must reach a private RDS endpoint without exposing the database publicly. After implementing the planned Lambda VPC private data access change, which observation is the MOST direct proof that its specific requirement has been met?
- Network tests confirm outbound connectivity from the function to the private endpoint on its service port.
- Recorded integration requests contain the exact backend field names and values expected by the service.
- The failure destination receives an invocation record after retries or age limits are exhausted.
- Execution history shows state transitions, retries, and the branch taken after an error.
Explanation
Correct Answer
A:Network tests confirm outbound connectivity from the function to the private endpoint on its service port. This directly validates Lambda VPC private data access under the stated workload and confirms the intended AWS behavior: vPC networking and security groups control reachability independently of IAM API authorization.
Incorrect Answers
B:This observation tests API Gateway mapping templates, rather than confirming Lambda VPC private data access. It does not by itself establish that network tests confirm outbound connectivity from the function to the private endpoint on its service port.
C:This observation tests Lambda asynchronous failure destination, rather than confirming Lambda VPC private data access. It does not by itself establish that network tests confirm outbound connectivity from the function to the private endpoint on its service port.
D:This observation tests Step Functions orchestration, rather than confirming Lambda VPC private data access. It does not by itself establish that network tests confirm outbound connectivity from the function to the private endpoint on its service port.
Question 254
An application writes free-form messages that make it hard to filter errors by tenant-safe operation code. After implementing the planned structured JSON logging change, which observation is the MOST direct proof that its specific requirement has been met?
- A trace view shows related segments or subsegments with timing for the connected service path.
- End-to-end traces show the integration completes under the configured limit without gateway timeouts.
- Cache tests show each allowed variant returns its own response without cross-user leakage.
- Log queries can reliably filter the same fields across success and failure events.
Explanation
Correct Answer
D:Log queries can reliably filter the same fields across success and failure events. This directly validates structured JSON logging under the stated workload and confirms the intended AWS behavior: structured fields make telemetry queryable while avoiding sensitive payload exposure.
Incorrect Answers
A:This observation tests X-Ray trace propagation, rather than confirming structured JSON logging. It does not by itself establish that log queries can reliably filter the same fields across success and failure events.
B:This observation tests API Gateway Lambda integration timeout, rather than confirming structured JSON logging. It does not by itself establish that log queries can reliably filter the same fields across success and failure events.
C:This observation tests API response caching variation, rather than confirming structured JSON logging. It does not by itself establish that log queries can reliably filter the same fields across success and failure events.
Question 255
An order API adds an optional field and must not break older mobile clients. After implementing the planned contract testing versioned API change, which observation is the MOST direct proof that its specific requirement has been met?
- New instances become healthy and application checks pass before old capacity is retired.
- Test and production invoke the correct Lambda alias without unintended cross-stage traffic.
- Older client fixtures and the revised contract both pass against the candidate API stage.
- Tests deterministically exercise success, timeout, and error handling without contacting the live partner.
Explanation
Correct Answer
C:Older client fixtures and the revised contract both pass against the candidate API stage. This directly validates contract testing versioned API under the stated workload and confirms the intended AWS behavior: contract testing checks wire-level compatibility beyond unit correctness of a single handler.
Incorrect Answers
A:This observation tests Elastic Beanstalk immutable update, rather than confirming contract testing versioned API. It does not by itself establish that older client fixtures and the revised contract both pass against the candidate API stage.
B:This observation tests API Gateway stage variables, rather than confirming contract testing versioned API. It does not by itself establish that older client fixtures and the revised contract both pass against the candidate API stage.
D:This observation tests API external dependency mocks, rather than confirming contract testing versioned API. It does not by itself establish that older client fixtures and the revised contract both pass against the candidate API stage.
Question 256
An application role in account B must decrypt objects encrypted under a customer-managed KMS key in account A. After implementing the planned KMS key-policy cross-account 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.
- Policy evaluation identifies a matching explicit deny even though an Allow statement also matches.
- Rotated secret versions become available to authorized consumers and the application refreshes its cached credential.
- The external role can use the approved KMS key while unrelated principals remain denied.
Explanation
Correct Answer
D:The external role can use the approved KMS key while unrelated principals remain denied. This directly validates KMS key-policy cross-account under the stated workload and confirms the intended AWS behavior: cross-account KMS use needs key-policy authorization in the owning account and corresponding caller permissions.
Incorrect Answers
A:This observation tests KMS envelope encryption, rather than confirming KMS key-policy cross-account. It does not by itself establish that the external role can use the approved KMS key while unrelated principals remain denied.
B:This observation tests IAM policy explicit deny, rather than confirming KMS key-policy cross-account. It does not by itself establish that the external role can use the approved KMS key while unrelated principals remain denied.
C:This observation tests Secrets Manager rotation, rather than confirming KMS key-policy cross-account. It does not by itself establish that the external role can use the approved KMS key while unrelated principals remain denied.
Question 257
A billing subscriber receives events for all product lines but should process only invoices. After implementing the planned SNS subscription filter policy 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.
- Cache tests show each allowed variant returns its own response without cross-user leakage.
- Traffic reaches only ready tasks while a temporary dependency delay does not force needless process restarts.
- Only events matching the subscriber's policy reach its target while other topics of work are skipped.
Explanation
Correct Answer
D:Only events matching the subscriber's policy reach its target while other topics of work are skipped. This directly validates SNS subscription filter policy under the stated workload and confirms the intended AWS behavior: sNS subscription filtering drops irrelevant deliveries before consumer processing.
Incorrect Answers
A:This observation tests AccessDenied troubleshooting chain, rather than confirming SNS subscription filter policy. It does not by itself establish that only events matching the subscriber's policy reach its target while other topics of work are skipped.
B:This observation tests API response caching variation, rather than confirming SNS subscription filter policy. It does not by itself establish that only events matching the subscriber's policy reach its target while other topics of work are skipped.
C:This observation tests readiness versus liveness checks, rather than confirming SNS subscription filter policy. It does not by itself establish that only events matching the subscriber's policy reach its target while other topics of work are skipped.
Question 258
A regulated client must encrypt documents before they leave its application boundary. After implementing the planned client-side versus server-side encryption change, which observation is the MOST direct proof that its specific requirement has been met?
- A successfully signed-in user receives correctly issued tokens whose signature, issuer, audience, and expiry validate.
- Rotated secret versions become available to authorized consumers and the application refreshes its cached credential.
- The external role can use the approved KMS key while unrelated principals remain denied.
- Network captures and storage samples contain encrypted payloads before S3 receives them.
Explanation
Correct Answer
D:Network captures and storage samples contain encrypted payloads before S3 receives them. This directly validates client-side versus server-side encryption under the stated workload and confirms the intended AWS behavior: client-side encryption protects data prior to upload; SSE encrypts it after S3 receives the request.
Incorrect Answers
A:This observation tests Cognito user pool authentication, rather than confirming client-side versus server-side encryption. It does not by itself establish that network captures and storage samples contain encrypted payloads before S3 receives them.
B:This observation tests Secrets Manager rotation, rather than confirming client-side versus server-side encryption. It does not by itself establish that network captures and storage samples contain encrypted payloads before S3 receives them.
C:This observation tests KMS key-policy cross-account, rather than confirming client-side versus server-side encryption. It does not by itself establish that network captures and storage samples contain encrypted payloads before S3 receives them.
Question 259
A CPU-heavy Lambda builds thumbnails and consistently uses its full timeout despite low memory consumption. After implementing the planned Lambda memory CPU tuning change, which observation is the MOST direct proof that its specific requirement has been met?
- No second delivery occurs during the normal work interval and a completed message is explicitly deleted.
- CloudTrail or SDK results confirm the expected action succeeds while unrelated resources remain denied.
- Duration and billed-duration measurements improve at a tested memory setting without breaching budget.
- Execution history shows state transitions, retries, and the branch taken after an error.
Explanation
Correct Answer
C:Duration and billed-duration measurements improve at a tested memory setting without breaching budget. This directly validates Lambda memory CPU tuning under the stated workload and confirms the intended AWS behavior: lambda CPU allocation scales with configured memory and can speed CPU-bound functions.
Incorrect Answers
A:This observation tests SQS visibility timeout, rather than confirming Lambda memory CPU tuning. It does not by itself establish that duration and billed-duration measurements improve at a tested memory setting without breaching budget.
B:This observation tests Lambda execution role least privilege, rather than confirming Lambda memory CPU tuning. It does not by itself establish that duration and billed-duration measurements improve at a tested memory setting without breaching budget.
D:This observation tests Step Functions orchestration, rather than confirming Lambda memory CPU tuning. It does not by itself establish that duration and billed-duration measurements improve at a tested memory setting without breaching budget.
Question 260
A JSON API must admit only callers with valid bearer access tokens issued by a trusted user directory. After implementing the planned API Gateway JWT authorizer change, which observation is the MOST direct proof that its specific requirement has been met?
- CloudTrail shows the expected assumed role session and only the allowed target-account API actions succeed.
- Authorized requests query only their tenant partition while cross-tenant requests are blocked.
- Valid JWTs reach integrations while expired, bad-signature, or wrong-audience tokens are rejected.
- An approved role can decrypt the wrapped data key while an unauthorized role cannot.
Explanation
Correct Answer
C:Valid JWTs reach integrations while expired, bad-signature, or wrong-audience tokens are rejected. This directly validates API Gateway JWT authorizer under the stated workload and confirms the intended AWS behavior: jWT verification checks cryptographic signature and claims, not only whether a header exists.
Incorrect Answers
A:This observation tests IAM STS AssumeRole cross-account, rather than confirming API Gateway JWT authorizer. It does not by itself establish that valid JWTs reach integrations while expired, bad-signature, or wrong-audience tokens are rejected.
B:This observation tests multi-tenant DynamoDB row isolation, rather than confirming API Gateway JWT authorizer. It does not by itself establish that valid JWTs reach integrations while expired, bad-signature, or wrong-audience tokens are rejected.
D:This observation tests KMS envelope encryption, rather than confirming API Gateway JWT authorizer. It does not by itself establish that valid JWTs reach integrations while expired, bad-signature, or wrong-audience tokens are rejected.