Amazon AWS Certified Developer - Associate DVA-C02 Practice Test 32
Question 310
A developer wants to filter traces by environment and operation while attaching detailed diagnostic context. A teammate asks why the proposed tracing annotations versus metadata approach is technically appropriate. Which AWS behavior BEST explains the decision?
- DynamoDB throttling can reflect hot partitions or configured capacity constraints, not just network faults.
- Lambda allocates CPU in proportion to memory, so more memory can reduce compute duration.
- CloudWatch log groups retain data indefinitely by default unless a retention setting is configured.
- X-Ray annotations are indexed for filtering; metadata provides supplementary nonindexed values.
Explanation
Correct Answer
D:X-Ray annotations are indexed for filtering; metadata provides supplementary nonindexed values. This is the governing behavior behind the recommended change: use low-cardinality X-Ray annotations for indexed filters and metadata for nonindexed diagnostic details.
Incorrect Answers
A:The statement describes DynamoDB throttling investigation, which is not the controlling AWS behavior for this tracing annotations versus metadata situation. The required implementation is: use low-cardinality X-Ray annotations for indexed filters and metadata for nonindexed diagnostic details.
B:The statement describes Lambda duration versus memory tradeoff, which is not the controlling AWS behavior for this tracing annotations versus metadata situation. The required implementation is: use low-cardinality X-Ray annotations for indexed filters and metadata for nonindexed diagnostic details.
C:The statement describes CloudWatch log retention, which is not the controlling AWS behavior for this tracing annotations versus metadata situation. The required implementation is: use low-cardinality X-Ray annotations for indexed filters and metadata for nonindexed diagnostic details.
Question 311
A batch worker consumes SQS messages faster than a constrained third-party dependency can process. A teammate asks why the proposed concurrency backpressure approach is technically appropriate. Which AWS behavior BEST explains the decision?
- CloudWatch log groups retain data indefinitely by default unless a retention setting is configured.
- Structured fields make telemetry queryable while avoiding sensitive payload exposure.
- SNS subscription filtering drops irrelevant deliveries before consumer processing.
- Concurrency controls must reflect downstream capacity rather than only upstream invocation volume.
Explanation
Correct Answer
D:Concurrency controls must reflect downstream capacity rather than only upstream invocation volume. This is the governing behavior behind the recommended change: limit parallelism and introduce queue-based backpressure with bounded retries and metrics.
Incorrect Answers
A:The statement describes CloudWatch log retention, which is not the controlling AWS behavior for this concurrency backpressure situation. The required implementation is: limit parallelism and introduce queue-based backpressure with bounded retries and metrics.
B:The statement describes structured JSON logging, which is not the controlling AWS behavior for this concurrency backpressure situation. The required implementation is: limit parallelism and introduce queue-based backpressure with bounded retries and metrics.
C:The statement describes SNS subscription filter policy, which is not the controlling AWS behavior for this concurrency backpressure situation. The required implementation is: limit parallelism and introduce queue-based backpressure with bounded retries and metrics.
Question 312
A Python service must authenticate API calls to AWS without putting a static signature string into requests. A teammate asks why the proposed SigV4 authenticated SDK requests approach is technically appropriate. Which AWS behavior BEST explains the decision?
- IAM database authentication issues short-lived login tokens but database user permissions still control SQL access.
- TLS certificates authenticate endpoint names and protect traffic in transit.
- Separate execution roles reduce blast radius when individual workloads are compromised.
- SigV4 signs request components using AWS credentials and short-lived credentials include a session token.
Explanation
Correct Answer
D:SigV4 signs request components using AWS credentials and short-lived credentials include a session token. This is the governing behavior behind the recommended change: use an AWS SDK with its default credential provider chain and SigV4 request signing.
Incorrect Answers
A:The statement describes IAM authentication and TLS for RDS, which is not the controlling AWS behavior for this SigV4 authenticated SDK requests situation. The required implementation is: use an AWS SDK with its default credential provider chain and SigV4 request signing.
B:The statement describes TLS certificate rotation ACM, which is not the controlling AWS behavior for this SigV4 authenticated SDK requests situation. The required implementation is: use an AWS SDK with its default credential provider chain and SigV4 request signing.
C:The statement describes Lambda execution-role separation, which is not the controlling AWS behavior for this SigV4 authenticated SDK requests situation. The required implementation is: use an AWS SDK with its default credential provider chain and SigV4 request signing.
Question 313
A support incident needs all function log events associated with one failed customer request. A teammate asks why the proposed CloudWatch Logs Insights root cause approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Structured fields make telemetry queryable while avoiding sensitive payload exposure.
- Correlation IDs allow developers to join related log records and reduce noisy searches.
- CloudWatch log groups retain data indefinitely by default unless a retention setting is configured.
- API integration timeout limits are independent of a Lambda function's own maximum runtime.
Explanation
Correct Answer
B:Correlation IDs allow developers to join related log records and reduce noisy searches. This is the governing behavior behind the recommended change: query CloudWatch Logs Insights with structured fields and the request correlation identifier.
Incorrect Answers
A:The statement describes structured JSON logging, which is not the controlling AWS behavior for this CloudWatch Logs Insights root cause situation. The required implementation is: query CloudWatch Logs Insights with structured fields and the request correlation identifier.
C:The statement describes CloudWatch log retention, which is not the controlling AWS behavior for this CloudWatch Logs Insights root cause situation. The required implementation is: query CloudWatch Logs Insights with structured fields and the request correlation identifier.
D:The statement describes API Gateway Lambda integration timeout, which is not the controlling AWS behavior for this CloudWatch Logs Insights root cause situation. The required implementation is: query CloudWatch Logs Insights with structured fields and the request correlation identifier.
Question 314
A media job runs longer than its SQS visibility timeout and two consumers start identical transcoding tasks. A teammate asks why the proposed SQS visibility timeout 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.
- Visibility hides an in-flight SQS message temporarily; it does not acknowledge completion.
- Query uses key conditions while Scan examines items beyond the requested partition.
- A GSI supports an alternate key-based access pattern with separately managed capacity and eventual consistency.
Explanation
Correct Answer
B:Visibility hides an in-flight SQS message temporarily; it does not acknowledge completion. This is the governing behavior behind the recommended change: set the SQS visibility timeout above the expected processing interval and delete the message after successful work.
Incorrect Answers
A:The statement describes Step Functions orchestration, which is not the controlling AWS behavior for this SQS visibility timeout situation. The required implementation is: set the SQS visibility timeout above the expected processing interval and delete the message after successful work.
C:The statement describes DynamoDB Query versus Scan, which is not the controlling AWS behavior for this SQS visibility timeout situation. The required implementation is: set the SQS visibility timeout above the expected processing interval and delete the message after successful work.
D:The statement describes DynamoDB GSI access pattern, which is not the controlling AWS behavior for this SQS visibility timeout situation. The required implementation is: set the SQS visibility timeout above the expected processing interval and delete the message after successful work.
Question 315
A mobile app wants managed account registration, confirmation, and JWT access tokens for backend endpoints. A teammate asks why the proposed Cognito user pool authentication approach is technically appropriate. Which AWS behavior BEST explains the decision?
- AWS credential provider chains support ephemeral sessions and remove the need for embedded static secrets.
- Envelope encryption uses a data key for payload encryption and protects that key using a KMS key.
- Separate execution roles reduce blast radius when individual workloads are compromised.
- Cognito user pools handle user sign-in and tokens, while identity pools serve temporary AWS credentials.
Explanation
Correct Answer
D:Cognito user pools handle user sign-in and tokens, while identity pools serve temporary AWS credentials. This is the governing behavior behind the recommended change: use an Amazon Cognito user pool as the user directory and authenticate users to obtain tokens.
Incorrect Answers
A:The statement describes temporary credential storage, which is not the controlling AWS behavior for this Cognito user pool authentication situation. The required implementation is: use an Amazon Cognito user pool as the user directory and authenticate users to obtain tokens.
B:The statement describes KMS envelope encryption, which is not the controlling AWS behavior for this Cognito user pool authentication situation. The required implementation is: use an Amazon Cognito user pool as the user directory and authenticate users to obtain tokens.
C:The statement describes Lambda execution-role separation, which is not the controlling AWS behavior for this Cognito user pool authentication situation. The required implementation is: use an Amazon Cognito user pool as the user directory and authenticate users to obtain tokens.
Question 316
A scheduled Lambda writes objects to a single S3 bucket and its role is missing PutObject. A teammate asks why the proposed Lambda execution role least privilege approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Full-text search uses analyzed inverted indexes rather than DynamoDB exact-key access.
- A dead-letter queue isolates messages that cannot be processed after bounded delivery attempts.
- Lambda code obtains AWS credentials from its execution role rather than hardcoded keys.
- SQS partial batch response avoids unnecessary redelivery of successful records in a partially failed batch.
Explanation
Correct Answer
C:Lambda code obtains AWS credentials from its execution role rather than hardcoded keys. This is the governing behavior behind the recommended change: attach a least-privilege policy to the Lambda execution role for the required API actions and resource ARN.
Incorrect Answers
A:The statement describes OpenSearch full-text queries, which is not the controlling AWS behavior for this Lambda execution role least privilege situation. The required implementation is: attach a least-privilege policy to the Lambda execution role for the required API actions and resource ARN.
B:The statement describes SQS dead-letter queues, which is not the controlling AWS behavior for this Lambda execution role least privilege situation. The required implementation is: attach a least-privilege policy to the Lambda execution role for the required API actions and resource ARN.
D:The statement describes Lambda event source partial batch response, which is not the controlling AWS behavior for this Lambda execution role least privilege situation. The required implementation is: attach a least-privilege policy to the Lambda execution role for the required API actions and resource ARN.
Question 317
An email worker subscribed to a shared SNS topic must ignore order telemetry messages. A teammate asks why the proposed SNS subscription filter policy approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Coordinated cache refresh and TTL jitter reduce thundering-herd load.
- Structured fields make telemetry queryable while avoiding sensitive payload exposure.
- Readiness controls whether a service should receive requests; liveness indicates whether the process needs restarting.
- SNS subscription filtering drops irrelevant deliveries before consumer processing.
Explanation
Correct Answer
D:SNS subscription filtering drops irrelevant deliveries before consumer processing. This is the governing behavior behind the recommended change: apply an SNS subscription filter policy on the relevant message attributes or payload fields.
Incorrect Answers
A:The statement describes application cache stampede, which is not the controlling AWS behavior for this SNS subscription filter policy situation. The required implementation is: apply an SNS subscription filter policy on the relevant message attributes or payload fields.
B:The statement describes structured JSON logging, which is not the controlling AWS behavior for this SNS subscription filter policy situation. The required implementation is: apply an SNS subscription filter policy on the relevant message attributes or payload fields.
C:The statement describes readiness versus liveness checks, which is not the controlling AWS behavior for this SNS subscription filter policy situation. The required implementation is: apply an SNS subscription filter policy on the relevant message attributes or payload fields.
Question 318
A production stack update fails with a permission or dependency error shown in resource events. A teammate asks why the proposed failed CloudFormation deployment approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Stack resource events reveal deployment-level failures that application logs might never contain.
- EMF lets supported log consumers extract metrics from structured events and dimensions affect metric series count.
- X-Ray annotations are indexed for filtering; metadata provides supplementary nonindexed values.
- Authorization for an encrypted object can involve multiple services and different policy evaluators.
Explanation
Correct Answer
A:Stack resource events reveal deployment-level failures that application logs might never contain. This is the governing behavior behind the recommended change: inspect CloudFormation stack events and failed resource status to identify the underlying deployment error.
Incorrect Answers
B:The statement describes CloudWatch embedded metric format, which is not the controlling AWS behavior for this failed CloudFormation deployment situation. The required implementation is: inspect CloudFormation stack events and failed resource status to identify the underlying deployment error.
C:The statement describes tracing annotations versus metadata, which is not the controlling AWS behavior for this failed CloudFormation deployment situation. The required implementation is: inspect CloudFormation stack events and failed resource status to identify the underlying deployment error.
D:The statement describes AccessDenied troubleshooting chain, which is not the controlling AWS behavior for this failed CloudFormation deployment situation. The required implementation is: inspect CloudFormation stack events and failed resource status to identify the underlying deployment error.
Question 319
A stage promotion should change the backend alias without copying an entire REST API definition. A teammate asks why the proposed API Gateway stage variables approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Environment isolation prevents test mutations from affecting production state.
- Lambda aliases can be repointed independently of immutable published version code.
- API Gateway stage configuration can parameterize integrations for separate environments.
- Mocks isolate code logic while independent integration checks validate real API contracts.
Explanation
Correct Answer
C:API Gateway stage configuration can parameterize integrations for separate environments. This is the governing behavior behind the recommended change: configure stage-specific variables or integrations pointing to the intended Lambda alias and grant invoke permissions.
Incorrect Answers
A:The statement describes stage-isolated integration stack, which is not the controlling AWS behavior for this API Gateway stage variables situation. The required implementation is: configure stage-specific variables or integrations pointing to the intended Lambda alias and grant invoke permissions.
B:The statement describes Lambda alias rollback, which is not the controlling AWS behavior for this API Gateway stage variables situation. The required implementation is: configure stage-specific variables or integrations pointing to the intended Lambda alias and grant invoke permissions.
D:The statement describes API external dependency mocks, which is not the controlling AWS behavior for this API Gateway stage variables situation. The required implementation is: configure stage-specific variables or integrations pointing to the intended Lambda alias and grant invoke permissions.
Question 320
A diagnostic middleware records full request headers including Authorization during a failed API call. A teammate asks why the proposed Lambda environment secret leakage 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.
- Encryption at rest does not stop an application from leaking plaintext secrets during logging.
- IAM database authentication issues short-lived login tokens but database user permissions still control SQL access.
- Secret scanning reduces accidental credential publication but exposed keys must be invalidated.
Explanation
Correct Answer
B:Encryption at rest does not stop an application from leaking plaintext secrets during logging. This is the governing behavior behind the recommended change: redact secret-bearing environment values and authorization headers from structured application logs.
Incorrect Answers
A:The statement describes SigV4 authenticated SDK requests, which is not the controlling AWS behavior for this Lambda environment secret leakage situation. The required implementation is: redact secret-bearing environment values and authorization headers from structured application logs.
C:The statement describes IAM authentication and TLS for RDS, which is not the controlling AWS behavior for this Lambda environment secret leakage situation. The required implementation is: redact secret-bearing environment values and authorization headers from structured application logs.
D:The statement describes secret scanning in CI, which is not the controlling AWS behavior for this Lambda environment secret leakage situation. The required implementation is: redact secret-bearing environment values and authorization headers from structured application logs.