300-910 Question #54: Real Exam Question with Answer & Explanation

Question

Refer to the exhibit. A distributed application contains data services that connect to databases via JDBC and to other remote services via HTTP. The overall response time is too long, and AppDynamics is used to investigate the root cause. From the application flow map, a specific data service running on Docker has been identified whose response time is over 10 seconds. Which action resolves the issue?

Options

• AChange from a JDBC call to a HTTP call to retrieve data faster
• BRun the AccountProfileMySQL service in Kubernetes
• CExplore the JDBC queries looking for optimization opportunities
• DVerify if the Docker container running MySQL is limiting CPU utilization

Explanation

When a data service running in Docker exhibits long response times due to slow JDBC calls, a critical first step is to verify if the Docker container running the database (e.g., MySQL) is being throttled by CPU utilization limits.

Common mistakes.

• A. Changing from JDBC to HTTP calls is an architectural redesign, not a direct performance optimization, and HTTP might introduce more overhead unless the API is highly optimized for the specific use case.
• B. Migrating a service from Docker to Kubernetes is a change in orchestration platform and does not inherently resolve underlying performance bottlenecks like slow queries or resource starvation if those issues persist in the new environment.
• C. Exploring JDBC queries for optimization is a valid step, but if the underlying database container is resource-starved (e.g., CPU-limited), even optimized queries will perform poorly; checking container resources often takes precedence as an initial diagnostic.

Concept tested. Docker container resource troubleshooting

Reference. https://docs.docker.com/config/containers/resource_constraints/

No community discussion yet for this question.