Key details for this exam, checked against the published exam outline
Each question shows the correct answer and an explanation of why it is right
EIC Admin encounters an error "Connection Name Specified in accountJSON is not found" while running the WSRETRY job. Which JSON needs to be corrected?
The error message'Connection Name Specified in accountJSON is not found'clearly indicates that the issue is related to theaccountJSON configuration, which directly corresponds toImportAccountJSONin Saviynt REST connector terminology. This JSON is responsible for handling account import (reconciliation) operations, including defining the connection name, API endpoints, and parsing logic for retrieving account data.
TheWSRETRY jobis typically used to retry failed web service (REST) operations, especially related to account imports or provisioning failures. Since the error explicitly referencesaccountJSON, it means the system is unable to locate the connection name defined within theImportAccountJSONconfiguration. This usually happens when the connection name is either misspelled, mismatched with the ConnectionJSON configuration, or incorrectly referenced.
Other options are incorrect becauseCreateAccountJSONis used for provisioning (account creation),ImportUserJSONis for identity import, andImportAccountEntJSONis primarily used for entitlement and combined account-entitlement imports.
Therefore, correcting the connection name inImportAccountJSONresolves this issue.
Which of these is NOT a valid campaign type in EIC?
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.
During a User Import, to define the maximum number of records to be processed in each page, specify the value of the MAX_PAGINATION_SIZE parameter. If this value is not defined, what is the default value?
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.
Which of the following EIC modules support configuration of active workflow? (Choose 3 options)
In Saviynt EIC, workflows are a core component used to control approval processes for access requests, provisioning, and other identity lifecycle events. These workflows can be configured at multiple levels depending on the scope and granularity required.
Security System (A)supports workflow configuration to define approval processes at the application level. This allows organizations to enforce consistent approval logic for all endpoints associated with that system.
Endpoint (B)also supports workflow configuration, enabling more granular control where different endpoints within the same security system may require distinct approval processes. This is particularly useful in complex environments with varied access control requirements.
Entitlement Type (D)supports workflows to manage approvals specific to entitlement categories (such as roles, groups, or permissions), ensuring appropriate governance at a finer level.
Global Configuration (C), while important for system-wide settings, is not typically used to directly assign active workflows to access requests. Instead, workflows are selected and applied within modules like Security System, Endpoint, and Entitlement Type.
Thus, the correct modules supporting active workflow configuration areSecurity System, Endpoint, and Entitlement Type.
For which of the following options duplicate identities can be identified in EIC?
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.
60 questions covering all exam domains, starting from $20
Exam domains verified against: Official Saviynt SCAIP exam guide, last checked September 2026.
Cover login and navigation in Saviynt, importing users from HR systems via connected systems, batch processes, CSV files and APIs, and onboarding applications by understanding the data model and relationship between security systems, endpoints and connections. Learn how to import application data including accounts, entitlements, and correlate users to accounts.
Work with the Access Request System module for applications and roles. Set up requestable workflows for applications, configure entitlement types, and manage the full request lifecycle including submissions, tracking, approvals and provisioning of access for both connected and disconnected applications.
Design and implement access policies for joiner, leaver and mover scenarios. Create technical rules for birthright access with defined conditions and actions, and develop user update rules to handle events automatically via user creation, import or scheduled jobs.
Understand coarse-grained and fine-grained SOD analysis and define functions and risks. Implement preventative SOD analysis during access requests, detect violations in existing access, and manage mitigating controls to accept violations while ensuring regulatory compliance.
Execute access review campaigns across different owners including user managers, entitlement owners and role owners. Manage the full campaign lifecycle, conduct certifications, implement post-certification processes, and use risk-based micro certifications and campaign tracking features.
Build reports and dashboards using SQL queries, runtime controls, custom controls and Elasticsearch queries. Understand the components of analytics including consumption, delivery, authoring and deployment, and distinguish between elastic and non-elastic controls for monitoring and governance.
Common questions about the exam itself
