SAVIGA-C01 Exam Dumps and Practice Questions

When access privileges for a specific Analytical Control are assigned using SAV Roles in Saviynt, users belonging to that role can, by default, perform the following tasks: B. View Control, Run Control, and View Analytic History of the Control. Here's a breakdown:

Saviynt's Role-Based Access Control (RBAC): Saviynt uses RBAC to manage access to various features and functionalities, including Analytical Controls.

Analytical Controls: These are pre-defined or custom-built analytics reports or dashboards.

Default Permissions: When a user is granted access to an Analytical Control via an SAV Role, they typically receive a set of default permissions:

View Control: Allows the user to view the configuration and definition of the Analytical Control (e.g., the query, parameters, visualization).

Run Control: Allows the user to execute the Analytical Control and generate results.

View Analytic History: Allows the user to see the history of previous executions of the Analytical Control, including the results and timestamps.

Why These Permissions Are Important:

Transparency: Users can understand how the analytics are defined and generated.

Usability: Users can run the analytics and obtain insights.

Auditing: Users can review past results for trend analysis or investigation.

Other Options:

A . Only view the configurations of the Control: This is too restrictive; users need to be able to run the control to get value from it.

C . Only view the Analytic History of the Control: This is also too limited; users should be able to run the control and view its configuration as well.

D . View Control and Run Control: While closer, it's missing the 'View Analytic History' permission, which is important for auditing and analysis.

MISCELLANEOUS

The correct sequence of workflow events for an application where the Manager's approval should be followed by the Application Owner's approval is D. Start > Manager's Approval > Resource Owner's Approval > Approve/Reject > End. Here's a breakdown:

Saviynt's Workflow Structure: Saviynt workflows follow a sequential structure, starting with a 'Start' event and ending with an 'End' event.

Workflow Activities: Each step in the workflow is represented by an activity, such as an approval task.

Manager's Approval: In this scenario, the first required approval is from the Manager. This would be represented by a 'TASK Access Approve' activity (or similar, depending on the specific configuration) assigned to the user's manager.

Application Owner's Approval: After the Manager's approval, the workflow needs to proceed to the Application Owner for their approval. This would be another 'TASK Access Approve' activity assigned to the Application Owner. In Saviynt terms, Application Owner is a type of Resource Owner.

Approve/Reject: This activity represents the decision point where the final approver (in this case, the Application Owner) either approves or rejects the request.

End: The workflow concludes with the 'End' event, signifying the completion of the process.

Other Options:

A . Start > Resource Owner's Approval > Manager's Approval > Approve/Reject > End: Incorrect order; the manager's approval should come before the application owner's.

B . Start > Manager's Approval > Custom Assignment > Approve/Reject > End: 'Custom Assignment' is not the most appropriate activity for a standard approval step. 'TASK Access Approve' would be more suitable.

C . Start > Manager's Approval > Access Approval > Approve/Reject > End: 'Access Approval' is a bit redundant; 'TASK Access Approve' assigned to the appropriate role is clearer.

In essence: The correct workflow sequence accurately reflects the required approval hierarchy: first the Manager, then the Application Owner, followed by the final decision (Approve/Reject) and the end of the workflow.

If the data displayed in the Campaign Preview mode does not meet the requirement in Saviynt, the appropriate action is A. Re-configure Campaign. Here's why:

Saviynt's Campaign Preview Mode: This mode allows administrators to review the data that will be included in a campaign before activating it. It's a crucial step for ensuring that the campaign scope, data, and configuration are correct.

Purpose of Preview Mode: The primary purpose of the preview is to identify any issues or discrepancies in the campaign setup before it goes live.

Re-configure Campaign: If the preview reveals problems (e.g., incorrect users or entitlements are included, the wrong Certifiers are assigned, filters are not working as expected), the administrator needs to go back and re-configure the campaign settings. This might involve:

Adjusting the campaign scope.

Modifying filters or selection criteria.

Changing Certifier assignments.

Updating the campaign schedule or notifications.

Why Other Options Are Incorrect:

B . Check Summary: The summary provides a high-level overview of the campaign, but it doesn't allow for detailed data review like the preview mode.

C . Export Campaign: Exporting the campaign data won't fix the underlying configuration issues.

D . Activate Campaign: Activating a campaign with incorrect data would lead to inaccurate certification decisions and potential security risks.

The bulk operation that is not typically a supported feature in the same way as the others is C. Bulk Approval - Single-click approval for multiple entitlements in a single request. Here's why:

Saviynt's Bulk Operations: Saviynt supports various bulk operations to streamline administration and user experience, especially when dealing with multiple users or requests.

Supported Bulk Operations:

A . Bulk Request Access: Saviynt allows users to request access for multiple users in a single request. This is a common and supported feature.

B . Disabling multiple users and their access: Administrators can disable multiple user accounts and revoke their access in bulk.

D . Deleting multiple users: Saviynt supports the bulk deletion of user accounts.

Bulk Approval - Granularity: While Saviynt supports bulk approvals (approving multiple requests at once), it typically operates at the request level, not at the individual entitlement level within a single request. Approving multiple separate requests in one go is a standard bulk approval action.

Each request (even if it's a bulk request for multiple users or contains multiple entitlements) is usually treated as a single unit for approval.

Approvers typically approve or reject the entire request, not individual entitlements within it.

Security and Control: This approach maintains better control and auditability. Approving each entitlement within a single request individually would require a more complex interface and potentially increase the risk of accidental approvals.

Possible Workarounds:

Separate Requests: To achieve a similar outcome, users could submit separate requests for each entitlement, allowing the approver to approve them individually (and potentially in bulk if they are separate requests).

Custom Workflows: In theory, it might be possible to create highly customized workflows to handle this scenario, but it's not a standard out-of-the-box feature.

In summary: While Saviynt excels at bulk operations for users and requests, single-click approval of individual entitlements within a single request is not a typical supported feature due to the need for granular control and a clear audit trail. Bulk approvals usually apply to entire requests, not to individual entitlements within them.

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.