Saviynt SCAIP Exam Questions

In Saviynt EIC, schema-based account import jobs rely heavily on theSAV file, which acts as the schema definition for interpreting incoming data. The error message''Schema definition file not found and No SAV file found''specifically indicates that Saviynt is unable to locate or process the required SAV file.

Option Ais correct because the SAV file must be placed in the designatedFile Directory SAV files location. If the file is missing from this directory, the system cannot read the schema definition, resulting in job failure.

Option Dis also correct because even if the SAV file is present, anincorrectly formatted or corrupted SAV filewill prevent Saviynt from parsing it properly, leading to the same error.

OptionBis incorrect since SAV files are not expected in the Data files directory. OptionCis unrelated to this specific error, as missing CSV files would generate a different error related to missing data, not schema definition.

Thus, the issue is specifically tied to missing or invalid SAV schema files.

In Saviynt EIC integration with ServiceNow as a ticketing system (ITSM), various JSON configurations are used to define how tickets are created, updated, and tracked. To enable users tocheck the status of tickets from EIC, the correct configuration isTICKETSTATUSJSON.

TICKETSTATUSJSONis specifically used to define how Saviynt retrieves the current status of a ticket from ServiceNow. It maps the API response fields from ServiceNow (such as state, status, or resolution) to Saviynt fields, allowing the system to display real-time ticket status within the EIC interface.

Option A (SYNCTICKETSTATUSJSON) is typically used for synchronization jobs that update ticket statuses in bulk, not for direct user-level status retrieval. Option B (CREATETICKETJSON) is used only for ticket creation, defining how requests are sent to ServiceNow. Option D is incorrect because Saviynt does support ticket status tracking through proper integration configuration.

Thus,TICKETSTATUSJSONis the correct option to enable visibility of ticket status within Saviynt EIC.

In Saviynt EIC,User Update Rulesare powerful automation mechanisms used to perform actions based on user attribute changes or conditions defined through SQL queries. These rules support multiple actions that help streamline identity lifecycle management.

Option A is correct because User Update Rules cantrigger Technical Rules, enabling further downstream processing such as provisioning, deprovisioning, or executing custom logic. This allows modular and scalable automation.

Option B is also valid since User Update Rules can be used togenerate usernames dynamicallybased on defined patterns or business logic, especially during onboarding or identity updates.

Option C is correct as well because these rules supportsending email notifications, which can be used for alerts, approvals, or informing stakeholders about identity changes.

Since all these actions are supported within User Update Rules, Option D (All the above) is correct. This highlights the flexibility of User Update Rules in handling automation, communication, and identity data transformations within Saviynt EIC.

In Saviynt EIC, when configuringdynamic attributes or custom forms, system variables are used to fetch context-specific data such as the currently logged-in user. To retrieve theDisplay Name of the logged-in user, the correct variable is${loggedInUser}, which directly represents the userkey of the active session user.

Option A correctly uses this variable in the SQL query to fetch the DISPLAYNAME from the Users table. This ensures that the attribute dynamically reflects the logged-in user's display name at runtime.

Option B is incorrect because${user.id}typically refers to the target user in a request context, not necessarily the logged-in user. Option C (${requestor}) may represent the requester in certain workflows but is not consistently equivalent to the logged-in user in all scenarios, especially in delegated or admin-driven requests.

Therefore, Option A is the most accurate and reliable approach for retrieving the logged-in user's display name in Saviynt configurations, ensuring proper context-aware data population.

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.