SCAIP Saviynt Certified Advanced IGA Professional (Level 200) Questions and Answers

In Saviynt EIC REST connector configuration, account reconciliation (also known as account import or aggregation) requires specific mandatory JSON parameters that define how the system connects to the target application and retrieves account data. The two essential parameters areConnectionJSONandImportAccountEntJSON.

ConnectionJSON (Option A)is mandatory because it contains the core connection details such as base URL, authentication mechanism (OAuth, Basic, etc.), headers, and endpoint configurations. Without this, Saviynt cannot establish communication with the target REST application.

ImportAccountEntJSON (Option B)is also required because it defines the API call used to fetch account (entitlement/account) data from the target system. It includes endpoint URLs, response parsing logic, pagination handling, and mapping rules needed to bring account data into Saviynt.

OptionC (ImportUserJSON)is typically used for identity/user import, not for account reconciliation in REST connectors. OptionD (CreateAccountJSON)is used during provisioning (account creation), not during reconciliation.

Therefore, for account reconciliation using REST connector, the mandatory configurations are ConnectionJSON and ImportAccountEntJSON, as per Saviynt IGA Level 200 connector guidelines.

In Saviynt EIC,job orchestration and sequencingare critical for automating identity lifecycle processes such as user import followed by provisioning. To ensure that provisioning starts immediately after user import completes, Saviynt provides the concept of aTrigger Chain Job.

ATrigger Chain Job (Option B)allows administrators to define a sequence of jobs where one job is automatically triggered upon the successful completion of another. In this scenario, once theUser Import Jobfinishes, the system can automatically trigger theProvisioning Job, ensuring seamless and immediate execution without manual intervention or time delays.

Option A (Multi-threading job) relates to performance optimization, not sequencing. Option C (Single Threaded Job) defines execution style but does not control job dependency. Option D (WSRetry job) is used for retrying failed web service calls, not for chaining processes.

Thus,Trigger Chain Jobis the correct approach for automating dependent job execution and is widely used in Saviynt for efficient workflow orchestration.

The correct answer is B. REST Connector . Saviynt documentation explains that REST integration is intended for applications whose data and lifecycle actions are available through REST endpoints. It states that the REST integration enables organizations to gain visibility, manage the user lifecycle, and govern access for data available in the REST application or REST endpoint. That directly matches the question, which requires imports plus provisioning and deprovisioning for an API-driven target system.

Saviynt’s REST connector documentation also notes that provisioning and deprovisioning are supported when the connection is configured correctly. This makes the REST connector the standard choice when the target system does not use an out-of-the-box native connector but does provide usable REST APIs. The other options do not fit the requirement. Active Directory Connector is specific to AD use cases, SMTP Configuration is only for email delivery, and Dataset Configuration is an administrative data-structuring feature rather than an application integration method. In Saviynt Level 200 terms, when an application is API-first and lifecycle actions must be automated, the REST connector is the appropriate design decision.

In Saviynt EIC,Role Intelligenceis a key component of Identity Governance that focuses on analyzing, optimizing, and managing roles effectively. It provides multiple features that help organizations improve role design and maintain compliance.

Role Governance (A)is a core feature that ensures roles are properly defined, reviewed, and certified. It helps maintain accountability and ensures that roles align with business policies.

Entitlement Discovery (B)enables identification and analysis of entitlements across applications, helping administrators understand what access exists and how it can be grouped into meaningful roles. This is essential for building accurate and efficient role models.

Role Mining (C)is one of the most important capabilities, allowing organizations to analyze user access patterns and automatically suggest roles based on common entitlement combinations. This improves role engineering and reduces manual effort.

Option D (Role-Access Mismatches) is not considered a standard feature under Role Intelligence; it is more aligned with analytics or audit findings rather than a core Role Intelligence function.

Therefore, the correct answers areA, B, and C, which represent the foundational features of Role Intelligence in Saviynt.

In Saviynt EIC, mass unintended changes—such as all accounts being disabled due to incorrect target application configuration—can be prevented usingthreshold-based controls. These controls are defined using theSTATUS_THRESHOLD_CONFIGconnection parameter, which acts as a safeguard during reconciliation and provisioning processes.

The correct attribute in this scenario isaccountThresholdValue (Option D). This parameter allows administrators to define a threshold limit for account status changes (such as disablement). If the number or percentage of accounts being disabled exceeds the defined threshold, Saviynt can stop or flag the operation, preventing large-scale unintended impact.

OptionA (accEntThresholdValue)is used for entitlement-level thresholds, not account status changes. OptionBis incorrect because Saviynt does provide this safeguard mechanism. OptionCis also incorrect since such controls are not managed externally but are part of Saviynt’s connector configuration.

By usingaccountThresholdValuewithin STATUS_THRESHOLD_CONFIG, organizations can implement strong governance and prevent bulk account disablement due to misconfigurations or data issues during account import or reconciliation.

In Saviynt EIC, retrieving reports such as users and their assigned SAV roles can be achieved through multiple analytics and reporting mechanisms. The correct approaches areOptions A, B, and C, all of which leverage SQL-based analytics capabilities.

Option Ais correct because Saviynt allows administrators to create analytics using SQL queries and schedule them. The“Send Email As Attachment”feature enables automated report delivery, making it useful for periodic reporting and compliance requirements.

Option Bis also valid, as analytics results can be exported directly into formats like CSV or Excel, allowing further analysis or sharing outside the platform.

Option Cis correct because theData Analyzertool enables administrators to run SQL queries directly on the Saviynt database to retrieve real-time data for reporting and troubleshooting purposes.

Option D (Using enhanced query)is not considered a standard or distinct reporting mechanism in Saviynt for this use case.

Together, these methods provide flexible reporting options, supporting both real-time access and scheduled report distribution within Saviynt.

In Saviynt EIC, password management includes configurable notification mechanisms to securely communicate password changes or resets to users. When aHelpdesk performs a password reset, the appropriate configuration to notify the user is through theReset Password notification under Password Policy.

Option C is correct because Saviynt provides a dedicatedReset Password notification templatewithin password policy configurations. This ensures that whenever a password is reset (either by user self-service or by Helpdesk), the system triggers the configured email template to notify the user. This template can include secure messaging and instructions related to the new password or next steps.

Option A is incorrect because the system does not automatically share passwords without proper configuration. Option B applies tochange password scenarios initiated by users, not Helpdesk resets. Option D is not recommended, as User Update Rules are not designed specifically for password notification workflows.

Thus, configuring theReset Password notification under password policyis the correct and secure approach.

In Saviynt EIC, workflows are internally represented inXML format, which defines the sequence of approval steps, conditions, and actions. The“Show XML”option is specifically designed to allow administrators toview the underlying XML structure of a workflow. However, this view is provided in aread-only mode, meaning administrators can inspect the configuration but cannot directly modify it from this option.

This feature is particularly useful fordebugging, auditing, and understanding workflow logic, especially in complex approval processes involving multiple steps and conditions. It helps administrators verify how a workflow is constructed without risking accidental changes to the configuration.

Option C is incorrect because editing workflow XML is not typically done directly through the “Show XML” view in Saviynt UI; modifications are handled through workflow configuration screens or controlled import/export processes. Option A is unrelated since Saviynt workflows are XML-based, not JSON-based. Option B is also incorrect because version history is managed separately and not through the Show XML option.

Thus, the correct purpose of “Show XML” is toview workflow configuration safely in read-only format.

In Saviynt EIC, password management is highly configurable, allowing organizations to defineseparate password policies for different account types, including service accounts and regular user accounts. This requirement is achieved by creating a dedicated password policy specifically for service accounts and associating it appropriately within the system.

Option A is correct because Saviynt allows administrators to define aseparate Password Policy for Service Accountsand map it using thePolicy Rule Service Account field under the Security System configuration. This ensures that when service account operations such as password resets or provisioning occur, the system enforces the correct policy distinct from regular user accounts.

Option B is incorrect since Saviynt supports multiple password policies and does not restrict to a single policy. Option C is incorrect because simply selecting a checkbox in password policy configuration does not link it to service account usage. Option D is incorrect as Global Configurations do not directly assign password policies for service accounts at the execution level.

Thus, configuring and mapping the policy at theSecurity System levelensures correct enforcement for service accounts.

In Saviynt REST connector configurations, data transformation and manipulation during import (reconciliation) are handled using special keywords or placeholders within JSON mappings. Among the given options,#VALUE#is the correct parameter used to manipulate and transform incoming data from the target application.

The#VALUE#keyword represents the actual value retrieved from the API response and allows administrators to apply transformations such as concatenation, conditional logic, or formatting before storing the data in Saviynt. It is commonly used within accountParams or entitlementParams mappings to ensure that incoming data aligns with Saviynt schema requirements.

OptionA (#nextApiKeyField#)is used for pagination handling in REST APIs, helping to fetch subsequent pages of data, not for manipulation. OptionC (#CHAR#)is not a valid or commonly used parameter in Saviynt REST connectors. OptionD (#CONST#)is used to assign constant/static values but does not manipulate incoming API data dynamically.

Therefore,#VALUE#is the correct parameter used for data manipulation during import in REST connector configurations.

In Saviynt EIC, identity data transformation and normalization during ingestion from authoritative sources like Workday are handled at theimport stage, specifically usingIMPORTUSERJSON. This JSON configuration governs how user data is fetched, parsed, and mapped into the Saviynt Identity Repository.

To meet the requirement of combining first name and last name into a full name and ensuring near real-time reflection of updates, aninline preprocessor within IMPORTUSERJSONis used. This allows administrators to apply transformation logic—such as concatenation, formatting, or conditional mapping—directly during the import process before the data is persisted in Saviynt.

OptionA (USERUPDATEJSON)andB (MODIFYUSERDATAJSON)are used for post-import updates or provisioning-related user modifications, not for initial transformation during ingestion. These do not meet the requirement of transforming data before it is stored in the Identity Repository.

OptionDis incorrect because Saviynt explicitly supports inline preprocessors in IMPORTUSERJSON for such use cases.

Thus, configuring an inline preprocessor inIMPORTUSERJSONis the correct and recommended approach for identity data normalization during import.

In Saviynt–ServiceNow integration using theSaviynt App for ServiceNow, therequest fulfillment location is flexible and depends on how the integration is configured. This is why Option C is correct.

Saviynt supports different integration patterns with ServiceNow. In one model,ServiceNow acts as the front-end request system, while Saviynt handles the fulfillment (provisioning, approvals, and access governance). In another model, ServiceNow can handle certain fulfillment steps depending on how workflows, APIs, and ticketing configurations are defined.

For example, if the integration is configured such that ServiceNow creates a request and passes it to Saviynt, thenSaviynt performs fulfillment. Alternatively, if certain fulfillment logic or orchestration is handled within ServiceNow workflows or ITSM processes, thenServiceNow may drive parts of the fulfillment process.

This flexibility allows organizations to align the integration with their operational model, whether centralized in Saviynt or distributed with ServiceNow. Therefore, fulfillment is not restricted to a single system and is determined byconfiguration and architectural design choices.

In Saviynt EIC,Technical Rulesare essential for automating provisioning, deprovisioning, and enforcing access policies. Following best practices ensures reliability, performance, and governance compliance. Hence,Option D (All of the above)is correct.

Using Advanced Configurations (Option A)allows administrators to implement complex logic, optimize rule execution, and handle sophisticated use cases such as conditional provisioning or attribute-based decisions.

Configuring Retrofit for all rules (Option B)is a recommended practice because it ensures that rules are applied not only to new users but also to existing users. This maintains consistency across the identity repository and prevents access gaps for legacy users.

Including a condition like user.statuskey = 1 (Option C)ensures that rules are applied only to active users. This avoids unnecessary processing for inactive or terminated users and prevents unintended provisioning actions.

Together, these practices improve rule efficiency, reduce errors, and ensure consistent enforcement of identity governance policies across the organization.

In Saviynt–ServiceNow integration, user visibility in request forms depends on properidentity correlation between ServiceNow users and Saviynt identities. The most common reason a valid ServiceNow (SNOW) user does not appear in the request form is that theSNOW user record is not linked or mapped to an imported Saviynt user(Option B).

Saviynt relies on its internal identity repository to populate requestable users. Even if a user exists in ServiceNow, they must also exist in Saviynt and be properly correlated (typically via attributes like username, email, or employee ID). Without this linkage, Saviynt cannot recognize the user during request submission, and therefore the user will not appear in the search results.

Option A is incorrect because even if the user already has access, they would still appear in search results (though requests may be restricted). Option C is unrelated to user visibility. Option D is incorrect because lack of an account does not prevent user selection—it only affects provisioning outcomes.

Thus, properuser correlation between SNOW and Saviyntis essential for request visibility.

Saviynt EIC provides multiple flexible integration options with ServiceNow to support different business and operational use cases. Therefore,Option D (All of the above)is correct.

ServiceNow as a Managed Application (Option A)allows Saviynt to treat ServiceNow like any other application, enabling account provisioning, deprovisioning, and access governance directly within ServiceNow using REST connectors.

ServiceNow as a Request Form (Option B)enables organizations to leverage ServiceNow’s front-end portal for access requests. Users can initiate requests in ServiceNow, which are then processed and fulfilled by Saviynt, ensuring seamless user experience while maintaining governance.

ServiceNow as a Ticketing System (ITSM) (Option C)is another key integration pattern where Saviynt generates tickets (incidents, requests, or tasks) in ServiceNow for approval workflows, provisioning actions, or tracking purposes. This ensures alignment with enterprise ITSM processes.

These multiple integration models provide flexibility, allowing organizations to choose the approach that best fits their operational and governance requirements.