To answer this question, you need to understand the alternatives to embedding Java code directly within the HTML markup of a JSP (JavaServer Pages) page. Let's go through each option to understand why it is correct or incorrect:
Option A) Moving the code into your session manager - This option is incorrect because the session manager is responsible for managing user sessions and maintaining session data. It does not provide an alternative for embedding Java code within the HTML markup of a JSP page.
Option B) Moving the code into scriptlets - This option is incorrect because scriptlets are a way to embed Java code directly within the HTML markup of a JSP page. It does not provide an alternative to embedding Java code.
Option C) Moving the code into JavaBeans and servlets - This option is correct because JavaBeans and servlets provide an alternative to embedding Java code directly within the HTML markup of a JSP page. JavaBeans are reusable components that encapsulate data and business logic, while servlets handle the request and response processing. By moving the code into JavaBeans and servlets, you can separate the business logic from the presentation layer, improving code modularity and maintainability.
Option D) Moving the code into a transaction manager - This option is incorrect because a transaction manager is responsible for managing database transactions and ensuring data consistency. It does not provide an alternative for embedding Java code within the HTML markup of a JSP page.
Therefore, the correct answer is Option C) Moving the code into JavaBeans and servlets. This option is correct because it provides an alternative to embedding Java code directly within the HTML markup of a JSP page by separating the business logic into reusable JavaBeans and servlets.