Prep and try our C2180-608 valid and latest training questions & answers

An application has been deployed on a clustered WebSphere Process Server environment using the Remote Messaging and Remote Support pattern. To handle asynchronous invocation problems, the store-and-forward capability is enabled for several applications. During the test phase one of the target services invoked by the application became unavailable. Which of the following statements is TRUE regarding recovery of events?

• A. No manual intervention is necessary. WebSphere Process Server will poll the target service
  and once it is available, all remaining sequenced
  events will be automatically processed.
• B. A single failed event has been generated by one of the cluster members when the target
  service became unavailable. Resubmit all failed
  events once the target service is available.
• C. Multiple failed events might have been created by different cluster members. All failed events
  must be resubmitted before the Store and
  Forward widget in the Business Space is set to Forward mode.
• D. No manual intervention is necessary. If the store-and-forward feature is activated on a single
  cluster member due to a target service outage,
  the remaining cluster members will take over and complete the invocation transactions.

A deployment professional is asked to clean up several failed events that belong to a long running business process in a clustered WebSphere Process Server environment. These failed events were created as a result of an identified outage of the backend database. Several instances of this business process were created during this outage and have been deleted. What corrective action should the deployment professional take to clean up these failed events?

• A. Create a custom program and use the queryFailedEvents method of the FailedEventManager interface to query all the events associated with this business process, and use the discardFailedEvents method.
• B. Find the events in the Failed Event Manager that belong to the Business Flow Manager hold queue and replay the Hold queue messages.
• C. Use the configRecoveryForCluster command to specify a cluster, that is configured to manage failed events.
• D. Create a custom program and use the Business Flow Manager API queryHldQueueMessage to query all the events and deleteHldQueueMessage to discard the failed events.

In a clustered WebSphere Process Server (WPS) V7.0.0 environment, a company has migrated several long running business processes from earlier V6.x versions. An application performance issue which was identified in earlier versions was resolved by adjusting the maximum concurrent endpoints parameter of the BPEInternalActivationSpec of the Message Driven Bean (MDB) based on the peak load. However, the long running business processes do not perform as well as before. In spite of adopting similar settings, what has happened in the new WebSphere Process Server V7.0.0 environment and what are the appropriate tuning settings?

• A. Modify the sib.msgstore.discardableDataBufferSize and sib.msgstore.cachedDataBufferSizeCachedDataBufferSize for optimal messaging engine (ME) performance.
• B. Modify the JMS connection factory BPECFC connection pool size to number of threads in the BPEInternalActivationSpec plus 10%. This is the required setting in WPS V7.0.0 used when work manager based navigation is enabled.
• C. In WPS V7.0.0, the default for business process navigation is modified to utilize the advanced performance optimizations feature that leverages work manager based navigation. Accordingly, adjust the BPENavigationWorkManager message pool size and the InterTransactionCache size to accommodate the maximum concurrent incoming requests.
• D. WPS V7.0.0 fix pack one must be installed to enable optimization introduced by the Business Object (BO) Runtime Framework.

During the processing of business processes, the following runtime message is observed by the deployment professional in the server log file: BpelEngine I CWWBE0057I: Activity 'Invoke' of processes '_PI:90030128.17946972.9b4886f6.93df0e66' has been stopped because of an unhandled failure. The deployment professional is informed by the development team that no fault handler has been implemented to cover the failing activity. Furthermore, the process is not designed to skip any runtime problems. However, the process must be reactivated as soon as possible. Which action is required to be taken by the deployment professional?

• A. The failed process instance cannot be recovered. Advise the development team to implement a fault handler in the next process version.
• B. No action is required because the transaction will be rolled back automatically and recovered. Investigate the root cause of the failure.
• C. Manually force the process activity to complete or retry using the Business Process Choreographer (BPC) Explorer and further investigate the root cause.
• D. Skip the failing activity using the Business Process Choreographer (BPC) Explorer to complete the process instance.

During the design of a large-scale high-volume topology, a deployment professional is consulting with a client on the planned design and configuration of the databases required for the messaging resources. During this discussion the deployment professional notes that it would be preferable to configure a separate database for the Business Process Choreographer (BPC) messaging engine. What is a reason for making such a suggestion?

• A. Shared databases between the BPC and the SCA bus are not supported in production environments.
• B. The separate database is created automatically in a network deployment environment.
• C. All of the components require the database schema to be named MEDBPM00.
• D. Database logging could become a performance bottleneck.