Amazon AWS Certified Developer - Associate DVA-C02 Practice Test 34
Question 330
An external tax service has a prolonged outage and checkout must degrade predictably. A teammate asks why the proposed third-party circuit breaker approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Runtime configuration separates deployment settings from executable code when values differ by environment.
- Multipart uploads allow independent parts and require a final completion call.
- Visibility hides an in-flight SQS message temporarily; it does not acknowledge completion.
- Circuit breakers limit cascading latency while allowing controlled recovery after dependency outages.
Explanation
Correct Answer
D:Circuit breakers limit cascading latency while allowing controlled recovery after dependency outages. This is the governing behavior behind the recommended change: use a circuit breaker with bounded timeouts and a documented fallback for the external dependency.
Incorrect Answers
A:The statement describes Lambda environment configuration, which is not the controlling AWS behavior for this third-party circuit breaker situation. The required implementation is: use a circuit breaker with bounded timeouts and a documented fallback for the external dependency.
B:The statement describes S3 multipart upload recovery, which is not the controlling AWS behavior for this third-party circuit breaker situation. The required implementation is: use a circuit breaker with bounded timeouts and a documented fallback for the external dependency.
C:The statement describes SQS visibility timeout, which is not the controlling AWS behavior for this third-party circuit breaker situation. The required implementation is: use a circuit breaker with bounded timeouts and a documented fallback for the external dependency.
Question 331
A team rolls out a pricing feature to only a small subset of users with rollback controls. A teammate asks why the proposed environment-specific AppConfig approach is technically appropriate. Which AWS behavior BEST explains the decision?
- API Gateway stages provide deployment boundaries and can hold environment-specific settings.
- Lambda ephemeral storage is separately configurable from memory and has finite per-environment capacity.
- Configuration releases can be separated from binary releases with validators and deployment controls.
- Explicit test fixtures make regression behavior reproducible across deployments.
Explanation
Correct Answer
C:Configuration releases can be separated from binary releases with validators and deployment controls. This is the governing behavior behind the recommended change: store environment-specific configuration in AWS AppConfig and deploy validated configuration versions.
Incorrect Answers
A:The statement describes API Gateway staging endpoints, which is not the controlling AWS behavior for this environment-specific AppConfig situation. The required implementation is: store environment-specific configuration in AWS AppConfig and deploy validated configuration versions.
B:The statement describes Lambda ephemeral disk sizing, which is not the controlling AWS behavior for this environment-specific AppConfig situation. The required implementation is: store environment-specific configuration in AWS AppConfig and deploy validated configuration versions.
D:The statement describes deployment test event generation, which is not the controlling AWS behavior for this environment-specific AppConfig situation. The required implementation is: store environment-specific configuration in AWS AppConfig and deploy validated configuration versions.
Question 332
A CI stage builds a container and should fail before image publish if unit tests fail. A teammate asks why the proposed CodeBuild buildspec sequencing approach is technically appropriate. Which AWS behavior BEST explains the decision?
- SAM local testing helps validate handler behavior before a cloud deployment but does not replace all integration tests.
- Immutable deployments create replacement capacity to limit in-place update impact.
- Lambda versions snapshot function code and configuration; aliases provide movable references.
- CodeBuild buildspec phases and exit codes control which artifacts advance in CI.
Explanation
Correct Answer
D:CodeBuild buildspec phases and exit codes control which artifacts advance in CI. This is the governing behavior behind the recommended change: define buildspec phases that install, test, and package artifacts in the correct order with failure propagation.
Incorrect Answers
A:The statement describes local SAM API testing, which is not the controlling AWS behavior for this CodeBuild buildspec sequencing situation. The required implementation is: define buildspec phases that install, test, and package artifacts in the correct order with failure propagation.
B:The statement describes Elastic Beanstalk immutable update, which is not the controlling AWS behavior for this CodeBuild buildspec sequencing situation. The required implementation is: define buildspec phases that install, test, and package artifacts in the correct order with failure propagation.
C:The statement describes Lambda alias version testing, which is not the controlling AWS behavior for this CodeBuild buildspec sequencing situation. The required implementation is: define buildspec phases that install, test, and package artifacts in the correct order with failure propagation.
Question 333
A partner application must call an AWS API in a customer account for a limited session. A teammate asks why the proposed IAM STS AssumeRole cross-account approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Bearer tokens are bounded credentials and server-side expiry checks cannot be replaced by client clock trust.
- Cross-account roles require both role trust and permission policy authorization.
- Cross-account KMS use needs key-policy authorization in the owning account and corresponding caller permissions.
- A tenant identifier from verified claims must control data scoping instead of untrusted request parameters.
Explanation
Correct Answer
B:Cross-account roles require both role trust and permission policy authorization. This is the governing behavior behind the recommended change: assume a scoped IAM role through STS with a trust policy permitting the source principal.
Incorrect Answers
A:The statement describes bearer token refresh and expiry, which is not the controlling AWS behavior for this IAM STS AssumeRole cross-account situation. The required implementation is: assume a scoped IAM role through STS with a trust policy permitting the source principal.
C:The statement describes KMS key-policy cross-account, which is not the controlling AWS behavior for this IAM STS AssumeRole cross-account situation. The required implementation is: assume a scoped IAM role through STS with a trust policy permitting the source principal.
D:The statement describes multi-tenant DynamoDB row isolation, which is not the controlling AWS behavior for this IAM STS AssumeRole cross-account situation. The required implementation is: assume a scoped IAM role through STS with a trust policy permitting the source principal.
Question 334
A production API needs an automated notification when 5xx responses cross a sustained threshold. A teammate asks why the proposed CloudWatch alarm notification approach is technically appropriate. Which AWS behavior BEST explains the decision?
- CloudWatch alarm evaluation compares metric periods against thresholds and actions trigger on state transitions.
- Authorization for an encrypted object can involve multiple services and different policy evaluators.
- EMF lets supported log consumers extract metrics from structured events and dimensions affect metric series count.
- SNS subscription filtering drops irrelevant deliveries before consumer processing.
Explanation
Correct Answer
A:CloudWatch alarm evaluation compares metric periods against thresholds and actions trigger on state transitions. This is the governing behavior behind the recommended change: create a CloudWatch alarm on the relevant metric and send state-change notifications to an approved SNS topic.
Incorrect Answers
B:The statement describes AccessDenied troubleshooting chain, which is not the controlling AWS behavior for this CloudWatch alarm notification situation. The required implementation is: create a CloudWatch alarm on the relevant metric and send state-change notifications to an approved SNS topic.
C:The statement describes CloudWatch embedded metric format, which is not the controlling AWS behavior for this CloudWatch alarm notification situation. The required implementation is: create a CloudWatch alarm on the relevant metric and send state-change notifications to an approved SNS topic.
D:The statement describes SNS subscription filter policy, which is not the controlling AWS behavior for this CloudWatch alarm notification situation. The required implementation is: create a CloudWatch alarm on the relevant metric and send state-change notifications to an approved SNS topic.
Question 335
A service stores a partner API credential and needs controlled update and audited retrieval. A teammate asks why the proposed Secrets Manager rotation approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Secrets Manager versions and rotation workflows manage sensitive values outside deployment artifacts.
- SecureString parameters protect parameter values at rest and require appropriate API and KMS permissions.
- IAM database authentication issues short-lived login tokens but database user permissions still control SQL access.
- Cognito identity pools broker temporary AWS credentials for supported identity providers.
Explanation
Correct Answer
A:Secrets Manager versions and rotation workflows manage sensitive values outside deployment artifacts. This is the governing behavior behind the recommended change: store the secret in Secrets Manager and use a supported rotation workflow with least-privilege GetSecretValue.
Incorrect Answers
B:The statement describes Parameter Store secure strings, which is not the controlling AWS behavior for this Secrets Manager rotation situation. The required implementation is: store the secret in Secrets Manager and use a supported rotation workflow with least-privilege GetSecretValue.
C:The statement describes IAM authentication and TLS for RDS, which is not the controlling AWS behavior for this Secrets Manager rotation situation. The required implementation is: store the secret in Secrets Manager and use a supported rotation workflow with least-privilege GetSecretValue.
D:The statement describes Cognito identity pool AWS access, which is not the controlling AWS behavior for this Secrets Manager rotation situation. The required implementation is: store the secret in Secrets Manager and use a supported rotation workflow with least-privilege GetSecretValue.
Question 336
An Elastic Beanstalk environment needs a safe update path that isolates new capacity before cutover. A teammate asks why the proposed Elastic Beanstalk immutable update approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Immutable deployments create replacement capacity to limit in-place update impact.
- Event-driven tests must exercise the actual source envelope and partial failure contract.
- ECS blue-green deployments route traffic between old and new task sets using load-balancer target groups.
- Explicit test fixtures make regression behavior reproducible across deployments.
Explanation
Correct Answer
A:Immutable deployments create replacement capacity to limit in-place update impact. This is the governing behavior behind the recommended change: use an immutable or blue-green deployment strategy and verify replacement health before shifting users.
Incorrect Answers
B:The statement describes SQS handler contract tests, which is not the controlling AWS behavior for this Elastic Beanstalk immutable update situation. The required implementation is: use an immutable or blue-green deployment strategy and verify replacement health before shifting users.
C:The statement describes CodeDeploy ECS blue-green, which is not the controlling AWS behavior for this Elastic Beanstalk immutable update situation. The required implementation is: use an immutable or blue-green deployment strategy and verify replacement health before shifting users.
D:The statement describes deployment test event generation, which is not the controlling AWS behavior for this Elastic Beanstalk immutable update situation. The required implementation is: use an immutable or blue-green deployment strategy and verify replacement health before shifting users.
Question 337
A DynamoDB Streams consumer needs to process only modifications with a specific status value. A teammate asks why the proposed Lambda event filtering approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Asynchronous Lambda destinations provide structured success or failure outcomes for supported invocation modes.
- Cache-aside populates on misses and requires an explicit freshness or invalidation strategy.
- Event-source filtering applies selection before Lambda invokes the function for supported sources.
- Circuit breakers limit cascading latency while allowing controlled recovery after dependency outages.
Explanation
Correct Answer
C:Event-source filtering applies selection before Lambda invokes the function for supported sources. This is the governing behavior behind the recommended change: configure a supported Lambda event source filtering pattern matching the required record fields.
Incorrect Answers
A:The statement describes Lambda asynchronous failure destination, which is not the controlling AWS behavior for this Lambda event filtering situation. The required implementation is: configure a supported Lambda event source filtering pattern matching the required record fields.
B:The statement describes ElastiCache cache-aside, which is not the controlling AWS behavior for this Lambda event filtering situation. The required implementation is: configure a supported Lambda event source filtering pattern matching the required record fields.
D:The statement describes third-party circuit breaker, which is not the controlling AWS behavior for this Lambda event filtering situation. The required implementation is: configure a supported Lambda event source filtering pattern matching the required record fields.
Question 338
A developer asks an AI assistant to generate edge-case fixtures for a new API payload. A teammate asks why the proposed AI-assisted test review approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Explicit test fixtures make regression behavior reproducible across deployments.
- Immutable artifact references make releases and rollbacks reproducible.
- Generated tests require human review and meaningful assertions to avoid false confidence.
- Event-driven tests must exercise the actual source envelope and partial failure contract.
Explanation
Correct Answer
C:Generated tests require human review and meaningful assertions to avoid false confidence. This is the governing behavior behind the recommended change: review AI-generated tests for assertions, data privacy, and realistic events before adding them to CI.
Incorrect Answers
A:The statement describes deployment test event generation, which is not the controlling AWS behavior for this AI-assisted test review situation. The required implementation is: review AI-generated tests for assertions, data privacy, and realistic events before adding them to CI.
B:The statement describes immutable container image tags, which is not the controlling AWS behavior for this AI-assisted test review situation. The required implementation is: review AI-generated tests for assertions, data privacy, and realistic events before adding them to CI.
D:The statement describes SQS handler contract tests, which is not the controlling AWS behavior for this AI-assisted test review situation. The required implementation is: review AI-generated tests for assertions, data privacy, and realistic events before adding them to CI.
Question 339
An SQS-triggered Lambda handles batches of invoice messages with one malformed item. A teammate asks why the proposed Lambda event source partial batch response approach is technically appropriate. Which AWS behavior BEST explains the decision?
- SQS partial batch response avoids unnecessary redelivery of successful records in a partially failed batch.
- Event-source filtering applies selection before Lambda invokes the function for supported sources.
- A managed state machine expresses multi-step application coordination beyond a single long-running handler.
- A dead-letter queue isolates messages that cannot be processed after bounded delivery attempts.
Explanation
Correct Answer
A:SQS partial batch response avoids unnecessary redelivery of successful records in a partially failed batch. This is the governing behavior behind the recommended change: enable partial batch responses and return the identifiers of failed batch items from the handler.
Incorrect Answers
B:The statement describes Lambda event filtering, which is not the controlling AWS behavior for this Lambda event source partial batch response situation. The required implementation is: enable partial batch responses and return the identifiers of failed batch items from the handler.
C:The statement describes Step Functions orchestration, which is not the controlling AWS behavior for this Lambda event source partial batch response situation. The required implementation is: enable partial batch responses and return the identifiers of failed batch items from the handler.
D:The statement describes SQS dead-letter queues, which is not the controlling AWS behavior for this Lambda event source partial batch response situation. The required implementation is: enable partial batch responses and return the identifiers of failed batch items from the handler.
Question 340
A shipping integration receives duplicate fulfilment notifications for the same order while a worker scales out. A teammate asks why the proposed idempotent event handling approach is technically appropriate. Which AWS behavior BEST explains the decision?
- A managed state machine expresses multi-step application coordination beyond a single long-running handler.
- Strongly consistent reads are available on DynamoDB tables and LSIs in a Region, not GSIs.
- At-least-once message delivery needs application-level idempotency for irreversible side effects.
- Lambda code obtains AWS credentials from its execution role rather than hardcoded keys.
Explanation
Correct Answer
C:At-least-once message delivery needs application-level idempotency for irreversible side effects. This is the governing behavior behind the recommended change: write a stable event ID with a conditional DynamoDB write and skip a side effect when that ID was processed.
Incorrect Answers
A:The statement describes Step Functions orchestration, which is not the controlling AWS behavior for this idempotent event handling situation. The required implementation is: write a stable event ID with a conditional DynamoDB write and skip a side effect when that ID was processed.
B:The statement describes DynamoDB strong read consistency, which is not the controlling AWS behavior for this idempotent event handling situation. The required implementation is: write a stable event ID with a conditional DynamoDB write and skip a side effect when that ID was processed.
D:The statement describes Lambda execution role least privilege, which is not the controlling AWS behavior for this idempotent event handling situation. The required implementation is: write a stable event ID with a conditional DynamoDB write and skip a side effect when that ID was processed.