Free Practice Questions for Saviynt SCAIP Exam

In Saviynt EIC’sDuplicate Identity Management (DIM), Global Configurations provide filtering mechanisms to identify potential duplicate identities efficiently. The two primary matching strategies used areCoarse MatchingandFine Matching, which together form the backbone of duplicate detection logic.

Coarse Matching (A)is used as an initial filtering mechanism. It applies broader criteria such as matching on common attributes like first name, last name, or email domain to quickly identify a pool of potential duplicate identities. This helps in reducing the dataset size before applying more detailed checks.

Fine Matching (C)is a more refined and precise comparison that evaluates stricter conditions such as exact matches on email ID, employee ID, or other unique identifiers. This step ensures higher accuracy in identifying true duplicates from the coarse match results.

Option B (Identity Matching) is not a standard configurable filter in DIM Global Configuration, and Option D (Merger Query) relates to post-identification actions rather than filtering criteria.

Thus, the correct answers areCoarse Matching and Fine Matching, which together enable effective duplicate identity detection.

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.

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.

In Saviynt EIC, handling special characters such as accents in user attributes (e.g., names used for email generation) is typically addressed usingRules, specificallyUser Update Rules or Technical Rules. Therefore,Option D (Rules)is the correct answer.

Rules allow administrators to apply transformation logic to user attributes during identity processing. For example, accent characters can be normalized or replaced (e.g., converting “é” to “e”) before generating email addresses. This ensures that generated emails conform to system or organizational standards and avoid issues with downstream systems that may not support special characters.

Datasets (Option B)are primarily used for data retrieval and reporting, not transformation.Roles (Option C)are related to access control and do not influence attribute formatting.API (Option A)could theoretically be used externally, but it is not the standard or recommended approach within Saviynt for solving this problem.

Thus, Rules provide the most effective and native way to sanitize and standardize user data, ensuring consistent and valid email generation.

The correct answers are A, B, and C . Saviynt documentation for Active Directory group management states that the connector can be used to create, update, and delete AD or ADSI groups. It also supports related group-management functions such as updating group attributes and maintaining group membership and owners. This confirms that Saviynt group management is not limited to visibility or request tracking; it supports the full operational lifecycle for AD groups when configured correctly.

Saviynt’s administrative documentation further explains that group management must be configured to enable users to create and manage groups in Saviynt Identity Cloud. That broader wording aligns with the specific lifecycle operations of create, update, and delete. Option D is incorrect because campaign launching is part of certification governance, not the core capability set of AD group management itself. A campaign may later review group-related access, but group management is fundamentally about administering the group object and its membership lifecycle. For Level 200 preparation, this distinction matters: group management handles the lifecycle of the group object, while campaigns handle review and attestation of access associated with identities, roles, or entitlements.

In Saviynt EIC,Duplicate Identity Management (DIM)supports multiple mechanisms to detect duplicate identities across the identity lifecycle, makingOption D (All of the above)the correct answer.

Firstly, duplicate identities can be detectedduring user import (Option A)when data is ingested from authoritative sources like HR systems. Saviynt can apply matching rules and prevent or flag duplicates at the ingestion stage. Secondly, duplicates can be identified by executing theDuplicate Identity Detection Job (Option B), which is a detective control that scans existing identities in the repository and identifies potential duplicates based on configured correlation rules such as email, username, or employee ID.

Additionally, duplicates may also be identifiedduring manual updates in the Identity Repository (Option C)when administrators modify user attributes. If updated values match existing identities based on defined criteria, Saviynt can flag potential duplicates.

These multiple detection points ensure both proactive and reactive duplicate management, helping maintain identity data accuracy and preventing access risks associated with duplicate identities.

In Saviynt EIC REST connector configuration,ImportAccountEntJSONis used to define how account and entitlement data are imported (reconciled) from a target system. This JSON structure includes several predefined and supported parameters that control how accounts, entitlements, and their ownership relationships are processed.

accountParams (Option C)is a valid parameter and is used to map account-level attributes such as account name, status, and identifiers.entitlementParams (Option B)is also valid and defines how entitlement data (groups, roles, permissions) are fetched and mapped.accountOwnerParams (Option A)is another valid parameter used to define account ownership mapping, helping assign owners to accounts during reconciliation.

However,entOwnerParams (Option D)is NOT a valid parameter in the ImportAccountEntJSON structure. The correct naming convention for entitlement ownership (if applicable) does not use "entOwnerParams" in Saviynt REST connector configuration. Saviynt follows strict parameter naming standards, and incorrect parameter names will not be recognized or processed by the connector.

Thus, Option D is the correct answer, as it represents an invalid configuration parameter in the context of ImportAccountEntJSON.

In Saviynt EIC,Campaigns (Certifications)are used to review and validate user access, ensuring compliance and governance. Saviynt provides several predefined campaign types based on different ownership and responsibility models.

User Manager Campaign (A)is a valid campaign type where managers review and certify access of their direct reports. This is one of the most commonly used certification types.

SAV Role Campaign (B)is also valid and focuses on reviewing access related to SAV roles, allowing role owners or administrators to validate role assignments.

Organization Owner Campaign (D)is another valid campaign type, typically used when organizational hierarchy or ownership structures are leveraged for certification responsibilities.

Option C (Application Owner Meta Data Campaign) isnot a valid standard campaign typein Saviynt. While application owner-based campaigns do exist (e.g., Entitlement Owner or Application Owner campaigns), “Meta Data Campaign” is not a recognized or supported campaign category in Saviynt EIC.

Thus, the correct answer isC, as it does not correspond to any valid campaign type in Saviynt.

In Saviynt EIC REST connector configurations, pagination is a critical mechanism used duringuser import (identity reconciliation)to efficiently process large datasets from target systems. The parameterMAX_PAGINATION_SIZEdetermines how many records are fetched and processed per API call (per page).

IfMAX_PAGINATION_SIZEis not explicitly defined, Saviynt uses adefault value of 1000 records per page. This default is designed to balance performance and system stability. Fetching too many records in a single API call can lead to performance bottlenecks, API timeouts, or memory issues, while too few records can increase the number of API calls and slow down the overall import process.

OptionA (50000)andC (10000)are incorrect because these values are typically too large for default settings and must be explicitly configured if required. OptionBis incorrect because Saviynt does provide a default fallback value rather than leaving it undefined.

Therefore, when MAX_PAGINATION_SIZE is not specified, Saviynt defaults to1000, ensuring efficient and stable data import operations.