Amazon AWS Certified Developer - Associate DVA-C02 Practice Test 38
Question 370
A financial API requires a human approval gate after canary metrics are reviewed. A teammate asks why the proposed CodePipeline gated promotion approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Lambda versions snapshot function code and configuration; aliases provide movable references.
- Immutable deployments create replacement capacity to limit in-place update impact.
- Environment isolation prevents test mutations from affecting production state.
- CI/CD stage ordering and approvals reduce uncontrolled deployment changes.
Explanation
Correct Answer
D:CI/CD stage ordering and approvals reduce uncontrolled deployment changes. This is the governing behavior behind the recommended change: configure the existing pipeline stages to build, test, approve where required, and promote immutable artifacts.
Incorrect Answers
A:The statement describes Lambda alias version testing, which is not the controlling AWS behavior for this CodePipeline gated promotion situation. The required implementation is: configure the existing pipeline stages to build, test, approve where required, and promote immutable artifacts.
B:The statement describes Elastic Beanstalk immutable update, which is not the controlling AWS behavior for this CodePipeline gated promotion situation. The required implementation is: configure the existing pipeline stages to build, test, approve where required, and promote immutable artifacts.
C:The statement describes stage-isolated integration stack, which is not the controlling AWS behavior for this CodePipeline gated promotion situation. The required implementation is: configure the existing pipeline stages to build, test, approve where required, and promote immutable artifacts.
Question 371
A document portal lets users download one private object for a limited time. A teammate asks why the proposed S3 presigned URLs approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Query uses key conditions while Scan examines items beyond the requested partition.
- 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.
- Presigned requests delegate bounded use of the signing principal's permissions without exposing long-lived keys.
Explanation
Correct Answer
D:Presigned requests delegate bounded use of the signing principal's permissions without exposing long-lived keys. This is the governing behavior behind the recommended change: generate a scoped presigned S3 URL with the intended method, object key, and expiration.
Incorrect Answers
A:The statement describes DynamoDB Query versus Scan, which is not the controlling AWS behavior for this S3 presigned URLs situation. The required implementation is: generate a scoped presigned S3 URL with the intended method, object key, and expiration.
B:The statement describes EventBridge event routing, which is not the controlling AWS behavior for this S3 presigned URLs situation. The required implementation is: generate a scoped presigned S3 URL with the intended method, object key, and expiration.
C:The statement describes Kinesis shard partitioning, which is not the controlling AWS behavior for this S3 presigned URLs situation. The required implementation is: generate a scoped presigned S3 URL with the intended method, object key, and expiration.
Question 372
A rollback exercise needs to switch a function's traffic pointer without editing code packages. A teammate asks why the proposed Lambda alias version testing approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Lambda versions snapshot function code and configuration; aliases provide movable references.
- Contract testing checks wire-level compatibility beyond unit correctness of a single handler.
- API Gateway stage configuration can parameterize integrations for separate environments.
- Lambda aliases can be repointed independently of immutable published version code.
Explanation
Correct Answer
A:Lambda versions snapshot function code and configuration; aliases provide movable references. This is the governing behavior behind the recommended change: publish immutable Lambda versions and point separate aliases to the intended tested version.
Incorrect Answers
B:The statement describes contract testing versioned API, which is not the controlling AWS behavior for this Lambda alias version testing situation. The required implementation is: publish immutable Lambda versions and point separate aliases to the intended tested version.
C:The statement describes API Gateway stage variables, which is not the controlling AWS behavior for this Lambda alias version testing situation. The required implementation is: publish immutable Lambda versions and point separate aliases to the intended tested version.
D:The statement describes Lambda alias rollback, which is not the controlling AWS behavior for this Lambda alias version testing situation. The required implementation is: publish immutable Lambda versions and point separate aliases to the intended tested version.
Question 373
An internal integration test requires a separate base path for new API behavior. A teammate asks why the proposed API Gateway staging endpoints approach is technically appropriate. Which AWS behavior BEST explains the decision?
- API Gateway stages provide deployment boundaries and can hold environment-specific settings.
- 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.
- IaC tracks declared infrastructure; out-of-band console edits can cause state divergence.
Explanation
Correct Answer
A:API Gateway stages provide deployment boundaries and can hold environment-specific settings. This is the governing behavior behind the recommended change: deploy API changes to an isolated API Gateway stage with stage-specific configuration.
Incorrect Answers
B:The statement describes local SAM API testing, which is not the controlling AWS behavior for this API Gateway staging endpoints situation. The required implementation is: deploy API changes to an isolated API Gateway stage with stage-specific configuration.
C:The statement describes Elastic Beanstalk immutable update, which is not the controlling AWS behavior for this API Gateway staging endpoints situation. The required implementation is: deploy API changes to an isolated API Gateway stage with stage-specific configuration.
D:The statement describes infrastructure drift detection, which is not the controlling AWS behavior for this API Gateway staging endpoints situation. The required implementation is: deploy API changes to an isolated API Gateway stage with stage-specific configuration.
Question 374
A developer must undo a failed deployment without overwriting published Lambda code. A teammate asks why the proposed Lambda alias rollback approach is technically appropriate. Which AWS behavior BEST explains the decision?
- API Gateway stage configuration can parameterize integrations for separate environments.
- Mocks isolate code logic while independent integration checks validate real API contracts.
- Lambda aliases can be repointed independently of immutable published version code.
- Event-driven tests must exercise the actual source envelope and partial failure contract.
Explanation
Correct Answer
C:Lambda aliases can be repointed independently of immutable published version code. This is the governing behavior behind the recommended change: point the production Lambda alias back to the previously tested immutable version.
Incorrect Answers
A:The statement describes API Gateway stage variables, which is not the controlling AWS behavior for this Lambda alias rollback situation. The required implementation is: point the production Lambda alias back to the previously tested immutable version.
B:The statement describes API external dependency mocks, which is not the controlling AWS behavior for this Lambda alias rollback situation. The required implementation is: point the production Lambda alias back to the previously tested immutable version.
D:The statement describes SQS handler contract tests, which is not the controlling AWS behavior for this Lambda alias rollback situation. The required implementation is: point the production Lambda alias back to the previously tested immutable version.
Question 375
An order-created event must reach separate inventory and loyalty queues even when one consumer is offline. A teammate asks why the proposed SNS fanout delivery approach is technically appropriate. Which AWS behavior BEST explains the decision?
- SNS fanout plus durable SQS subscriptions decouples independent asynchronous consumers.
- Jittered bounded retries spread transient failure load instead of synchronized retry spikes.
- Reserved concurrency reserves and caps function concurrency; provisioned concurrency addresses pre-initialized capacity.
- A GSI supports an alternate key-based access pattern with separately managed capacity and eventual consistency.
Explanation
Correct Answer
A:SNS fanout plus durable SQS subscriptions decouples independent asynchronous consumers. This is the governing behavior behind the recommended change: publish the event to SNS and subscribe separate SQS queues for each independently processed concern.
Incorrect Answers
B:The statement describes SDK adaptive retries, which is not the controlling AWS behavior for this SNS fanout delivery situation. The required implementation is: publish the event to SNS and subscribe separate SQS queues for each independently processed concern.
C:The statement describes Lambda concurrency reservation, which is not the controlling AWS behavior for this SNS fanout delivery situation. The required implementation is: publish the event to SNS and subscribe separate SQS queues for each independently processed concern.
D:The statement describes DynamoDB GSI access pattern, which is not the controlling AWS behavior for this SNS fanout delivery situation. The required implementation is: publish the event to SNS and subscribe separate SQS queues for each independently processed concern.
Question 376
A multi-tenant service needs to prevent an authenticated tenant from querying another tenant's keyspace. A teammate asks why the proposed multi-tenant DynamoDB row isolation approach is technically appropriate. Which AWS behavior BEST explains the decision?
- A tenant identifier from verified claims must control data scoping instead of untrusted request parameters.
- Separate execution roles reduce blast radius when individual workloads are compromised.
- KMS-managed rotation retains key identity and the old material required to decrypt previous ciphertext.
- Response masking and field authorization must run before data is returned to a caller.
Explanation
Correct Answer
A:A tenant identifier from verified claims must control data scoping instead of untrusted request parameters. This is the governing behavior behind the recommended change: derive a tenant-scoped key prefix from verified identity and enforce tenant authorization on each query.
Incorrect Answers
B:The statement describes Lambda execution-role separation, which is not the controlling AWS behavior for this multi-tenant DynamoDB row isolation situation. The required implementation is: derive a tenant-scoped key prefix from verified identity and enforce tenant authorization on each query.
C:The statement describes KMS rotation scope, which is not the controlling AWS behavior for this multi-tenant DynamoDB row isolation situation. The required implementation is: derive a tenant-scoped key prefix from verified identity and enforce tenant authorization on each query.
D:The statement describes PII response field masking, which is not the controlling AWS behavior for this multi-tenant DynamoDB row isolation situation. The required implementation is: derive a tenant-scoped key prefix from verified identity and enforce tenant authorization on each query.
Question 377
A retail clickstream table routes a high write volume to only one partition-key value. A teammate asks why the proposed DynamoDB partition key cardinality 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.
- DynamoDB partition-key choice influences physical request distribution and hot-key throttling.
- SQS partial batch response avoids unnecessary redelivery of successful records in a partially failed batch.
- Query uses key conditions while Scan examines items beyond the requested partition.
Explanation
Correct Answer
B:DynamoDB partition-key choice influences physical request distribution and hot-key throttling. This is the governing behavior behind the recommended change: choose a high-cardinality partition-key design that spreads requests while preserving required access patterns.
Incorrect Answers
A:The statement describes API Gateway mapping templates, which is not the controlling AWS behavior for this DynamoDB partition key cardinality situation. The required implementation is: choose a high-cardinality partition-key design that spreads requests while preserving required access patterns.
C:The statement describes Lambda event source partial batch response, which is not the controlling AWS behavior for this DynamoDB partition key cardinality situation. The required implementation is: choose a high-cardinality partition-key design that spreads requests while preserving required access patterns.
D:The statement describes DynamoDB Query versus Scan, which is not the controlling AWS behavior for this DynamoDB partition key cardinality situation. The required implementation is: choose a high-cardinality partition-key design that spreads requests while preserving required access patterns.
Question 378
A rollback needs to deploy exactly the container bytes that passed integration testing last week. A teammate asks why the proposed immutable container image tags approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Mocks isolate code logic while independent integration checks validate real API contracts.
- Lambda aliases can be repointed independently of immutable published version code.
- Immutable artifact references make releases and rollbacks reproducible.
- Explicit test fixtures make regression behavior reproducible across deployments.
Explanation
Correct Answer
C:Immutable artifact references make releases and rollbacks reproducible. This is the governing behavior behind the recommended change: pin deployment manifests to an immutable image digest or unique tested release tag.
Incorrect Answers
A:The statement describes API external dependency mocks, which is not the controlling AWS behavior for this immutable container image tags situation. The required implementation is: pin deployment manifests to an immutable image digest or unique tested release tag.
B:The statement describes Lambda alias rollback, which is not the controlling AWS behavior for this immutable container image tags situation. The required implementation is: pin deployment manifests to an immutable image digest or unique tested release tag.
D:The statement describes deployment test event generation, which is not the controlling AWS behavior for this immutable container image tags situation. The required implementation is: pin deployment manifests to an immutable image digest or unique tested release tag.
Question 379
A backup application needs to retry portions of multi-gigabyte objects without retransmitting the whole object. A teammate asks why the proposed S3 multipart upload recovery approach is technically appropriate. Which AWS behavior BEST explains the decision?
- EventBridge rules route structured events by matching attributes without embedding consumer addresses in producer code.
- DynamoDB partition-key choice influences physical request distribution and hot-key throttling.
- Multipart uploads allow independent parts and require a final completion call.
- Jittered bounded retries spread transient failure load instead of synchronized retry spikes.
Explanation
Correct Answer
C:Multipart uploads allow independent parts and require a final completion call. This is the governing behavior behind the recommended change: use the S3 multipart upload API with part tracking and complete or abort the upload correctly.
Incorrect Answers
A:The statement describes EventBridge event routing, which is not the controlling AWS behavior for this S3 multipart upload recovery situation. The required implementation is: use the S3 multipart upload API with part tracking and complete or abort the upload correctly.
B:The statement describes DynamoDB partition key cardinality, which is not the controlling AWS behavior for this S3 multipart upload recovery situation. The required implementation is: use the S3 multipart upload API with part tracking and complete or abort the upload correctly.
D:The statement describes SDK adaptive retries, which is not the controlling AWS behavior for this S3 multipart upload recovery situation. The required implementation is: use the S3 multipart upload API with part tracking and complete or abort the upload correctly.
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.