The following error is displayed when an IBM FileNet P8 Administrator launches the Process Task Manager:

What is the reason that may cause this error?

• A. The Component Manager did not start.
• B. The administrator did not start the Process Engine by running the "initfnsw start" command.
• C. The Process Engine's database is down.
• D. The Process Engine Manager service did not start.

A client is planning the implementation of an IBM FileNet P8 platform and needs to identify and plan for deployment environments. What are the installation types that should be considered while planning for a IBM FileNet P8 deployment?

• A. Preproduction, Disaster recovery, and Production.
• B. Development and Production.
• C. Development, Test, Disaster recovery, and Production.
• D. Development, Test, Preproduction, Disaster recovery, and Production.

A customer is designing a highly available IBM FileNet P8 system with both horizontally and vertically scaled implementations of Content Engine and Workplace XT. The customer desires to use a hardware load balancer in front of a series of HTTP proxy servers to spread all HTTP/HTTPS traffic. Additionally, a hardware load balancer will be used to spread traffic across multiple Process Engine servers. The J2EE server being used is IBM WebSphere Application Server Network Deployment. There is a single WAS Cell with one Content Engine cluster defined and one Workplace XT cluster defined. In order to facilitate proper high availability functionality of the IBM FileNet P8 environment, what context format should be used when specifying the RemoteServerUrl in Workplace XT? (Choose two.)

• A. cemp:t3://node1_name:node1_port,node2_name:node2_port/FileNet/Engine
• B. cemp:iiop://CEserver:2809/FileNet/Engine
• C. cemp:corbaloc:rir:/cell/clusters/<cluster_name>/FileNet/Engine
• D. cemp:jnp://node1_name:node1_port,node2_name:node2_port/FileNet/Engine
• E. cemp:corbaloc::node1_name:node1_port,:node2_name:node2_port/cell/clusters/<cluster_n ame>/FileNet/Engine

A highly available IBM FileNet P8 environment has just been installed with horizontally scaled Process Engine (PE) servers using a hardware load balancer. There are currently two PE servers in this farm. There are three Connection Points currently configured, one for PE #1, one for PE #2, and one for the virtual address and port of the farm as defined in the load balancer. Additionally there are load balanced implementations of Workplace XT (WPXT) and Content Engine (CE). Assuming all P8 core components are currently active, and the Connection Point for the PE farm is currently selected in the WPXT Site Preferences, which of the following is the best choice for validating PE functionality in conjunction with the load balancer.

• A. The required PE session affinity, defined in the load balancer, prevents in-process transactions from failing over to a secondary PE in farmed environment. If a failure occurs, the transaction is rolled-back and the user must restart that transaction upon failing over to a new PE. To test this functionality, begin some PE related work such as launching a workflow and just before completing a step, shutdown the active PE. When attempting to complete the workflow step, the user will have to relaunch that step to continue.
• B. Open two browsers. In the first browser logon to WPXT and change the Site Preferences by selecting a Connection Point that is configured for PE #1. In the second browser, logon to WPXT, launch a previously created two-step workflow. Complete the first step of the workflow. In the first browser select a Connection Point that is configured for PE #2. In the second browser, complete the second step of the workflow.
• C. Shutdown PE #2. Logon via WPXT. Open Process Designer. Create a simple two-step workflow definition. Validate the workflow definition. Start PE #2 and shutdown PE #1. Launch the workflow. Close Process Designer. Complete the first step of the workflow. Start PE #1 and shutdown PE #2. Complete the second step of the workflow.
• D. View the PE Ping Page of the load balancer (i.e. http://<virtual_name>:<virtual_port>/IOR/ping). Continue to refresh this page in the browser until both PE servers respond. View the PE Ping Page of each PE server directly. Compare the results.

A customer creates two file storage areas, D:\FileStores\SA1 and D:\FileStores\SA2, and associates the storage areas with a storage policy: "Farmed Storage Policy". The Default Storage Policy and the Default Storage Area for the Document class is set as follows:

What happens when new documents of type Document are added to this object store?

• A. The Farmed Storage Policy is in place as well as the default database storage area. Documents are added randomly to either of the three storage areas.
• B. The Farmed Storage Policy is ignored and the documents gets added to the default database storage area.
• C. The Farmed Storage Policy is in place and the documents gets added to the farmed storage areas.
• D. The system is not able to decide whether the storage policy takes precedence over the storage area. The user is prompted to select the storage area and adds the document based on the user's selection.