CTFL-v4 Testing Throughout the SDLC Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Ignore the error as it only occurs under high load, which is not the primary focus.

  Why it's wrong here

  Performance testing is a critical part of the SDLC. Ignoring performance-related errors like connection pool exhaustion leads to production failures under real-world usage. A robust system must handle expected load levels, so these errors indicate a defect that must be prioritized and corrected to meet non-functional requirements.

• ✗

  Increase the number of threads in the API gateway to mask the timeout.

  Why it's wrong here

  Simply increasing threads is a reactive fix that often hides the underlying issue without resolving the resource exhaustion. This is poor practice as it ignores the root cause, which is a connection pool mismanagement, likely leading to similar issues in the future as the user base grows further.

• ✓

  Conduct a root cause analysis on the connection pool configuration and design.

  Why this is correct

  Root cause analysis addresses the source of the timeout. By examining the connection pool, the team can determine if it is a configuration issue or a design flaw, such as failing to close connections properly. This systematic approach ensures long-term stability and aligns with the professional testing responsibility.

• ✗

  Immediately roll back the last code deployment to the production environment.

  Why it's wrong here

  Rolling back is premature without understanding the cause. If the issue is a standard configuration oversight, a rollback will not fix it. The tester must first investigate and confirm if the issue is code-related or environment-related before recommending any irreversible actions like rolling back a production deployment.