Advanced IGA Professional SCAIP Syllabus Exam Questions Answers

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

Statement A is correct becauseRole Miningin Saviynt analyzes user access patterns and identifies relationships between users who share similar entitlements. These patterns are then used to logically group access into roles, enabling efficient role-based access control (RBAC) implementation and reducing manual effort in role creation.

Statement B is incorrect because apercentage cut-off (e.g., 60%)in role mining means that entitlements common to at least 60% of users are considered for role creation—not 100%. The statement incorrectly interprets how threshold-based mining works.

Statement C is correct since access toDuplicate Identity Management (DIM)features is controlled viaSAV Role configurations. Administrators must grant appropriate permissions within SAV roles to allow users to view and manage duplicate identities in the system.

Statement D is incorrect because DIM supports merging not only user attributes but also associated accounts and access depending on configuration. It is not limited to attributes alone.

Thus, the correct answers areA and C.

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.