IBM WebSphere Portal 8.0 Solution Development Sample Questions:

1. A client wants to write several portlets for their new website. Each portlet must be labeled and record some trace information whenever it is accessed. The portlets must share common information with each other as well. When discussing best practices options with the client, which of the following would not be recommended?

A) Portlets communicate via writing to a common file in the root directory.
B) Trace information can be logged to log files.
C) JSPs should be used to separate output and functionality of the portlets.
D) Each portlet can be labeled by its own title bar.

2. When creating and registering a custom portlet service, it is possible to set initialization parameters. What code would Adrienne use to access a parameter with the name sample.portletservice.HelloServiceImpl2.message?

A) public void init(Preferences servicePreferences) {
String message = servicePreferences.get("message",
"Hello");
}
B) public void sayHello(RenderRequest request, RenderResponse response)
{
String message = request.getAttribute("message");
}
C) public void init(Preferences servicePreferences) {
String message = servicePreferences.getInitParam("message",
"Hello");
}
D) public void sayHello(RenderRequest request, RenderResponse response)
{
String message = request.getParameter("message");
}

3. Roger has been discussing iWidgets with a prospective client and has been highlighting certain aspects of the specification. Which of the following statements is false and thus ill-advised?

A) The iDescriptor is a special ManagedItemSet which is always persisted by the iContext.
B) Three modes are defined in the iContext Constants (VIEW, EDIT and HELP). An iWidget does not need to support all three modes.
C) iScope is a mechanism to support encapsulation of an iWidget's assests.
D) Overall page management components are provided by the iContext. These include iWidget coordination, page layout and controls, andbackend service interaction.

4. PreferencePortlet is Portlet Specification 2.0-compliant and the system is running IBM WebSphere Portal 8.0. What is the output of the following code? public PreferencePortlet extends GenericPortlet{ protected void processAction(ActionRequest actionRequest, ActionResponse){ actionRequest.getPreferences().setValue("test","ViewModePreferenceValue"); actionRequest.getPreferences().store(); } protected void doView(RenderRequest renderRequest, RenderResponse renderResponse) throws PortletException, IOException { // Generate action URL }

A) The container throws javax.portlet.ReadOnlyException because it is only allowed to view preferences in the processAction() method.
B) The container throws java.lang.IllegalStateException because it is not allowed to change preferences in the processAction() method.
C) The code compiles and executes fine. It stores a "test" preference at the end of the processAction() method call.
D) This code results in a compiler error because PortletPreference does not have the store() method.

5. Quinn is creating a module that adds a customized Dojo lightbox for a disclaimer to overlay the screen as soon as the page loads using dojo.addOnLoad. She has already created myLightBox.css and intends to write the JavaScript event triggering the lightbox inline. What must Quinn do to ensure she gets the desired functionality at minimal performance cost?

A) Quinn must create a CSS sub-contribution type in her module pointing to myLightBox.css. The JavaScript can be added anywhere therein aslong as the page uses the default deferred profile and the event is added to the event handler.
B) Quinn should add all this code right after the theme's tag to ensure the functionality happens as soon as the body markup is loading.
C) Quinn must add the tag pointing to myLightBox.css into the block. The JavaScript can be added anywhere therein as long asthe page uses the nondeferred profile and the event is added to the event handler
D) Quinn should really write all CSS and JavaScript inline for performance reasons so secondary requests to the server are never made.

Solutions: