Saviynt SAVIGA-C01 Exam Dumps

In Saviynt, 'Entitlements' refers to any type of access granted to users within a managed system or application. This broad term encompasses various forms of access controls, including:

Groups: Collections of users with shared access permissions.

Roles: Sets of permissions that define a user's job function or responsibilities.

Permissions: Specific access rights to resources or functionalities.

Responsibilities: Duties or tasks associated with a particular role.

Why other options are incorrect:

Endpoints: Refer to network devices or systems, not access rights.

Workflows: Are automated processes for tasks like approvals, not access itself.

Accounts: Represent user identities, not the specific access they have.

Saviynt IGA Reference:

Saviynt Documentation: Saviynt's documentation consistently uses the term 'Entitlements' to describe the various types of access it manages.

Saviynt User Interface: The Saviynt interface uses 'Entitlements' throughout its menus and features related to 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.

The Job responsible for configuring a dashboard (among other configurations) in a Saviynt Campaign is B. Create or Schedule Attestation Job. Here's a detailed explanation:

Saviynt's Campaigns: Campaigns in Saviynt are used for access certification, allowing reviewers (Certifiers) to review and approve or revoke user access.

Create or Schedule Attestation Job: This job is the core mechanism for creating and configuring various aspects of a campaign, including:

Campaign Scope: Defining which users, entitlements, or resources are included in the campaign.

Certifier Selection: Specifying who will be the reviewers for the campaign.

Scheduling: Setting the start and end dates for the campaign.

Notifications: Configuring email notifications for Certifiers and other stakeholders.

Dashboard Configuration: Defining the information and layout displayed on the campaign dashboard for Certifiers. This includes selecting which data points, charts, and filters are visible.

Why Other Options Are Incorrect:

A . Campaign Export Job: This job is used to export campaign data, not to configure the campaign itself.

C . Campaign Import Job: This job is used to import data into a campaign, typically from an external source.

D . Upgrade Job: This job is related to upgrading the Saviynt platform, not to campaign configuration.

In summary: The 'Create or Schedule Attestation Job' is the central job for setting up and configuring all aspects of a Saviynt campaign, including the dashboard that provides Certifiers with a summarized view of the certification data.

In this scenario, where John is a new full-time employee required to work from the Sydney office, the most specific and appropriate Enterprise Role assigned from the Birthright Rule would likely be A. Birthright - Sydney. Here's the reasoning:

Saviynt's Birthright Roles and Rules: Birthright roles are designed to automatically provision access based on specific criteria like location, job role, or employment type. Birthright rules define the conditions for assigning these roles.

Specificity of Role Assignment: The goal is to assign the most relevant and granular role based on the available information. In this case, John's location (Sydney) is the most specific criterion mentioned.

Why Other Options Are Less Likely:

B . Birthright - Permanent - Full-time: While John is a full-time employee, this role might be too broad if there are other location-specific roles.

C . Birthright - All: This role is likely too generic and would grant excessive access. It's generally not good practice to have an 'all-encompassing' birthright role.

D . Birthright - Employee: Similar to the 'Full-time' role, this might be too broad if location-specific roles are available.

Best Practices: It's a best practice in identity governance to use the most specific criteria possible when assigning birthright access. This helps enforce the principle of least privilege.

In summary: The 'Birthright - Sydney' role is the most appropriate choice because it aligns with John's specific work location, ensuring he receives the necessary access for his role while adhering to the principle of least privilege.

The Job that should be created and scheduled to evaluate Rules on a need basis in Saviynt is A . Run Detective Rules and Take Action. Here's an explanation:

Saviynt's Jobs: Saviynt uses Jobs to perform various tasks, including data imports, rule evaluations, and provisioning operations.

'Run Detective Rules and Take Action': This specific job is designed to:

Evaluate Rules: It evaluates rules that are configured for detective (monitoring) purposes. These rules typically check for specific conditions or changes in user attributes, access rights, or other data.

Take Action (Optional): Based on the rule evaluation results, the job can be configured to automatically take actions, such as:

Generating alerts or notifications.

Creating tasks for administrators to review.

Triggering workflows.

Automatically remediating issues (e.g., revoking access if a rule detects a violation).

Scheduling: This job can be scheduled to run periodically (e.g., daily, hourly) to continuously monitor for changes and enforce defined rules.

On-Demand Execution: You can also run this job on-demand to evaluate rules immediately.

Other Options:

B . Provisioning Job: This job is primarily used for provisioning access to target systems, not for evaluating general-purpose rules.

C . User Import via Connection: This job is for importing user data from external sources.

D . Trigger Chain Job: This allows for running a series or 'chain' of jobs, but it doesn't directly evaluate rules itself.