I agree that "methods have grown big" is vague. You have to make your best guesses.
You have to approach it asking "Why are they too big?"
In order of likelihood in a typical application:
Situation 1) Too much business logic - you can abstract this closer to the backend... I think that's why the question author chose "Business Delegate" since that pattern is the closest of the SCWCD patterns to the backend, but quite honestly your Business Delegate shouldn't have business logic... you're better off putting that logic in a service class or Session Facade. If your service class or Session Facade is remote, then you can use a Business Delegate to hide the complexities of communicating those remote components.
Situation 2) Some crazy dude has us in a Model 1 architecture where the Servlets are all writing html to the response directly. Or maybe the Servlets are making direct database calls. Bring in the MVC!
Situation 3) Too much boiler-plate code - if every Servlet does some of the same exact work, you could move that code to a Front Controller.
So my answer of likelihood would be:
Session Facade
MVC
Front Controller
However, Session Facade is no longer one of the SCWCD's Big 6 patterns and so will never be a correct answer on the real exam...
So, with that in mind, MVC and Front Controller are the best "real exam" answers. Good job.
