Free SCAIP Practice Test Questions and Answers (2026)

Setting up an emergency access role in Saviynt EIC is a comprehensive process that requires configuration at multiple levels. First, a workflow for handling such requests must be defined and selected under Global Configurations. Second, the specific feature must be enabled for users via their SAV Role Configurations, granting them the ability to make emergency requests. Finally, the target enterprise role must be configured at the role level to be available for emergency access, often specifying parameters like the approver and maximum duration. All these steps are necessary for the feature to function correctly.

A. This is only one part of the configuration; without the global workflow and SAV role permissions, the setup is incomplete.

C. This grants users the ability to request, but without a configured role and workflow, the request cannot be processed.

D. This defines the process, but without a role configured for emergency access and users permitted to request it, the workflow is useless.

1. Saviynt EIC Documentation, "Configuring Emergency Access Management," Chapter 4. This chapter details the end-to-end setup process, explicitly mentioning the need to configure (1) a request workflow in Global Configurations, (2) feature access in SAV Roles, and (3) emergency access parameters on the Enterprise Role itself.

To interact with Saviynt EIC's REST APIs, a client application must first authenticate and obtain a bearer token. This is achieved by sending an HTTP POST request to the token generation endpoint (e.g., /api/v1/token). The request body must contain authentication credentials, such as clientid, clientsecret, and granttype. The server validates these credentials and, if successful, returns an access token in the response. This token is then included in the Authorization header for subsequent API calls.

A. PUT is an idempotent method used for updating or replacing a resource at a specific URI, not for generating authentication tokens.

B. GET is used to retrieve data from a specified resource. Sending credentials in a GET request is insecure and not standard practice for token generation.

D. GIVE is not a standard or valid HTTP method. The standard methods are defined by the HTTP protocol specification (RFC 7231).

- Saviynt Enterprise Identity Cloud (EIC) Documentation, "REST APIs for EIC," Section: "Generating the Authorization Token." The documentation specifies that a POST method must be used to send a request to the /api/v1/token endpoint.

- Saviynt Training Courseware, "Module: EIC Platform and Architecture," Topic: "API Integration." The material details the OAuth 2.0 client credentials grant flow, which explicitly uses the HTTP POST method for token acquisition.

The IMPORTUSERJSON configuration is specifically designed to be used with an inline preprocessor during the user import reconciliation process. It allows for the manipulation and transformation of raw data fetched from the source system (like Workday) before it is saved into the Saviynt Identity Repository. This is the correct place to implement logic for combining attributes, such as concatenating firstname and lastname to create a fullname, ensuring the data is normalized upon entry into EIC.

A. USERUPDATEJSON is used for processing near real-time user attribute updates from a source, not for the bulk transformation logic during the initial import reconciliation.

B. MODIFYUSERDATAJSON is not a standard Saviynt JSON configuration name for pre-processing user import data in this context.

D. An option is available and correct. IMPORTUSERJSON directly addresses the requirement described in the scenario.

1. Saviynt Enterprise Identity Cloud (EIC) Documentation, "Connector Guide" for relevant application (e.g., Workday). The section on "Configuring the Connector for Import" details the use of IMPORTUSERJSON for data transformation.

2. Saviynt EIC Documentation, "Administrator Guide", Chapter on Data Integration and Connectors, Section on "Inline Preprocessor" and its JSON configurations.

Saviynt's SMTP configuration is designed for flexibility to integrate with various enterprise email systems. It supports multiple authentication modes. These include Basic (username and password), NTLM for Microsoft Windows network environments, and OAuth 2.0 for modern, token-based authentication with cloud services like Microsoft 365 and Google Workspace. This ensures secure and compatible connectivity for sending email notifications from the platform.

C. None of the above: This is incorrect as Saviynt explicitly supports several standard authentication modes, including Basic, NTLM, and OAuth.

1. Saviynt Enterprise Identity Cloud (EIC) v23.x Documentation, "Admin Guide", Chapter: Global Configurations, Section: Configuring Email Service for Notifications. The guide details the SMTP server settings, where the 'Authentication Type' dropdown menu explicitly lists 'Basic', 'NTLM', and 'OAuth' as selectable options.

Saviynt supports two primary integration modes with ServiceNow. The first, "ServiceNow as a Managed Application," treats ServiceNow as a target system where Saviynt manages user accounts, groups, and roles through provisioning, deprovisioning, and reconciliation tasks. The second, "ServiceNow as a Ticketing System," leverages ServiceNow's ITSM capabilities. In this mode, Saviynt creates, updates, and tracks tickets (e.g., Incidents, Service Requests) in ServiceNow to fulfill access requests or manage other identity-related processes that require manual intervention or adhere to ITIL processes.

B. The integration modes are for core identity and service management functions, not primarily for branding, labels, or analytics.

C. These functions are too specific; the integration modes cover a much broader range of capabilities than just SAV roles or password sync.

D. The two modes are functionally distinct and serve different integration purposes: one for identity lifecycle management and the other for ITSM process integration.

1. Saviynt Enterprise Identity Cloud (EIC) Documentation, "ServiceNow Integration Guide," v23.x, Chapter 1: Introduction, Section: Integration Modes.

2. Saviynt Enterprise Identity Cloud (EIC) Documentation, "ServiceNow Integration Guide," v23.x, Chapter 2: Configuring ServiceNow as a Ticketing System.

3. Saviynt Enterprise Identity Cloud (EIC) Documentation, "Connector Guide: ServiceNow," v23.x, Section: Features Supported (describes provisioning/reconciliation for the managed application mode).

The most effective way to handle data transformation issues within Saviynt EIC is by using rules. An administrator can create a User Update Rule that triggers during the user import process. This rule would contain a Groovy script designed to parse user attributes, such as firstname or lastname, and replace any accent characters with their non-accented ASCII equivalents. This cleanses the data before it is used by other processes, like the email notification service, thereby resolving the generation issues.

A. API: An API is an interface for external systems to interact with Saviynt, not an internal tool for transforming data that is already being processed.

B. Datasets: Datasets are used to store and look up reference data, not to perform transformations on user attributes during an import.

C. Roles: Roles are used to define access permissions and entitlements for users within the application, not to manipulate their data attributes.

1. Saviynt Enterprise Identity Cloud (EIC) v23.x Documentation, "Admin Guide", Chapter: Rule Management, Section: Configuring User Update Rules. This section explains how to use rules to modify user attributes based on custom logic during identity lifecycle events.

To reconcile accounts using the REST connector, two primary JSON configurations are mandatory. The ConnectionJSON is required to establish the foundational connection to the target system, defining parameters like the base URL, authentication method, and credentials. The ImportAccountEntJSON is then required to define the specific API endpoints, parameters, and mappings needed to fetch account and entitlement data from the target system. Together, these two configurations enable the connector to both connect and import the necessary data for reconciliation.

C. ImportUserJSON is used for reconciling user data from an HR source, not for reconciling application accounts and their entitlements.

D. CreateAccountJSON is a provisioning-related configuration used to define the API call for creating new accounts, not for reconciliation (importing existing accounts).

1. Saviynt Enterprise Identity Cloud (EIC) Documentation, "REST Connector Guide v23.x", Section: "Connector Configurations", Subsection: "ConnectionJSON". This section details the mandatory parameters for establishing a connection.

2. Saviynt Enterprise Identity Cloud (EIC) Documentation, "REST Connector Guide v23.x", Section: "Connector Configurations", Subsection: "ImportAccountEntJSON". This section explains its role in fetching account and entitlement data, which is fundamental to reconciliation.

A. This statement accurately defines the primary purpose of role mining, which is to analyze existing user access permissions to identify common patterns. These patterns can then be consolidated into business or technical roles, simplifying access management and governance.

C. Access to specific features within the Saviynt Identity Cloud (EIC) platform, such as Duplicate Identity Management, is controlled by permissions assigned to SAV Roles. An administrator must have the appropriate permissions within their assigned SAV Role to view and manage this functionality.

B. A percentage cut-off of 60% means the mining process will identify and suggest access that is common to 60% or more of the user population, not only access held by 100% of users.

D. The Duplicate Identity Management feature is designed to merge both user attributes and their associated access, including accounts and entitlements, into a single, consolidated identity.

Saviynt Enterprise Identity Cloud (EIC) Documentation, "Role and Entitlement Management Guide," Section: Role Mining, Subsection: Performing Role Mining.

Saviynt Enterprise Identity Cloud (EIC) Documentation, "Administration Guide," Section: Identity and Access Management, Subsection: Duplicate Identity Management.

Saviynt Enterprise Identity Cloud (EIC) Documentation, "Administration Guide," Section: Role-Based Access Control for Saviynt, Subsection: Managing SAV Roles.

Saviynt's security model aggregates permissions from all roles assigned to a user. The resulting access is the union of all granted permissions, following a "least restrictive" or "most privileged" principle. The built-in ROLEADMIN is a superuser role that grants unrestricted view and edit access across the entire platform. Therefore, even if a restrictive "Read Only" role is also assigned, the permissions from ROLEADMIN take precedence, and the user retains full administrative capabilities.

A. User can only view/edit the modules as mapped under Features for ROLECUSTOMREAD: This is incorrect because the expansive permissions of ROLEADMIN are not constrained by a lesser role.

B. User can only view all EIC configurations: This is incorrect because ROLEADMIN provides full edit capabilities, not just view-only access.

C. It depends; the access defined in the SAV Role that was assigned later takes precedence over the other: This is incorrect as role assignment is not sequential; permissions are aggregated cumulatively.

1. Saviynt Enterprise Identity Cloud (EIC) Security Architecture Guide, "Role-Based Access Control (RBAC) Model", Section: Permission Aggregation. The documentation specifies that a user's effective permissions are the sum of all permissions from all assigned roles.

Saviynt allows you to decide whether each entitlement in a disconnected-application request is raised as its own ServiceNow ticket. The global setting Enable Multi Entitlement Request (Admin > Global Configuration > Request) controls the behavior. When the flag is ON the request is split and EIC invokes the ServiceNow connector three times, generating three individual RITMs/incidents. When the flag is OFF, EIC bundles all selected entitlements into a single provisioning task and therefore a single ServiceNow ticket is created.

B – Saviynt does support multiple-entitlement requests; the feature is governed by a configuration flag.

C – Always true only when the flag is enabled; otherwise Saviynt can create just one ticket, so statement is incomplete.

D – Combining into one ticket happens only when the flag is disabled, not unconditionally.

1. Saviynt Enterprise Identity Cloud – ServiceNow Integration Guide v23.4, Section “Enable Multi-Entitlement Request for Disconnected Applications”, p. 37–38.

2. Saviynt Enterprise Identity Cloud Administrator Guide v23.3, “Global Configuration > Request”, para. ‘Enable Multi Entitlement Request’, p. 118.