Amazon AWS Certified Developer - Associate DVA-C02 Practice Test 68
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.
Question 671
A mobile app authenticated by an external provider needs short-lived access to upload its own images to S3. Select TWO statements that together form a sound implementation and validation plan for this requirement.
- Embed root account access keys in the app bundle.
- Federated users obtain expiring role credentials constrained to the intended S3 paths.
- Mark every bucket public to bypass client authorization.
- Use only a user pool token as an S3 SigV4 signing secret.
- Exchange trusted identities through a Cognito identity pool for role-scoped temporary AWS credentials.
Explanation
Correct Answers
B:Federated users obtain expiring role credentials constrained to the intended S3 paths. This is the workload-specific evidence needed to validate the change.
E:Exchange trusted identities through a Cognito identity pool for role-scoped temporary AWS credentials. This is the concrete implementation required for Cognito identity pool AWS access.
Incorrect Answers
A:Embed root account access keys in the app bundle. This is not a suitable implementation or validation step for Cognito identity pool AWS access; it would leave the risk that shipping permanent IAM access keys in a client creates unrestricted reusable credentials.
C:Mark every bucket public to bypass client authorization. This is not a suitable implementation or validation step for Cognito identity pool AWS access; it would leave the risk that shipping permanent IAM access keys in a client creates unrestricted reusable credentials.
D:Use only a user pool token as an S3 SigV4 signing secret. This is not a suitable implementation or validation step for Cognito identity pool AWS access; it would leave the risk that shipping permanent IAM access keys in a client creates unrestricted reusable credentials.
Question 672
An ECS service needs to deploy a new task definition while retaining immediate rollback to the prior revision. Select TWO statements that together form a sound implementation and validation plan for this requirement.
- Use a blue-green ECS deployment with CodeDeploy and controlled target-group traffic switching.
- Disable load-balancer checks to force an unhealthy task set live.
- Point both target groups at an unrelated static S3 site.
- Terminate the healthy original task set before testing replacement tasks.
- The replacement task set passes health checks before traffic moves and the old target remains available for rollback.
Explanation
Correct Answers
A:Use a blue-green ECS deployment with CodeDeploy and controlled target-group traffic switching. This is the concrete implementation required for CodeDeploy ECS blue-green.
E:The replacement task set passes health checks before traffic moves and the old target remains available for rollback.
Incorrect Answers
B:Disable load-balancer checks to force an unhealthy task set live. This is not a suitable implementation or validation step for CodeDeploy ECS blue-green; it would leave the risk that replacing all tasks in place can increase downtime or remove a quick rollback path.
C:Point both target groups at an unrelated static S3 site. This is not a suitable implementation or validation step for CodeDeploy ECS blue-green; it would leave the risk that replacing all tasks in place can increase downtime or remove a quick rollback path.
D:Terminate the healthy original task set before testing replacement tasks. This is not a suitable implementation or validation step for CodeDeploy ECS blue-green; it would leave the risk that replacing all tasks in place can increase downtime or remove a quick rollback path.
Question 673
A Kinesis-connected Lambda should process only IoT records with an alarm category to reduce unnecessary invocations. Select TWO statements that together form a sound implementation and validation plan for this requirement.
- Rebuild the DynamoDB table on every event.
- Implement EventBridge rule patterns against a queue message with no EventBridge integration.
- Matching records reach the handler and unrelated records do not produce application processing.
- Raise the function timeout to filter records automatically.
- Configure a supported Lambda event source filtering pattern matching the required record fields.
Explanation
Correct Answers
C:Matching records reach the handler and unrelated records do not produce application processing. This is the workload-specific evidence needed to validate the change.
E:Configure a supported Lambda event source filtering pattern matching the required record fields. This is the concrete implementation required for Lambda event filtering.
Incorrect Answers
A:Rebuild the DynamoDB table on every event. This is not a suitable implementation or validation step for Lambda event filtering; it would leave the risk that missing or incorrect event filter patterns cause unwanted work or dropped eligible records.
B:Implement EventBridge rule patterns against a queue message with no EventBridge integration. This is not a suitable implementation or validation step for Lambda event filtering; it would leave the risk that missing or incorrect event filter patterns cause unwanted work or dropped eligible records.
D:Raise the function timeout to filter records automatically. This is not a suitable implementation or validation step for Lambda event filtering; it would leave the risk that missing or incorrect event filter patterns cause unwanted work or dropped eligible records.
Question 674
Multiple Python Lambda functions must share a versioned dependency without copying vendor packages into each source tree. Select THREE statements that together form a sound implementation and validation plan for this requirement.
- Put the dependency archive in CloudWatch Logs expecting Lambda to import it.
- Use an API Gateway mapping template to install native Python packages.
- Publish compatible dependencies as a versioned Lambda layer and attach the required layer version to functions.
- Attach the layer without checking runtime or architecture compatibility.
- Lambda layers package reusable dependencies separately while runtime compatibility must still match.
- Each function loads the expected dependency version under the declared runtime and architecture.
Explanation
Correct Answers
C:Publish compatible dependencies as a versioned Lambda layer and attach the required layer version to functions. This is the concrete implementation required for Lambda layer dependency management.
E:Lambda layers package reusable dependencies separately while runtime compatibility must still match. This states the AWS behavior that makes the implementation valid.
F:Each function loads the expected dependency version under the declared runtime and architecture. This is the workload-specific evidence needed to validate the change.
Incorrect Answers
A:Put the dependency archive in CloudWatch Logs expecting Lambda to import it. This is not a suitable implementation or validation step for Lambda layer dependency management; it would leave the risk that a layer built for a different runtime or architecture can cause module import failures.
B:Use an API Gateway mapping template to install native Python packages. This is not a suitable implementation or validation step for Lambda layer dependency management; it would leave the risk that a layer built for a different runtime or architecture can cause module import failures.
D:Attach the layer without checking runtime or architecture compatibility. This is not a suitable implementation or validation step for Lambda layer dependency management; it would leave the risk that a layer built for a different runtime or architecture can cause module import failures.
Question 675
A checkout service writes an order and immediately reads it from the same Region's base table. Select TWO statements that together form a sound implementation and validation plan for this requirement.
- Use ConsistentRead on a GSI Query and assume it is supported.
- Increase the item's TTL to force immediate visibility.
- An immediate post-write read returns the latest committed item in the supported read path.
- Cache the previous response to obtain stronger consistency.
- Request a strongly consistent read for the DynamoDB table or LSI where supported.
Explanation
Correct Answers
C:An immediate post-write read returns the latest committed item in the supported read path. This is the workload-specific evidence needed to validate the change.
E:Request a strongly consistent read for the DynamoDB table or LSI where supported. This is the concrete implementation required for DynamoDB strong read consistency.
Incorrect Answers
A:Use ConsistentRead on a GSI Query and assume it is supported. This is not a suitable implementation or validation step for DynamoDB strong read consistency; it would leave the risk that an eventually consistent read may briefly return a stale value after a successful write.
B:Increase the item's TTL to force immediate visibility. This is not a suitable implementation or validation step for DynamoDB strong read consistency; it would leave the risk that an eventually consistent read may briefly return a stale value after a successful write.
D:Cache the previous response to obtain stronger consistency. This is not a suitable implementation or validation step for DynamoDB strong read consistency; it would leave the risk that an eventually consistent read may briefly return a stale value after a successful write.
Question 676
A web application cannot tolerate losing all healthy instances during a major version deployment. Select THREE statements that together form a sound implementation and validation plan for this requirement.
- Disable enhanced health reporting to hide startup failures.
- Use an immutable or blue-green deployment strategy and verify replacement health before shifting users.
- New instances become healthy and application checks pass before old capacity is retired.
- Immutable deployments create replacement capacity to limit in-place update impact.
- Delete the existing environment before validating the replacement.
- Replace all application instances simultaneously during the busiest period.
Explanation
Correct Answers
B:Use an immutable or blue-green deployment strategy and verify replacement health before shifting users. This is the concrete implementation required for Elastic Beanstalk immutable update.
C:New instances become healthy and application checks pass before old capacity is retired. This is the workload-specific evidence needed to validate the change.
D:Immutable deployments create replacement capacity to limit in-place update impact. This states the AWS behavior that makes the implementation valid.
Incorrect Answers
A:Disable enhanced health reporting to hide startup failures. This is not a suitable implementation or validation step for Elastic Beanstalk immutable update; it would leave the risk that an all-at-once update can take the complete fleet offline if the revision fails.
E:Delete the existing environment before validating the replacement. This is not a suitable implementation or validation step for Elastic Beanstalk immutable update; it would leave the risk that an all-at-once update can take the complete fleet offline if the revision fails.
F:Replace all application instances simultaneously during the busiest period. This is not a suitable implementation or validation step for Elastic Beanstalk immutable update; it would leave the risk that an all-at-once update can take the complete fleet offline if the revision fails.
Question 677
A developer must test a Lambda-backed API endpoint before promoting a build to a shared AWS environment. Select TWO statements that together form a sound implementation and validation plan for this requirement.
- Unit-test only a text file containing the handler name.
- Test output demonstrates the expected HTTP or handler response for valid and invalid fixtures.
- Run AWS SAM CLI local API or invoke tests with representative events and runtime-compatible containers.
- Deploy directly to production to inspect each syntax error.
- Treat a template lint pass as proof that every business branch behaves correctly.
Explanation
Correct Answers
B:Test output demonstrates the expected HTTP or handler response for valid and invalid fixtures. This is the workload-specific evidence needed to validate the change.
C:Run AWS SAM CLI local API or invoke tests with representative events and runtime-compatible containers. This is the concrete implementation required for local SAM API testing.
Incorrect Answers
A:Unit-test only a text file containing the handler name. This is not a suitable implementation or validation step for local SAM API testing; it would leave the risk that skipping runtime-compatible local tests can miss event-shape and handler configuration bugs.
D:Deploy directly to production to inspect each syntax error. This is not a suitable implementation or validation step for local SAM API testing; it would leave the risk that skipping runtime-compatible local tests can miss event-shape and handler configuration bugs.
E:Treat a template lint pass as proof that every business branch behaves correctly. This is not a suitable implementation or validation step for local SAM API testing; it would leave the risk that skipping runtime-compatible local tests can miss event-shape and handler configuration bugs.
Question 678
A billing subscriber receives events for all product lines but should process only invoices. Select TWO statements that together form a sound implementation and validation plan for this requirement.
- Increase the Lambda timeout so SNS filters events automatically.
- Put every event into one SQS message body without useful filter fields.
- Remove all subscriber policies and expect SNS to infer business intent.
- Apply an SNS subscription filter policy on the relevant message attributes or payload fields.
- Only events matching the subscriber's policy reach its target while other topics of work are skipped.
Explanation
Correct Answers
D:Apply an SNS subscription filter policy on the relevant message attributes or payload fields. This is the concrete implementation required for SNS subscription filter policy.
E:Only events matching the subscriber's policy reach its target while other topics of work are skipped.
Incorrect Answers
A:Increase the Lambda timeout so SNS filters events automatically. This is not a suitable implementation or validation step for SNS subscription filter policy; it would leave the risk that without a filter the subscriber receives unrelated messages and spends capacity rejecting them.
B:Put every event into one SQS message body without useful filter fields. This is not a suitable implementation or validation step for SNS subscription filter policy; it would leave the risk that without a filter the subscriber receives unrelated messages and spends capacity rejecting them.
C:Remove all subscriber policies and expect SNS to infer business intent. This is not a suitable implementation or validation step for SNS subscription filter policy; it would leave the risk that without a filter the subscriber receives unrelated messages and spends capacity rejecting them.
Question 679
A product catalog has repeated reads of slowly changing entries and the database is overloaded. Select TWO statements that together form a sound implementation and validation plan for this requirement.
- Cache every mutable value forever with no invalidation.
- Use a cache-aside pattern with a defined TTL and invalidation on application updates.
- Cache hit-rate increases and backend read load falls while update invalidation keeps freshness within policy.
- Replace database writes with cache-only updates.
- Increase retry counts on cache misses without ever reading the source of truth.
Explanation
Correct Answers
B:Use a cache-aside pattern with a defined TTL and invalidation on application updates. This is the concrete implementation required for ElastiCache cache-aside.
C:Cache hit-rate increases and backend read load falls while update invalidation keeps freshness within policy.
Incorrect Answers
A:Cache every mutable value forever with no invalidation. This is not a suitable implementation or validation step for ElastiCache cache-aside; it would leave the risk that never expiring cached entries can continue to return stale records after updates.
D:Replace database writes with cache-only updates. This is not a suitable implementation or validation step for ElastiCache cache-aside; it would leave the risk that never expiring cached entries can continue to return stale records after updates.
E:Increase retry counts on cache misses without ever reading the source of truth. This is not a suitable implementation or validation step for ElastiCache cache-aside; it would leave the risk that never expiring cached entries can continue to return stale records after updates.
Question 680
One API Gateway deployment serves test and production stages that use different backend Lambda aliases. Select TWO statements that together form a sound implementation and validation plan for this requirement.
- Change only a deployment description and assume backend ARNs update automatically.
- Configure stage-specific variables or integrations pointing to the intended Lambda alias and grant invoke permissions.
- Treat CloudFront cache invalidation as an integration alias update.
- Test and production invoke the correct Lambda alias without unintended cross-stage traffic.
- Delete all API stages and keep one mutable production endpoint.
Explanation
Correct Answers
B:Configure stage-specific variables or integrations pointing to the intended Lambda alias and grant invoke permissions. This is the concrete implementation required for API Gateway stage variables.
D:Test and production invoke the correct Lambda alias without unintended cross-stage traffic. This is the workload-specific evidence needed to validate the change.
Incorrect Answers
A:Change only a deployment description and assume backend ARNs update automatically. This is not a suitable implementation or validation step for API Gateway stage variables; it would leave the risk that a hardcoded backend alias in a shared integration can route test traffic into production.
C:Treat CloudFront cache invalidation as an integration alias update. This is not a suitable implementation or validation step for API Gateway stage variables; it would leave the risk that a hardcoded backend alias in a shared integration can route test traffic into production.
E:Delete all API stages and keep one mutable production endpoint. This is not a suitable implementation or validation step for API Gateway stage variables; it would leave the risk that a hardcoded backend alias in a shared integration can route test traffic into production.