The application you have created with activation set to Single AppNode is deployed into an AppSpace consisting of two AppNodes (A1 and A2). It is…

The key distinction is between an administrative action and a system fault. Managed Fault Tolerance is designed to provide high availability by automatically responding to an unplanned failure of an AppNode. When an administrator explicitly issues a "stop" command, it is a deliberate, planned action. The TIBCO Enterprise Administrator (TEA) interprets this as an intentional directive to halt the application across the entire AppSpace. Consequently, the active instance on AppNode A1 is stopped, and the standby configuration on AppNode A2 is also removed, changing its state to "Stopped". The system will not initiate a failover, as no fault has occurred.

A. This describes the behavior of an automatic failover, which is triggered by an AppNode failure (e.g., a crash), not a deliberate administrative "stop" command.

C. The "stop" command applies to the application within the entire AppSpace; it would not leave an instance in a "Standby" state, as this would contradict the stop directive.

D. A manual stop does not trigger activation on another node. Furthermore, the statement that it would be activated but not process requests is logically inconsistent.

---

1. TIBCO BusinessWorks™ Container Edition Application Monitoring and Troubleshooting, Version 2.8.1, Chapter 2: Administering Applications, AppSpaces, and AppNodes, Section: Stopping an Application.

This document explicitly states: "When you stop an application, the application is stopped on all the AppNodes in an AppSpace." This directly supports the chosen answer, confirming that the stop command is a global action for the application within its AppSpace.

2. TIBCO BusinessWorks™ Container Edition Concepts, Version 2.8.1, Chapter 5: Administration Concepts, Section: Fault Tolerance.

This section clarifies the trigger for failover in managed fault tolerance mode: "...if an AppNode running an application fails, the TIBCO Enterprise Administrator agent automatically starts the application on another AppNode in the same AppSpace." This confirms that the trigger is a failure, not a manual stop command, thereby invalidating options A and D.

3. TIBCO BusinessWorks™ Container Edition Concepts, Version 2.8.1, Chapter 5: Administration Concepts, Section: Application State.

This section describes the various states of an application, including "Running," "Stopped," and "Standby." An administrative stop command transitions the application to the "Stopped" state on all nodes, not leaving one in "Standby" (invalidating option C).