A project lead is turning a proof of concept into a governed production workflow. The team is focused on platform support. Which recommendation is most appropriate?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Here's the deal: you would not ship a production change with no owner and no rollback plan. The same common sense applies here. In this scenario, answer B is the practical move because it keeps the implementation tied to the real IBM capability instead of chasing a shortcut.
Full explanation below image
Full Explanation
Here's the deal: you would not ship a production change with no owner and no rollback plan. The same common sense applies here. In this scenario, answer B 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 B. Confirm sensors, tracers, languages, and platforms are supported before rollout. That aligns with the Domain 5: Planning 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 sounds related, but it does not solve the platform support requirement described in the scenario. - Option C 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 sounds related, but it does not solve the platform support requirement described in the scenario. 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 'Confirm sensors, tracers, languages, and platforms are supported before rollout.'. The incorrect options — 'Deploy blindly and wait for missing services', 'Assume every library produces traces automatically', 'Use unsupported runtimes for critical proof points' — 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 5: Planning domain of the IBM Instana Observability certification.