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 57

Question 560

An order-created event must reach separate inventory and loyalty queues even when one consumer is offline. The incident review finds the following problem: Invoking each downstream worker synchronously couples availability and latency. What is the BEST targeted corrective action?

  1. Store all consumer tasks in one local thread.
  2. Send events to one shared SQS queue expecting every consumer to see every event.
  3. Call each worker inside one HTTP request.
  4. Give each consumer its own SQS subscription and allow workers to retry independently.

Explanation

Correct Answer

D:

Give each consumer its own SQS subscription and allow workers to retry independently. This directly addresses the recorded SNS fanout delivery failure and should be checked by observing that each subscriber queue receives its own copy and an unavailable worker can process its backlog later.

Incorrect Answers

A:

Store all consumer tasks in one local thread. This does not repair the identified SNS fanout delivery failure; the targeted remediation is to give each consumer its own SQS subscription and allow workers to retry independently.

B:

Send events to one shared SQS queue expecting every consumer to see every event. This does not repair the identified SNS fanout delivery failure; the targeted remediation is to give each consumer its own SQS subscription and allow workers to retry independently.

C:

Call each worker inside one HTTP request. This does not repair the identified SNS fanout delivery failure; the targeted remediation is to give each consumer its own SQS subscription and allow workers to retry independently.

Question 561

A refund process must pause for approval and track which previous steps succeeded before compensating. The incident review finds the following problem: A one-shot Lambda chain obscures per-step recovery and can exceed execution constraints. What is the BEST targeted corrective action?

  1. Poll a local variable in a single Lambda for human approval.
  2. Put the entire state machine inside one synchronous API Gateway mapping.
  3. Correct the failing state transition and resume or restart with an explicit compensation path.
  4. Trigger all dependent steps concurrently without preserving ordering.

Explanation

Correct Answer

C:

Correct the failing state transition and resume or restart with an explicit compensation path. This directly addresses the recorded Step Functions orchestration failure and should be checked by observing that execution history shows state transitions, retries, and the branch taken after an error.

Incorrect Answers

A:

Poll a local variable in a single Lambda for human approval. This does not repair the identified Step Functions orchestration failure; the targeted remediation is to correct the failing state transition and resume or restart with an explicit compensation path.

B:

Put the entire state machine inside one synchronous API Gateway mapping. This does not repair the identified Step Functions orchestration failure; the targeted remediation is to correct the failing state transition and resume or restart with an explicit compensation path.

D:

Trigger all dependent steps concurrently without preserving ordering. This does not repair the identified Step Functions orchestration failure; the targeted remediation is to correct the failing state transition and resume or restart with an explicit compensation path.

Question 562

A data-sharing workload has S3 read access but cannot decrypt an encrypted cross-account report. The incident review finds the following problem: An S3 object permission alone does not give decrypt access to its KMS key. What is the BEST targeted corrective action?

  1. Add only s3:GetObject and assume it grants kms:Decrypt.
  2. Turn on public bucket read to bypass the KMS key policy.
  3. Copy the key's internal material into the application log.
  4. Update the key policy and caller IAM policy with scoped decrypt rights and test the target object.

Explanation

Correct Answer

D:

Update the key policy and caller IAM policy with scoped decrypt rights and test the target object. This directly addresses the recorded KMS key-policy cross-account failure and should be checked by observing that the external role can use the approved KMS key while unrelated principals remain denied.

Incorrect Answers

A:

Add only s3:GetObject and assume it grants kms:Decrypt. This does not repair the identified KMS key-policy cross-account failure; the targeted remediation is to update the key policy and caller IAM policy with scoped decrypt rights and test the target object.

B:

Turn on public bucket read to bypass the KMS key policy. This does not repair the identified KMS key-policy cross-account failure; the targeted remediation is to update the key policy and caller IAM policy with scoped decrypt rights and test the target object.

C:

Copy the key's internal material into the application log. This does not repair the identified KMS key-policy cross-account failure; the targeted remediation is to update the key policy and caller IAM policy with scoped decrypt rights and test the target object.

Question 563

An event processor wants richer failure records than the original event alone after async retries. The incident review finds the following problem: Treating an async DLQ as a complete execution trace omits response context. What is the BEST targeted corrective action?

  1. Drop the event after the first retry without a failure sink.
  2. Use Lambda destinations for each synchronous SDK invocation without wrapping.
  3. Replace async destinations with S3 object versioning.
  4. Configure and authorize the on-failure destination and inspect its invocation record.

Explanation

Correct Answer

D:

Configure and authorize the on-failure destination and inspect its invocation record. This directly addresses the recorded Lambda destinations versus DLQ failure and should be checked by observing that the target receives a record including request details and failure response context.

Incorrect Answers

A:

Drop the event after the first retry without a failure sink. This does not repair the identified Lambda destinations versus DLQ failure; the targeted remediation is to configure and authorize the on-failure destination and inspect its invocation record.

B:

Use Lambda destinations for each synchronous SDK invocation without wrapping. This does not repair the identified Lambda destinations versus DLQ failure; the targeted remediation is to configure and authorize the on-failure destination and inspect its invocation record.

C:

Replace async destinations with S3 object versioning. This does not repair the identified Lambda destinations versus DLQ failure; the targeted remediation is to configure and authorize the on-failure destination and inspect its invocation record.

Question 564

A developer needs a distributed trace of an asynchronous dependency call chain. The incident review finds the following problem: Missing trace context between calls breaks a distributed trace even when local segments exist. What is the BEST targeted corrective action?

  1. Turn off tracing in every downstream service.
  2. Enable tracing at supported integrations and propagate trace identifiers through outgoing calls.
  3. Generate an unrelated trace ID for every internal call.
  4. Replace trace context with a fixed user password.

Explanation

Correct Answer

B:

Enable tracing at supported integrations and propagate trace identifiers through outgoing calls. This directly addresses the recorded X-Ray trace propagation failure and should be checked by observing that a trace view shows related segments or subsegments with timing for the connected service path.

Incorrect Answers

A:

Turn off tracing in every downstream service. This does not repair the identified X-Ray trace propagation failure; the targeted remediation is to enable tracing at supported integrations and propagate trace identifiers through outgoing calls.

C:

Generate an unrelated trace ID for every internal call. This does not repair the identified X-Ray trace propagation failure; the targeted remediation is to enable tracing at supported integrations and propagate trace identifiers through outgoing calls.

D:

Replace trace context with a fixed user password. This does not repair the identified X-Ray trace propagation failure; the targeted remediation is to enable tracing at supported integrations and propagate trace identifiers through outgoing calls.

Question 565

A service caches an API token and must recover promptly when that token is rotated. The incident review finds the following problem: A process-wide cache with no expiry continues to use revoked values. What is the BEST targeted corrective action?

  1. Store secrets in publicly writable object tags.
  2. Cache the sensitive value forever in the container image.
  3. Disable auditing for GetSecretValue requests.
  4. Add a refresh policy and invalidate cached credentials after rotation or authentication failures.

Explanation

Correct Answer

D:

Add a refresh policy and invalidate cached credentials after rotation or authentication failures. This directly addresses the recorded credential caching refresh failure and should be checked by observing that secret-read API volume declines while newly rotated credentials are adopted within the specified refresh window.

Incorrect Answers

A:

Store secrets in publicly writable object tags. This does not repair the identified credential caching refresh failure; the targeted remediation is to add a refresh policy and invalidate cached credentials after rotation or authentication failures.

B:

Cache the sensitive value forever in the container image. This does not repair the identified credential caching refresh failure; the targeted remediation is to add a refresh policy and invalidate cached credentials after rotation or authentication failures.

C:

Disable auditing for GetSecretValue requests. This does not repair the identified credential caching refresh failure; the targeted remediation is to add a refresh policy and invalidate cached credentials after rotation or authentication failures.

Question 566

A Python service must authenticate API calls to AWS without putting a static signature string into requests. The incident review finds the following problem: Manually reusing an old signature fails when headers, body, timestamps, or credentials change. What is the BEST targeted corrective action?

  1. Remove the signature header and rely on network privacy.
  2. Use the SDK credential chain, refresh session credentials, and allow its signer to build requests.
  3. Put a Cognito ID token into the SigV4 secret-key field.
  4. Paste a fixed signed header into every outgoing request.

Explanation

Correct Answer

B:

Use the SDK credential chain, refresh session credentials, and allow its signer to build requests. This directly addresses the recorded SigV4 authenticated SDK requests failure and should be checked by observing that aPI requests carry valid signatures derived from current credentials and pass IAM authorization.

Incorrect Answers

A:

Remove the signature header and rely on network privacy. This does not repair the identified SigV4 authenticated SDK requests failure; the targeted remediation is to use the SDK credential chain, refresh session credentials, and allow its signer to build requests.

C:

Put a Cognito ID token into the SigV4 secret-key field. This does not repair the identified SigV4 authenticated SDK requests failure; the targeted remediation is to use the SDK credential chain, refresh session credentials, and allow its signer to build requests.

D:

Paste a fixed signed header into every outgoing request. This does not repair the identified SigV4 authenticated SDK requests failure; the targeted remediation is to use the SDK credential chain, refresh session credentials, and allow its signer to build requests.

Question 567

An API integration must map headers and body properties to a required downstream payload contract. The incident review finds the following problem: A mismatched integration payload causes field-level validation errors even with a healthy backend. What is the BEST targeted corrective action?

  1. Update the mapping expressions and test a representative request against the backend contract.
  2. Change the Lambda runtime version to alter JSON keys automatically.
  3. Disable all API authorizers to bypass mapping errors.
  4. Add more SQS consumers without changing the request shape.

Explanation

Correct Answer

A:

Update the mapping expressions and test a representative request against the backend contract. This directly addresses the recorded API Gateway mapping templates failure and should be checked by observing that recorded integration requests contain the exact backend field names and values expected by the service.

Incorrect Answers

B:

Change the Lambda runtime version to alter JSON keys automatically. This does not repair the identified API Gateway mapping templates failure; the targeted remediation is to update the mapping expressions and test a representative request against the backend contract.

C:

Disable all API authorizers to bypass mapping errors. This does not repair the identified API Gateway mapping templates failure; the targeted remediation is to update the mapping expressions and test a representative request against the backend contract.

D:

Add more SQS consumers without changing the request shape. This does not repair the identified API Gateway mapping templates failure; the targeted remediation is to update the mapping expressions and test a representative request against the backend contract.

Question 568

A document portal lets users download one private object for a limited time. The incident review finds the following problem: Publishing access keys in client code exposes reusable credentials beyond one object operation. What is the BEST targeted corrective action?

  1. Embed an IAM user's permanent secret access key in mobile apps.
  2. Make the entire bucket publicly writable.
  3. Sign the exact object operation with a short expiry and ensure IAM permissions are scoped.
  4. Use an unsigned GET URL for a private PUT upload.

Explanation

Correct Answer

C:

Sign the exact object operation with a short expiry and ensure IAM permissions are scoped. This directly addresses the recorded S3 presigned URLs failure and should be checked by observing that a request succeeds before expiry for the intended action and fails after the URL is invalid.

Incorrect Answers

A:

Embed an IAM user's permanent secret access key in mobile apps. This does not repair the identified S3 presigned URLs failure; the targeted remediation is to sign the exact object operation with a short expiry and ensure IAM permissions are scoped.

B:

Make the entire bucket publicly writable. This does not repair the identified S3 presigned URLs failure; the targeted remediation is to sign the exact object operation with a short expiry and ensure IAM permissions are scoped.

D:

Use an unsigned GET URL for a private PUT upload. This does not repair the identified S3 presigned URLs failure; the targeted remediation is to sign the exact object operation with a short expiry and ensure IAM permissions are scoped.

Question 569

A retail clickstream table routes a high write volume to only one partition-key value. The incident review finds the following problem: A low-cardinality or hot partition key concentrates traffic despite available table capacity. What is the BEST targeted corrective action?

  1. Use one constant partition key for every customer.
  2. Replace Query with Scan and assume hot-key writes disappear.
  3. Redesign the key distribution with entity-aware or write-sharded values if access patterns permit.
  4. Add a DynamoDB TTL attribute to raise per-key write throughput.

Explanation

Correct Answer

C:

Redesign the key distribution with entity-aware or write-sharded values if access patterns permit. This directly addresses the recorded DynamoDB partition key cardinality failure and should be checked by observing that consumed capacity and throttling metrics distribute more evenly across partition keys.

Incorrect Answers

A:

Use one constant partition key for every customer. This does not repair the identified DynamoDB partition key cardinality failure; the targeted remediation is to redesign the key distribution with entity-aware or write-sharded values if access patterns permit.

B:

Replace Query with Scan and assume hot-key writes disappear. This does not repair the identified DynamoDB partition key cardinality failure; the targeted remediation is to redesign the key distribution with entity-aware or write-sharded values if access patterns permit.

D:

Add a DynamoDB TTL attribute to raise per-key write throughput. This does not repair the identified DynamoDB partition key cardinality failure; the targeted remediation is to redesign the key distribution with entity-aware or write-sharded values if access patterns permit.

Question 570

A deployment artifact should use the same IaC source but separate S3 bucket names by environment. The incident review finds the following problem: Hardcoding production resource names in a shared template can cause cross-environment collisions. What is the BEST targeted corrective action?

  1. Duplicate production secrets in template descriptions.
  2. Pass the correct parameter values and inspect the generated change set before execution.
  3. Change DNS cache time-to-live instead of template parameters.
  4. Hand-edit each deployed resource in the console after every commit.

Explanation

Correct Answer

B:

Pass the correct parameter values and inspect the generated change set before execution. This directly addresses the recorded CloudFormation resource parameters failure and should be checked by observing that the change set shows the intended resource values for the selected environment without modifying source templates.

Incorrect Answers

A:

Duplicate production secrets in template descriptions. This does not repair the identified CloudFormation resource parameters failure; the targeted remediation is to pass the correct parameter values and inspect the generated change set before execution.

C:

Change DNS cache time-to-live instead of template parameters. This does not repair the identified CloudFormation resource parameters failure; the targeted remediation is to pass the correct parameter values and inspect the generated change set before execution.

D:

Hand-edit each deployed resource in the console after every commit. This does not repair the identified CloudFormation resource parameters failure; the targeted remediation is to pass the correct parameter values and inspect the generated change set before execution.

AWS Certified Developer - Associate DVA-C02 Practice Tests