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.

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 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 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.

In Saviynt EIC, theSOD (Segregation of Duties) Risk Evaluation Jobis used to identify conflicts in user access that violate defined SOD policies. To efficiently analyze and review these violations, Saviynt provides several filtering options.

Users (A)is a valid filter that allows administrators to view SOD violations specific to individual users or a group of users. This is helpful for targeted investigations or audits.

Security System (B)is also a valid filter, enabling administrators to narrow down violations based on specific applications or systems. This is useful when analyzing risks within a particular application landscape.

Ruleset (C)is another important filter, as SOD violations are evaluated based on predefined rule sets. Administrators can filter results based on specific rulesets to understand which policies are being violated.

Option D (User Account Evaluation) is not a standard filter in the SOD Risk Evaluation Job. It is more related to job execution scope rather than filtering results.

Thus, the correct answers areUsers, Security System, and Ruleset, which are the primary filters for analyzing SOD violations.

Saviynt EIC provides multiple standardized approaches for integrating applications, primarily focusing onconnector-based integrationandapplication onboarding via the Design module. OptionA (Classic integration using connectors)is correct because Saviynt supports a wide range of out-of-the-box connectors such as Active Directory, REST, JDBC, SAP, etc. These connectors enable provisioning, deprovisioning, and account aggregation, forming the foundation of application integration in Saviynt.

OptionB (Application Onboarding using Design module)is also correct and represents a modern and structured way of onboarding applications. The Design module simplifies integration by allowing administrators to configure applications, schemas, and connections using a guided UI-driven approach. It ensures consistency, faster onboarding, and better governance alignment.

OptionC (Using Connector framework)is incorrect because it is not considered a separate integration method from an administrator’s perspective; rather, it is the underlying technical architecture that supports connectors. OptionD (Upload Connection file)is also incorrect, as Saviynt does not define application integration as a file-upload-driven process in its standard onboarding methodology.

Thus, the two valid integration methods aligned with Saviynt IGA Level 200 documentation are connector-based integration and Design module onboarding.

In Saviynt REST connector configuration,acctEntMappingsis used to define how account-entitlement relationships are extracted and mapped from the target system response. This configuration is critical when importing entitlements associated with accounts, such as groups, roles, or permissions.

The required parameters for configuring acctEntMappings includelistPath, idPath, and keyField.listPath (Option A)specifies the JSON path where the entitlement list is located within the API response. This allows Saviynt to identify the array or collection containing entitlement data.idPath (Option B)defines the unique identifier for each entitlement within that list, ensuring proper tracking and mapping.keyField (Option C)is used to associate the entitlement back to the account, effectively linking account and entitlement records.

OptionD (accountID)is not a valid parameter within acctEntMappings configuration. While account identifiers are important in overall mapping, acctEntMappings specifically uses keyField instead of accountID to establish relationships.

Thus, the correct parameters required for acctEntMappings are listPath, idPath, and keyField, as per Saviynt REST connector configuration standards.