Observability-Self-Hosted-Fundamentals practice question 5 of 10

A user indicates when a map is created, only entities can be seen and status is not available. In addition, maps are unable to be nested. What is causing this issue?

Full set: 75 questions
Answer options
A: user account doesn't have administrative rights
B: user account doesn't have map editing rights Correct answer
C: user account doesn't have node management rights
D: user account doesn't have view edit rights
Correct Answer:
B. user account doesn't have map editing rights
Explanation

The described symptoms—inability to see entity status and the unavailability of the map nesting feature—are indicative of insufficient permissions for the Orion Maps feature. A user account lacking full "Map Editing Rights" can be restricted to a view-only or a basic creation mode. This prevents the use of advanced editor functions like nesting maps and can also limit the dynamic display of object statuses, as full data polling and rendering are part of the complete editing and management feature set. The combination of both issues points directly to a limitation on the map management functionality itself.

Why Incorrect

A. Administrative rights are not required; a non-admin can have full map permissions. This option is too broad.
C. Node management rights pertain to adding, deleting, or editing nodes, not the functionality of the map editor like nesting.
D. View edit rights relate to customizing web console dashboards and pages, which is a separate permission from managing Orion Maps.

References

SolarWinds Platform Administrator Guide. (2023). Define what users can do with Orion Platform features and modules. SolarWinds Success Center. Retrieved from solarwinds.com. In the section "Account rights for Orion Platform features," the "Orion Maps Management" permission governs the ability to create and edit maps.

Scroll to Top