In which deployment type is the log indexing disabled by default?

The correct answer is D. Official R82 Logging and Monitoring documentation states that log indexing is enabled by default on a Security Management Server or Log Server, but in a standalone deployment, log indexing is disabled by default. This is because standalone deployments combine management and gateway functions on the same machine, so indexing can create additional CPU, disk, and memory load on a system that is already enforcing traffic. Option A is wrong because Bridge mode is a gateway traffic deployment mode, not the management/logging deployment type identified for default log indexing behavior. Option B is wrong because distributed deployments typically separate gateway and management/logging roles, allowing indexing by default. Option C is unrelated; Maestro Orchestrator is not the default-disabled log indexing deployment type in this question. The administrator can enable indexing on standalone, but official guidance says to do so only when the standalone server has sufficient CPU resources. Reference topics: Log Indexing, Standalone deployment, Logging and Monitoring, SmartConsole log search.