Amazon AWS Certified Developer - Associate DVA-C02 Practice Test 29
Question 280
A CPU-bound Lambda runs slowly and has billed time far above the business latency target. After implementing the planned Lambda duration versus memory tradeoff change, which observation is the MOST direct proof that its specific requirement has been met?
- Telemetry separates initialization delay from handler time and shows improvement after the change.
- Cache tests show each allowed variant returns its own response without cross-user leakage.
- Comparative load tests show latency and billed cost at the chosen memory setting.
- Metrics and request logs identify concentrated key traffic or exhausted write/read capacity.
Explanation
Correct Answer
C:Comparative load tests show latency and billed cost at the chosen memory setting. This directly validates Lambda duration versus memory tradeoff under the stated workload and confirms the intended AWS behavior: lambda allocates CPU in proportion to memory, so more memory can reduce compute duration.
Incorrect Answers
A:This observation tests Lambda Init Duration diagnosis, rather than confirming Lambda duration versus memory tradeoff. It does not by itself establish that comparative load tests show latency and billed cost at the chosen memory setting.
B:This observation tests API response caching variation, rather than confirming Lambda duration versus memory tradeoff. It does not by itself establish that comparative load tests show latency and billed cost at the chosen memory setting.
D:This observation tests DynamoDB throttling investigation, rather than confirming Lambda duration versus memory tradeoff. It does not by itself establish that comparative load tests show latency and billed cost at the chosen memory setting.
Question 281
An application encrypts large exported reports while keeping master keys protected by KMS. After implementing the planned KMS envelope encryption change, which observation is the MOST direct proof that its specific requirement has been met?
- CloudTrail and target logs show requests authorized only for the permitted source principal.
- Authenticated connections accept fresh tokens for the mapped database user and reject unauthorized principals.
- Controlled failure tests produce usable trace metadata but no credential material in logs.
- An approved role can decrypt the wrapped data key while an unauthorized role cannot.
Explanation
Correct Answer
D:An approved role can decrypt the wrapped data key while an unauthorized role cannot. This directly validates KMS envelope encryption under the stated workload and confirms the intended AWS behavior: envelope encryption uses a data key for payload encryption and protects that key using a KMS key.
Incorrect Answers
A:This observation tests service-to-service IAM authorization, rather than confirming KMS envelope encryption. It does not by itself establish that an approved role can decrypt the wrapped data key while an unauthorized role cannot.
B:This observation tests IAM authentication and TLS for RDS, rather than confirming KMS envelope encryption. It does not by itself establish that an approved role can decrypt the wrapped data key while an unauthorized role cannot.
C:This observation tests Lambda environment secret leakage, rather than confirming KMS envelope encryption. It does not by itself establish that an approved role can decrypt the wrapped data key while an unauthorized role cannot.
Question 282
A Lambda application needs custom order value metrics without a high-cardinality API PutMetricData call for each request. After implementing the planned CloudWatch embedded metric format change, which observation is the MOST direct proof that its specific requirement has been met?
- CloudWatch extracts a named custom metric from the structured log events with the expected dimensions.
- End-to-end traces show the integration completes under the configured limit without gateway timeouts.
- A controlled threshold breach moves the alarm to ALARM and the subscribed channel receives a notification.
- Telemetry separates initialization delay from handler time and shows improvement after the change.
Explanation
Correct Answer
A:CloudWatch extracts a named custom metric from the structured log events with the expected dimensions. This directly validates CloudWatch embedded metric format under the stated workload and confirms the intended AWS behavior: eMF lets supported log consumers extract metrics from structured events and dimensions affect metric series count.
Incorrect Answers
B:This observation tests API Gateway Lambda integration timeout, rather than confirming CloudWatch embedded metric format. It does not by itself establish that cloudWatch extracts a named custom metric from the structured log events with the expected dimensions.
C:This observation tests CloudWatch alarm notification, rather than confirming CloudWatch embedded metric format. It does not by itself establish that cloudWatch extracts a named custom metric from the structured log events with the expected dimensions.
D:This observation tests Lambda Init Duration diagnosis, rather than confirming CloudWatch embedded metric format. It does not by itself establish that cloudWatch extracts a named custom metric from the structured log events with the expected dimensions.
Question 283
A deployment build must install dependencies, execute tests, and package a versioned Lambda artifact. After implementing the planned CodeBuild buildspec sequencing change, which observation is the MOST direct proof that its specific requirement has been met?
- Calls through each alias invoke the expected immutable version and production remains stable.
- Drift results identify divergent supported properties and a later deployment restores intended state.
- The build fails on a seeded test failure and publishes an artifact only after tests succeed.
- Pipeline execution history shows the same artifact revision crossing successful gates before production.
Explanation
Correct Answer
C:The build fails on a seeded test failure and publishes an artifact only after tests succeed. This directly validates CodeBuild buildspec sequencing under the stated workload and confirms the intended AWS behavior: codeBuild buildspec phases and exit codes control which artifacts advance in CI.
Incorrect Answers
A:This observation tests Lambda alias version testing, rather than confirming CodeBuild buildspec sequencing. It does not by itself establish that the build fails on a seeded test failure and publishes an artifact only after tests succeed.
B:This observation tests infrastructure drift detection, rather than confirming CodeBuild buildspec sequencing. It does not by itself establish that the build fails on a seeded test failure and publishes an artifact only after tests succeed.
D:This observation tests CodePipeline gated promotion, rather than confirming CodeBuild buildspec sequencing. It does not by itself establish that the build fails on a seeded test failure and publishes an artifact only after tests succeed.
Question 284
A Lambda role has an allow statement for S3 reads but calls are still denied by a higher-scope policy. After implementing the planned IAM policy explicit deny change, which observation is the MOST direct proof that its specific requirement has been met?
- Rotated secret versions become available to authorized consumers and the application refreshes its cached credential.
- A seeded test secret blocks the merge and revocation evidence confirms the exposed credential is unusable.
- Valid JWTs reach integrations while expired, bad-signature, or wrong-audience tokens are rejected.
- Policy evaluation identifies a matching explicit deny even though an Allow statement also matches.
Explanation
Correct Answer
D:Policy evaluation identifies a matching explicit deny even though an Allow statement also matches. This directly validates IAM policy explicit deny under the stated workload and confirms the intended AWS behavior: an explicit Deny takes precedence over any applicable Allow in AWS policy evaluation.
Incorrect Answers
A:This observation tests Secrets Manager rotation, rather than confirming IAM policy explicit deny. It does not by itself establish that policy evaluation identifies a matching explicit deny even though an Allow statement also matches.
B:This observation tests secret scanning in CI, rather than confirming IAM policy explicit deny. It does not by itself establish that policy evaluation identifies a matching explicit deny even though an Allow statement also matches.
C:This observation tests API Gateway JWT authorizer, rather than confirming IAM policy explicit deny. It does not by itself establish that policy evaluation identifies a matching explicit deny even though an Allow statement also matches.
Question 285
An asynchronous Lambda must preserve request and response context when a job ultimately fails. After implementing the planned Lambda destinations versus DLQ change, which observation is the MOST direct proof that its specific requirement has been met?
- The target receives a record including request details and failure response context.
- Consumed capacity and throttling metrics distribute more evenly across partition keys.
- Network tests confirm outbound connectivity from the function to the private endpoint on its service port.
- One competing write succeeds and the other receives a conditional-check failure.
Explanation
Correct Answer
A:The target receives a record including request details and failure response context. This directly validates Lambda destinations versus DLQ under the stated workload and confirms the intended AWS behavior: destinations for async Lambda invocations capture richer invocation outcomes than traditional dead-letter queues.
Incorrect Answers
B:This observation tests DynamoDB partition key cardinality, rather than confirming Lambda destinations versus DLQ. It does not by itself establish that the target receives a record including request details and failure response context.
C:This observation tests Lambda VPC private data access, rather than confirming Lambda destinations versus DLQ. It does not by itself establish that the target receives a record including request details and failure response context.
D:This observation tests DynamoDB conditional update, rather than confirming Lambda destinations versus DLQ. It does not by itself establish that the target receives a record including request details and failure response context.
Question 286
A product service loses most of its cache entries at once and the backing database receives thousands of simultaneous reloads. After implementing the planned application cache stampede change, which observation is the MOST direct proof that its specific requirement has been met?
- CloudWatch extracts a named custom metric from the structured log events with the expected dimensions.
- Cache-miss burst metrics shrink and backend query rates stay controlled during expiration.
- Profile output identifies the costly query phase and a revised query reduces latency under representative load.
- Trace searches filter by annotations without exposing private payloads as indexed labels.
Explanation
Correct Answer
B:Cache-miss burst metrics shrink and backend query rates stay controlled during expiration. This directly validates application cache stampede under the stated workload and confirms the intended AWS behavior: coordinated cache refresh and TTL jitter reduce thundering-herd load.
Incorrect Answers
A:This observation tests CloudWatch embedded metric format, rather than confirming application cache stampede. It does not by itself establish that cache-miss burst metrics shrink and backend query rates stay controlled during expiration.
C:This observation tests OpenSearch query performance profiling, rather than confirming application cache stampede. It does not by itself establish that cache-miss burst metrics shrink and backend query rates stay controlled during expiration.
D:This observation tests tracing annotations versus metadata, rather than confirming application cache stampede. It does not by itself establish that cache-miss burst metrics shrink and backend query rates stay controlled during expiration.
Question 287
A build service in one account needs read-only access to a deployment artifact bucket in a second account. After implementing the planned IAM STS AssumeRole cross-account change, which observation is the MOST direct proof that its specific requirement has been met?
- CloudTrail shows the expected assumed role session and only the allowed target-account API actions succeed.
- A successfully signed-in user receives correctly issued tokens whose signature, issuer, audience, and expiry validate.
- Secret-read API volume declines while newly rotated credentials are adopted within the specified refresh window.
- Requests from nonprivileged roles contain masked fields while approved roles get only permitted detail.
Explanation
Correct Answer
A:CloudTrail shows the expected assumed role session and only the allowed target-account API actions succeed. This directly validates IAM STS AssumeRole cross-account under the stated workload and confirms the intended AWS behavior: cross-account roles require both role trust and permission policy authorization.
Incorrect Answers
B:This observation tests Cognito user pool authentication, rather than confirming IAM STS AssumeRole cross-account. It does not by itself establish that cloudTrail shows the expected assumed role session and only the allowed target-account API actions succeed.
C:This observation tests credential caching refresh, rather than confirming IAM STS AssumeRole cross-account. It does not by itself establish that cloudTrail shows the expected assumed role session and only the allowed target-account API actions succeed.
D:This observation tests PII response field masking, rather than confirming IAM STS AssumeRole cross-account. It does not by itself establish that cloudTrail shows the expected assumed role session and only the allowed target-account API actions succeed.
Question 288
A session store records an expiration timestamp but the app must deny an expired session immediately. After implementing the planned DynamoDB TTL expiry semantics change, which observation is the MOST direct proof that its specific requirement has been met?
- Poisoned messages appear in the DLQ after the chosen receives while valid events continue.
- An expired item is denied by the app even when the physical DynamoDB item has not yet disappeared.
- Invocations in each environment show the configured nonsecret value without changing application source.
- One competing write succeeds and the other receives a conditional-check failure.
Explanation
Correct Answer
B:An expired item is denied by the app even when the physical DynamoDB item has not yet disappeared. This directly validates DynamoDB TTL expiry semantics under the stated workload and confirms the intended AWS behavior: dynamoDB TTL deletion is asynchronous and must not be the only immediate expiry enforcement.
Incorrect Answers
A:This observation tests SQS dead-letter queues, rather than confirming DynamoDB TTL expiry semantics. It does not by itself establish that an expired item is denied by the app even when the physical DynamoDB item has not yet disappeared.
C:This observation tests Lambda environment configuration, rather than confirming DynamoDB TTL expiry semantics. It does not by itself establish that an expired item is denied by the app even when the physical DynamoDB item has not yet disappeared.
D:This observation tests DynamoDB conditional update, rather than confirming DynamoDB TTL expiry semantics. It does not by itself establish that an expired item is denied by the app even when the physical DynamoDB item has not yet disappeared.
Question 289
A Python Lambda needs distinct API base URLs in staging and production without code forks. After implementing the planned Lambda environment configuration change, which observation is the MOST direct proof that its specific requirement has been met?
- Matching records reach the handler and unrelated records do not produce application processing.
- During a sustained fault, calls fail fast through the fallback and recover through controlled probes.
- Consumed capacity and throttling metrics distribute more evenly across partition keys.
- Invocations in each environment show the configured nonsecret value without changing application source.
Explanation
Correct Answer
D:Invocations in each environment show the configured nonsecret value without changing application source. This directly validates Lambda environment configuration under the stated workload and confirms the intended AWS behavior: runtime configuration separates deployment settings from executable code when values differ by environment.
Incorrect Answers
A:This observation tests Lambda event filtering, rather than confirming Lambda environment configuration. It does not by itself establish that invocations in each environment show the configured nonsecret value without changing application source.
B:This observation tests third-party circuit breaker, rather than confirming Lambda environment configuration. It does not by itself establish that invocations in each environment show the configured nonsecret value without changing application source.
C:This observation tests DynamoDB partition key cardinality, rather than confirming Lambda environment configuration. It does not by itself establish that invocations in each environment show the configured nonsecret value without changing application source.
Question 290
A successful signup must independently notify billing, analytics, and email workers without sequential calls. After implementing the planned SNS fanout delivery change, which observation is the MOST direct proof that its specific requirement has been met?
- The target receives a record including request details and failure response context.
- Each subscriber queue receives its own copy and an unavailable worker can process its backlog later.
- Invocations in each environment show the configured nonsecret value without changing application source.
- Records for one entity remain ordered while shard-level incoming and processing rates stay within quotas.
Explanation
Correct Answer
B:Each subscriber queue receives its own copy and an unavailable worker can process its backlog later. This directly validates SNS fanout delivery under the stated workload and confirms the intended AWS behavior: sNS fanout plus durable SQS subscriptions decouples independent asynchronous consumers.
Incorrect Answers
A:This observation tests Lambda destinations versus DLQ, rather than confirming SNS fanout delivery. It does not by itself establish that each subscriber queue receives its own copy and an unavailable worker can process its backlog later.
C:This observation tests Lambda environment configuration, rather than confirming SNS fanout delivery. It does not by itself establish that each subscriber queue receives its own copy and an unavailable worker can process its backlog later.
D:This observation tests Kinesis shard partitioning, rather than confirming SNS fanout delivery. It does not by itself establish that each subscriber queue receives its own copy and an unavailable worker can process its backlog later.