Amazon AWS Certified Developer - Associate DVA-C02 Practice Test 37
Question 360
A locally run test harness needs role credentials to call a single AWS API without storing secrets in its repository. A teammate asks why the proposed temporary credential storage approach is technically appropriate. Which AWS behavior BEST explains the decision?
- JWT verification checks cryptographic signature and claims, not only whether a header exists.
- Encryption at rest does not stop an application from leaking plaintext secrets during logging.
- AWS credential provider chains support ephemeral sessions and remove the need for embedded static secrets.
- Resource policies can restrict the source principals or network context independently from route authorizers.
Explanation
Correct Answer
C:AWS credential provider chains support ephemeral sessions and remove the need for embedded static secrets. This is the governing behavior behind the recommended change: use the AWS SDK default credential chain with short-lived credentials from an approved profile or federation.
Incorrect Answers
A:The statement describes API Gateway JWT authorizer, which is not the controlling AWS behavior for this temporary credential storage situation. The required implementation is: use the AWS SDK default credential chain with short-lived credentials from an approved profile or federation.
B:The statement describes Lambda environment secret leakage, which is not the controlling AWS behavior for this temporary credential storage situation. The required implementation is: use the AWS SDK default credential chain with short-lived credentials from an approved profile or federation.
D:The statement describes API Gateway resource policy, which is not the controlling AWS behavior for this temporary credential storage situation. The required implementation is: use the AWS SDK default credential chain with short-lived credentials from an approved profile or federation.
Question 361
An SDK request passes S3 authorization but fails at KMS decrypt during an export download. A teammate asks why the proposed AccessDenied troubleshooting chain 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.
- 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.
- Authorization for an encrypted object can involve multiple services and different policy evaluators.
Explanation
Correct Answer
D:Authorization for an encrypted object can involve multiple services and different policy evaluators. This is the governing behavior behind the recommended change: trace the caller identity, the requested S3 action, and the KMS key permissions with CloudTrail evidence.
Incorrect Answers
A:The statement describes readiness versus liveness checks, which is not the controlling AWS behavior for this AccessDenied troubleshooting chain situation. The required implementation is: trace the caller identity, the requested S3 action, and the KMS key permissions with CloudTrail evidence.
B:The statement describes failed CloudFormation deployment, which is not the controlling AWS behavior for this AccessDenied troubleshooting chain situation. The required implementation is: trace the caller identity, the requested S3 action, and the KMS key permissions with CloudTrail evidence.
C:The statement describes CloudWatch embedded metric format, which is not the controlling AWS behavior for this AccessDenied troubleshooting chain situation. The required implementation is: trace the caller identity, the requested S3 action, and the KMS key permissions with CloudTrail evidence.
Question 362
A compliance job uses an existing symmetric customer-managed KMS key and must rotate cryptographic material for future encryptions. A teammate asks why the proposed KMS rotation scope approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Separate execution roles reduce blast radius when individual workloads are compromised.
- Bearer tokens are bounded credentials and server-side expiry checks cannot be replaced by client clock trust.
- KMS-managed rotation retains key identity and the old material required to decrypt previous ciphertext.
- SSE-KMS authorization involves both S3 API access and KMS cryptographic authorization.
Explanation
Correct Answer
C:KMS-managed rotation retains key identity and the old material required to decrypt previous ciphertext. This is the governing behavior behind the recommended change: use supported KMS automatic key rotation while keeping the original KMS key identity for decryption.
Incorrect Answers
A:The statement describes Lambda execution-role separation, which is not the controlling AWS behavior for this KMS rotation scope situation. The required implementation is: use supported KMS automatic key rotation while keeping the original KMS key identity for decryption.
B:The statement describes bearer token refresh and expiry, which is not the controlling AWS behavior for this KMS rotation scope situation. The required implementation is: use supported KMS automatic key rotation while keeping the original KMS key identity for decryption.
D:The statement describes S3 SSE-KMS access, which is not the controlling AWS behavior for this KMS rotation scope situation. The required implementation is: use supported KMS automatic key rotation while keeping the original KMS key identity for decryption.
Question 363
An infrequently invoked Lambda spends most of its latency initializing libraries before its handler starts. A teammate asks why the proposed Lambda Init Duration diagnosis approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Authorization for an encrypted object can involve multiple services and different policy evaluators.
- EMF lets supported log consumers extract metrics from structured events and dimensions affect metric series count.
- Lambda cold-start initialization is distinct from code execution duration.
- X-Ray annotations are indexed for filtering; metadata provides supplementary nonindexed values.
Explanation
Correct Answer
C:Lambda cold-start initialization is distinct from code execution duration. This is the governing behavior behind the recommended change: inspect Lambda init-duration and handler-duration metrics and reduce startup work or use provisioned concurrency when justified.
Incorrect Answers
A:The statement describes AccessDenied troubleshooting chain, which is not the controlling AWS behavior for this Lambda Init Duration diagnosis situation. The required implementation is: inspect Lambda init-duration and handler-duration metrics and reduce startup work or use provisioned concurrency when justified.
B:The statement describes CloudWatch embedded metric format, which is not the controlling AWS behavior for this Lambda Init Duration diagnosis situation. The required implementation is: inspect Lambda init-duration and handler-duration metrics and reduce startup work or use provisioned concurrency when justified.
D:The statement describes tracing annotations versus metadata, which is not the controlling AWS behavior for this Lambda Init Duration diagnosis situation. The required implementation is: inspect Lambda init-duration and handler-duration metrics and reduce startup work or use provisioned concurrency when justified.
Question 364
A payments API needs automated rollback if errors rise during a Lambda alias traffic shift. A teammate asks why the proposed CodeDeploy Lambda canary approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Event-driven tests must exercise the actual source envelope and partial failure contract.
- API Gateway stages provide deployment boundaries and can hold environment-specific settings.
- Canary deployment limits initial exposure by progressively shifting live traffic to a candidate version.
- API Gateway stage configuration can parameterize integrations for separate environments.
Explanation
Correct Answer
C:Canary deployment limits initial exposure by progressively shifting live traffic to a candidate version. This is the governing behavior behind the recommended change: configure CodeDeploy Lambda traffic shifting with alarms and a tested rollback policy.
Incorrect Answers
A:The statement describes SQS handler contract tests, which is not the controlling AWS behavior for this CodeDeploy Lambda canary situation. The required implementation is: configure CodeDeploy Lambda traffic shifting with alarms and a tested rollback policy.
B:The statement describes API Gateway staging endpoints, which is not the controlling AWS behavior for this CodeDeploy Lambda canary situation. The required implementation is: configure CodeDeploy Lambda traffic shifting with alarms and a tested rollback policy.
D:The statement describes API Gateway stage variables, which is not the controlling AWS behavior for this CodeDeploy Lambda canary situation. The required implementation is: configure CodeDeploy Lambda traffic shifting with alarms and a tested rollback policy.
Question 365
A federated user must obtain scoped temporary AWS credentials instead of embedding access keys in the app. A teammate asks why the proposed Cognito identity pool AWS access approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Cognito identity pools broker temporary AWS credentials for supported identity providers.
- An explicit Deny takes precedence over any applicable Allow in AWS policy evaluation.
- Secrets Manager versions and rotation workflows manage sensitive values outside deployment artifacts.
- Encryption at rest does not stop an application from leaking plaintext secrets during logging.
Explanation
Correct Answer
A:Cognito identity pools broker temporary AWS credentials for supported identity providers. This is the governing behavior behind the recommended change: exchange trusted identities through a Cognito identity pool for role-scoped temporary AWS credentials.
Incorrect Answers
B:The statement describes IAM policy explicit deny, which is not the controlling AWS behavior for this Cognito identity pool AWS access situation. The required implementation is: exchange trusted identities through a Cognito identity pool for role-scoped temporary AWS credentials.
C:The statement describes Secrets Manager rotation, which is not the controlling AWS behavior for this Cognito identity pool AWS access situation. The required implementation is: exchange trusted identities through a Cognito identity pool for role-scoped temporary AWS credentials.
D:The statement describes Lambda environment secret leakage, which is not the controlling AWS behavior for this Cognito identity pool AWS access situation. The required implementation is: exchange trusted identities through a Cognito identity pool for role-scoped temporary AWS credentials.
Question 366
A profile service performs frequent lookups with occasional updates requiring bounded stale data. A teammate asks why the proposed ElastiCache cache-aside approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Cache-aside populates on misses and requires an explicit freshness or invalidation strategy.
- 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.
- Circuit breakers limit cascading latency while allowing controlled recovery after dependency outages.
Explanation
Correct Answer
A:Cache-aside populates on misses and requires an explicit freshness or invalidation strategy. This is the governing behavior behind the recommended change: use a cache-aside pattern with a defined TTL and invalidation on application updates.
Incorrect Answers
B:The statement describes Step Functions orchestration, which is not the controlling AWS behavior for this ElastiCache cache-aside situation. The required implementation is: use a cache-aside pattern with a defined TTL and invalidation on application updates.
C:The statement describes DynamoDB strong read consistency, which is not the controlling AWS behavior for this ElastiCache cache-aside situation. The required implementation is: use a cache-aside pattern with a defined TTL and invalidation on application updates.
D:The statement describes third-party circuit breaker, which is not the controlling AWS behavior for this ElastiCache cache-aside situation. The required implementation is: use a cache-aside pattern with a defined TTL and invalidation on application updates.
Question 367
An inventory service sees intermittent upstream 503 responses while a partner's rate limit tightens. A teammate asks why the proposed SDK adaptive retries approach is technically appropriate. Which AWS behavior BEST explains the decision?
- At-least-once message delivery needs application-level idempotency for irreversible side effects.
- Lambda layers package reusable dependencies separately while runtime compatibility must still match.
- Strongly consistent reads are available on DynamoDB tables and LSIs in a Region, not GSIs.
- Jittered bounded retries spread transient failure load instead of synchronized retry spikes.
Explanation
Correct Answer
D:Jittered bounded retries spread transient failure load instead of synchronized retry spikes. This is the governing behavior behind the recommended change: use bounded exponential backoff with jitter, an explicit timeout, and an idempotent request design.
Incorrect Answers
A:The statement describes idempotent event handling, which is not the controlling AWS behavior for this SDK adaptive retries situation. The required implementation is: use bounded exponential backoff with jitter, an explicit timeout, and an idempotent request design.
B:The statement describes Lambda layer dependency management, which is not the controlling AWS behavior for this SDK adaptive retries situation. The required implementation is: use bounded exponential backoff with jitter, an explicit timeout, and an idempotent request design.
C:The statement describes DynamoDB strong read consistency, which is not the controlling AWS behavior for this SDK adaptive retries situation. The required implementation is: use bounded exponential backoff with jitter, an explicit timeout, and an idempotent request design.
Question 368
A document index returns results quickly for exact terms but not for certain expensive aggregations. A teammate asks why the proposed OpenSearch query performance profiling approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Structured fields make telemetry queryable while avoiding sensitive payload exposure.
- EMF lets supported log consumers extract metrics from structured events and dimensions affect metric series count.
- Search engine query structure and indexing choices can dominate latency beyond API worker CPU.
- Concurrency controls must reflect downstream capacity rather than only upstream invocation volume.
Explanation
Correct Answer
C:Search engine query structure and indexing choices can dominate latency beyond API worker CPU. This is the governing behavior behind the recommended change: inspect query profiles, shard pressure, and index mappings before optimizing the search request.
Incorrect Answers
A:The statement describes structured JSON logging, which is not the controlling AWS behavior for this OpenSearch query performance profiling situation. The required implementation is: inspect query profiles, shard pressure, and index mappings before optimizing the search request.
B:The statement describes CloudWatch embedded metric format, which is not the controlling AWS behavior for this OpenSearch query performance profiling situation. The required implementation is: inspect query profiles, shard pressure, and index mappings before optimizing the search request.
D:The statement describes concurrency backpressure, which is not the controlling AWS behavior for this OpenSearch query performance profiling situation. The required implementation is: inspect query profiles, shard pressure, and index mappings before optimizing the search request.
Question 369
A REST API accepts JSON orders and needs schema validation with a predictable client error. A teammate asks why the proposed API Gateway request validation approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Lambda CPU allocation scales with configured memory and can speed CPU-bound functions.
- Jittered bounded retries spread transient failure load instead of synchronized retry spikes.
- SQS partial batch response avoids unnecessary redelivery of successful records in a partially failed batch.
- Validating at the API boundary reduces invalid traffic and keeps backend operations focused.
Explanation
Correct Answer
D:Validating at the API boundary reduces invalid traffic and keeps backend operations focused. This is the governing behavior behind the recommended change: configure an API Gateway request validator and matching request model for required JSON structure.
Incorrect Answers
A:The statement describes Lambda memory CPU tuning, which is not the controlling AWS behavior for this API Gateway request validation situation. The required implementation is: configure an API Gateway request validator and matching request model for required JSON structure.
B:The statement describes SDK adaptive retries, which is not the controlling AWS behavior for this API Gateway request validation situation. The required implementation is: configure an API Gateway request validator and matching request model for required JSON structure.
C:The statement describes Lambda event source partial batch response, which is not the controlling AWS behavior for this API Gateway request validation situation. The required implementation is: configure an API Gateway request validator and matching request model for required JSON structure.
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.