Saviynt Saviynt IGA Certified Professional Exam (L100) SAVIGA-C01 Exam Dumps: Updated Questions & Answers (September 2025)

To apply a User Update Rule to existing users in Saviynt, you should enable the option B. Retrofit rule actions for users. Here's an explanation:

Saviynt's User Update Rules - Initial Application: When a User Update Rule is created, it typically applies to users who are newly created or updated after the rule is put in place.

Retrofit Functionality: The "Retrofit rule actions for users" option allows you to apply the rule retroactively to users who already exist in the system and meet the rule's conditions.

How it Works: When enabled, Saviynt will evaluate the rule against all existing users. If a user matches the rule's conditions, the defined actions (e.g., assigning roles, updating attributes) will be applied to that user, even if they were created before the rule.

Use Cases: This is useful when you create a new rule that should have been in place all along, or when you need to make a broad change to existing user configurations based on a new policy.

Other Options:

A. Trigger when user is created from import: This applies the rule to new users imported into Saviynt, not existing users.

C. Trigger when user is updated from import: This applies the rule when existing users are updated via import, but it won't necessarily apply to all existing users who meet the conditions.

D. Action > Rerun All Provisioning Rules: This action is more general and might not be the most efficient way to apply a specific User Update Rule retroactively.

In summary: The "Retrofit rule actions for users" setting within a Saviynt User Update Rule is crucial for applying the rule's logic and actions to existing users, ensuring consistent configuration across the user base.

Given that an Admin launched a Role Ownership Campaign for you in Saviynt, the option you can not certify is A. Role Ownership. Here's why:

Saviynt's Role Ownership Campaign: This type of campaign is specifically designed for reviewing and certifying the ownership of roles, not the other aspects of a role.

Your Role as Certifier: In this scenario, you are the designated reviewer for role ownership. This means you are responsible for confirming who should be the owner of specific roles.

What You Can Certify in a Role Ownership Campaign:

Confirm or Change Role Owner: You can confirm that the current role owner is correct or assign a new owner.

What You Cannot Certify in This Campaign:

A. Role Ownership: You are the one certifying role ownership, so you cannot certify your own action of assigning an owner. It would be a circular process.

B. User membership of the Role: This is typically reviewed in a User Access Campaign or a Role Membership Campaign.

C. Delete Role: Role deletion is an administrative action, not typically part of a Role Ownership Campaign.

D. Associated Entitlements: Entitlement certification is usually handled in an Entitlement Owner Campaign or as part of a broader User Access Campaign.

In essence: A Role Ownership Campaign focuses solely on validating and assigning role owners. Other aspects of role management, such as user membership or associated entitlements, are handled in different campaign types or through separate administrative actions. As the certifier in this specific campaign, you cannot certify the very action you are performing, which is assigning role ownership.

The Account status that is not typically considered in a User Manager Campaign certification in Saviynt is D. Manually Provisioned. Here's why:

Saviynt's User Manager Campaign Focus: User Manager Campaigns primarily focus on reviewing and certifying access that is actively managed and tracked within Saviynt.

Account Statuses and Their Relevance:

A. Manually Suspended: Indicates an account that has been intentionally disabled within Saviynt. These accounts are often included in reviews to ensure the suspension is still valid.

B. Inactive: Indicates an account that has not been used for a certain period. These accounts are often included in reviews to determine if they should be disabled or removed.

C. Suspended from Import Service: Indicates an account that has been suspended due to issues during an import process. These accounts are typically reviewed to resolve the import problem and determine the appropriate account status.

Manually Provisioned Accounts: These accounts are created directly in the target system, bypassing Saviynt's provisioning processes. As such, they might not be fully tracked or managed within Saviynt.

Out-of-Band Access: Manually provisioned accounts represent a form of out-of-band access, which is often excluded from standard User Manager Campaigns.

Separate Review Process: Organizations might have separate processes for reviewing manually provisioned accounts, such as using the RevokeOutOfBandAccessJob or a different type of campaign.

In conclusion: While other account statuses like Manually Suspended, Inactive, and Suspended from Import Service are relevant to access management within Saviynt and are often included in User Manager Campaigns, Manually Provisioned accounts might be excluded because they represent access granted outside of Saviynt's control and might require a different review process.

To configure a single report that displays the account attributes of all the accounts to their respective Application Owners in Saviynt, the best approach is D. V2 Analytics using SQL Query with User Context. Here's a breakdown:

Saviynt's Analytics V2: This is Saviynt's newer analytics platform, offering more advanced features and flexibility compared to the older version.

SQL Query with User Context: This is the key to achieving the desired outcome. "User Context" means that the query will be executed in the context of the currently logged-in user (in this case, the Application Owner).

How it Works:

Dynamic Filtering: When an Application Owner runs the report, the "User Context" will automatically filter the data to show only the accounts that they own.

Security and Data Privacy: This ensures that each Application Owner only sees the data that they are authorized to access.

SQL Query Structure: The SQL query would likely involve a JOIN between the accounts table and a table that defines application ownership (e.g., applications), using a WHERE clause that filters based on the current user's ID or username. Something like this (syntax might need adjustment for Saviynt's specific SQL dialect):

SELECT a.*

FROM accounts a

JOIN applications app ON a.application_id = app.application_id

WHERE app.owner_id = ${CURRENT_USER_ID} -- This is the user context part

Why Other Options Are Less Suitable:

A. Use Elasticsearch Query: While Elasticsearch can be used for analytics, it might not be the best tool for this specific requirement, as it doesn't inherently support the concept of "User Context" in the same way as SQL queries in Analytics V2.

B. V2 Analytics using SQL Query with External Connection: External connections are used to query data from external databases, which is not necessary in this scenario.

C. V2 Analytics using SQL Query with Allowed Action: Allowed Actions are used to define actions that can be performed on analytics results, not for filtering data based on user context.

The component that filters the requestable applications under "Request New Access" in Saviynt is the Access Query. Here's a detailed explanation:

Saviynt's Access Request System (ARS): As the front end for requesting access, the ARS needs a mechanism to determine which applications (and entitlements) should be displayed to a user as requestable.

Access Query: This is a powerful feature within Saviynt that allows administrators to define specific criteria to control the visibility of applications and entitlements in the ARS. Think of it as a filter that determines what a user can see and request.

How Access Queries Work:

Defined on Applications/Entitlements: Access Queries are configured on individual applications or entitlements within Saviynt.

Based on User Attributes: They use user attributes (e.g., department, location, job title, group memberships) and other criteria (e.g., risk level) to determine if a user should see a particular application or entitlement.

Dynamic Filtering: When a user accesses the "Request New Access" section, Saviynt evaluates the Access Queries associated with each application and entitlement in real-time. Based on the user's attributes, the system dynamically filters the list, showing only the applications and entitlements that match the query conditions.

Saviynt's Security Model: Access Queries are a fundamental part of Saviynt's security model. They ensure that users are only presented with access options that are relevant and appropriate for their role and context, preventing accidental over-provisioning and reducing the attack surface.

Other Options:

Access Add Workflow: While essential for processing access requests, the workflow itself doesn't filter which applications are initially displayed.

Provisioning Connection: This relates to how Saviynt connects to target systems for automated provisioning. It doesn't control the initial visibility of applications in the ARS.

Whom to Request: This setting might determine the available approvers, but it doesn't filter the list of requestable applications.

In essence: Access Queries act as a dynamic filter, leveraging user attributes and defined criteria to determine which applications and entitlements are presented to a user within Saviynt's "Request New Access" interface, ensuring a personalized and secure access request experience.

=================

To view the Entitlements Query used in a previously launched Campaign in Saviynt, a Campaign Owner can use the C. Campaign Summary. Here's why:

Saviynt's Campaign Summary: The Campaign Summary provides a detailed overview of a campaign's configuration, including:

Campaign Scope: The users, applications, or entitlements included in the campaign.

Filters and Queries: Any filters or queries used to define the campaign scope, including the Entitlements Query.

Certifier Information: Details about the assigned certifiers.

Schedule: The campaign's start and end dates.

Status: The current status of the campaign (e.g., Active, Completed, Expired).

Accessing the Entitlements Query: The Campaign Summary typically includes a section that displays the exact query used to select the entitlements included in the campaign.

Why Other Options Are Less Suitable:

A. Reconfigure option: While you might be able to see the query by going into the reconfiguration, it's not the most direct way. The Campaign Summary is designed to provide this information readily.

B. Campaign Export: Exporting the campaign data might include the list of entitlements but not necessarily the original query used to select them.

D. Export option at the top right corner of the page, next to the Refresh Progress option: This option typically exports the current view of the campaign data, not the underlying configuration details like the Entitlements Query.

In conclusion: The Campaign Summary in Saviynt is the most direct and convenient place for a Campaign Owner to review the detailed configuration of a campaign, including the Entitlements Query used to define the campaign's scope.

=================

User Account Correlation Rules in Saviynt are specifically designed to map imported accounts to existing users within the system. These rules define the logic for matching accounts to users based on various attributes, such as employee ID, email address, or username.

Why other options are incorrect:

Account to User Rule: This is not a standard rule type in Saviynt.

Account Name Rule: This might focus on naming conventions for accounts, not correlating them to users.

Technical Rule: This is a broader category of rules and doesn't specifically address account-user mapping.

Saviynt IGA References:

Saviynt Documentation: The section on Account Correlation Rules provides detailed information on how to configure these rules for different scenarios.

Saviynt Use Cases: Saviynt often provides examples and use cases demonstrating how to use User Account Correlation Rules to automate account mapping during imports.

In Saviynt, a User represents the unique identity of a person. It's the central object that ties together all the information about an individual, including their accounts, entitlements, roles, and attributes.

Why other options are incorrect:

Endpoint: Represents a system or application, not a person.

Employee: While many users might be employees, the term "user" is more general and can include contractors, partners, etc.

Account: Represents a user's access to a specific system, not their overall identity.

Saviynt IGA References:

Saviynt Documentation: Throughout the documentation, "User" consistently refers to the individual's identity within the system.

Saviynt User Interface: The User Management section in Saviynt focuses on managing the lifecycle and access of individual users.

To decommission an AD Group and revoke access for all users, Jane should use D. Entitlement Owner Certification. Here is why:

AD Group as an Entitlement: In Saviynt, an AD Group is typically represented as an Entitlement.

Entitlement Owner Certification: This type of campaign allows the designated owner of an entitlement (in this case, Jane, as the manager of the AD Group) to review and certify who should have access to that entitlement.

Revoking Access: As the Entitlement Owner, Jane can use the certification campaign to:

Review the list of users: See all users who are currently members of the AD Group.

Revoke access for all users: Mark all users for removal from the group.

Decommissioning the Group: After revoking access for all users through the certification, Jane can then proceed with decommissioning the AD Group itself (either through Saviynt if it manages AD group lifecycle or directly in Active Directory).

Why Other Options Are Less Suitable:

A. Segregation of Duties: SoD is a principle, not a specific action for revoking access.

B. Entitlement Update Rule: While rules can automate some actions, a certification campaign provides a more controlled and auditable way to review and revoke access, especially for a sensitive action like decommissioning a group.

C. Mitigation Control: Mitigation controls are used to manage SoD conflicts, not for revoking access to entitlements.

In conclusion: An Entitlement Owner Certification campaign provides a structured and auditable way for Jane to review the membership of the AD Group, revoke access for all users, and prepare for the group's decommissioning, aligning with best practices for access management.

=================

The object that is available in the User Update Rule to configure Rule conditions in Saviynt is A. Users. Here's an explanation:

User Update Rule Purpose: As mentioned before, User Update Rules are used to automatically update user attributes based on certain conditions.

Condition Based on User Attributes: The conditions for triggering a User Update Rule are primarily based on attributes of the User object itself.

Examples of User Attributes: These attributes can include:

User Status: (e.g., Active, Inactive, Disabled)

Department:

Location:

Job Title:

Manager:

Custom Attributes: Any custom attributes defined for users in your Saviynt environment.

Triggering the Rule: When a user's attributes change, and those changes match the conditions defined in a User Update Rule, the rule is triggered.

Other Options:

B. Accounts: While account attributes can be updated as an action of a User Update Rule, the conditions for triggering the rule are typically based on user attributes, not account attributes.

C. Roles: Similar to accounts, roles can be assigned or removed as an action of a User Update Rule, but the triggering conditions are usually based on user attributes.

D. Entitlements: Entitlements are also typically managed as an action of a User Update Rule, not as part of the triggering condition.

In conclusion: The User object and its attributes are the primary focus for defining conditions within a Saviynt User Update Rule. Changes to user attributes trigger the rule, which can then perform actions such as updating other user attributes, accounts, roles, or entitlements.