ISC2 Certified Secure Software Lifecycle Professional (CSSLP) Practice Question

During a code review of a Java servlet-based payment API, assessors notice that uncaught runtime exceptions propagate to the container, which returns full stack traces to callers and leaves request threads active until they time out. Which remediation best aligns with secure exception-handling practice to curb both denial-of-service risk and information leakage?

  • Add a global exception handler that catches unhandled exceptions, logs them, frees resources, and returns a generic 500 error page without the stack trace.

  • Disable logging of runtime exceptions so stack traces are never written to the response or log files.

  • Surround each business method with a catch block that swallows Throwable and continues processing without reporting an error.

  • Increase the servlet container's maximum thread pool size so additional requests can be served despite lingering faulted threads.

ISC2 Certified Secure Software Lifecycle Professional (CSSLP)
Secure Software Implementation
Your Score:
Settings & Objectives
Random Mixed
Questions are selected randomly from all chosen topics, with a preference for those you haven’t seen before. You may see several questions from the same objective or domain in a row.
Rotate by Objective
Questions cycle through each objective or domain in turn, helping you avoid long streaks of questions from the same area. You may see some repeat questions, but the distribution will be more balanced across topics.

Check or uncheck an objective to set which questions you will receive.

Bash, the Crucial Exams Chat Bot
AI Bot