IT Cert Ready

AWS

AWS Certified Developer – Associate

Exam code: DVA-C02

Start practicing

About this certification

AWS Certified Developer – Associate is a AWS certification. Exam code DVA-C02. IT Cert Ready offers 1,153 practice questions with domain quizzes, full mock exams, and detailed explanations. Practice by official domain with 4 blueprint-aligned domains.

Official exam domain weights

Verified blueprint weights from the official exam outline.

  • Domain 1 · Development with AWS Services · 32%
  • Domain 2 · Security · 26%
  • Domain 3 · Deployment · 24%
  • Domain 4 · Troubleshooting and Optimization · 18%

Sample AWS Certified Developer – Associate practice questions

Preview realistic multiple-choice items from the IT Cert Ready question bank. Expand each answer for the correct choice and explanation—the same format used in domain quizzes and mock exams.

  1. Sample question 1 · Troubleshooting and Optimization (18%)

    Polaris Cargo Networks, a regional logistics startup operating in Southeast Asia, recently launched an API-driven partner onboarding portal built on Amazon API Gateway and AWS Lambda. The portal issues short-lived TLS client certificates to new carrier partners. A senior partner, Dawnstar Shipping Co., has formally complained to Polaris's CTO that their onboarding API calls intermittently return HTTP 500 errors. The CTO has asked the development team to provide a stakeholder-ready explanation of the failure pattern, including whether the errors are consistent or random, and whether they correlate with specific API resources or Lambda cold starts. As the AWS developer, which combination of AWS observability tools will MOST effectively help you determine whether the HTTP 500 errors are caused by Lambda cold starts, a specific API resource path, or an application exception — and produce findings suitable for a stakeholder briefing?

    • A. Enable API Gateway access logging to a CloudWatch Logs log group with a log format that includes $context.resourcePath, $context.status, and $context.integrationStatus, then use CloudWatch Logs Insights to group errors by resource path; simultaneously review Lambda CloudWatch Logs for INIT_START entries to identify cold start invocations coinciding with 500 errors.
    • B. Configure an Amazon CloudWatch alarm on the API Gateway 5XXError metric with a threshold of one error per minute and subscribe an Amazon SNS topic to notify the CTO in real time, then wait for the next occurrence to capture live log data.
    • C. Enable AWS X-Ray on the Lambda function only and review subsegment annotations to determine which downstream service call is faulting, then present the X-Ray service map screenshot to the CTO as the stakeholder briefing artifact.
    • D. Increase the Lambda function's reserved concurrency to eliminate cold starts, redeploy the function, and monitor the API Gateway 5XXError CloudWatch metric over 48 hours to determine if the error rate decreases before conducting any log analysis.
    View answer & explanation

    Correct answer: A. Enable API Gateway access logging to a CloudWatch Logs log group with a log format that includes $context.resourcePath, $context.status, and $context.integrationStatus, then use CloudWatch Logs Insights to group errors by resource path; simultaneously review Lambda CloudWatch Logs for INIT_START entries to identify cold start invocations coinciding with 500 errors.

    [Domain 4 - Troubleshooting and Optimization, Subtopic 4 - Troubleshooting and Optimization - Area 1 - CloudWatch Logs] Core Concept: Troubleshoot application failures using AWS tools. centers on cloudwatch logs as defined in the official (ISC)² exam outline. Correct Answer (A): Enable API Gateway access logging to a CloudWatch Logs log group with a log format that includes $context.resourcePath, $context.status, and $context.integrationStatus, then use CloudWatch Logs Insights to group errors by resource path; simultaneously review Lambda CloudWatch Logs for INIT_START entries to identify cold start invocations coinciding with 500 errors. Why the other options are incorrect: Option B: Configuring a CloudWatch alarm on the 5XXError metric provides real-time notification of error rate thresholds but does not capture the resource path, integration status, or cold start context needed to explain the failure pattern; waiting for the next occurrence without pre-configured structured logging delays the investigation and does not produce the analytical depth required for a stakeholder briefing. Option C: Enabling X-Ray only on the Lambda function and presenting the service map addresses downstream subsegment faults but omits the API Gateway layer entirely; without API Gateway access logs, the developer cannot determine whether errors are path-specific or correlate with cold starts, and a service map screenshot alone is insufficient as a stakeholder briefing artifact without supporting log evidence. Option D: Increasing reserved concurrency to eliminate cold starts is a remediation action, not a diagnostic step; applying a fix before completing root cause analysis risks masking the actual failure mechanism, and monitoring a metric over 48 hours without structured log data cannot confirm whether cold starts were the true cause or whether an application exception is independently generating 500 errors.

  2. Sample question 2 · Troubleshooting and Optimization (18%)

    Crestline Federal Credit Union is a small financial institution in the Pacific Northwest that recently migrated its member authentication service to AWS Lambda. Following a wave of credential-stuffing attacks linked to a phishing campaign, the bank's incident response team needs to correlate Lambda function invocation errors with specific member session identifiers to determine which accounts were targeted. The Lambda function currently writes standard console.log output, but the team cannot find the session IDs in CloudWatch Logs because the log group has not been structured for searchable queries. The developer must implement a solution that allows the team to filter Lambda log output by session ID within CloudWatch Logs Insights without redeploying the function's core business logic. As the AWS developer, which implementation best meets this requirement to enable the incident response team to query Lambda logs by session ID in CloudWatch Logs Insights?

    • A. Refactor the Lambda function to emit structured JSON log lines that include a sessionId field alongside the log level and message, then use a CloudWatch Logs Insights query with a filter on the sessionId field to isolate targeted accounts.
    • B. Enable AWS X-Ray active tracing on the Lambda function and add sessionId as a custom annotation on each X-Ray segment so the team can filter traces by session ID in the X-Ray console's filter expression.
    • C. Create a CloudWatch metric filter on the Lambda log group that extracts session IDs from unstructured log lines and publishes a custom metric, then graph the metric in a CloudWatch dashboard to identify affected sessions.
    • D. Configure a Lambda Destinations rule to send failed invocation records to an SQS queue, then write a secondary Lambda function that reads from the queue and indexes session IDs into a DynamoDB table for the incident team to query.
    View answer & explanation

    Correct answer: A. Refactor the Lambda function to emit structured JSON log lines that include a sessionId field alongside the log level and message, then use a CloudWatch Logs Insights query with a filter on the sessionId field to isolate targeted accounts.

    [Domain 4 - Troubleshooting and Optimization, Subtopic 4 - Troubleshooting and Optimization - Area 1 - CloudWatch Logs] Core Concept: Troubleshoot application failures using AWS tools. centers on cloudwatch logs as defined in the official (ISC)² exam outline. Correct Answer (A): Refactor the Lambda function to emit structured JSON log lines that include a sessionId field alongside the log level and message, then use a CloudWatch Logs Insights query with a filter on the sessionId field to isolate targeted accounts. Why the other options are incorrect: Option B: X-Ray annotations enable trace-level filtering in the X-Ray console and are valuable for latency and fault analysis, but X-Ray does not provide the full log-line context (error messages, stack traces, business data) that the incident team needs to reconstruct the attack sequence per session. Option C: CloudWatch metric filters extract numeric or counted values from log lines to publish CloudWatch metrics, but they do not preserve the raw log content or enable ad-hoc querying of individual session records; they are suited for alerting on aggregate counts, not forensic session-level investigation. Option D: Lambda Destinations capture only failed or successful invocation metadata records, not the full application log output; routing these records to SQS and DynamoDB adds significant operational complexity and does not address the requirement to query existing Lambda log output by session ID.

  3. Sample question 3 · Troubleshooting and Optimization (18%)

    Harborlight Life Insurance, a small regional insurer with a single AWS region deployment, is conducting its annual BCP/DR tabletop exercise focused on backup validation. During the exercise, the team simulates a scenario where their serverless claims-adjudication workflow — built with Step Functions invoking multiple Lambda functions — produces incorrect adjudication decisions without throwing any errors. Post-exercise, the developer is tasked with implementing observability so that future silent logic failures (wrong output, no exception) can be detected and traced across the multi-step workflow. The developer has already confirmed that each Lambda function writes structured JSON logs to its respective CloudWatch log group, but there is no cross-function correlation today. As the AWS developer, which approach best enables the team to trace a single claims request across all Lambda functions in the Step Functions workflow and identify which step produced the incorrect output during a silent logic failure?

    • A. Enable AWS X-Ray tracing on the Step Functions state machine and on each Lambda function, then use the X-Ray Service Map and trace timeline to correlate segments across all steps of the workflow for a given execution, identifying the step where output diverged.
    • B. Create a single aggregated CloudWatch log group and configure each Lambda function to write logs to that shared group using a common log stream name based on the Lambda function name.
    • C. Enable CloudWatch Container Insights on the Step Functions state machine to collect execution-level metrics and identify the failing step through anomaly detection.
    • D. Configure a CloudWatch Logs subscription filter on each Lambda log group to stream logs to Amazon Kinesis Data Firehose, then use Amazon Athena to query logs across functions by timestamp range.
    View answer & explanation

    Correct answer: A. Enable AWS X-Ray tracing on the Step Functions state machine and on each Lambda function, then use the X-Ray Service Map and trace timeline to correlate segments across all steps of the workflow for a given execution, identifying the step where output diverged.

    [Domain 4 - Troubleshooting and Optimization, Subtopic 4 - Troubleshooting and Optimization - Area 1 - CloudWatch Logs] Core Concept: Troubleshoot application failures using AWS tools. centers on cloudwatch logs as defined in the official (ISC)² exam outline. Correct Answer (A): Enable AWS X-Ray tracing on the Step Functions state machine and on each Lambda function, then use the X-Ray Service Map and trace timeline to correlate segments across all steps of the workflow for a given execution, identifying the step where output diverged. Why the other options are incorrect: Option B: Writing all Lambda functions to a single shared CloudWatch log group with function-name-based stream names does not provide cross-request correlation; without a shared request or execution ID embedded in every log entry, it is still impossible to reconstruct the full journey of a single claims request across all steps, and this approach creates log management complexity without solving the tracing problem. Option C: CloudWatch Container Insights is designed for containerized workloads running on ECS, EKS, or Kubernetes; it does not apply to Step Functions or Lambda functions and would not provide step-level execution tracing or output inspection for a serverless workflow. Option D: Streaming logs to Kinesis Data Firehose and querying with Athena is a valid long-term analytics pattern but requires a common correlation identifier (such as a trace ID or execution ID) to be present in every log entry; without X-Ray or explicit developer-injected correlation IDs, Athena queries on timestamp alone cannot reliably reconstruct the causal chain of a single request across multiple Lambda functions.

  4. Sample question 4 · Troubleshooting and Optimization (18%)

    Cargolux Meridian, a large international freight operator headquartered in Europe, uses AWS Lambda to process inbound EDI messages from partner logistics firms. Each Lambda function validates partner TLS certificates against an internal certificate authority before processing shipment data. The compliance officer has escalated a governance concern: over the past two weeks, three partner integrations silently failed to process messages, and no alerts were generated. The head of IT governance has requested a formal root cause report and demands that the development team demonstrate which specific Lambda invocations failed, when they failed, and what error messages were produced. As the AWS developer preparing the root cause report for the IT governance committee, which approach using AWS Lambda logs and CloudWatch Logs Insights will BEST allow you to retrieve the specific invocation failures, their timestamps, and associated error messages for the two-week window?

    • A. Use the AWS X-Ray console to filter traces by fault status within the two-week date range, export the trace summaries, and include the fault annotations and metadata in the governance report.
    • B. Run a CloudWatch Logs Insights query against the Lambda function's log group using fields @timestamp, @message, and filter @message like /ERROR/ with a time range covering the two-week window, then sort results by @timestamp to enumerate each failed invocation.
    • C. Pull Lambda function invocation metrics from CloudWatch Metrics using the Errors metric with a two-week period and 1-minute granularity, then export the metric data as a CSV and attach it to the governance report.
    • D. Enable AWS Config rules to detect Lambda function configuration changes over the two-week period and correlate configuration drift events with the dates when partner integrations were reported as failing.
    View answer & explanation

    Correct answer: B. Run a CloudWatch Logs Insights query against the Lambda function's log group using fields @timestamp, @message, and filter @message like /ERROR/ with a time range covering the two-week window, then sort results by @timestamp to enumerate each failed invocation.

    [Domain 4 - Troubleshooting and Optimization, Subtopic 4 - Troubleshooting and Optimization - Area 1 - CloudWatch Logs] Core Concept: Troubleshoot application failures using AWS tools. centers on cloudwatch logs as defined in the official (ISC)² exam outline. Correct Answer (B): Run a CloudWatch Logs Insights query against the Lambda function's log group using fields @timestamp, @message, and filter @message like /ERROR/ with a time range covering the two-week window, then sort results by @timestamp to enumerate each failed invocation. Why the other options are incorrect: Option A: X-Ray traces capture latency and fault status at the segment level but require active tracing to have been enabled prior to the failures; if tracing was not pre-configured, no historical trace data will exist, and even when available, X-Ray does not expose the full Lambda log message text needed for the governance report. Option C: CloudWatch Metrics Errors counts provide aggregate invocation failure totals per time interval but do not contain the individual error messages, invocation identifiers, or stack traces required to explain what failed and why; metrics alone cannot satisfy the governance committee's demand for specific error detail. Option D: AWS Config tracks configuration changes to Lambda function resources such as memory, timeout, and environment variables, but it does not record runtime invocation failures or log output; certificate validation errors at runtime are application-layer events invisible to AWS Config.

  5. Sample question 5 · Troubleshooting and Optimization (18%)

    Aldenmoor University's IT security office is investigating a malware alert that triggered during a Lambda function processing incoming research grant submissions through an API Gateway REST API. The university's compliance officer needs to determine whether the Lambda function's execution duration spiked abnormally during the incident window — a potential indicator of cryptomining malware — and whether any cold starts occurred that might have introduced new execution environments. The developer must also confirm whether X-Ray sampling was active and whether the traces captured during the window are statistically representative enough to support the compliance report. The university operates under a state records retention mandate requiring that all investigative findings be documented with the specific AWS log sources and sampling parameters used. As the AWS developer at Aldenmoor University, which combination of actions best supports the compliance officer's requirement to document Lambda duration anomalies, cold start occurrences, and X-Ray trace sampling coverage during the incident window?

    • A. Review Lambda CloudWatch log streams for REPORT log lines to extract Duration, Billed Duration, and Init Duration fields indicating cold starts; query CloudWatch Logs Insights for statistical aggregation of duration values; and retrieve the X-Ray sampling rule configuration from the X-Ray console to document the sampling rate and reservoir size applied during the window.
    • B. Enable AWS Lambda Power Tuning after the incident to test different memory configurations and use the resulting duration benchmarks as a proxy for the incident window behavior, then document those benchmarks in the compliance report.
    • C. Create a CloudWatch alarm on the Lambda Duration metric with a threshold set above the observed spike value, then use the alarm history as the primary evidence of the duration anomaly in the compliance report.
    • D. Use AWS CloudTrail to retrieve the Lambda invocation history for the window and calculate average duration from the CloudTrail event timestamps, then assume X-Ray captured all requests because tracing was enabled on the function.
    View answer & explanation

    Correct answer: A. Review Lambda CloudWatch log streams for REPORT log lines to extract Duration, Billed Duration, and Init Duration fields indicating cold starts; query CloudWatch Logs Insights for statistical aggregation of duration values; and retrieve the X-Ray sampling rule configuration from the X-Ray console to document the sampling rate and reservoir size applied during the window.

    [Domain 4 - Troubleshooting and Optimization, Subtopic 4 - Troubleshooting and Optimization - Area 1 - CloudWatch Logs] Core Concept: Troubleshoot application failures using AWS tools. centers on cloudwatch logs as defined in the official (ISC)² exam outline. Correct Answer (A): Review Lambda CloudWatch log streams for REPORT log lines to extract Duration, Billed Duration, and Init Duration fields indicating cold starts; query CloudWatch Logs Insights for statistical aggregation of duration values; and retrieve the X-Ray sampling rule configuration from the X-Ray console to document the sampling rate and reservoir size applied during the window. Why the other options are incorrect: Option B: Lambda Power Tuning tests future memory configurations under synthetic load and produces no evidence about what actually occurred during the incident window; its output cannot be used as a proxy for historical execution behavior in a compliance report. Option C: A CloudWatch alarm created after the incident cannot retroactively establish an alarm history for the window that preceded its creation, and alarm history alone does not provide the per-invocation duration detail or cold start evidence required by the compliance officer. Option D: CloudTrail records Lambda Invoke API calls at the control-plane level and does not include function execution duration; additionally, assuming X-Ray captured all requests ignores the statistical sampling model and fails to document the actual sampling rate, which is a required disclosure under the state records retention mandate.

AWS Certified Developer – Associate exam prep FAQ

What is the passing score for the AWS Certified Developer – Associate exam?
Passing scores for AWS Certified Developer – Associate are set by AWS and can change between exam versions. Check the latest official exam outline on the AWS website for the current passing standard.
How many questions are on the AWS Certified Developer – Associate certification exam?
Official AWS Certified Developer – Associate exam length and item types are defined by AWS. Review the current exam blueprint for the latest question counts and timing.
How do domain quizzes help with AWS Certified Developer – Associate exam prep?
Domain quizzes on IT Cert Ready let you practice AWS Certified Developer – Associate one blueprint domain at a time across 4 official exam domains. You get immediate feedback, detailed explanations, and can revisit weak areas before taking a full timed mock exam.
How many AWS Certified Developer – Associate practice questions are on IT Cert Ready?
IT Cert Ready includes 1,153 published AWS Certified Developer – Associate practice questions with domain quizzes, full-length mock exams, and answer explanations mapped to the official outline.