Hello @gsoni
The correct answer is:
Applications downloaded from 3rd party ServiceNow application developers cannot have naming conflicts.
Explanation:
All applications are automatically part of the Global scope
- False: Applications can be in the global scope or their own custom scope. Scoped applications are specifically designed to prevent conflicts with other applications.
Applications downloaded from 3rd party ServiceNow application developers cannot have naming conflicts
- True: Scoped applications ensure that naming conflicts are avoided. Each scoped application has its own namespace, making it unique and preventing conflicts with other applications.
Any developer can edit any application
- False: Developers can only edit applications they have access to, depending on the application scope and permissions configured.
Developers can choose the prefix for a scope
- False: The prefix for a scope is automatically generated by ServiceNow based on the developer instance and cannot be manually chosen by developers.
Hope this helps!
"If you found my answer helpful, please like and mark it as an "accepted solution". It helps future readers to locate the solution easily and supports the community!"
Thank You
Juhi Poddar
