What parameter informs a probe to use 'sudo' on commands?

The parameter that informs a probe to use 'sudo' on commands is 'must_sudo.' This setting is specifically designed to ensure that the probe executes certain commands with elevated privileges, which is a requirement for accessing and gathering specific system information that regular user privileges may not allow.

When 'must_sudo' is set to true, it signals the probe that administrative capabilities are necessary for the task it is performing. This is critical in scenarios where the probe needs to retrieve data that is sensitive or requires higher access rights, such as inspecting system configurations or accessing files that are not available to standard users. By utilizing 'sudo,' the probe can run commands with the higher privileges necessary for the complete and correct execution of its tasks, ensuring that it can effectively gather the required data without running into permission issues.

The other options mentioned may not provide the same level of specificity or may serve different roles in configuration management or permissions. Therefore, 'must_sudo' is the correct choice due to its direct implication for commanding elevated privileges during the probe's operations.