A team is preparing a production rollout and needs to avoid a design mistake. What is the best way to handle log levels while staying aligned with the certification objectives?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Here's the deal: this is where a demo turns into an operation. The design has to survive real users, real failures, and real audits. 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.
Full explanation below image
Full Explanation
Here's the deal: this is where a demo turns into an operation. The design has to survive real users, real failures, and real audits. 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. Increase log levels temporarily and narrowly when deeper diagnostic detail is needed. That aligns with the Domain 6: Troubleshooting 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 log levels requirement described in the scenario. - 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 sounds related, but it does not solve the log levels 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 'Increase log levels temporarily and narrowly when deeper diagnostic detail is needed.'. The incorrect options — 'Run debug logging forever in production', 'Enable all logs globally without a reason', 'Reduce log detail during active troubleshooting' — 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 6: Troubleshooting domain of the IBM Instana Observability certification.