A. Portlets are set to not render parallel globally on the IBM WebSphere Portal server with this value.

B. Portlets are not able to finish rendering if the data is not accessible immediately. This speeds up rendering.

C. Portlets have no timeout and the main thread waits for all portlets to finish rendering.

D. Portlets wait sequentially for each previous portlet to render its data.

A. Enabling security, and transferring the portal database.

B. Enabling security.

C. Enabling security, transferring the portal database, connecting to an existing database, and enabling IBM Lotus Domino integration (collaborative features, directory integration, and so on).

D. Enabling security, transferring the portal database, and connecting to an existing database.

A. SystemErr.log

B. ConfigEngine.log

C. ConfigTrace.log

D. SystemOut.log

A. 1.Use WebSphere Application Server Network Deployment to create a cell and managed node for each portal node in the cluster.
2.Use the WebSphere Portal cluster profile template to install WebSphere Portal onto each node.
3.Use the ConfigEngine tasks to configure the nodes to use the same database and user registy.
4.Federate each of these nodes into the cluster by using the addNode and ConfigEngine tasks.

B. 1.Install WebSphere Portal on the first node, configure the database, and use the ConfigEngine tasks to create a profile template.
2.Prepare the first node to communicate WebSphere Application Server Network Deployment, and use addNode and ConfigEngine tasks to configure the cluster and user registry.
3.Install WebSphere Portal on additional nodes and use the profile template to configure.
4.Use the addNode and ConfigEngine tasks to federate the additional nodes and complete the cluster setup.

C. 1.Use WebSphere Application Server Network Deployment to create a managed node for each portal node in the cluster.
2.Federate each of these nodes into the WebSphere Application Server Network Deployment cell using the addNode command.
3.Install and configure WebSphere Portal on each portal server node.
4.Use ConfigEngine tasks to configure the database, user registry, and create the cluster.

D. 1.Install and configure WebSphere Portal as a stand-alone node for each cluster node.
2.Federate each portal server node to the WebSphere Application Server Network Deployment cell using the addNode command.
3.Create a portal cluster using the ConfigEngine tasks.
4.Configure the cluster members to use the same database and user registry.

A. IBM WebSphere Portal access control

B. Portlet security control

C. Virtual portal restriction

D. Virtual Member Manager

A. When administrators use the XML configuration interface (xmlaccess) to externalize or internalize access control for a resource, access control for all of its public child resources moves with it.

B. Private pages cannot be externalized.

C. When administrators use the Resource Permissions portlet to externalize or internalize access control for a resource, access control for all of its public child resources moves with it.

D. If a user inherits access to a resource from a parent resource, the user will lose the inherited access when the resource is externalized.

A. pre-post-filtering

B. pre-filtering

C. secure-filtering

D. post-filtering

A. wkplc_comp.properties and wkplc_dbtype.properties

B. wkplc_comp.properties, wkplc_dbtype.properties, and db.config.properties

C. wkplc_dbtype.properties, wkplc_dbdomain.properties and wkplc.properties

D. wkplc_comp.properties

A. Session persistence is enabled by default on all four server instances..

B. Using a shared installation, all four server instances that become a part of the portal farm can be installed on different operating systems.

C. All the server instances need to be configured such that they have an identical security configuration and user repository, such as LDAP.

D. Portal and content caches across all four server instances are replicated seamlessly.