{"question":{"id":12422,"htmlId":"question12422","kind":"SingleChoice","specVersion":null,"questionHtml":"

After the deployment of a new feature, your web application starts experiencing unpredictable delays. During peak hours, the system struggles to maintain optimal performance. To address the issue, you consult the service map from AWS X-Ray and notice increased latency in the communication between a serverless computing service and a managed relational database. What should this observation prompt you to investigate further?

","descriptionHtml":"

When a service map shows high latency between a serverless component and a managed database, it often implies that the database could be the source of the delays. You should inspect the database's performance metrics for possible bottlenecks, such as poorly optimized queries or inadequate CPU or memory resources. Tuning queries or scaling the database can mitigate the problem. The other responses are less relevant because they do not directly address the database-related latency indicated on the service map.

","answers":[{"id":2537374,"html":"

Check for any recent updates to the SDK in the serverless function that could be incompatible with the managed database communication protocols.

","isCorrect":false},{"id":2537373,"html":"

Review the execution role associated with the serverless function for possible misconfigurations or insufficient permissions leading to latency.

","isCorrect":false},{"id":2537375,"html":"

Inspect network configurations, since a misconfiguration in network ACLs or security groups might lead to increased response times.

","isCorrect":false},{"id":2537372,"html":"

Analyze the performance of the managed database, checking for suboptimal queries or resource limitations, and consider enhancements or scaling.

","isCorrect":true}],"textInput":null,"matching":null,"objectiveId":1735,"objectiveTitle":"Troubleshooting and Optimization","nextQuestionUrl":"/study/questions/dva-c02/which-statement-best-describes-how-amazon-dynamodb-streams-can-be/12772?HideScore=false&ObjectiveMode=RoundRobbinObjectives","questionUrl":"/study/questions/dva-c02/after-the-deployment-of-a-new-feature-your-web-application-starts/12422","followUpPrompts":[{"id":341445,"prompt":"How can I use AWS X-Ray to pinpoint slow database queries?","response":"Enable active tracing for your serverless functions (for example, Lambda) so X‑Ray records traces and the service map shows latency between your function and the database. Instrument the code to create subsegments around DB calls and add metadata/annotations (for example, query name, table, or normalized SQL) so traces show which queries are slow. Note: X‑Ray does not automatically capture full SQL for most drivers, so add that context where safe (avoid logging sensitive data). Use the traces to see which requests have the largest DB subsegment durations and drill into their timeline to find whether latency is spent on waiting for the DB or network. Correlate those traces with database-side tools — enable RDS/Aurora slow query logs and use Performance Insights to see top SQL by execution time and active sessions. Combining X‑Ray (which pinpoints which requests are affected) with DB logs/Performance Insights (which show the exact SQL and DB resource waits) gives the most actionable view."},{"id":341446,"prompt":"Which database metrics should I check to determine if resource limitations are causing latency?","response":"Use CloudWatch, RDS/Aurora Performance Insights, and the DB slow query log. Key metrics: - CPUUtilization and FreeableMemory: high CPU or low memory indicate resource contention. - ReadLatency / WriteLatency and ReadIOPS / WriteIOPS: elevated latency or sustained high IOPS show I/O bottlenecks. - DiskQueueDepth: growing queue depth means storage can’t keep up. - DatabaseConnections: too many connections can exhaust resources (important for serverless spikes). - AverageActiveSessions / Top SQL (Performance Insights): shows whether waits come from a few heavy queries. - SwapUsage and PageFaults: memory pressure signs. Also inspect slow query logs, lock/ deadlock counts, and index usage. These metrics help determine whether you need query tuning, more CPU/memory, faster storage (provisioned IOPS), or connection management (RDS Proxy)."},{"id":341447,"prompt":"What immediate and longer‑term actions reduce latency between serverless functions and a managed relational database?","response":"Immediate actions: - Identify and optimize slow SQL (add indexes, rewrite queries, limit result sets, add pagination). - Enable Performance Insights and slow query logging to find hotspots. - Use caching (ElastiCache) for frequent reads to remove DB pressure. - Use RDS Proxy to pool and manage connections from serverless functions to avoid connection storms. - Scale the DB (larger instance class or provisioned IOPS) if resource metrics show saturation. Longer‑term actions: - Schema and query refactor (normalization/denormalization where appropriate) and materialized views. - Add read replicas for read scaling or use Aurora with Reader endpoints. - Implement asynchronous patterns (queues) for non‑critical work to smooth traffic spikes. - Consider serverless‑friendly database options (Aurora Serverless v2) or sharding for extreme scale. Combine monitoring (X‑Ray + Performance Insights + CloudWatch) with these mitigations to validate improvements and prevent recurrence."}],"presentationMode":false,"hideFeedbackForm":false,"hideResponseBadges":false,"setId":null,"skipSaveResponse":false},"canVote":false,"streak":{"value":null,"title":null,"launchConfetti":false,"isRecord":false},"id":"crucial-react-93b9bfc7d8da433fbe7c73f1a08a190d"}

AWS Certified Developer Associate DVA-C02 Practice Question

Report Issue