Filters can be used to manipulate the __________ and __________ before they reach a servlet or JSP.
- context, attributes
- headers, body
- request, response
- session, cookie
Filters can manipulate the request and response objects before they reach a servlet or JSP, allowing for various pre-processing tasks.
To apply multiple filters to a single resource, the web.xml file must define a __________ for each filter.
- filter-chain
- filter-group
- filter-list
- filter-mapping
In the web.xml file, a filter-mapping element must be defined for each filter to apply multiple filters to a single resource.
Consider a scenario where a request needs to be authenticated and then logged. How should the filters be arranged in the filter chain?
- Authenticate, Log, Other Filters, Process Request
- Authenticate, Other Filters, Log, Process Request
- Log, Authenticate, Other Filters, Process Request
- Other Filters, Authenticate, Log, Process Request
In this scenario, it is ideal to perform authentication before logging. Therefore, the correct order is to place the authentication filter before the logging filter in the filter chain. This ensures that the request is authenticated first, and then the logging is done.
In a scenario where a filter chain is used for both compression and encryption, which process should ideally occur first?
- Compression, Encryption, Other Filters, Process Request
- Compression, Other Filters, Encryption, Process Request
- Encryption, Compression, Other Filters, Process Request
- Other Filters, Compression, Encryption, Process Request
In this scenario, it is generally recommended to perform encryption before compression. This ensures that the data is first secured through encryption and then compressed. Therefore, the correct order is to place the encryption filter before the compression filter in the filter chain.
When a request is processed through multiple filters, how is the order of execution determined in a servlet application?
- The order is determined alphabetically based on filter names.
- The order is determined by the order in the web.xml file.
- The order is determined by the order in which filters are added programmatically in the servlet code.
- The order is determined randomly at runtime.
The order of execution of filters is determined by the order in which they are declared in the deployment descriptor (web.xml) file. The filters are applied to the request and response objects in the order specified in the deployment descriptor.
Which listener interface in Servlets is used for receiving notification about ServletContext lifecycle changes?
- HttpSessionListener
- ServletContextAttributeListener
- ServletContextListener
- ServletRequestListener
The ServletContextListener interface is used for receiving notifications about ServletContext lifecycle changes, such as when it is initialized or destroyed.
The __________ element in web.xml is used to define a logical name for a servlet.
- logical-name
- name
- servlet-logical
- servlet-name
The element in web.xml is used to define a logical name for a servlet.
What is the primary use of the ServletContextAttributeListener in a web application?
- To handle changes in session attributes.
- To listen for changes in the servlet context.
- To monitor changes in attributes at the application scope.
- To track the addition or removal of servlets in the application.
The primary use of ServletContextAttributeListener is to monitor changes in attributes at the application scope, such as when attributes are added, removed, or replaced in the ServletContext.
If you want to perform some task when a session is created or destroyed, which listener should you implement?
- HttpSessionAttributeListener
- HttpSessionListener
- ServletContextListener
- ServletRequestListener
The HttpSessionListener interface is used to perform tasks when a session is created or destroyed.
Which listener is used to track changes to the attributes of the ServletRequest?
- HttpSessionListener
- ServletContextListener
- ServletRequestAttributeListener
- ServletRequestListener
The ServletRequestAttributeListener interface is used to track changes to the attributes of the ServletRequest, such as when an attribute is added, removed, or replaced.