Amazon AWS Certified Developer - Associate DVA-C02 Practice Test 40
Question 390
A Kubernetes-style web service restarts unnecessarily when downstream readiness briefly fails. A teammate asks why the proposed readiness versus liveness checks approach is technically appropriate. Which AWS behavior BEST explains the decision?
- EMF lets supported log consumers extract metrics from structured events and dimensions affect metric series count.
- DynamoDB throttling can reflect hot partitions or configured capacity constraints, not just network faults.
- Readiness controls whether a service should receive requests; liveness indicates whether the process needs restarting.
- Correlation IDs allow developers to join related log records and reduce noisy searches.
Explanation
Correct Answer
C:Readiness controls whether a service should receive requests; liveness indicates whether the process needs restarting. This is the governing behavior behind the recommended change: separate liveness checks from readiness checks and return healthy only when the correct condition holds.
Incorrect Answers
A:The statement describes CloudWatch embedded metric format, which is not the controlling AWS behavior for this readiness versus liveness checks situation. The required implementation is: separate liveness checks from readiness checks and return healthy only when the correct condition holds.
B:The statement describes DynamoDB throttling investigation, which is not the controlling AWS behavior for this readiness versus liveness checks situation. The required implementation is: separate liveness checks from readiness checks and return healthy only when the correct condition holds.
D:The statement describes CloudWatch Logs Insights root cause, which is not the controlling AWS behavior for this readiness versus liveness checks situation. The required implementation is: separate liveness checks from readiness checks and return healthy only when the correct condition holds.
Question 391
A data processor's release checks need controlled success and failure events for regression testing. A teammate asks why the proposed deployment test event generation approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Immutable artifact references make releases and rollbacks reproducible.
- Explicit test fixtures make regression behavior reproducible across deployments.
- IaC tracks declared infrastructure; out-of-band console edits can cause state divergence.
- Zip packages must include importable dependencies in correct paths for the target runtime.
Explanation
Correct Answer
B:Explicit test fixtures make regression behavior reproducible across deployments. This is the governing behavior behind the recommended change: create versioned JSON test event fixtures and assert both expected outputs and error paths during automated tests.
Incorrect Answers
A:The statement describes immutable container image tags, which is not the controlling AWS behavior for this deployment test event generation situation. The required implementation is: create versioned JSON test event fixtures and assert both expected outputs and error paths during automated tests.
C:The statement describes infrastructure drift detection, which is not the controlling AWS behavior for this deployment test event generation situation. The required implementation is: create versioned JSON test event fixtures and assert both expected outputs and error paths during automated tests.
D:The statement describes Lambda deployment package dependencies, which is not the controlling AWS behavior for this deployment test event generation situation. The required implementation is: create versioned JSON test event fixtures and assert both expected outputs and error paths during automated tests.
Question 392
A streaming application needs per-customer record order while spreading load across independent partitions. A teammate asks why the proposed Kinesis shard partitioning approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Kinesis ordering is guaranteed within a shard and partition key choices determine shard affinity.
- Cache-aside populates on misses and requires an explicit freshness or invalidation strategy.
- At-least-once message delivery needs application-level idempotency for irreversible side effects.
- A GSI supports an alternate key-based access pattern with separately managed capacity and eventual consistency.
Explanation
Correct Answer
A:Kinesis ordering is guaranteed within a shard and partition key choices determine shard affinity. This is the governing behavior behind the recommended change: select a stable partition key for each entity and distribute different keys across Kinesis shards.
Incorrect Answers
B:The statement describes ElastiCache cache-aside, which is not the controlling AWS behavior for this Kinesis shard partitioning situation. The required implementation is: select a stable partition key for each entity and distribute different keys across Kinesis shards.
C:The statement describes idempotent event handling, which is not the controlling AWS behavior for this Kinesis shard partitioning situation. The required implementation is: select a stable partition key for each entity and distribute different keys across Kinesis shards.
D:The statement describes DynamoDB GSI access pattern, which is not the controlling AWS behavior for this Kinesis shard partitioning situation. The required implementation is: select a stable partition key for each entity and distribute different keys across Kinesis shards.
Question 393
A serverless handler emits structured events and wants CloudWatch to extract metrics from logs. A teammate asks why the proposed CloudWatch embedded metric format approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Lambda cold-start initialization is distinct from code execution duration.
- CloudWatch log groups retain data indefinitely by default unless a retention setting is configured.
- EMF lets supported log consumers extract metrics from structured events and dimensions affect metric series count.
- API integration timeout limits are independent of a Lambda function's own maximum runtime.
Explanation
Correct Answer
C:EMF lets supported log consumers extract metrics from structured events and dimensions affect metric series count. This is the governing behavior behind the recommended change: emit valid CloudWatch Embedded Metric Format JSON with metric definitions and safe dimension cardinality.
Incorrect Answers
A:The statement describes Lambda Init Duration diagnosis, which is not the controlling AWS behavior for this CloudWatch embedded metric format situation. The required implementation is: emit valid CloudWatch Embedded Metric Format JSON with metric definitions and safe dimension cardinality.
B:The statement describes CloudWatch log retention, which is not the controlling AWS behavior for this CloudWatch embedded metric format situation. The required implementation is: emit valid CloudWatch Embedded Metric Format JSON with metric definitions and safe dimension cardinality.
D:The statement describes API Gateway Lambda integration timeout, which is not the controlling AWS behavior for this CloudWatch embedded metric format situation. The required implementation is: emit valid CloudWatch Embedded Metric Format JSON with metric definitions and safe dimension cardinality.
Question 394
A shopping-cart table uses TTL cleanup and needs correct authorization even before deletion. A teammate asks why the proposed DynamoDB TTL expiry semantics approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Multipart uploads allow independent parts and require a final completion call.
- DynamoDB TTL deletion is asynchronous and must not be the only immediate expiry enforcement.
- At-least-once message delivery needs application-level idempotency for irreversible side effects.
- Reserved concurrency reserves and caps function concurrency; provisioned concurrency addresses pre-initialized capacity.
Explanation
Correct Answer
B:DynamoDB TTL deletion is asynchronous and must not be the only immediate expiry enforcement. This is the governing behavior behind the recommended change: check the epoch expiration attribute in application logic while using DynamoDB TTL for eventual cleanup.
Incorrect Answers
A:The statement describes S3 multipart upload recovery, which is not the controlling AWS behavior for this DynamoDB TTL expiry semantics situation. The required implementation is: check the epoch expiration attribute in application logic while using DynamoDB TTL for eventual cleanup.
C:The statement describes idempotent event handling, which is not the controlling AWS behavior for this DynamoDB TTL expiry semantics situation. The required implementation is: check the epoch expiration attribute in application logic while using DynamoDB TTL for eventual cleanup.
D:The statement describes Lambda concurrency reservation, which is not the controlling AWS behavior for this DynamoDB TTL expiry semantics situation. The required implementation is: check the epoch expiration attribute in application logic while using DynamoDB TTL for eventual cleanup.
Question 395
A product catalog needs tokenized free-text matching rather than exact primary-key lookups. A teammate asks why the proposed OpenSearch full-text queries approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Asynchronous Lambda destinations provide structured success or failure outcomes for supported invocation modes.
- Lambda layers package reusable dependencies separately while runtime compatibility must still match.
- Full-text search uses analyzed inverted indexes rather than DynamoDB exact-key access.
- Multipart uploads allow independent parts and require a final completion call.
Explanation
Correct Answer
C:Full-text search uses analyzed inverted indexes rather than DynamoDB exact-key access. This is the governing behavior behind the recommended change: index searchable fields in Amazon OpenSearch Service and query the text index with an appropriate analyzer.
Incorrect Answers
A:The statement describes Lambda asynchronous failure destination, which is not the controlling AWS behavior for this OpenSearch full-text queries situation. The required implementation is: index searchable fields in Amazon OpenSearch Service and query the text index with an appropriate analyzer.
B:The statement describes Lambda layer dependency management, which is not the controlling AWS behavior for this OpenSearch full-text queries situation. The required implementation is: index searchable fields in Amazon OpenSearch Service and query the text index with an appropriate analyzer.
D:The statement describes S3 multipart upload recovery, which is not the controlling AWS behavior for this OpenSearch full-text queries situation. The required implementation is: index searchable fields in Amazon OpenSearch Service and query the text index with an appropriate analyzer.
Question 396
An application principal has matching resource access but an explicit deny in its policy boundary. A teammate asks why the proposed IAM policy explicit deny approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Secret scanning reduces accidental credential publication but exposed keys must be invalidated.
- Resource policies can restrict the source principals or network context independently from route authorizers.
- An explicit Deny takes precedence over any applicable Allow in AWS policy evaluation.
- TLS certificates authenticate endpoint names and protect traffic in transit.
Explanation
Correct Answer
C:An explicit Deny takes precedence over any applicable Allow in AWS policy evaluation. This is the governing behavior behind the recommended change: evaluate explicit denies in identity, resource, permissions-boundary, and organization policy paths.
Incorrect Answers
A:The statement describes secret scanning in CI, which is not the controlling AWS behavior for this IAM policy explicit deny situation. The required implementation is: evaluate explicit denies in identity, resource, permissions-boundary, and organization policy paths.
B:The statement describes API Gateway resource policy, which is not the controlling AWS behavior for this IAM policy explicit deny situation. The required implementation is: evaluate explicit denies in identity, resource, permissions-boundary, and organization policy paths.
D:The statement describes TLS certificate rotation ACM, which is not the controlling AWS behavior for this IAM policy explicit deny situation. The required implementation is: evaluate explicit denies in identity, resource, permissions-boundary, and organization policy paths.
Question 397
A containerized API uses separate target groups to validate a new task set before production traffic changes. A teammate asks why the proposed CodeDeploy ECS blue-green approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Immutable artifact references make releases and rollbacks reproducible.
- ECS blue-green deployments route traffic between old and new task sets using load-balancer target groups.
- Mocks isolate code logic while independent integration checks validate real API contracts.
- Template parameters and mappings allow controlled environment variation from one IaC definition.
Explanation
Correct Answer
B:ECS blue-green deployments route traffic between old and new task sets using load-balancer target groups. This is the governing behavior behind the recommended change: use a blue-green ECS deployment with CodeDeploy and controlled target-group traffic switching.
Incorrect Answers
A:The statement describes immutable container image tags, which is not the controlling AWS behavior for this CodeDeploy ECS blue-green situation. The required implementation is: use a blue-green ECS deployment with CodeDeploy and controlled target-group traffic switching.
C:The statement describes API external dependency mocks, which is not the controlling AWS behavior for this CodeDeploy ECS blue-green situation. The required implementation is: use a blue-green ECS deployment with CodeDeploy and controlled target-group traffic switching.
D:The statement describes CloudFormation resource parameters, which is not the controlling AWS behavior for this CodeDeploy ECS blue-green situation. The required implementation is: use a blue-green ECS deployment with CodeDeploy and controlled target-group traffic switching.
Question 398
A team needs cost control and predictable deletion of old routine Lambda logs. A teammate asks why the proposed CloudWatch log retention approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Readiness controls whether a service should receive requests; liveness indicates whether the process needs restarting.
- Concurrency controls must reflect downstream capacity rather than only upstream invocation volume.
- API integration timeout limits are independent of a Lambda function's own maximum runtime.
- CloudWatch log groups retain data indefinitely by default unless a retention setting is configured.
Explanation
Correct Answer
D:CloudWatch log groups retain data indefinitely by default unless a retention setting is configured. This is the governing behavior behind the recommended change: set a CloudWatch Logs retention policy matching the operational retention requirement.
Incorrect Answers
A:The statement describes readiness versus liveness checks, which is not the controlling AWS behavior for this CloudWatch log retention situation. The required implementation is: set a CloudWatch Logs retention policy matching the operational retention requirement.
B:The statement describes concurrency backpressure, which is not the controlling AWS behavior for this CloudWatch log retention situation. The required implementation is: set a CloudWatch Logs retention policy matching the operational retention requirement.
C:The statement describes API Gateway Lambda integration timeout, which is not the controlling AWS behavior for this CloudWatch log retention situation. The required implementation is: set a CloudWatch Logs retention policy matching the operational retention requirement.
Question 399
A team needs to deploy a shared Node.js utility library with several separate Lambda handlers. A teammate asks why the proposed Lambda layer dependency management approach is technically appropriate. Which AWS behavior BEST explains the decision?
- A dead-letter queue isolates messages that cannot be processed after bounded delivery attempts.
- AI coding suggestions accelerate development but do not replace validation or security review.
- Lambda layers package reusable dependencies separately while runtime compatibility must still match.
- Runtime configuration separates deployment settings from executable code when values differ by environment.
Explanation
Correct Answer
C:Lambda layers package reusable dependencies separately while runtime compatibility must still match. This is the governing behavior behind the recommended change: publish compatible dependencies as a versioned Lambda layer and attach the required layer version to functions.
Incorrect Answers
A:The statement describes SQS dead-letter queues, which is not the controlling AWS behavior for this Lambda layer dependency management situation. The required implementation is: publish compatible dependencies as a versioned Lambda layer and attach the required layer version to functions.
B:The statement describes Amazon Q Developer review, which is not the controlling AWS behavior for this Lambda layer dependency management situation. The required implementation is: publish compatible dependencies as a versioned Lambda layer and attach the required layer version to functions.
D:The statement describes Lambda environment configuration, which is not the controlling AWS behavior for this Lambda layer dependency management situation. The required implementation is: publish compatible dependencies as a versioned Lambda layer and attach the required layer version to functions.
Question 400
A product system routes events to different consumers based on detail-type and account metadata. A teammate asks why the proposed EventBridge event routing approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Full-text search uses analyzed inverted indexes rather than DynamoDB exact-key access.
- Strongly consistent reads are available on DynamoDB tables and LSIs in a Region, not GSIs.
- EventBridge rules route structured events by matching attributes without embedding consumer addresses in producer code.
- Kinesis ordering is guaranteed within a shard and partition key choices determine shard affinity.
Explanation
Correct Answer
C:EventBridge rules route structured events by matching attributes without embedding consumer addresses in producer code. This is the governing behavior behind the recommended change: put events on an EventBridge bus and create rules matching the required event patterns to targets.
Incorrect Answers
A:The statement describes OpenSearch full-text queries, which is not the controlling AWS behavior for this EventBridge event routing situation. The required implementation is: put events on an EventBridge bus and create rules matching the required event patterns to targets.
B:The statement describes DynamoDB strong read consistency, which is not the controlling AWS behavior for this EventBridge event routing situation. The required implementation is: put events on an EventBridge bus and create rules matching the required event patterns to targets.
D:The statement describes Kinesis shard partitioning, which is not the controlling AWS behavior for this EventBridge event routing situation. The required implementation is: put events on an EventBridge bus and create rules matching the required event patterns to targets.