A hot standby node belongs to a clique of nodes and does not host virtual processes such as AMPs or Parsing Engines.
Part of the Teradata Internals and Operations guide.
The standby node remains idle until a member of its clique crashes or fails. At this point, the standby node is activated to take over the failed node’s responsibilities.
Failover may move AMPs to a standby node, but interruption and performance effects depend on platform, state recovery and workload. No failover or negligible-loss guarantee was tested.

The intelligence of the design lies in the fact that once the failed node goes back online, it automatically takes over as the active standby node.

This describes a platform-specific clique/hot-standby architecture, not every cloud or Teradata deployment. Confirm recovery and availability behavior for the actual system.
Need help with query performance or platform costs?
Diagnose plans, skew, spool pressure and expensive workloads. Agree a baseline and acceptance criteria before making changes.
