Which of the following statements about restarting Grid services are true?

Comprehensive and Detailed In-Depth Explanation:Restarting services (e.g., DNS, DHCP) on NIOS Grid members is a common administrative task, often required after configuration changes. Let’s break down each option with detailed reasoning:

A:"Poll members to see which services will be restarted" suggests proactively querying members for restart eligibility. NIOS doesn’t offer a specific polling feature for this—administrators check service status (e.g., via Grid Manager > Members > Services) or logs, but there’s no pre-restart polling tool. Incorrect.

B:In Grid Manager (Grid > Grid Manager > Members), you can select a member and click "Restart Services" with a "Force Restart" option, overriding any checks for necessity. This is useful in troubleshooting (e.g., clearing a hung DNS service). Correct.

C:NIOS allows scheduling service restarts via the "Schedule Restart" option in Grid Manager, letting you specify a time to minimize disruption (e.g., off-hours). This aligns with Grid management best practices taught in INE. Correct.

D:There’s no default daily restart policy in NIOS. Restarts occur only when triggered by an admin or system event (e.g., upgrade). This would disrupt service unnecessarily if true. Incorrect.

Practical Example:During an INE lab, you might force a restart on a member to resolve a DHCP failover issue or schedule a restart after updating a DNS zone to ensure propagation, reflecting real-world Grid troubleshooting.References:Infoblox NIOS Administrator Guide – Managing Grid Services; INE Course Content: NIOS DDI Grid Troubleshooting.