Question 1060
The production review includes this finding: A deployment fails after two app-local configuration files both set the same key and the incident report states that all apps have equal precedence. What principle should guide the diagnosis?
Explanation
Correct Answer
App-directory ordering can break ties and differs between global and app/user contexts. The actionable correction is check the official app-order and context-specific precedence rules before resolving the collision. Evidence of correct operation is the chosen effective value is consistent with a documented context-specific precedence trace.
Incorrect Answers
The option would apply to “A user-level saved search behaves differently from the same saved search in the shared app”. User and current-app settings can outrank system settings for search-time knowledge objects. This question instead requires “App-directory ordering can break ties and differs between global and app/user contexts”.
This principle explains a different operational condition: A universal forwarder receives an inputs.conf value in system/local that conflicts with an app/default value. For the current issue, app-directory ordering can break ties and differs between global and app/user contexts. The corresponding action is Check the official app-order and context-specific precedence rules before resolving the collision.
The alternative is associated with two installed apps each define an indexing setting and the team cannot explain which attribute survives. That does not explain the reported behavior; the applicable mechanism is App-directory ordering can break ties and differs between global and app/user contexts.