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 41

Question 400

A product system routes events to different consumers based on detail-type and account metadata. A teammate asks why the proposed EventBridge event routing approach is technically appropriate. Which AWS behavior BEST explains the decision?

  1. Full-text search uses analyzed inverted indexes rather than DynamoDB exact-key access.
  2. Strongly consistent reads are available on DynamoDB tables and LSIs in a Region, not GSIs.
  3. EventBridge rules route structured events by matching attributes without embedding consumer addresses in producer code.
  4. Kinesis ordering is guaranteed within a shard and partition key choices determine shard affinity.

Explanation

Correct Answer

C:

EventBridge rules route structured events by matching attributes without embedding consumer addresses in producer code. This is the governing behavior behind the recommended change: put events on an EventBridge bus and create rules matching the required event patterns to targets.

Incorrect Answers

A:

The statement describes OpenSearch full-text queries, which is not the controlling AWS behavior for this EventBridge event routing situation. The required implementation is: put events on an EventBridge bus and create rules matching the required event patterns to targets.

B:

The statement describes DynamoDB strong read consistency, which is not the controlling AWS behavior for this EventBridge event routing situation. The required implementation is: put events on an EventBridge bus and create rules matching the required event patterns to targets.

D:

The statement describes Kinesis shard partitioning, which is not the controlling AWS behavior for this EventBridge event routing situation. The required implementation is: put events on an EventBridge bus and create rules matching the required event patterns to targets.

Question 401

A pipeline needs to prevent credentials in code, configuration, or test fixtures from reaching release artifacts. A teammate asks why the proposed secret scanning in CI approach is technically appropriate. Which AWS behavior BEST explains the decision?

  1. Encryption at rest does not stop an application from leaking plaintext secrets during logging.
  2. SigV4 signs request components using AWS credentials and short-lived credentials include a session token.
  3. Secret scanning reduces accidental credential publication but exposed keys must be invalidated.
  4. TLS certificates authenticate endpoint names and protect traffic in transit.

Explanation

Correct Answer

C:

Secret scanning reduces accidental credential publication but exposed keys must be invalidated. This is the governing behavior behind the recommended change: run automated secret scanning in CI and revoke exposed credentials instead of merely deleting one commit.

Incorrect Answers

A:

The statement describes Lambda environment secret leakage, which is not the controlling AWS behavior for this secret scanning in CI situation. The required implementation is: run automated secret scanning in CI and revoke exposed credentials instead of merely deleting one commit.

B:

The statement describes SigV4 authenticated SDK requests, which is not the controlling AWS behavior for this secret scanning in CI situation. The required implementation is: run automated secret scanning in CI and revoke exposed credentials instead of merely deleting one commit.

D:

The statement describes TLS certificate rotation ACM, which is not the controlling AWS behavior for this secret scanning in CI situation. The required implementation is: run automated secret scanning in CI and revoke exposed credentials instead of merely deleting one commit.

Question 402

A client uploads confidential data and needs the server never to receive unencrypted object bytes. A teammate asks why the proposed client-side versus server-side encryption approach is technically appropriate. Which AWS behavior BEST explains the decision?

  1. Secret scanning reduces accidental credential publication but exposed keys must be invalidated.
  2. Envelope encryption uses a data key for payload encryption and protects that key using a KMS key.
  3. Client-side encryption protects data prior to upload; SSE encrypts it after S3 receives the request.
  4. Cross-account roles require both role trust and permission policy authorization.

Explanation

Correct Answer

C:

Client-side encryption protects data prior to upload; SSE encrypts it after S3 receives the request. This is the governing behavior behind the recommended change: encrypt in the client with properly protected keys before uploading ciphertext to storage.

Incorrect Answers

A:

The statement describes secret scanning in CI, which is not the controlling AWS behavior for this client-side versus server-side encryption situation. The required implementation is: encrypt in the client with properly protected keys before uploading ciphertext to storage.

B:

The statement describes KMS envelope encryption, which is not the controlling AWS behavior for this client-side versus server-side encryption situation. The required implementation is: encrypt in the client with properly protected keys before uploading ciphertext to storage.

D:

The statement describes IAM STS AssumeRole cross-account, which is not the controlling AWS behavior for this client-side versus server-side encryption situation. The required implementation is: encrypt in the client with properly protected keys before uploading ciphertext to storage.

Question 403

An event-driven worker retries DynamoDB writes heavily during a predictable product launch. A teammate asks why the proposed DynamoDB throttling investigation approach is technically appropriate. Which AWS behavior BEST explains the decision?

  1. Lambda allocates CPU in proportion to memory, so more memory can reduce compute duration.
  2. DynamoDB throttling can reflect hot partitions or configured capacity constraints, not just network faults.
  3. CloudWatch log groups retain data indefinitely by default unless a retention setting is configured.
  4. Authorization for an encrypted object can involve multiple services and different policy evaluators.

Explanation

Correct Answer

B:

DynamoDB throttling can reflect hot partitions or configured capacity constraints, not just network faults. This is the governing behavior behind the recommended change: inspect DynamoDB throttling and consumed-capacity metrics, key access patterns, and application retry behavior.

Incorrect Answers

A:

The statement describes Lambda duration versus memory tradeoff, which is not the controlling AWS behavior for this DynamoDB throttling investigation situation. The required implementation is: inspect DynamoDB throttling and consumed-capacity metrics, key access patterns, and application retry behavior.

C:

The statement describes CloudWatch log retention, which is not the controlling AWS behavior for this DynamoDB throttling investigation situation. The required implementation is: inspect DynamoDB throttling and consumed-capacity metrics, key access patterns, and application retry behavior.

D:

The statement describes AccessDenied troubleshooting chain, which is not the controlling AWS behavior for this DynamoDB throttling investigation situation. The required implementation is: inspect DynamoDB throttling and consumed-capacity metrics, key access patterns, and application retry behavior.

Question 404

A feature branch needs a disposable serverless stack with test-only API endpoints. A teammate asks why the proposed stage-isolated integration stack approach is technically appropriate. Which AWS behavior BEST explains the decision?

  1. Environment isolation prevents test mutations from affecting production state.
  2. Generated tests require human review and meaningful assertions to avoid false confidence.
  3. Event-driven tests must exercise the actual source envelope and partial failure contract.
  4. CI/CD stage ordering and approvals reduce uncontrolled deployment changes.

Explanation

Correct Answer

A:

Environment isolation prevents test mutations from affecting production state. This is the governing behavior behind the recommended change: deploy a separate IaC-managed test stack with isolated resource names and clean it up after testing.

Incorrect Answers

B:

The statement describes AI-assisted test review, which is not the controlling AWS behavior for this stage-isolated integration stack situation. The required implementation is: deploy a separate IaC-managed test stack with isolated resource names and clean it up after testing.

C:

The statement describes SQS handler contract tests, which is not the controlling AWS behavior for this stage-isolated integration stack situation. The required implementation is: deploy a separate IaC-managed test stack with isolated resource names and clean it up after testing.

D:

The statement describes CodePipeline gated promotion, which is not the controlling AWS behavior for this stage-isolated integration stack situation. The required implementation is: deploy a separate IaC-managed test stack with isolated resource names and clean it up after testing.

Question 405

A billing subscriber receives events for all product lines but should process only invoices. Suppose the team omits the intended SNS subscription filter policy safeguard. Which failure mode is the MOST direct risk of that omission?

  1. Without the correct metric statistic or alarm action, sustained incidents can remain unnoticed.
  2. Unbounded fanout can overwhelm a dependency even if the caller has ample compute capacity.
  3. Putting sensitive free-form payloads in indexed annotations creates exposure and high-cardinality filtering problems.
  4. Without a filter the subscriber receives unrelated messages and spends capacity rejecting them.

Explanation

Correct Answer

D:

Without a filter the subscriber receives unrelated messages and spends capacity rejecting them. The planned prevention is to apply an SNS subscription filter policy on the relevant message attributes or payload fields; the most direct verification is that only events matching the subscriber's policy reach its target while other topics of work are skipped.

Incorrect Answers

A:

That failure mechanism is associated with CloudWatch alarm notification. The omitted SNS subscription filter policy protection instead causes this problem: without a filter the subscriber receives unrelated messages and spends capacity rejecting them.

B:

That failure mechanism is associated with concurrency backpressure. The omitted SNS subscription filter policy protection instead causes this problem: without a filter the subscriber receives unrelated messages and spends capacity rejecting them.

C:

That failure mechanism is associated with tracing annotations versus metadata. The omitted SNS subscription filter policy protection instead causes this problem: without a filter the subscriber receives unrelated messages and spends capacity rejecting them.

Question 406

A legacy backend expects a compact JSON shape while clients send a differently named field. Suppose the team omits the intended API Gateway mapping templates safeguard. Which failure mode is the MOST direct risk of that omission?

  1. Treating an async DLQ as a complete execution trace omits response context.
  2. Accepting generated code without review can introduce incorrect APIs or excessive permissions.
  3. The execution role lacks a required resource permission and AWS denies the API call.
  4. A mismatched integration payload causes field-level validation errors even with a healthy backend.

Explanation

Correct Answer

D:

A mismatched integration payload causes field-level validation errors even with a healthy backend. The planned prevention is to define an API Gateway mapping template or parameter mapping that explicitly transforms the incoming request; the most direct verification is that recorded integration requests contain the exact backend field names and values expected by the service.

Incorrect Answers

A:

That failure mechanism is associated with Lambda destinations versus DLQ. The omitted API Gateway mapping templates protection instead causes this problem: a mismatched integration payload causes field-level validation errors even with a healthy backend.

B:

That failure mechanism is associated with Amazon Q Developer review. The omitted API Gateway mapping templates protection instead causes this problem: a mismatched integration payload causes field-level validation errors even with a healthy backend.

C:

That failure mechanism is associated with Lambda execution role least privilege. The omitted API Gateway mapping templates protection instead causes this problem: a mismatched integration payload causes field-level validation errors even with a healthy backend.

Question 407

Unit tests call a paid third-party API and become flaky during external outages. Suppose the team omits the intended API external dependency mocks safeguard. Which failure mode is the MOST direct risk of that omission?

  1. Tests using only happy-path payloads miss error handling and event-shape incompatibilities.
  2. Skipping runtime-compatible local tests can miss event-shape and handler configuration bugs.
  3. Relying only on live third-party calls makes tests slow and nondeterministic.
  4. Packaging before test validation can promote artifacts containing known defects.

Explanation

Correct Answer

C:

Relying only on live third-party calls makes tests slow and nondeterministic. The planned prevention is to mock external dependency responses in unit tests and retain separate contract or integration tests; the most direct verification is that tests deterministically exercise success, timeout, and error handling without contacting the live partner.

Incorrect Answers

A:

That failure mechanism is associated with deployment test event generation. The omitted API external dependency mocks protection instead causes this problem: relying only on live third-party calls makes tests slow and nondeterministic.

B:

That failure mechanism is associated with local SAM API testing. The omitted API external dependency mocks protection instead causes this problem: relying only on live third-party calls makes tests slow and nondeterministic.

D:

That failure mechanism is associated with CodeBuild buildspec sequencing. The omitted API external dependency mocks protection instead causes this problem: relying only on live third-party calls makes tests slow and nondeterministic.

Question 408

A session store records an expiration timestamp but the app must deny an expired session immediately. Suppose the team omits the intended DynamoDB TTL expiry semantics safeguard. Which failure mode is the MOST direct risk of that omission?

  1. Treating TTL cleanup as synchronous can keep expired data valid until deletion occurs.
  2. Holding memory at the minimum can constrain compute even when the function has spare heap.
  3. An unconditional PutItem can overwrite valid concurrent state without a conflict signal.
  4. Duplicate deliveries bypass a stable deduplication check and cause the same side effect twice.

Explanation

Correct Answer

A:

The planned prevention is to check the epoch expiration attribute in application logic while using DynamoDB TTL for eventual cleanup; the most direct verification is that an expired item is denied by the app even when the physical DynamoDB item has not yet disappeared.

Incorrect Answers

B:

That failure mechanism is associated with Lambda memory CPU tuning. The omitted DynamoDB TTL expiry semantics protection instead causes this problem: treating TTL cleanup as synchronous can keep expired data valid until deletion occurs.

C:

That failure mechanism is associated with DynamoDB conditional update. The omitted DynamoDB TTL expiry semantics protection instead causes this problem: treating TTL cleanup as synchronous can keep expired data valid until deletion occurs.

D:

That failure mechanism is associated with idempotent event handling. The omitted DynamoDB TTL expiry semantics protection instead causes this problem: treating TTL cleanup as synchronous can keep expired data valid until deletion occurs.

Question 409

A JSON API must admit only callers with valid bearer access tokens issued by a trusted user directory. Suppose the team omits the intended API Gateway JWT authorizer safeguard. Which failure mode is the MOST direct risk of that omission?

  1. Merely checking that Authorization is nonempty accepts fabricated or expired tokens.
  2. An S3 object permission alone does not give decrypt access to its KMS key.
  3. Adding another Allow statement does not override an explicit Deny.
  4. A plaintext String parameter does not provide the intended encrypted-at-rest secret boundary.

Explanation

Correct Answer

A:

Merely checking that Authorization is nonempty accepts fabricated or expired tokens. The planned prevention is to configure a JWT authorizer with the trusted issuer and audience and bind it to protected API routes; the most direct verification is that valid JWTs reach integrations while expired, bad-signature, or wrong-audience tokens are rejected.

Incorrect Answers

B:

That failure mechanism is associated with KMS key-policy cross-account. The omitted API Gateway JWT authorizer protection instead causes this problem: merely checking that Authorization is nonempty accepts fabricated or expired tokens.

C:

That failure mechanism is associated with IAM policy explicit deny. The omitted API Gateway JWT authorizer protection instead causes this problem: merely checking that Authorization is nonempty accepts fabricated or expired tokens.

D:

That failure mechanism is associated with Parameter Store secure strings. The omitted API Gateway JWT authorizer protection instead causes this problem: merely checking that Authorization is nonempty accepts fabricated or expired tokens.

Question 410

A staging deployment should use a different feature flag than production without changing code. Suppose the team omits the intended environment-specific AppConfig safeguard. Which failure mode is the MOST direct risk of that omission?

  1. Missing or wrongly packaged dependencies cause runtime import failures before handler logic runs.
  2. Copying production flags into staging accidentally enables functionality in the wrong environment.
  3. A pipeline that rebuilds a different artifact after approval breaks artifact provenance.
  4. Updating the production stage for every test exposes incomplete behavior to consumers.

Explanation

Correct Answer

B:

Copying production flags into staging accidentally enables functionality in the wrong environment. The planned prevention is to store environment-specific configuration in AWS AppConfig and deploy validated configuration versions; the most direct verification is that the correct environment retrieves its scoped configuration and a failed rollout can be rolled back.

Incorrect Answers

A:

That failure mechanism is associated with Lambda deployment package dependencies. The omitted environment-specific AppConfig protection instead causes this problem: copying production flags into staging accidentally enables functionality in the wrong environment.

C:

That failure mechanism is associated with CodePipeline gated promotion. The omitted environment-specific AppConfig protection instead causes this problem: copying production flags into staging accidentally enables functionality in the wrong environment.

D:

That failure mechanism is associated with API Gateway staging endpoints. The omitted environment-specific AppConfig protection instead causes this problem: copying production flags into staging accidentally enables functionality in the wrong environment.

AWS Certified Developer - Associate DVA-C02 Practice Tests