Amazon AWS Certified Developer - Associate DVA-C02 Practice Test 39
Question 380
An IaC-managed stack has configuration differences from its recorded template. A teammate asks why the proposed infrastructure drift detection approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Mocks isolate code logic while independent integration checks validate real API contracts.
- IaC tracks declared infrastructure; out-of-band console edits can cause state divergence.
- Environment isolation prevents test mutations from affecting production state.
- CPU architecture and container-image manifests must match the target runtime.
Explanation
Correct Answer
B:IaC tracks declared infrastructure; out-of-band console edits can cause state divergence. This is the governing behavior behind the recommended change: run CloudFormation drift detection for supported resource types and reconcile unexpected changes into the source template.
Incorrect Answers
A:The statement describes API external dependency mocks, which is not the controlling AWS behavior for this infrastructure drift detection situation. The required implementation is: run CloudFormation drift detection for supported resource types and reconcile unexpected changes into the source template.
C:The statement describes stage-isolated integration stack, which is not the controlling AWS behavior for this infrastructure drift detection situation. The required implementation is: run CloudFormation drift detection for supported resource types and reconcile unexpected changes into the source template.
D:The statement describes container image architecture compatibility, which is not the controlling AWS behavior for this infrastructure drift detection situation. The required implementation is: run CloudFormation drift detection for supported resource types and reconcile unexpected changes into the source template.
Question 381
An event processor wants richer failure records than the original event alone after async retries. A teammate asks why the proposed Lambda destinations versus DLQ 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.
- Destinations for async Lambda invocations capture richer invocation outcomes than traditional dead-letter queues.
- Jittered bounded retries spread transient failure load instead of synchronized retry spikes.
- Conditional writes enforce state preconditions atomically during concurrent writes.
Explanation
Correct Answer
B:Destinations for async Lambda invocations capture richer invocation outcomes than traditional dead-letter queues. This is the governing behavior behind the recommended change: use a Lambda asynchronous failure destination for an invocation record instead of relying solely on a DLQ.
Incorrect Answers
A:The statement describes Lambda event source partial batch response, which is not the controlling AWS behavior for this Lambda destinations versus DLQ situation. The required implementation is: use a Lambda asynchronous failure destination for an invocation record instead of relying solely on a DLQ.
C:The statement describes SDK adaptive retries, which is not the controlling AWS behavior for this Lambda destinations versus DLQ situation. The required implementation is: use a Lambda asynchronous failure destination for an invocation record instead of relying solely on a DLQ.
D:The statement describes DynamoDB conditional update, which is not the controlling AWS behavior for this Lambda destinations versus DLQ situation. The required implementation is: use a Lambda asynchronous failure destination for an invocation record instead of relying solely on a DLQ.
Question 382
A browser-based app stores temporary tokens and should not reuse one after its expiry time. A teammate asks why the proposed bearer token refresh and expiry approach is technically appropriate. Which AWS behavior BEST explains the decision?
- SigV4 signs request components using AWS credentials and short-lived credentials include a session token.
- Bearer tokens are bounded credentials and server-side expiry checks cannot be replaced by client clock trust.
- IAM database authentication issues short-lived login tokens but database user permissions still control SQL access.
- SSE-KMS authorization involves both S3 API access and KMS cryptographic authorization.
Explanation
Correct Answer
B:Bearer tokens are bounded credentials and server-side expiry checks cannot be replaced by client clock trust. This is the governing behavior behind the recommended change: validate token expiry and use the provider's supported refresh flow rather than accepting expired tokens.
Incorrect Answers
A:The statement describes SigV4 authenticated SDK requests, which is not the controlling AWS behavior for this bearer token refresh and expiry situation. The required implementation is: validate token expiry and use the provider's supported refresh flow rather than accepting expired tokens.
C:The statement describes IAM authentication and TLS for RDS, which is not the controlling AWS behavior for this bearer token refresh and expiry situation. The required implementation is: validate token expiry and use the provider's supported refresh flow rather than accepting expired tokens.
D:The statement describes S3 SSE-KMS access, which is not the controlling AWS behavior for this bearer token refresh and expiry situation. The required implementation is: validate token expiry and use the provider's supported refresh flow rather than accepting expired tokens.
Question 383
Concurrent inventory updates must reject a stale version instead of silently overwriting each other. A teammate asks why the proposed DynamoDB conditional update approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Conditional writes enforce state preconditions atomically during concurrent writes.
- Reserved concurrency reserves and caps function concurrency; provisioned concurrency addresses pre-initialized capacity.
- DynamoDB partition-key choice influences physical request distribution and hot-key throttling.
- At-least-once message delivery needs application-level idempotency for irreversible side effects.
Explanation
Correct Answer
A:Conditional writes enforce state preconditions atomically during concurrent writes. This is the governing behavior behind the recommended change: use DynamoDB ConditionExpression with an expected state or version for the atomic update.
Incorrect Answers
B:The statement describes Lambda concurrency reservation, which is not the controlling AWS behavior for this DynamoDB conditional update situation. The required implementation is: use DynamoDB ConditionExpression with an expected state or version for the atomic update.
C:The statement describes DynamoDB partition key cardinality, which is not the controlling AWS behavior for this DynamoDB conditional update situation. The required implementation is: use DynamoDB ConditionExpression with an expected state or version for the atomic update.
D:The statement describes idempotent event handling, which is not the controlling AWS behavior for this DynamoDB conditional update situation. The required implementation is: use DynamoDB ConditionExpression with an expected state or version for the atomic update.
Question 384
A multi-client HTTP API must reject expired or wrong-audience access tokens before the Lambda integration. A teammate asks why the proposed API Gateway JWT authorizer approach is technically appropriate. Which AWS behavior BEST explains the decision?
- JWT verification checks cryptographic signature and claims, not only whether a header exists.
- Secret scanning reduces accidental credential publication but exposed keys must be invalidated.
- Authentication proves a principal, whereas tenant-level authorization constrains which records it may access.
- SecureString parameters protect parameter values at rest and require appropriate API and KMS permissions.
Explanation
Correct Answer
A:JWT verification checks cryptographic signature and claims, not only whether a header exists. This is the governing behavior behind the recommended change: configure a JWT authorizer with the trusted issuer and audience and bind it to protected API routes.
Incorrect Answers
B:The statement describes secret scanning in CI, which is not the controlling AWS behavior for this API Gateway JWT authorizer situation. The required implementation is: configure a JWT authorizer with the trusted issuer and audience and bind it to protected API routes.
C:The statement describes application tenant authorization, which is not the controlling AWS behavior for this API Gateway JWT authorizer situation. The required implementation is: configure a JWT authorizer with the trusted issuer and audience and bind it to protected API routes.
D:The statement describes Parameter Store secure strings, which is not the controlling AWS behavior for this API Gateway JWT authorizer situation. The required implementation is: configure a JWT authorizer with the trusted issuer and audience and bind it to protected API routes.
Question 385
A developer needs a distributed trace of an asynchronous dependency call chain. A teammate asks why the proposed X-Ray trace propagation approach is technically appropriate. Which AWS behavior BEST explains the decision?
- X-Ray annotations are indexed for filtering; metadata provides supplementary nonindexed values.
- Trace propagation links work across components; isolated logs alone cannot reconstruct spans reliably.
- Cache-key design determines which requests may share cached content.
- SNS subscription filtering drops irrelevant deliveries before consumer processing.
Explanation
Correct Answer
B:Trace propagation links work across components; isolated logs alone cannot reconstruct spans reliably. This is the governing behavior behind the recommended change: enable supported tracing and propagate trace context through service calls and instrumentation.
Incorrect Answers
A:The statement describes tracing annotations versus metadata, which is not the controlling AWS behavior for this X-Ray trace propagation situation. The required implementation is: enable supported tracing and propagate trace context through service calls and instrumentation.
C:The statement describes API response caching variation, which is not the controlling AWS behavior for this X-Ray trace propagation situation. The required implementation is: enable supported tracing and propagate trace context through service calls and instrumentation.
D:The statement describes SNS subscription filter policy, which is not the controlling AWS behavior for this X-Ray trace propagation situation. The required implementation is: enable supported tracing and propagate trace context through service calls and instrumentation.
Question 386
A worker fetches a sensitive connection string at startup without putting the value in source code. A teammate asks why the proposed Parameter Store secure strings approach is technically appropriate. Which AWS behavior BEST explains the decision?
- SecureString parameters protect parameter values at rest and require appropriate API and KMS permissions.
- JWT verification checks cryptographic signature and claims, not only whether a header exists.
- SigV4 signs request components using AWS credentials and short-lived credentials include a session token.
- AWS credential provider chains support ephemeral sessions and remove the need for embedded static secrets.
Explanation
Correct Answer
A:SecureString parameters protect parameter values at rest and require appropriate API and KMS permissions. This is the governing behavior behind the recommended change: store the parameter as an SSM Parameter Store SecureString with KMS protection and restricted retrieval.
Incorrect Answers
B:The statement describes API Gateway JWT authorizer, which is not the controlling AWS behavior for this Parameter Store secure strings situation. The required implementation is: store the parameter as an SSM Parameter Store SecureString with KMS protection and restricted retrieval.
C:The statement describes SigV4 authenticated SDK requests, which is not the controlling AWS behavior for this Parameter Store secure strings situation. The required implementation is: store the parameter as an SSM Parameter Store SecureString with KMS protection and restricted retrieval.
D:The statement describes temporary credential storage, which is not the controlling AWS behavior for this Parameter Store secure strings situation. The required implementation is: store the parameter as an SSM Parameter Store SecureString with KMS protection and restricted retrieval.
Question 387
A Lambda produces mixed plain text and exception dumps and operators need machine-queryable event fields. A teammate asks why the proposed structured JSON logging approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Concurrency controls must reflect downstream capacity rather than only upstream invocation volume.
- Structured fields make telemetry queryable while avoiding sensitive payload exposure.
- CloudWatch alarm evaluation compares metric periods against thresholds and actions trigger on state transitions.
- API integration timeout limits are independent of a Lambda function's own maximum runtime.
Explanation
Correct Answer
B:Structured fields make telemetry queryable while avoiding sensitive payload exposure. This is the governing behavior behind the recommended change: emit consistent structured JSON logs with timestamp, request ID, operation, severity, and redacted error fields.
Incorrect Answers
A:The statement describes concurrency backpressure, which is not the controlling AWS behavior for this structured JSON logging situation. The required implementation is: emit consistent structured JSON logs with timestamp, request ID, operation, severity, and redacted error fields.
C:The statement describes CloudWatch alarm notification, which is not the controlling AWS behavior for this structured JSON logging situation. The required implementation is: emit consistent structured JSON logs with timestamp, request ID, operation, severity, and redacted error fields.
D:The statement describes API Gateway Lambda integration timeout, which is not the controlling AWS behavior for this structured JSON logging situation. The required implementation is: emit consistent structured JSON logs with timestamp, request ID, operation, severity, and redacted error fields.
Question 388
A data parsing handler is configured with minimal memory and consumes high CPU time per request. A teammate asks why the proposed Lambda duration versus memory tradeoff approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Trace propagation links work across components; isolated logs alone cannot reconstruct spans reliably.
- Cache-key design determines which requests may share cached content.
- Lambda allocates CPU in proportion to memory, so more memory can reduce compute duration.
- Correlation IDs allow developers to join related log records and reduce noisy searches.
Explanation
Correct Answer
C:Lambda allocates CPU in proportion to memory, so more memory can reduce compute duration. This is the governing behavior behind the recommended change: benchmark memory settings and pick a measured memory and CPU allocation optimizing duration and total cost.
Incorrect Answers
A:The statement describes X-Ray trace propagation, which is not the controlling AWS behavior for this Lambda duration versus memory tradeoff situation. The required implementation is: benchmark memory settings and pick a measured memory and CPU allocation optimizing duration and total cost.
B:The statement describes API response caching variation, which is not the controlling AWS behavior for this Lambda duration versus memory tradeoff situation. The required implementation is: benchmark memory settings and pick a measured memory and CPU allocation optimizing duration and total cost.
D:The statement describes CloudWatch Logs Insights root cause, which is not the controlling AWS behavior for this Lambda duration versus memory tradeoff situation. The required implementation is: benchmark memory settings and pick a measured memory and CPU allocation optimizing duration and total cost.
Question 389
An API integration must map headers and body properties to a required downstream payload contract. A teammate asks why the proposed API Gateway mapping templates approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Cache-aside populates on misses and requires an explicit freshness or invalidation strategy.
- Integration mapping is a boundary transformation rather than a change to the client's published contract.
- Validating at the API boundary reduces invalid traffic and keeps backend operations focused.
- DynamoDB partition-key choice influences physical request distribution and hot-key throttling.
Explanation
Correct Answer
B:Integration mapping is a boundary transformation rather than a change to the client's published contract. This is the governing behavior behind the recommended change: define an API Gateway mapping template or parameter mapping that explicitly transforms the incoming request.
Incorrect Answers
A:The statement describes ElastiCache cache-aside, which is not the controlling AWS behavior for this API Gateway mapping templates situation. The required implementation is: define an API Gateway mapping template or parameter mapping that explicitly transforms the incoming request.
C:The statement describes API Gateway request validation, which is not the controlling AWS behavior for this API Gateway mapping templates situation. The required implementation is: define an API Gateway mapping template or parameter mapping that explicitly transforms the incoming request.
D:The statement describes DynamoDB partition key cardinality, which is not the controlling AWS behavior for this API Gateway mapping templates situation. The required implementation is: define an API Gateway mapping template or parameter mapping that explicitly transforms the incoming request.
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.