cert
cert-1
cert-2

Pass Amazon AWS Certified Developer - Associate DVA-C02 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers to Pass the Actual Exam!
30 Days Free Updates, Instant Download!

cert-5
cert-6
AWS Certified Developer - Associate DVA-C02 Exam - Verified By Experts
AWS Certified Developer - Associate DVA-C02 Premium Bundle
$29.98

AWS Certified Developer - Associate DVA-C02 Premium Bundle

$79.99
$109.97
  • Premium File 653 Questions & Answers. Last update: Nov 10, 2026
  • Training Course 430 Video Lectures
  • Study Guide 1091 Pages
 
$109.97
$79.99
accept 27 downloads in last 7 days
block-screenshots
Purchase Amazon AWS Certified Developer - Associate DVA-C02 Exam Training Products Individually
Amazon AWS Certified Developer - Associate DVA-C02 Premium File
Premium File 653 Q&A
$76.99$69.99
Amazon AWS Certified Developer - Associate DVA-C02 Video Training Course
Training Course 430 Lectures
$21.99 $19.99
Amazon AWS Certified Developer - Associate DVA-C02 PDF Study Guide
Study Guide 1091 Pages
$21.99 $19.99
Amazon AWS Certified Developer - Associate DVA-C02 Practice Test 17

Question 160

A retail clickstream table routes a high write volume to only one partition-key value. Which developer action MOST directly meets the stated constraint?

  1. Use one constant partition key for every customer.
  2. Use DynamoDB Query with the customer partition key and an appropriate sort-key condition.
  3. Replace Query with Scan and assume hot-key writes disappear.
  4. Choose a high-cardinality partition-key design that spreads requests while preserving required access patterns.

Explanation

Correct Answer

D:

Choose a high-cardinality partition-key design that spreads requests while preserving required access patterns. DynamoDB partition-key choice influences physical request distribution and hot-key throttling. For this second operating case, verify that consumed capacity and throttling metrics distribute more evenly across partition keys.

Incorrect Answers

A:

Use one constant partition key for every customer. This shortcut would leave the DynamoDB partition key cardinality requirement unresolved; a low-cardinality or hot partition key concentrates traffic despite available table capacity.

B:

This technique primarily addresses DynamoDB Query versus Scan; it would not demonstrate DynamoDB partition key cardinality or directly prove that consumed capacity and throttling metrics distribute more evenly across partition keys.

C:

Replace Query with Scan and assume hot-key writes disappear. This shortcut would leave the DynamoDB partition key cardinality requirement unresolved; a low-cardinality or hot partition key concentrates traffic despite available table capacity.

Question 161

A team needs cost control and predictable deletion of old routine Lambda logs. Which developer action MOST directly meets the stated constraint?

  1. Set a CloudWatch Logs retention policy matching the operational retention requirement.
  2. Increase the Lambda timeout to control log retention.
  3. Delete the log group daily including current troubleshooting events.
  4. Create a CloudWatch alarm on the relevant metric and send state-change notifications to an approved SNS topic.

Explanation

Correct Answer

A:

Set a CloudWatch Logs retention policy matching the operational retention requirement. CloudWatch log groups retain data indefinitely by default unless a retention setting is configured. For this second operating case, verify that old routine log events age out according to policy while newer diagnostic events stay queryable.

Incorrect Answers

B:

Increase the Lambda timeout to control log retention. This shortcut would leave the CloudWatch log retention requirement unresolved; leaving retention unlimited can accumulate unnecessary log storage and compliance exposure.

C:

Delete the log group daily including current troubleshooting events. This shortcut would leave the CloudWatch log retention requirement unresolved; leaving retention unlimited can accumulate unnecessary log storage and compliance exposure.

D:

This technique primarily addresses CloudWatch alarm notification; it would not demonstrate CloudWatch log retention or directly prove that old routine log events age out according to policy while newer diagnostic events stay queryable.

Question 162

A shopping-cart table uses TTL cleanup and needs correct authorization even before deletion. Which developer action MOST directly meets the stated constraint?

  1. Assume DynamoDB TTL removes a record at the exact second.
  2. Use the S3 multipart upload API with part tracking and complete or abort the upload correctly.
  3. Use a GSI to force TTL deletion instantly.
  4. Check the epoch expiration attribute in application logic while using DynamoDB TTL for eventual cleanup.

Explanation

Correct Answer

D:

Check the epoch expiration attribute in application logic while using DynamoDB TTL for eventual cleanup. DynamoDB TTL deletion is asynchronous and must not be the only immediate expiry enforcement. For this second operating case, verify that an expired item is denied by the app even when the physical DynamoDB item has not yet disappeared.

Incorrect Answers

A:

Assume DynamoDB TTL removes a record at the exact second. This shortcut would leave the DynamoDB TTL expiry semantics requirement unresolved; treating TTL cleanup as synchronous can keep expired data valid until deletion occurs.

B:

This technique primarily addresses S3 multipart upload recovery; it would not demonstrate DynamoDB TTL expiry semantics or directly prove that an expired item is denied by the app even when the physical DynamoDB item has not yet disappeared.

C:

Use a GSI to force TTL deletion instantly. This shortcut would leave the DynamoDB TTL expiry semantics requirement unresolved; treating TTL cleanup as synchronous can keep expired data valid until deletion occurs.

Question 163

A profile service performs frequent lookups with occasional updates requiring bounded stale data. Which developer action MOST directly meets the stated constraint?

  1. Replace database writes with cache-only updates.
  2. Cache every mutable value forever with no invalidation.
  3. Use a cache-aside pattern with a defined TTL and invalidation on application updates.
  4. Use DynamoDB Query with the customer partition key and an appropriate sort-key condition.

Explanation

Correct Answer

C:

Use a cache-aside pattern with a defined TTL and invalidation on application updates. Cache-aside populates on misses and requires an explicit freshness or invalidation strategy. For this second operating case, verify that cache hit-rate increases and backend read load falls while update invalidation keeps freshness within policy.

Incorrect Answers

A:

Replace database writes with cache-only updates. This shortcut would leave the ElastiCache cache-aside requirement unresolved; never expiring cached entries can continue to return stale records after updates.

B:

Cache every mutable value forever with no invalidation. This shortcut would leave the ElastiCache cache-aside requirement unresolved; never expiring cached entries can continue to return stale records after updates.

D:

This technique primarily addresses DynamoDB Query versus Scan; it would not demonstrate ElastiCache cache-aside or directly prove that cache hit-rate increases and backend read load falls while update invalidation keeps freshness within policy.

Question 164

A backup application needs to retry portions of multi-gigabyte objects without retransmitting the whole object. Which developer action MOST directly meets the stated constraint?

  1. Use the S3 multipart upload API with part tracking and complete or abort the upload correctly.
  2. Retry the full multi-gigabyte PUT for every lost packet.
  3. Treat uploaded parts as a complete object before CompleteMultipartUpload.
  4. Generate a scoped presigned S3 URL with the intended method, object key, and expiration.

Explanation

Correct Answer

A:

Use the S3 multipart upload API with part tracking and complete or abort the upload correctly. Multipart uploads allow independent parts and require a final completion call. For this second operating case, verify that uploaded parts can be retried independently and the completed object is present only after completion.

Incorrect Answers

B:

Retry the full multi-gigabyte PUT for every lost packet. This shortcut would leave the S3 multipart upload recovery requirement unresolved; unfinished multipart uploads accumulate stored parts and cannot be read as a completed object.

C:

Treat uploaded parts as a complete object before CompleteMultipartUpload. This shortcut would leave the S3 multipart upload recovery requirement unresolved; unfinished multipart uploads accumulate stored parts and cannot be read as a completed object.

D:

This technique primarily addresses S3 presigned URLs; it would not demonstrate S3 multipart upload recovery or directly prove that uploaded parts can be retried independently and the completed object is present only after completion.

Question 165

A developer wants to filter traces by environment and operation while attaching detailed diagnostic context. Which developer action MOST directly meets the stated constraint?

  1. Set a CloudWatch Logs retention policy matching the operational retention requirement.
  2. Store full access tokens as trace annotations.
  3. Put all filterable dimensions only into unindexed metadata.
  4. Use low-cardinality X-Ray annotations for indexed filters and metadata for nonindexed diagnostic details.

Explanation

Correct Answer

D:

Use low-cardinality X-Ray annotations for indexed filters and metadata for nonindexed diagnostic details. X-Ray annotations are indexed for filtering; metadata provides supplementary nonindexed values. For this second operating case, verify that trace searches filter by annotations without exposing private payloads as indexed labels.

Incorrect Answers

A:

This technique primarily addresses CloudWatch log retention; it would not demonstrate tracing annotations versus metadata or directly prove that trace searches filter by annotations without exposing private payloads as indexed labels.

B:

Store full access tokens as trace annotations. This shortcut would leave the tracing annotations versus metadata requirement unresolved; putting sensitive free-form payloads in indexed annotations creates exposure and high-cardinality filtering problems.

C:

Put all filterable dimensions only into unindexed metadata. This shortcut would leave the tracing annotations versus metadata requirement unresolved; putting sensitive free-form payloads in indexed annotations creates exposure and high-cardinality filtering problems.

Question 166

A team rolls out a pricing feature to only a small subset of users with rollback controls. Which developer action MOST directly meets the stated constraint?

  1. Commit different copies of the application for every flag value.
  2. Store feature flags in an unvalidated browser cookie only.
  3. Store environment-specific configuration in AWS AppConfig and deploy validated configuration versions.
  4. Parameterize the CloudFormation or SAM template and supply environment-specific values at deployment.

Explanation

Correct Answer

C:

Store environment-specific configuration in AWS AppConfig and deploy validated configuration versions. Configuration releases can be separated from binary releases with validators and deployment controls. For this second operating case, verify that the correct environment retrieves its scoped configuration and a failed rollout can be rolled back.

Incorrect Answers

A:

Commit different copies of the application for every flag value. This shortcut would leave the environment-specific AppConfig requirement unresolved; copying production flags into staging accidentally enables functionality in the wrong environment.

B:

Store feature flags in an unvalidated browser cookie only. This shortcut would leave the environment-specific AppConfig requirement unresolved; copying production flags into staging accidentally enables functionality in the wrong environment.

D:

This technique primarily addresses CloudFormation resource parameters; it would not demonstrate environment-specific AppConfig or directly prove that the correct environment retrieves its scoped configuration and a failed rollout can be rolled back.

Question 167

A refund process must pause for approval and track which previous steps succeeded before compensating. Which developer action MOST directly meets the stated constraint?

  1. Put the entire state machine inside one synchronous API Gateway mapping.
  2. Poll a local variable in a single Lambda for human approval.
  3. Use AWS Step Functions to coordinate states, retries, catches, and compensating tasks explicitly.
  4. Define an API Gateway mapping template or parameter mapping that explicitly transforms the incoming request.

Explanation

Correct Answer

C:

Use AWS Step Functions to coordinate states, retries, catches, and compensating tasks explicitly. A managed state machine expresses multi-step application coordination beyond a single long-running handler. For this second operating case, verify that execution history shows state transitions, retries, and the branch taken after an error.

Incorrect Answers

A:

Put the entire state machine inside one synchronous API Gateway mapping. This shortcut would leave the Step Functions orchestration requirement unresolved; a one-shot Lambda chain obscures per-step recovery and can exceed execution constraints.

B:

Poll a local variable in a single Lambda for human approval. This shortcut would leave the Step Functions orchestration requirement unresolved; a one-shot Lambda chain obscures per-step recovery and can exceed execution constraints.

D:

This technique primarily addresses API Gateway mapping templates; it would not demonstrate Step Functions orchestration or directly prove that execution history shows state transitions, retries, and the branch taken after an error.

Question 168

A service caches an API token and must recover promptly when that token is rotated. Which developer action MOST directly meets the stated constraint?

  1. Cache secrets for a bounded interval and refresh on expiry or authentication failure using least-privilege access.
  2. Cache the sensitive value forever in the container image.
  3. Apply field-level authorization and mask sensitive attributes before serializing responses.
  4. Store secrets in publicly writable object tags.

Explanation

Correct Answer

A:

Cache secrets for a bounded interval and refresh on expiry or authentication failure using least-privilege access. Bounded secret caching reduces repeated retrieval without making old credentials permanent. For this second operating case, verify that secret-read API volume declines while newly rotated credentials are adopted within the specified refresh window.

Incorrect Answers

B:

Cache the sensitive value forever in the container image. This shortcut would leave the credential caching refresh requirement unresolved; a process-wide cache with no expiry continues to use revoked values.

C:

This technique primarily addresses PII response field masking; it would not demonstrate credential caching refresh or directly prove that secret-read API volume declines while newly rotated credentials are adopted within the specified refresh window.

D:

Store secrets in publicly writable object tags. This shortcut would leave the credential caching refresh requirement unresolved; a process-wide cache with no expiry continues to use revoked values.

Question 169

A rollback needs to deploy exactly the container bytes that passed integration testing last week. Which developer action MOST directly meets the stated constraint?

  1. Pull latest without recording its digest.
  2. Pin deployment manifests to an immutable image digest or unique tested release tag.
  3. Configure stage-specific variables or integrations pointing to the intended Lambda alias and grant invoke permissions.
  4. Rebuild source from the main branch during a rollback.

Explanation

Correct Answer

B:

Pin deployment manifests to an immutable image digest or unique tested release tag. Immutable artifact references make releases and rollbacks reproducible. For this second operating case, verify that the running task image digest matches the tested build artifact after deployment and rollback.

Incorrect Answers

A:

Pull latest without recording its digest. This shortcut would leave the immutable container image tags requirement unresolved; a mutable latest tag can point to different image bytes on separate deployments.

C:

This technique primarily addresses API Gateway stage variables; it would not demonstrate immutable container image tags or directly prove that the running task image digest matches the tested build artifact after deployment and rollback.

D:

Rebuild source from the main branch during a rollback. This shortcut would leave the immutable container image tags requirement unresolved; a mutable latest tag can point to different image bytes on separate deployments.

Question 170

A team needs repeatable local invocation of SAM-defined handlers using saved JSON events. Which developer action MOST directly meets the stated constraint?

  1. Unit-test only a text file containing the handler name.
  2. Build test events using realistic SQS Records metadata and verify handler output plus failure identifiers.
  3. Deploy directly to production to inspect each syntax error.
  4. Run AWS SAM CLI local API or invoke tests with representative events and runtime-compatible containers.

Explanation

Correct Answer

D:

Run AWS SAM CLI local API or invoke tests with representative events and runtime-compatible containers. SAM local testing helps validate handler behavior before a cloud deployment but does not replace all integration tests. For this second operating case, verify that test output demonstrates the expected HTTP or handler response for valid and invalid fixtures.

Incorrect Answers

A:

Unit-test only a text file containing the handler name. This shortcut would leave the local SAM API testing requirement unresolved; skipping runtime-compatible local tests can miss event-shape and handler configuration bugs.

B:

This technique primarily addresses SQS handler contract tests; it would not demonstrate local SAM API testing or directly prove that test output demonstrates the expected HTTP or handler response for valid and invalid fixtures.

C:

Deploy directly to production to inspect each syntax error. This shortcut would leave the local SAM API testing requirement unresolved; skipping runtime-compatible local tests can miss event-shape and handler configuration bugs.

AWS Certified Developer - Associate DVA-C02 Practice Tests