試験NCP-BC-7.5 トピック1 問題64 スレッド

The Nutanix architecture relies on specialized services running on each Controller VM (CVM) to handle specific cluster operations. The " Cerebro " service is the primary engine responsible for data protection and replication tasks across the Nutanix cluster. It manages recovery points, snapshot schedules, and the actual transfer of data between the local cluster and remote sites. Consequently, the cerebro.INFO log file is the most vital resource for an administrator troubleshooting replication health or site-to-site connectivity. This log records critical events such as the start and completion of replication jobs, handshake failures between clusters, and timeout errors during snapshot transfers. If an administrator notices that replication is " hung " or failing consistently, cerebro.INFO provides the granular detail needed to see if the issue is a network timeout, a remote service unavailability, or a metadata synchronization error. Reviewing this log helps ensure that the connection stability is maintained and that any deviations in replication performance are identified before they impact the Recovery Point Objective (RPO). Other logs like genesis.out (Option B) are more focused on service startup and configuration rather than the ongoing health of the BCDR replication stream.