Which of the following must be linked to the Active Directory Security System to automatically reconcile Accounts from AD into Saviynt?
Answer(s): C
An AD Connection in Saviynt is required to establish communication and data exchange with an Active Directory (AD) domain. This connection enables Saviynt to automatically reconcile accounts from AD, ensuring that the identity information in Saviynt stays synchronized with the AD.Why other options are incorrect:AD Control, AD Rule, AD Role: These terms are not standard components within Saviynt's framework for integrating with Active Directory.Saviynt IGA
Saviynt Documentation: The section on integrating with Active Directory clearly outlines the need for an AD Connection and provides step-by-step instructions for configuring it. Saviynt Connectors: Saviynt offers pre-built connectors for Active Directory that simplify the process of establishing the connection.
Which of the following Connections is used for integrating Saviynt with a ticketing system?
A Service Desk Connection in Saviynt is used to integrate with external ticketing systems. This integration allows Saviynt to:Automate request fulfillment: Access requests created in Saviynt can automatically generate tickets in the service desk system.Track request status: Saviynt can update the status of access requests based on the corresponding ticket status in the service desk system.Improve communication: Integration facilitates seamless communication and collaboration between Saviynt and the service desk team.Why other options are incorrect:Service Ticket Connection, Ticket Connection, Provisioning Connection: These are not standard terms used in Saviynt for service desk integration.Saviynt IGA
Saviynt Documentation: The documentation on integrating with Service Desk systems explains the purpose and configuration of a Service Desk Connection.Saviynt Connectors: Saviynt provides connectors for popular service desk solutions like ServiceNow, facilitating the integration process.
Which of the following options is part of the Saviynt Identity Repository?
Saviynt's Identity Repository is the central hub for storing and managing all identity-related information. It includes:Users: Representing individuals and their attributes.Accounts: Representing user access to specific systems or applications. Entitlements: Representing permissions and access rights within those systems. Roles: Representing collections of entitlements that define job functions or responsibilities.Why other options are incorrect:A, B, and D: These options include elements like Identity Rules, Workflows, and SAV Roles, which are important components of Saviynt but are not core parts of the Identity Repository itself.Saviynt IGA
Saviynt Documentation: The section on the Identity Repository describes its function and the types of data it stores.Saviynt User Interface: The Identity Repository is a key section within the Saviynt interface, where you can view and manage users, accounts, entitlements, and roles.
Marty, an Administrator, reconciled Oracle Accounts into Saviynt. During the import, the incoming accounts were required to be mapped to the existing users in Saviynt. Which of the following Rules should be used to successfully associate Accounts to the correct users?
Answer(s): D
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
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.
If you want an application to be available for requesting access (self or other), which of the following should be configured?
To make an application available for access requests (either self-service or requests for others), the Access Add Workflow needs to be configured within Saviynt. This workflow defines the process that governs how access to the application is granted. Here's a breakdown with Saviynt IGA references:Saviynt's Access Request System (ARS): This is the module within Saviynt that handles access requests. The ARS relies on defined workflows to manage the approval and provisioning process.Access Add Workflow: This specific type of workflow within Saviynt's ARS is triggered when a user requests access to an application or entitlement. It dictates the steps involved, such as:Requester Details: Capturing information about who is requesting access. Application/Entitlement Selection: The user selects the application (and potentially specific roles or entitlements within that application) for which they are requesting access. Approval Routing: Defining the approval chain (e.g., manager approval, application owner approval, etc.). This is configured within the workflow using various approval activities. Provisioning: Upon approval, the workflow can trigger automated provisioning of access to the target system (if connected integration is set up).Saviynt's Application Onboarding: For an application to be available in the ARS, it needs to be onboarded into Saviynt. During this process, you would typically define the relevant entitlements (access rights) associated with the application.Workflow Configuration in Saviynt: Saviynt's admin interface allows administrators to create and customize workflows using a visual designer. This includes setting up conditions, defining approval steps, and configuring actions to be taken at each stage of the workflow.Other options:Proposed Accounts Workflow: This is less common, often used to suggest potential accounts during the request or account creation process. It's not the primary mechanism for making an application available for access requests.Access Remove Workflow: This workflow is used when access needs to be revoked, not granted. Emergency Access ID Request Workflow: This workflow is specific to requesting temporary, elevated access in emergency situations. It's not the workflow for general access requests to applications.
Post your Comments and Discuss Saviynt SAVIGA-C01 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the SAVIGA-C01 content, but please register or login to continue.