Which role is not part of ServiceNow GRC?

Which role is not part of ServiceNow GRC?

• A. Risk User
• B. Risk Developer
• C. Risk Manager
• D. Risk Reader

Answer: (B)

In ServiceNow GRC, roles are defined around what a user does in governance, risk, and compliance processes—creating and managing risk records, approving actions, viewing dashboards, or configuring the app for risk workflows. The built-in roles align with these operational needs, such as users who handle risks, readers who can only view, and managers who oversee and assign work. There isn’t a standard role for development work named “Risk Developer”; development and configuration tasks are performed by administrators or developers with higher privileges (like admin or app developer roles), not by a dedicated risk development role. So the role that isn’t part of ServiceNow GRC’s default role set is the one intended for development work.

In ServiceNow GRC, roles are defined around what a user does in governance, risk, and compliance processes—creating and managing risk records, approving actions, viewing dashboards, or configuring the app for risk workflows. The built-in roles align with these operational needs, such as users who handle risks, readers who can only view, and managers who oversee and assign work. There isn’t a standard role for development work named “Risk Developer”; development and configuration tasks are performed by administrators or developers with higher privileges (like admin or app developer roles), not by a dedicated risk development role. So the role that isn’t part of ServiceNow GRC’s default role set is the one intended for development work.