Amazon AWS Certified Developer - Associate DVA-C02 Practice Test 67
Question 660
A product API needs all purchases for a known customer ID and must avoid reading an entire table. Select THREE statements that together form a sound implementation and validation plan for this requirement.
- Put the customer identifier only into an unused document attribute.
- Use DynamoDB Query with the customer partition key and an appropriate sort-key condition.
- Call BatchWriteItem to retrieve customer records.
- Query uses key conditions while Scan examines items beyond the requested partition.
- Filter a full-table Scan after reading every item.
- Read capacity and response results are limited to the target key range rather than the whole table.
Explanation
Correct Answers
B:Use DynamoDB Query with the customer partition key and an appropriate sort-key condition. This is the concrete implementation required for DynamoDB Query versus Scan.
D:Query uses key conditions while Scan examines items beyond the requested partition. This states the AWS behavior that makes the implementation valid.
F:Read capacity and response results are limited to the target key range rather than the whole table. This is the workload-specific evidence needed to validate the change.
Incorrect Answers
A:Put the customer identifier only into an unused document attribute. This is not a suitable implementation or validation step for DynamoDB Query versus Scan; it would leave the risk that using Scan for a predictable partition lookup wastes read capacity and creates latency.
C:Call BatchWriteItem to retrieve customer records. This is not a suitable implementation or validation step for DynamoDB Query versus Scan; it would leave the risk that using Scan for a predictable partition lookup wastes read capacity and creates latency.
E:Filter a full-table Scan after reading every item. This is not a suitable implementation or validation step for DynamoDB Query versus Scan; it would leave the risk that using Scan for a predictable partition lookup wastes read capacity and creates latency.
Question 661
A regulated client must encrypt documents before they leave its application boundary. Select TWO statements that together form a sound implementation and validation plan for this requirement.
- Put the secret encryption key in the public download URL.
- Encrypt in the client with properly protected keys before uploading ciphertext to storage.
- Encode the JSON payload with Base64.
- Network captures and storage samples contain encrypted payloads before S3 receives them.
- Enable SSE-S3 and call it encryption before upload.
Explanation
Correct Answers
B:Encrypt in the client with properly protected keys before uploading ciphertext to storage. This is the concrete implementation required for client-side versus server-side encryption.
D:Network captures and storage samples contain encrypted payloads before S3 receives them. This is the workload-specific evidence needed to validate the change.
Incorrect Answers
A:Put the secret encryption key in the public download URL. This is not a suitable implementation or validation step for client-side versus server-side encryption; it would leave the risk that using only S3 server-side encryption does not satisfy a requirement to encrypt before transmission.
C:Encode the JSON payload with Base64. This is not a suitable implementation or validation step for client-side versus server-side encryption; it would leave the risk that using only S3 server-side encryption does not satisfy a requirement to encrypt before transmission.
E:Enable SSE-S3 and call it encryption before upload. This is not a suitable implementation or validation step for client-side versus server-side encryption; it would leave the risk that using only S3 server-side encryption does not satisfy a requirement to encrypt before transmission.
Question 662
A release should pass unit and staging integration tests before any production deploy. Select TWO statements that together form a sound implementation and validation plan for this requirement.
- Configure the existing pipeline stages to build, test, approve where required, and promote immutable artifacts.
- Bypass failing staging tests automatically.
- Trigger production deployment before build artifacts exist.
- Pipeline execution history shows the same artifact revision crossing successful gates before production.
- Pull arbitrary latest images in production instead of the tested digest.
Explanation
Correct Answers
A:Configure the existing pipeline stages to build, test, approve where required, and promote immutable artifacts. This is the concrete implementation required for CodePipeline gated promotion.
D:Pipeline execution history shows the same artifact revision crossing successful gates before production.
Incorrect Answers
B:Bypass failing staging tests automatically. This is not a suitable implementation or validation step for CodePipeline gated promotion; it would leave the risk that a pipeline that rebuilds a different artifact after approval breaks artifact provenance.
C:Trigger production deployment before build artifacts exist. This is not a suitable implementation or validation step for CodePipeline gated promotion; it would leave the risk that a pipeline that rebuilds a different artifact after approval breaks artifact provenance.
E:Pull arbitrary latest images in production instead of the tested digest. This is not a suitable implementation or validation step for CodePipeline gated promotion; it would leave the risk that a pipeline that rebuilds a different artifact after approval breaks artifact provenance.
Question 663
A customer profile endpoint depends on a vendor scoring API with repeated timeouts. Select TWO statements that together form a sound implementation and validation plan for this requirement.
- Use a circuit breaker with bounded timeouts and a documented fallback for the external dependency.
- Make the user interface responsible for restoring backend network connectivity.
- During a sustained fault, calls fail fast through the fallback and recover through controlled probes.
- Retry every failed request with zero delay forever.
- Remove every timeout from partner calls.
Explanation
Correct Answers
A:Use a circuit breaker with bounded timeouts and a documented fallback for the external dependency. This is the concrete implementation required for third-party circuit breaker.
C:During a sustained fault, calls fail fast through the fallback and recover through controlled probes.
Incorrect Answers
B:Make the user interface responsible for restoring backend network connectivity. This is not a suitable implementation or validation step for third-party circuit breaker; it would leave the risk that keeping all requests waiting for an unhealthy dependency exhausts caller concurrency.
D:Retry every failed request with zero delay forever. This is not a suitable implementation or validation step for third-party circuit breaker; it would leave the risk that keeping all requests waiting for an unhealthy dependency exhausts caller concurrency.
E:Remove every timeout from partner calls. This is not a suitable implementation or validation step for third-party circuit breaker; it would leave the risk that keeping all requests waiting for an unhealthy dependency exhausts caller concurrency.
Question 664
An onboarding workflow invokes verification, account creation, and compensation with observable retries. Select TWO statements that together form a sound implementation and validation plan for this requirement.
- Put the entire state machine inside one synchronous API Gateway mapping.
- Execution history shows state transitions, retries, and the branch taken after an error.
- Poll a local variable in a single Lambda for human approval.
- Use AWS Step Functions to coordinate states, retries, catches, and compensating tasks explicitly.
- Trigger all dependent steps concurrently without preserving ordering.
Explanation
Correct Answers
B:Execution history shows state transitions, retries, and the branch taken after an error. This is the workload-specific evidence needed to validate the change.
D:Use AWS Step Functions to coordinate states, retries, catches, and compensating tasks explicitly. This is the concrete implementation required for Step Functions orchestration.
Incorrect Answers
A:Put the entire state machine inside one synchronous API Gateway mapping. This is not a suitable implementation or validation step for Step Functions orchestration; it would leave the risk that a one-shot Lambda chain obscures per-step recovery and can exceed execution constraints.
C:Poll a local variable in a single Lambda for human approval. This is not a suitable implementation or validation step for Step Functions orchestration; it would leave the risk that a one-shot Lambda chain obscures per-step recovery and can exceed execution constraints.
E:Trigger all dependent steps concurrently without preserving ordering. This is not a suitable implementation or validation step for Step Functions orchestration; it would leave the risk that a one-shot Lambda chain obscures per-step recovery and can exceed execution constraints.
Question 665
A successful signup must independently notify billing, analytics, and email workers without sequential calls. Select TWO statements that together form a sound implementation and validation plan for this requirement.
- Call each worker inside one HTTP request.
- Store all consumer tasks in one local thread.
- Each subscriber queue receives its own copy and an unavailable worker can process its backlog later.
- Send events to one shared SQS queue expecting every consumer to see every event.
- Publish the event to SNS and subscribe separate SQS queues for each independently processed concern.
Explanation
Correct Answers
C:Each subscriber queue receives its own copy and an unavailable worker can process its backlog later.
E:Publish the event to SNS and subscribe separate SQS queues for each independently processed concern. This is the concrete implementation required for SNS fanout delivery.
Incorrect Answers
A:Call each worker inside one HTTP request. This is not a suitable implementation or validation step for SNS fanout delivery; it would leave the risk that invoking each downstream worker synchronously couples availability and latency.
B:Store all consumer tasks in one local thread. This is not a suitable implementation or validation step for SNS fanout delivery; it would leave the risk that invoking each downstream worker synchronously couples availability and latency.
D:Send events to one shared SQS queue expecting every consumer to see every event. This is not a suitable implementation or validation step for SNS fanout delivery; it would leave the risk that invoking each downstream worker synchronously couples availability and latency.
Question 666
A client uploads very large video files over unstable networks and must resume failed parts. Select TWO statements that together form a sound implementation and validation plan for this requirement.
- Retry the full multi-gigabyte PUT for every lost packet.
- Use the S3 multipart upload API with part tracking and complete or abort the upload correctly.
- Set public-read on the bucket to resume failed parts.
- Treat uploaded parts as a complete object before CompleteMultipartUpload.
- Uploaded parts can be retried independently and the completed object is present only after completion.
Explanation
Correct Answers
B:Use the S3 multipart upload API with part tracking and complete or abort the upload correctly. This is the concrete implementation required for S3 multipart upload recovery.
E:Uploaded parts can be retried independently and the completed object is present only after completion.
Incorrect Answers
A:Retry the full multi-gigabyte PUT for every lost packet. This is not a suitable implementation or validation step for S3 multipart upload recovery; it would leave the risk that unfinished multipart uploads accumulate stored parts and cannot be read as a completed object.
C:Set public-read on the bucket to resume failed parts. This is not a suitable implementation or validation step for S3 multipart upload recovery; it would leave the risk that unfinished multipart uploads accumulate stored parts and cannot be read as a completed object.
D:Treat uploaded parts as a complete object before CompleteMultipartUpload. This is not a suitable implementation or validation step for S3 multipart upload recovery; it would leave the risk that unfinished multipart uploads accumulate stored parts and cannot be read as a completed object.
Question 667
A container-based Lambda built on an ARM workstation fails because its image architecture differs from the selected function architecture. Select THREE statements that together form a sound implementation and validation plan for this requirement.
- Reduce load-balancer health-check frequency to repair an executable-format error.
- Assume all OCI image manifests work on every CPU architecture.
- Change the API Gateway stage to arm64 without changing the image.
- Build and publish a container image for the target runtime platform and set compatible deployment architecture.
- CPU architecture and container-image manifests must match the target runtime.
- The image manifest and a deployed smoke test match the target compute architecture.
Explanation
Correct Answers
D:Build and publish a container image for the target runtime platform and set compatible deployment architecture. This is the concrete implementation required for container image architecture compatibility.
E:CPU architecture and container-image manifests must match the target runtime. This states the AWS behavior that makes the implementation valid.
F:The image manifest and a deployed smoke test match the target compute architecture. This is the workload-specific evidence needed to validate the change.
Incorrect Answers
A:Reduce load-balancer health-check frequency to repair an executable-format error. This is not a suitable implementation or validation step for container image architecture compatibility; it would leave the risk that an architecture mismatch can prevent image startup even when application source is valid.
B:Assume all OCI image manifests work on every CPU architecture. This is not a suitable implementation or validation step for container image architecture compatibility; it would leave the risk that an architecture mismatch can prevent image startup even when application source is valid.
C:Change the API Gateway stage to arm64 without changing the image. This is not a suitable implementation or validation step for container image architecture compatibility; it would leave the risk that an architecture mismatch can prevent image startup even when application source is valid.
Question 668
A Lambda SQS consumer must handle the Records envelope and malformed message bodies correctly. Select TWO statements that together form a sound implementation and validation plan for this requirement.
- Disable tests for malformed records entirely.
- Send API Gateway request templates as direct SQS Records fixtures without adaptation.
- Contract tests prove valid records process once logically and only failed IDs are reported.
- Assert only that the Lambda function imports successfully.
- Build test events using realistic SQS Records metadata and verify handler output plus failure identifiers.
Explanation
Correct Answers
C:Contract tests prove valid records process once logically and only failed IDs are reported. This is the workload-specific evidence needed to validate the change.
E:Build test events using realistic SQS Records metadata and verify handler output plus failure identifiers. This is the concrete implementation required for SQS handler contract tests.
Incorrect Answers
A:Disable tests for malformed records entirely. This is not a suitable implementation or validation step for SQS handler contract tests; it would leave the risk that testing a bare JSON object instead of an SQS event misses envelope parsing defects.
B:Send API Gateway request templates as direct SQS Records fixtures without adaptation. This is not a suitable implementation or validation step for SQS handler contract tests; it would leave the risk that testing a bare JSON object instead of an SQS event misses envelope parsing defects.
D:Assert only that the Lambda function imports successfully. This is not a suitable implementation or validation step for SQS handler contract tests; it would leave the risk that testing a bare JSON object instead of an SQS event misses envelope parsing defects.
Question 669
A support platform emits typed ticket-updated events and several services need only selected event kinds. Select THREE statements that together form a sound implementation and validation plan for this requirement.
- Configure every event to invoke every target irrespective of type.
- Put events on an EventBridge bus and create rules matching the required event patterns to targets.
- Rule-matching events reach the intended targets while nonmatching event types do not.
- Treat EventBridge as a relational database query engine.
- EventBridge rules route structured events by matching attributes without embedding consumer addresses in producer code.
- Put filtering logic only in the front-end browser.
Explanation
Correct Answers
B:Put events on an EventBridge bus and create rules matching the required event patterns to targets. This is the concrete implementation required for EventBridge event routing.
C:Rule-matching events reach the intended targets while nonmatching event types do not. This is the workload-specific evidence needed to validate the change.
E:EventBridge rules route structured events by matching attributes without embedding consumer addresses in producer code. This states the AWS behavior that makes the implementation valid.
Incorrect Answers
A:Configure every event to invoke every target irrespective of type. This is not a suitable implementation or validation step for EventBridge event routing; it would leave the risk that a producer hardcoded to one downstream endpoint cannot independently route new event types.
D:Treat EventBridge as a relational database query engine. This is not a suitable implementation or validation step for EventBridge event routing; it would leave the risk that a producer hardcoded to one downstream endpoint cannot independently route new event types.
F:Put filtering logic only in the front-end browser. This is not a suitable implementation or validation step for EventBridge event routing; it would leave the risk that a producer hardcoded to one downstream endpoint cannot independently route new event types.
Question 670
A legacy backend expects a compact JSON shape while clients send a differently named field. Select TWO statements that together form a sound implementation and validation plan for this requirement.
- Disable all API authorizers to bypass mapping errors.
- Change the Lambda runtime version to alter JSON keys automatically.
- Add more SQS consumers without changing the request shape.
- Recorded integration requests contain the exact backend field names and values expected by the service.
- Define an API Gateway mapping template or parameter mapping that explicitly transforms the incoming request.
Explanation
Correct Answers
D:Recorded integration requests contain the exact backend field names and values expected by the service.
E:Define an API Gateway mapping template or parameter mapping that explicitly transforms the incoming request. This is the concrete implementation required for API Gateway mapping templates.
Incorrect Answers
A:Disable all API authorizers to bypass mapping errors. This is not a suitable implementation or validation step for API Gateway mapping templates; it would leave the risk that a mismatched integration payload causes field-level validation errors even with a healthy backend.
B:Change the Lambda runtime version to alter JSON keys automatically. This is not a suitable implementation or validation step for API Gateway mapping templates; it would leave the risk that a mismatched integration payload causes field-level validation errors even with a healthy backend.
C:Add more SQS consumers without changing the request shape. This is not a suitable implementation or validation step for API Gateway mapping templates; it would leave the risk that a mismatched integration payload causes field-level validation errors even with a healthy backend.