Pass the Saviynt Advanced IGA Professional SCAIP Questions and answers with ExamsMirror

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.

In Saviynt EIC,time-bound accessis a standard feature used to ensure that access granted to users is automatically revoked after a defined duration. This requirement is fulfilled by enabling thetime-bound configuration for roles under Global Configurations > Roles(Option B). Once this setting is enabled, users can request roles with a specified start and end date, and Saviynt automatically deprovisions the access when the validity period expires.

This capability is essential for enforcingleast privilege and compliance requirements, as it eliminates the need for manual revocation and reduces the risk of lingering access. The system leverages scheduled jobs to monitor and remove expired entitlements or roles.

Option A is incorrect because Dynamic Attributes are mainly used for form customization and conditional logic, not for enforcing access expiration. Option C (Emergency Access Role) is designed for temporary elevated access but follows a different configuration pattern and use case. Option D is not a valid standard approach for enabling automatic revocation.

Thus, enablingtime-bound roles in global configurationis the correct and scalable solution.

In Saviynt–ServiceNow integration, the synchronization ofRITM (Request Item) statusbetween Saviynt and ServiceNow is handled through bothmanual and automated mechanisms.

Option B is correct because users or administrators can manuallyclick the Refresh button on the RITM page in ServiceNowto immediately fetch the latest status from Saviynt. This is useful for real-time validation when monitoring request progress.

Option C is also correct as ServiceNow includes aRequest Item History Job, which runs periodically (commonly every minute) to automatically sync and update the RITM status based on the latest state in Saviynt. This ensures near real-time consistency between both systems without manual intervention.

Option A is incorrect because Postman API calls are not a standard or supported operational method for end users to refresh RITM status. Option D is unrelated, as regenerating catalog items does not impact ticket status synchronization.

Thus, the correct answers aremanual refresh and automated job-based synchronization.

In Saviynt EIC, approval assignment for access requests is primarily controlled throughworkflow configurations, which are associated either at theendpoint level or security system level. Therefore, the first step in troubleshooting incorrect approver assignment is to validate whether the correct workflow is attached and properly configured at both levels (Options A and C). Workflows define approval logic such as manager, owner, or custom approvers, and misconfiguration here often leads to incorrect routing.

Option B is also correct becausedelegation settingscan override the intended approver. If a delegate is configured for an approver, the request may be routed to the delegate instead of the original approver, causing confusion if not validated.

Option D is incorrect because in Saviynt, approvers are typicallysystem-driven based on workflow rules, not manually selected by the requester in most standard configurations. The requester does not usually control approver assignment unless explicitly customized, making this option irrelevant for standard troubleshooting.

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.

Saviynt’sRole MiningandDuplicate Identity Management (DIM)features are key components of Identity Analytics and Governance.

Option Ais correct because Role Mining analyzes user access patterns and identifies similarities across users. Based on these similarities, Saviynt suggests logical groupings of entitlements that can be converted into roles, improving role design and governance.

Option Bis also correct. Thepercentage cut-offin Role Mining defines the threshold for common access across users. A higher threshold (e.g., 60% or more) ensures that only frequently shared entitlements are considered. In practice, this drives mining toward highly consistent access patterns, often close to universally assigned (near 100%), ensuring stronger role accuracy.

Option Cis correct because access to DIM functionality is controlled throughSAV Roles. Administrators must explicitly grant permissions to view and manage duplicate identities.

Option Dis incorrect because DIM not only merges identity attributes but can also consolidate associated access (accounts and entitlements), ensuring a unified identity profile.

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

In Saviynt EIC, generating anAuthorization Tokenfor API access is performed using theHTTP POST method. This is aligned with standard REST API authentication practices, where sensitive information such as credentials (username, password, client ID, or client secret) is securely transmitted in the request body rather than in the URL.

Saviynt provides API endpoints (such as/ECM/api/login) that require aPOST requestcontaining authentication details in JSON format. Upon successful authentication, the system returns asession token or authorization token, which is then used in subsequent API calls (typically passed in headers likeAuthorizationortoken).

Option A (PUT) and Option B (GET) are not suitable for authentication token generation. GET exposes parameters in the URL and is not secure for credential transmission, while PUT is typically used for updating resources. Option D (GIVE) is not a valid HTTP method.

Therefore, POST is the correct and secure method used in Saviynt APIs forauthentication and token generation, ensuring compliance with RESTful and security best practices.

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.