A team is preparing a production rollout and needs to avoid a design mistake. What is the best way to handle golden signals while staying aligned with the certification objectives?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Here's the deal: think of golden signals like labeling the cables before you close the rack door. If you skip that discipline, troubleshooting gets ugly fast. In this scenario, answer A 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: think of golden signals like labeling the cables before you close the rack door. If you skip that discipline, troubleshooting gets ugly fast. In this scenario, answer A 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 A. Monitor latency, traffic, errors, and saturation to understand service health. That aligns with the Domain 1: Operations 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 B is incorrect because it narrows the solution to one artifact or metric and misses the broader golden signals requirement. - Option C is incorrect because it sounds related, but it does not solve the golden signals requirement described in the scenario. - Option D is incorrect because it sounds related, but it does not solve the golden signals 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 'Monitor latency, traffic, errors, and saturation to understand service health.'. The incorrect options — 'Monitor only server hostnames', 'Use deployment dates as the primary health metric', 'Track color themes in dashboards' — 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 1: Operations domain of the IBM Instana Observability certification.