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

Here's the deal: OpenTelemetry integration 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. Configure OpenTelemetry ingestion so traces and metrics fit Instana's service model. That aligns with the Domain 2: Configuration 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 relies on an assumption rather than verifying the architecture, permissions, or operational behavior. - Option B is incorrect because it sounds related, but it does not solve the OpenTelemetry integration requirement described in the scenario. - Option D is incorrect because it uses an overbroad rule instead of matching the design to the actual workload and risk. 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 'Configure OpenTelemetry ingestion so traces and metrics fit Instana's service model.'. The incorrect options — 'Assume OpenTelemetry data appears without endpoint configuration', 'Strip trace context at the gateway', 'Send telemetry to a closed firewall port' — 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 2: Configuration domain of the IBM Instana Observability certification.