In determining the controller deployment mode, what factor is less relevant?

Question

Options

• AThe latency sensitivity of the monitored applications
• BThe visual preferences of the dashboard users
• CThe resilience requirements of the system
• DThe disaster recovery capabilities

• A
  8% (2)
• B
  88% (23)
• C
  4% (1)

Explanation

Option B is correct because visual preferences of dashboard users are a cosmetic concern - they affect how data is displayed, not where or how controllers are deployed. Dashboard aesthetics can be configured independently of deployment topology.

Why the distractors are wrong:

• A (Latency sensitivity) directly impacts deployment placement - latency-sensitive applications require controllers positioned close to the monitored workloads to avoid measurement distortion.
• C (Resilience requirements) drives decisions about redundancy and clustering - high-availability systems need controllers deployed in fault-tolerant configurations.
• D (Disaster recovery capabilities) influences geographic distribution - DR planning determines whether controllers must span multiple sites or regions to survive failures.

Memory tip: Think of deployment mode decisions as purely operational and architectural - latency, resilience, and DR are all infrastructure concerns that physically constrain where a controller must live. Anything in the "how it looks" category (UI, visuals, dashboards) is application-layer configuration that doesn't touch deployment topology. If a factor could be changed after deployment without moving anything, it's probably not a deployment factor.

No community discussion yet for this question.