A team is preparing a production rollout and needs to avoid a design mistake. What is the best way to handle agent modes while staying aligned with the certification objectives?

Here's the deal: agent modes is not just a checkbox; it is the difference between a clean handoff and a late-night recovery call. In this scenario, answer C is the practical move because it keeps the implementation tied to the real IBM capability instead of chasing a shortcut. The other choices sound tempting, but they either skip governance, ignore operational reality, or solve the wrong problem.

The correct answer is C. Choose the agent mode that matches platform and operational constraints. That aligns with the Domain 3: Installation objective because it applies the feature or practice in the context where IBM expects a practitioner to use it. It also keeps the design reviewable, supportable, and realistic for a production environment.

Let's examine why the other options are incorrect: - Option A is incorrect because it uses an overbroad rule instead of matching the design to the actual workload and risk. - Option B is incorrect because it uses an overbroad rule instead of matching the design to the actual workload and risk. - Option D is incorrect because it removes visibility or governance at the exact point where the team needs it most. For the exam, connect the feature to the operational outcome: the right answer is the one that preserves control, accuracy, and maintainability instead of relying on a brittle shortcut. The correct answer is 'Choose the agent mode that matches platform and operational constraints.'. The incorrect options — 'Assume all agents must run with identical privileges', 'Use serverless agents for every VM workload', 'Disable auto-discovery in dynamic platforms' — are wrong because they do not align with IBM Instana's architecture or recommended practices for this scenario. Understanding this concept is essential for the Domain 3: Installation domain of the IBM Instana Observability certification.