Amazon AWS Certified Developer - Associate DVA-C02 Practice Test 35
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.
Question 341
A Node.js Lambda package cannot load its dependency because the build omitted node_modules. A teammate asks why the proposed Lambda deployment package dependencies approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Environment isolation prevents test mutations from affecting production state.
- Zip packages must include importable dependencies in correct paths for the target runtime.
- Explicit test fixtures make regression behavior reproducible across deployments.
- Lambda ephemeral storage is separately configurable from memory and has finite per-environment capacity.
Explanation
Correct Answer
B:Zip packages must include importable dependencies in correct paths for the target runtime. This is the governing behavior behind the recommended change: build the deployment archive with runtime-compatible dependencies at the expected package paths.
Incorrect Answers
A:The statement describes stage-isolated integration stack, which is not the controlling AWS behavior for this Lambda deployment package dependencies situation. The required implementation is: build the deployment archive with runtime-compatible dependencies at the expected package paths.
C:The statement describes deployment test event generation, which is not the controlling AWS behavior for this Lambda deployment package dependencies situation. The required implementation is: build the deployment archive with runtime-compatible dependencies at the expected package paths.
D:The statement describes Lambda ephemeral disk sizing, which is not the controlling AWS behavior for this Lambda deployment package dependencies situation. The required implementation is: build the deployment archive with runtime-compatible dependencies at the expected package paths.
Question 342
A Lambda handler must read a nonsecret feature mode and memory setting for its deployed environment. A teammate asks why the proposed Lambda environment configuration approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Integration mapping is a boundary transformation rather than a change to the client's published contract.
- A dead-letter queue isolates messages that cannot be processed after bounded delivery attempts.
- Runtime configuration separates deployment settings from executable code when values differ by environment.
- VPC networking and security groups control reachability independently of IAM API authorization.
Explanation
Correct Answer
C:Runtime configuration separates deployment settings from executable code when values differ by environment. This is the governing behavior behind the recommended change: set environment-specific Lambda configuration or AWS AppConfig values and read them at runtime.
Incorrect Answers
A:The statement describes API Gateway mapping templates, which is not the controlling AWS behavior for this Lambda environment configuration situation. The required implementation is: set environment-specific Lambda configuration or AWS AppConfig values and read them at runtime.
B:The statement describes SQS dead-letter queues, which is not the controlling AWS behavior for this Lambda environment configuration situation. The required implementation is: set environment-specific Lambda configuration or AWS AppConfig values and read them at runtime.
D:The statement describes Lambda VPC private data access, which is not the controlling AWS behavior for this Lambda environment configuration situation. The required implementation is: set environment-specific Lambda configuration or AWS AppConfig values and read them at runtime.
Question 343
A downstream client depends on a stable JSON error body even when backend implementation changes. A teammate asks why the proposed contract testing versioned API approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Explicit test fixtures make regression behavior reproducible across deployments.
- Contract testing checks wire-level compatibility beyond unit correctness of a single handler.
- API Gateway stages provide deployment boundaries and can hold environment-specific settings.
- Configuration releases can be separated from binary releases with validators and deployment controls.
Explanation
Correct Answer
B:Contract testing checks wire-level compatibility beyond unit correctness of a single handler. This is the governing behavior behind the recommended change: run consumer contract tests across supported API versions and stage new behavior before promotion.
Incorrect Answers
A:The statement describes deployment test event generation, which is not the controlling AWS behavior for this contract testing versioned API situation. The required implementation is: run consumer contract tests across supported API versions and stage new behavior before promotion.
C:The statement describes API Gateway staging endpoints, which is not the controlling AWS behavior for this contract testing versioned API situation. The required implementation is: run consumer contract tests across supported API versions and stage new behavior before promotion.
D:The statement describes environment-specific AppConfig, which is not the controlling AWS behavior for this contract testing versioned API situation. The required implementation is: run consumer contract tests across supported API versions and stage new behavior before promotion.
Question 344
An ETL job reads SSE-KMS objects but sees AccessDenied despite having s3:GetObject. A teammate asks why the proposed S3 SSE-KMS access approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Cross-account roles require both role trust and permission policy authorization.
- Client-side encryption protects data prior to upload; SSE encrypts it after S3 receives the request.
- Response masking and field authorization must run before data is returned to a caller.
- SSE-KMS authorization involves both S3 API access and KMS cryptographic authorization.
Explanation
Correct Answer
D:SSE-KMS authorization involves both S3 API access and KMS cryptographic authorization. This is the governing behavior behind the recommended change: ensure the principal has S3 object permission and the required KMS decrypt permission on the encryption key.
Incorrect Answers
A:The statement describes IAM STS AssumeRole cross-account, which is not the controlling AWS behavior for this S3 SSE-KMS access situation. The required implementation is: ensure the principal has S3 object permission and the required KMS decrypt permission on the encryption key.
B:The statement describes client-side versus server-side encryption, which is not the controlling AWS behavior for this S3 SSE-KMS access situation. The required implementation is: ensure the principal has S3 object permission and the required KMS decrypt permission on the encryption key.
C:The statement describes PII response field masking, which is not the controlling AWS behavior for this S3 SSE-KMS access situation. The required implementation is: ensure the principal has S3 object permission and the required KMS decrypt permission on the encryption key.
Question 345
A checkout integration test needs to control a partner's timeout and invalid-signature responses. A teammate asks why the proposed API external dependency mocks approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Immutable deployments create replacement capacity to limit in-place update impact.
- Mocks isolate code logic while independent integration checks validate real API contracts.
- Lambda aliases can be repointed independently of immutable published version code.
- API Gateway stages provide deployment boundaries and can hold environment-specific settings.
Explanation
Correct Answer
B:Mocks isolate code logic while independent integration checks validate real API contracts. This is the governing behavior behind the recommended change: mock external dependency responses in unit tests and retain separate contract or integration tests.
Incorrect Answers
A:The statement describes Elastic Beanstalk immutable update, which is not the controlling AWS behavior for this API external dependency mocks situation. The required implementation is: mock external dependency responses in unit tests and retain separate contract or integration tests.
C:The statement describes Lambda alias rollback, which is not the controlling AWS behavior for this API external dependency mocks situation. The required implementation is: mock external dependency responses in unit tests and retain separate contract or integration tests.
D:The statement describes API Gateway staging endpoints, which is not the controlling AWS behavior for this API external dependency mocks situation. The required implementation is: mock external dependency responses in unit tests and retain separate contract or integration tests.
Question 346
A popular key expires during a promotion and every worker requests the same expensive database value. A teammate asks why the proposed application cache stampede approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Trace propagation links work across components; isolated logs alone cannot reconstruct spans reliably.
- EMF lets supported log consumers extract metrics from structured events and dimensions affect metric series count.
- Coordinated cache refresh and TTL jitter reduce thundering-herd load.
- Lambda allocates CPU in proportion to memory, so more memory can reduce compute duration.
Explanation
Correct Answer
C:Coordinated cache refresh and TTL jitter reduce thundering-herd load. This is the governing behavior behind the recommended change: add expiration jitter and single-flight request coalescing or locking around cache repopulation.
Incorrect Answers
A:The statement describes X-Ray trace propagation, which is not the controlling AWS behavior for this application cache stampede situation. The required implementation is: add expiration jitter and single-flight request coalescing or locking around cache repopulation.
B:The statement describes CloudWatch embedded metric format, which is not the controlling AWS behavior for this application cache stampede situation. The required implementation is: add expiration jitter and single-flight request coalescing or locking around cache repopulation.
D:The statement describes Lambda duration versus memory tradeoff, which is not the controlling AWS behavior for this application cache stampede situation. The required implementation is: add expiration jitter and single-flight request coalescing or locking around cache repopulation.
Question 347
A VPC-attached Lambda accesses an internal service on private subnets and receives connection timeouts. A teammate asks why the proposed Lambda VPC private data access approach is technically appropriate. Which AWS behavior BEST explains the decision?
- VPC networking and security groups control reachability independently of IAM API authorization.
- A GSI supports an alternate key-based access pattern with separately managed capacity and eventual consistency.
- Circuit breakers limit cascading latency while allowing controlled recovery after dependency outages.
- Lambda CPU allocation scales with configured memory and can speed CPU-bound functions.
Explanation
Correct Answer
A:VPC networking and security groups control reachability independently of IAM API authorization. This is the governing behavior behind the recommended change: attach Lambda to appropriate subnets and security groups with allowed routes and database connectivity.
Incorrect Answers
B:The statement describes DynamoDB GSI access pattern, which is not the controlling AWS behavior for this Lambda VPC private data access situation. The required implementation is: attach Lambda to appropriate subnets and security groups with allowed routes and database connectivity.
C:The statement describes third-party circuit breaker, which is not the controlling AWS behavior for this Lambda VPC private data access situation. The required implementation is: attach Lambda to appropriate subnets and security groups with allowed routes and database connectivity.
D:The statement describes Lambda memory CPU tuning, which is not the controlling AWS behavior for this Lambda VPC private data access situation. The required implementation is: attach Lambda to appropriate subnets and security groups with allowed routes and database connectivity.
Question 348
A synchronous API frequently reaches its integration timeout despite a long Lambda function timeout. A teammate asks why the proposed API Gateway Lambda integration timeout 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.
- Readiness controls whether a service should receive requests; liveness indicates whether the process needs restarting.
- API integration timeout limits are independent of a Lambda function's own maximum runtime.
- SNS subscription filtering drops irrelevant deliveries before consumer processing.
Explanation
Correct Answer
C:API integration timeout limits are independent of a Lambda function's own maximum runtime. This is the governing behavior behind the recommended change: measure the integration latency and redesign or optimize synchronous work to finish within the API integration limit.
Incorrect Answers
A:The statement describes DynamoDB throttling investigation, which is not the controlling AWS behavior for this API Gateway Lambda integration timeout situation. The required implementation is: measure the integration latency and redesign or optimize synchronous work to finish within the API integration limit.
B:The statement describes readiness versus liveness checks, which is not the controlling AWS behavior for this API Gateway Lambda integration timeout situation. The required implementation is: measure the integration latency and redesign or optimize synchronous work to finish within the API integration limit.
D:The statement describes SNS subscription filter policy, which is not the controlling AWS behavior for this API Gateway Lambda integration timeout situation. The required implementation is: measure the integration latency and redesign or optimize synchronous work to finish within the API integration limit.
Question 349
A service opens IAM-authenticated RDS connections over TLS with short-lived login tokens. A teammate asks why the proposed IAM authentication and TLS for RDS approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Authentication proves a principal, whereas tenant-level authorization constrains which records it may access.
- Bounded secret caching reduces repeated retrieval without making old credentials permanent.
- Client-side encryption protects data prior to upload; SSE encrypts it after S3 receives the request.
- IAM database authentication issues short-lived login tokens but database user permissions still control SQL access.
Explanation
Correct Answer
D:IAM database authentication issues short-lived login tokens but database user permissions still control SQL access. This is the governing behavior behind the recommended change: enable supported IAM database authentication, generate an auth token with the SDK, and connect over TLS with required database grants.
Incorrect Answers
A:The statement describes application tenant authorization, which is not the controlling AWS behavior for this IAM authentication and TLS for RDS situation. The required implementation is: enable supported IAM database authentication, generate an auth token with the SDK, and connect over TLS with required database grants.
B:The statement describes credential caching refresh, which is not the controlling AWS behavior for this IAM authentication and TLS for RDS situation. The required implementation is: enable supported IAM database authentication, generate an auth token with the SDK, and connect over TLS with required database grants.
C:The statement describes client-side versus server-side encryption, which is not the controlling AWS behavior for this IAM authentication and TLS for RDS situation. The required implementation is: enable supported IAM database authentication, generate an auth token with the SDK, and connect over TLS with required database grants.
Question 350
An internal API returns user objects and needs role-specific masking of email and national identifiers. A teammate asks why the proposed PII response field masking approach is technically appropriate. Which AWS behavior BEST explains the decision?
- KMS-managed rotation retains key identity and the old material required to decrypt previous ciphertext.
- 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.
- Response masking and field authorization must run before data is returned to a caller.
Explanation
Correct Answer
D:Response masking and field authorization must run before data is returned to a caller. This is the governing behavior behind the recommended change: apply field-level authorization and mask sensitive attributes before serializing responses.
Incorrect Answers
A:The statement describes KMS rotation scope, which is not the controlling AWS behavior for this PII response field masking situation. The required implementation is: apply field-level authorization and mask sensitive attributes before serializing responses.
B:The statement describes KMS key-policy cross-account, which is not the controlling AWS behavior for this PII response field masking situation. The required implementation is: apply field-level authorization and mask sensitive attributes before serializing responses.
C:The statement describes multi-tenant DynamoDB row isolation, which is not the controlling AWS behavior for this PII response field masking situation. The required implementation is: apply field-level authorization and mask sensitive attributes before serializing responses.