Computer Knowledge
Java Enterprise and Web Technologies
2,279 Questions
Java enterprise and web technologies questions focus on J2EE architecture, web services like SOAP, and servlet functionalities. These topics frequently appear in IT officer and specialist scale examinations. Regular practice ensures familiarity with enterprise application components.
HttpServlet methodsSOAP and web servicesEJB architecture rolesJ2EE componentsJSP servlet callingUDDI concepts
Java Enterprise and Web Technologies Questions
-
ClientId
-
jsessionid
-
Formclass
-
FormId
-
ReqID
-
Reload
A,B,E,F
Correct answer
Explanation
In Documentum web applications, dynamic session and request identifiers like ClientId, jsessionid, ReqID, and Reload change with each request or session and must be correlated in LoadRunner to maintain a valid session. Formclass and FormId are typically static application-level identifiers and do not require correlation.
-
SAP-Web
-
Web(HTTP/HTML)
-
Web(Click and Script)
-
Web Services
B
Correct answer
Explanation
Webtop is a web-based application that runs over HTTP/HTTPS. LoadRunner's 'Web (HTTP/HTML)' protocol is designed to record and replay web browser traffic by capturing the underlying HTTP requests, which is the correct protocol for testing Documentum's web interface.
-
Viewlet
-
Applet
-
Servlet
-
Object
B
Correct answer
Explanation
An Applet is a specialized Java program designed to run within web browsers, transmitted over the Internet and executed client-side. Unlike Servlets which run server-side, Applets provided early web interactivity before modern JavaScript frameworks emerged.
-
Flex
-
JSP
-
Silver Light
-
Dot net
D
Correct answer
Explanation
Projectserver.nielsen.com uses Dot Net (Microsoft .NET) technology. This is consistent with Microsoft-based enterprise project management systems. Flex (A) and Silverlight (C) are RIA frameworks, not backend server technologies. JSP (B) is Java-based, while .NET is Microsoft's framework.
-
Clean separation of concerns between HTML and Java
-
Automated state management
-
conjunction with JSP and custom tag libraries
-
Abstraction away from Servlet API and HTTP protocol details
A,B,D
Correct answer
Explanation
Wicket's key benefits are: clean HTML/Java separation (pages are pure XHTML with minimal Wicket tags), automated state management (no manual HTTP session handling), and abstraction from Servlet/HTTP protocol details (developers work with Java components, not HTTP requests directly). Option C describes JSP/taglibs, which Wicket specifically avoids.
-
It is not particularly object-oriented.
-
You work with hierarchies of components and design your application as such.
-
Unless you output HTML directly from your Java code you still need to learn another major technology JSP plus custom tag libraries in order to produce output HTML pages.
-
A very clean object-oriented and component based approach.
A,C
Correct answer
Explanation
Struts is considered outdated because: (A) it's not truly object-oriented - Action classes are HTTP-driven rather than OO-designed; (C) it requires learning JSP and custom taglibs for HTML output. Options B and D incorrectly describe Struts - B mentions hierarchies (not a Struts strength) and D claims it's clean OO (which it is not).
-
Each Action class defines an abstraction, but the abstraction is determined by the HTTP procotol request mechanism rather than by an object-oriented analysis
-
Wicket is fully object-oriented. You work with hierarchies of components and design your application as such.
-
Wicket markup files are as close to pure HTML as it is possible to get. Where Wicket does introduce content into the markup it is very clean and complies with all XHTML standards
-
Wicket is based around intercepting each HTTP request to a web application and directing it to a specific Action class that handles the request
B,C
Correct answer
Explanation
Wicket solves Struts' problems by: (B) being fully object-oriented with component hierarchies, and (C) using pure HTML markup that complies with XHTML standards. Option A describes Struts' problem (Action classes tied to HTTP), and D describes Struts' architecture (not Wicket's).
B
Correct answer
Explanation
Wicket explicitly abstracts away Servlet API and HTTP protocol details. Developers work with Java components and models, while Wicket handles HTTP requests, sessions, and parameters behind the scenes. The statement claims Wicket does NOT hide these details, which is false.
C
Correct answer
Explanation
With Apache Wicket, developers get the benefits of Ajax functionality (partial page updates, dynamic content refresh) without writing raw JavaScript code. Wicket's Ajax-enabled components handle all the complex Ajax plumbing behind the scenes while you work with just Java and HTML. The correct answer is Ajax.
-
WebLogic Application Server 9.x, 10.x
-
Apache Tomcat Web server 5.5x or higher
-
IBM WebSphere Application Server 5.1, 6.1
-
All of the above
D
Correct answer
Explanation
Oracle Adaptive Risk Manager is certified to run on multiple application servers including Oracle WebLogic, Apache Tomcat, and IBM WebSphere, providing deployment flexibility across different Java EE environments.
-
Standalone
-
Server Farm
-
Standalone & Server Farm
-
None of the above
C
Correct answer
Explanation
SharePoint supports two primary deployment configurations: Standalone (where all components and a basic database reside on a single machine) and Server Farm (which allows databases, application servers, and web front-ends to scale across multiple servers).
-
C:\inetpub
-
C:\inetpub\wwwroot\wss\VirtualDirectories
-
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12
-
As per user’s convenience.
B
Correct answer
Explanation
In Microsoft SharePoint (specifically older versions like SharePoint 2007), when a new Web Application is provisioned, IIS virtual directory folders and configurations are created by default under the C:\inetpub\wwwroot\wss\VirtualDirectories folder path.
-
Cookies
-
A query String
-
A URL
-
A javascript function
-
A hidden form field
E
Correct answer
Explanation
Hidden form fields are ideal for storing small amounts of frequently changing page-specific data when security isn't a concern, as they persist with the page and form without the size limitations of cookies or URL complexity. Cookies have size limits (~4KB) and are sent with every HTTP request, while query strings and URLs are visible in the address bar and limited in length.
-
In Cache
-
In Cookies
-
In A Global Variable
-
In URL
B
Correct answer
Explanation
ASP.NET stores SessionIDs in cookies by default, using a non-persistent cookie named ASP.NET_SessionId that identifies the user session across requests. The SessionID can be stored in the URL if cookieless sessions are configured, but cookies are the standard default mechanism.
B
Correct answer
Explanation
ASP.NET 2.0 includes the Cassini web server (WebDev.WebServer.exe) which allows development without IIS installed. You can build and test ASP.NET applications using only the built-in development web server, though IIS is required for production deployment.