Saviynt SAVIGA-C01 Exam Dumps

The feature that best describes the Authorization mechanism for the EIC (Enterprise Identity Cloud) application in Saviynt is A. Security System. Here's an explanation:

Saviynt's Security System: This is the core component within Saviynt that handles authentication and authorization for various applications and resources, including EIC.

Authorization in EIC: The Security System determines what actions users are allowed to perform within EIC, such as:

Creating, updating, or deleting users.

Managing roles and entitlements.

Running reports.

Configuring connections.

Role-Based Access Control (RBAC): The Security System typically uses RBAC to manage these permissions. Users are assigned to roles, and roles are granted specific permissions within EIC.

Why Other Options Are Less Relevant:

B . SSO (Single Sign-On): SSO is an authentication mechanism that allows users to log in once and access multiple applications. While Saviynt supports SSO, it's not the primary authorization mechanism for EIC.

C . WSRETRY Job: This is a job related to retrying web service calls, not authorization.

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.

The Saviynt feature that allows detection of access rights granted outside the Saviynt platform is the B. RevokeOutOfBandAccessJob. Here's a detailed explanation:

Out-of-Band Access: This refers to access that is provisioned directly in the target system, bypassing the normal access request and approval processes within Saviynt. This can create security risks and compliance issues.

Saviynt's Reconciliation Process: Saviynt uses a reconciliation process to compare the access rights defined within its system with the actual access rights present in connected applications.

RevokeOutOfBandAccessJob: This specific job is designed to identify and flag out-of-band access. It works by:

Importing Account and Entitlement Data: The job imports data from the target system, capturing the current state of user access.

Comparing with Saviynt Data: It compares this imported data with the access rights managed within Saviynt.

Identifying Discrepancies: Any discrepancies, where a user has access in the target system that wasn't granted through Saviynt, are identified as out-of-band access.

Taking Action (Optional): The job can be configured to automatically revoke this out-of-band access or to simply generate a report for review and manual remediation. Or it can be configured to create a task for an administrator to review.

Saviynt's Access Governance: This feature is a crucial part of Saviynt's overall access governance capabilities, helping organizations maintain control over user access and enforce the principle of least privilege.

Other Options:

A . REST API: While Saviynt's REST API can be used to interact with the system and potentially retrieve access data, it's not the specific feature designed for out-of-band access detection.

C . Bulk Upload: This is a method for importing data into Saviynt, but it doesn't inherently detect out-of-band access.

D . ARS > Request Access for Others: This is part of the access request process, not related to detecting access granted outside of Saviynt.

In conclusion: The RevokeOutOfBandAccessJob in Saviynt plays a vital role in identifying and remediating out-of-band access, ensuring that access rights are managed centrally and consistently through the Saviynt platform.

The image signifies B. Assigning of Enterprise Role based on users' location. Here's a breakdown, assuming the image depicts a portion of a Saviynt User Update Rule configuration:

Dynamic Variable 'City': The image highlights the use of a dynamic variable called 'city.' This strongly suggests that the rule is using the user's location (city) as a key factor in determining role assignment.

Saviynt's User Update Rules and Dynamic Variables: User Update Rules in Saviynt allow for the use of dynamic variables, which represent user attributes. These variables can be used in conditions and actions within the rule.

Enterprise Role Assignment: The context of the question implies that the rule is assigning an Enterprise Role based on the value of this 'city' variable.

Example: The rule might be configured to assign an Enterprise Role like 'Sydney-Users' to users whose 'city' attribute is 'Sydney.'

Why Other Options Are Less Likely:

A . Assigning of Enterprise Role based on users' department: There's no mention of 'department' in the provided information.

C . Assigning of Enterprise Role based on concatenation of dynamic variable city and Finance: While concatenation is possible in Saviynt, there's no indication that 'Finance' is involved here. The focus seems to be solely on the 'city' variable.

In conclusion: Based on the information given, the image most likely represents a Saviynt User Update Rule that assigns an Enterprise Role based on the user's location, as indicated by the dynamic variable 'city.

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.