What is not true about delegated development in ServiceNow?

What is not true about delegated development in ServiceNow?

• A. Administrators can grant non-admin users the ability to develop global applications.
• B. Delegated development enables non-admin users to work on applications within restricted scopes.
• C. It helps distribute development tasks while limiting admin access.
• D. It is designed to improve governance over who can create apps.

Answer: (A)

Delegated development lets admins grant non-admin users the ability to build and customize apps, but only within defined app scopes. In ServiceNow, applications are organized into scopes to keep code and data isolated; global applications live in the global scope and usually require higher privileges. So allowing non-admins to develop in the global scope isn’t part of delegated development. The whole idea is to distribute work while keeping admin access limited and governance strong, by letting users work on specific, restricted-scoped apps. For instance, a non-admin might be enabled to work on a particular scoped HR app, without gaining the ability to affect other apps or the global environment.

Delegated development lets admins grant non-admin users the ability to build and customize apps, but only within defined app scopes. In ServiceNow, applications are organized into scopes to keep code and data isolated; global applications live in the global scope and usually require higher privileges. So allowing non-admins to develop in the global scope isn’t part of delegated development. The whole idea is to distribute work while keeping admin access limited and governance strong, by letting users work on specific, restricted-scoped apps. For instance, a non-admin might be enabled to work on a particular scoped HR app, without gaining the ability to affect other apps or the global environment.