Saviynt Certified Advanced IGA Professional (Level 200) SCAIP Exam Questions

Answer : A

The correct answer is A. Saviynt documentation describes two major ServiceNow integration models: ServiceNow as a Managed Application and ServiceNow as a Ticketing System. The managed application model is used for application-style integration, including reconciliation or import and provisioning or deprovisioning activities. The ticketing system model is used when ServiceNow functions as the ITSM workflow and ticket platform connected to Saviynt request processing. This distinction is repeatedly emphasized in the ServiceNow integration overview documentation.

Saviynt further notes that integration with ServiceNow is required to perform reconciliation, provisioning, and deprovisioning tasks, and separately documents ServiceNow as a ticketing system for request-related use cases. That means the two modes are complementary but not identical. Option D is therefore wrong because the modes serve different architectural purposes. Options B and C are incorrect because branding, analytics-only usage, SAV-role-only usage, and password-sync-only behavior do not describe the documented ServiceNow integration patterns. For Level 200 exam preparation, this is a high-value distinction: choose Managed Application when ServiceNow is the governed target system, and Ticketing System when ServiceNow is the ITSM workflow engine around Saviynt processes

Answer : A, D

In Saviynt EIC, theservice account name generationis controlled through configuration-driven mechanisms to ensure consistency, automation, and compliance with naming standards.

Option A is correct because administrators can define naming conventions at theEndpoint level using the Service Account Name Rule. This allows dynamic generation of account names based on attributes such as application name, environment, or other identifiers, ensuring standardized naming across systems.

Option D is also correct since in many connector-based integrations, theCreate Account JSONconfiguration plays a role in provisioning. The account name can be derived or constructed within this JSON payload based on defined mappings and logic, especially for REST or custom connectors.

Option B is incorrect because service account creation in Saviynt is typically controlled and standardized; manual entry of account names is generally restricted or governed to avoid inconsistencies. Option C is incorrect because Global Configurations do not directly define service account naming rules in standard implementations.

Thus, the correct answers areEndpoint-based naming rules and Connection-level JSON configuration, ensuring automated and consistent service account naming.

Answer : B

In Saviynt EIC, the correct configuration for controlling which roles appear in the Access Request screen is theRequest Roles Query / Role Request QueryunderGlobal Configuration. Saviynt's official documentation forConfiguring Role Requestsstates that this setting is used tospecify a query to control the display of roles in Access Request, meaning only roles returned by that query are shown to the requester. That is exactly the use case in this question: filtering the visible role list by a user attribute such as country or location. A query can be written so that users from Country A see only the roles mapped for Country A.

The other options are not correct in this context.SAV Rolecontrols administrative UI permissions in Saviynt, not end-user role catalog filtering.Role Configuration -> User Queryis not the standard setting used to drive request-time role visibility for this scenario. Option D is incorrect because Saviynt explicitly supports this use case through the Request Roles Query capability.

Answer : A

In Saviynt EIC,Dynamic Attributesare often used in request forms to capture additional information, and some of these attributes may be configured ashidden fieldsfor backend processing. By default, hidden dynamic attributes are not exposed in workflows, which can prevent administrators from accessing their values during request processing.

To resolve this issue, Saviynt provides a specific configuration inGlobal Configurationscalled''Expose hidden dynamic attributes in workflow''. Enabling this setting (Option A) ensures that even if the dynamic attributes are hidden in the UI, their values are still accessible within workflows for processing, approvals, and provisioning logic.

Option B is incorrect because this setting is not configured at the endpoint level. Option C relates to saving default values but does not ensure visibility in workflows. Option D is unrelated to hidden attribute exposure.

Thus, enabling theGlobal Config setting to expose hidden dynamic attributesis the correct solution to ensure their values are available within workflow execution.

Answer : B

The correct answer is B. Technical Rule. Saviynt documentation clearly states that a Technical Rule is primarily used to provision birthright access, also referred to as zero-day provisioning, to users joining the organization based on specified conditions. This is one of the most important distinctions in the Rules and Policies section of the Level 200 syllabus. Technical Rules are intended for automated access assignment logic, especially where access must be granted immediately when user attributes match business conditions such as department, location, or cost center.

The other options are not correct for this use case. User Update Rules are generally used to take actions when user records change and can support lifecycle events, but the documentation identifies Technical Rules as the primary mechanism for birthright provisioning. Scan Rules are used for detection and policy-based scanning use cases, not default access assignment. SAV Role controls platform authorization inside Saviynt rather than provisioning target application access. Saviynt also documents that entitlement assignments in a Birthright Rule can be parameterized using user attributes, which reinforces that Technical Rules are the intended framework for this type of zero-day access automation.

Answer : B

In Saviynt EIC,Service Account Managementincludes mechanisms to ensure continuity of ownership when an account owner leaves the organization. When a user is terminated, the system automatically determines the new owner based on a predefined configuration.

The correct approach is through theuser attribute ''Owner On Terminate''(Option B). This attribute is maintained at the user level and specifies who should inherit ownership of service accounts if the current owner is terminated. During the termination process, Saviynt checks this attribute and transfers ownership accordingly, ensuring there is no orphaned service account and maintaining accountability.

Option A is incorrect because SQL queries in Global Configuration are not typically used for ownership reassignment in this context. Option C (Manage Owners Page) is used for manual updates, not automatic reassignment upon termination. Option D is incorrect because the ownership transfer logic is driven by theuser attribute, not a service account attribute.

Thus, using the''Owner On Terminate'' user attributeensures automated, policy-driven ownership transitions in Saviynt.

Answer : A, B, C

In Saviynt EIC, retrieving reports such as users and their assigned SAV roles can be achieved through multipleanalytics and reporting mechanisms.

Option A is correct because administrators can createAnalytics using SQL queriesand configure them tosend results via email as attachments, which is useful for scheduled reporting and automated distribution.

Option B is also valid since Analytics allows administrators toexport query results into CSV or Excel formats, enabling offline analysis, auditing, and sharing with stakeholders.

Option C is correct becauseData Analyzerprovides a direct interface to execute SQL queries on the Saviynt database, allowing administrators to quickly retrieve required data without creating a formal analytics job.

Option D (Using enhanced query) is not a standard or recognized reporting method within Saviynt for this use case. While advanced queries can be written, ''enhanced query'' is not a defined feature or module for report extraction.

Thus, the correct answers areA, B, and C, which represent the primary supported methods for reporting in Saviynt.