Legit CAD Exam Download

See list of triggers on right hand side of this webpage:

The trigger types in Flow Designer are Application, Record, Schedule, and Topic. Outbound Email is not a trigger type, but an action type that can be used in a flow to send an email message1. References: Flow Designer Trigger Types

The correct statement regarding Application Scope is that applications downloaded from 3rd party ServiceNow application developers cannot have naming conflicts. Application Scope is a feature that identifies and isolates applications and their related artifacts from other applications. Each scoped application has a unique namespace identifier that consists of a prefix and a scope name. This prevents cross-application name collisions and ensures that only authorized scripts can access or modify data in a scoped application. References: [Product Documentation | ServiceNow], [How To Create a Scoped App in ServiceNow - YouTube]

The following roles grant access to source control repository operations such as importing applications from source control, or linking an application to source control:

source_control. This is a role that allows users to perform basic source control operations, such as importing an application from a source control repository, updating an application from a source control repository, or committing changes to a source control repository.

admin. This is a role that grants full access to all the features and functions of the ServiceNow platform, including source control operations. Users with this role can also perform advanced source control operations, such as creating or deleting source control repositories, configuring source control properties, or resolving conflicts.

The following roles do not grant access to source control repository operations:

source_control_admin. This is not a valid role in ServiceNow. There is no separate role for source control administration, as this function is included in the admin role.

git_admin. This is not a valid role in ServiceNow. Git is a specific type of source control system that ServiceNow supports, but there is no role dedicated to Git administration. References: Source Control, Source Control Roles

Restricted caller access is enabled through a platform capability delivered as a plugin. The direct method to activate it is to activate the Scoped Application Restricted Caller Access plugin, which turns on the restricted caller access behavior and supporting controls for cross-scope interactions. Additionally, certain ServiceNow applications, such as HR Service Delivery or Security Incident Response, may require this capability and, when requested/installed, can drive activation of the necessary supporting features as part of meeting that application’s security model. That aligns to option B as an activation path tied to obtaining the applications that depend on the feature. Option A is not an activation method, it is a blanket security stance that does not represent how the feature is turned on in the platform. Option D is different functionality: Cross-Scope Access Override is a specific override mechanism for cross-scope calls and does not itself activate restricted caller access. The verified activation methods are the plugin activation and obtaining the applications that require it.