SAVIGA-C01 Saviynt IGA Certified Professional Exam (L100) Free Practice Exam Questions (2025 Updated)

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.

The process of Attestation or Certification in the context of Saviynt can be best described as B. Access Reviews. Here's why:

Attestation/Certification: These terms are often used interchangeably in the context of identity governance. They refer to the process of formally reviewing and approving or revoking user access rights.

Access Reviews: This is the broader term that encompasses the entire process of periodically reviewing user access to ensure it is appropriate and aligned with business needs and security policies. Attestation and Certification are specific actions performed within an access review.

Saviynt's Campaigns: Saviynt's campaigns are designed to facilitate and manage access reviews.

Why Other Options Are Less Suitable:

A. Segregation of Duties: SoD is a principle that aims to prevent fraud and errors by dividing critical tasks among different individuals. While access reviews can help enforce SoD, they are not the same thing.

C. Access Request: This is the process of requesting access to resources, which is a separate process from reviewing existing access.

D. Application Onboarding: This is the process of integrating an application into Saviynt, which is a prerequisite for access reviews but not the review process itself.

In conclusion: Attestation or Certification, as performed within Saviynt campaigns, are integral parts of the broader process of Access Reviews, which aim to ensure that user access is appropriate, authorized, and aligned with security policies.

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

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.

When an "Add Access" task is successfully completed in Saviynt, the applicable status is typically "Provisioned." Here's a detailed explanation with Saviynt references:

Saviynt's Task Management: Saviynt uses tasks to track the progress of various operations, including access provisioning. These tasks are generated as part of workflows, such as the "Access Add Workflow."

"Add Access" Task Type: This specific task type is created when the access request is approved and the system is ready to grant the requested access to the target application.

Task Statuses in Saviynt: Saviynt uses different statuses to indicate the current state of a task. Common statuses include:

Pending: The task is waiting to be processed.

In Progress: The task is currently being executed.

Provisioned: This status signifies that the requested access has been successfully granted to the user in the target system.

Failed: The task encountered an error and could not be completed.

Manually Provisioned: The task was completed manually by an administrator, rather than through automated provisioning.

Success: While sometimes used, this status is less specific than "Provisioned" in the context of "Add Access" tasks, since it does not specify that the action completed was a provisioning action.

Active: Typically applies to accounts or users, not tasks.

Saviynt's Workflow Engine: The workflow engine in Saviynt updates the task status as it progresses through the defined steps. For connected applications, the workflow engine might directly interact with the target system's API to provision the access. Once the provisioning is successful, the status is updated to "Provisioned."

Saviynt's Audit Trails: Saviynt maintains detailed audit trails, and the task status changes are logged. This provides a clear record of when access was provisioned for a user.

Other Options:

Success: As mentioned above, this is a general status. While technically correct (the task succeeded), "Provisioned" provides more context.

Manually Provisioned: This status is only applicable if an administrator intervened and manually granted the access outside of the automated workflow.

Active: This status typically pertains to a user or account's overall status, not specifically to the completion of an "Add Access" task.

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

In Saviynt's SAML 2.0 based Single Sign-On (SSO) configuration, the "SP Entity ID" uniquely identifies Saviynt as the Service Provider (SP) to the Identity Provider (IdP). The correct SSO URL structure incorporates this "SP Entity ID" within a specific path.

Saviynt's URL Structure: Saviynt's SSO URLs follow a pattern to ensure proper routing and authentication. The /ECM/saml/SSO/alias/ portion is crucial for directing SAML-based login attempts.

Why the other options are incorrect:

A. https://myorg.saviyntcloud.com/ECM/saml/SSO/SaviyntSP: This URL is missing the crucial "alias" segment in the path, making it invalid for SAML SSO.

B. https://myorg.saviyntcloud.com/SaviyntSP: This URL doesn't include the necessary components for SAML-based authentication within Saviynt.

Saviynt IGA References:

Saviynt Documentation: Saviynt's official documentation on configuring SAML SSO provides details on the correct URL structure and the significance of the "SP Entity ID."

Saviynt Support: Saviynt's support resources and knowledge base articles often address issues related to SSO configuration, reinforcing the correct URL format

To automatically deprovision birthright access when the defining condition fails, the correct option is C. Remove the birthright Access if the condition fails under the created Rule. Here's a detailed explanation:

Saviynt's Birthright Access (Automatic Provisioning): Saviynt allows administrators to define rules that automatically grant access (birthright access) based on user attributes or other criteria (e.g., new hires in a specific department automatically get access to certain applications).

Rule-Based Access Management: These rules are a core part of Saviynt's access management capabilities, allowing for dynamic and automated provisioning.

"Remove the birthright Access if the condition fails": This option, typically found within the birthright rule configuration itself, is crucial for ensuring that access is revoked when the conditions that granted it are no longer met.

Example: If a user is granted access to an application because they are in the "Sales" department, and they are later moved to the "Marketing" department, the condition for the birthright rule would fail, and Saviynt would automatically deprovision the access.

Saviynt's Continuous Monitoring: Saviynt continuously monitors user attributes and rule conditions. When a change occurs that causes a condition to fail, the deprovisioning action is triggered.

Other Options:

A. Remove the Access Rule: This would remove the entire rule, preventing it from granting access to anyone, not just the user whose condition has failed.

B. Apply a new Technical Rule to remove the Access: While technically possible, it's less efficient and more complex than using the built-in option within the birthright rule.

D. Use the Request Rule: Request Rules are for access requests, not for automatically provisioning or deprovisioning birthright access.

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

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.

The UIADMIN ROLE in Saviynt grants users the privilege to edit UI (User Interface) labels. This role is crucial for customizing the Saviynt interface to align with an organization's terminology and branding.

UI Customization: Saviynt allows administrators to modify various UI elements, including labels, to improve user experience and comprehension. The UIADMIN ROLE provides the necessary permissions for these modifications.

Why other options are incorrect:

The other options are not standard Saviynt roles and do not have any associated privileges for UI label editing.

Saviynt IGA References:

Saviynt Documentation: The documentation on Saviynt's administration and configuration settings includes information about UI customization and the associated UIADMIN ROLE.

Saviynt Support: Saviynt's support resources may contain articles or knowledge base entries related to UI customization and the permissions required.

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.

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

To get the details of a successfully executed Rule in Saviynt, an Admin should look in the C. Current Rule Trail. Here's why:

Saviynt's Rule Engine and Logging: Saviynt's rule engine executes various types of rules (e.g., birthright rules, user update rules, technical rules). It maintains logs to track rule execution and outcomes.

Current Rule Trail: This log specifically captures the details of recently executed rules, including:

Rule Name: The name of the rule that was executed.

Execution Time: The timestamp of when the rule was executed.

Status: Whether the rule execution was successful or not.

Details: Specific information about the rule's execution, such as the conditions that were evaluated and the actions that were taken.

Troubleshooting and Auditing: The Current Rule Trail is invaluable for troubleshooting rule behavior and for auditing purposes, providing a clear record of what rules were executed and their results.

Other Options:

A. Archived Rule Trail: This log stores details of older rule executions that have been archived. It's useful for historical analysis but not for recent executions.

B. Archived Application Logs: These logs are related to application activity, not rule execution.

D. Action Trail: The Action Trail captures general user and administrative actions within Saviynt, but it might not provide the detailed information about rule execution that the Current Rule Trail does.

User matches with Identity

Security System matches with Application Category

Endpoint matches with Application

Workflow matches with Access Approval

User and Identity: In the context of Identity and Access Management (IAM), "User" often relates to "Identity" management, which deals with user accounts, profiles, and their associated attributes.

Security System and Application Category: "Security System" is a broad term. Within the image, it is a category under which applications are managed, making "Application Category" the correct match.

Endpoint and Application: "Endpoints" in Saviynt refer to the target systems or applications that are being managed or integrated. Therefore "Endpoint" relates to "Application."

Workflow and Access Approval: "Workflows" are often used to define and automate processes, and in this case, it relates to the "Access Approval" process.

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.

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

To make an Entitlement request time-bound in Saviynt, the configuration used on the Entitlement Type is D. Start Date/End Date while raising a Request. Here's a breakdown:

Saviynt's Entitlement Management: Entitlements represent specific access rights within an application. Saviynt allows fine-grained control over how these entitlements are requested and granted.

Entitlement Type Configuration: Within Saviynt, each Entitlement Type can be configured with various settings that govern its behavior during access requests.

Time-Bound Access: To enforce time-limited access, Saviynt provides the option to require a Start Date and End Date during the request process.

"Start Date/End Date while raising a Request": This configuration setting, when enabled on an Entitlement Type, forces the requester to specify a desired start and end date for the access. This ensures that the granted access will only be valid for a specific period.

Saviynt's Workflow Engine and Provisioning: When a request with a start and end date is approved, Saviynt's workflow engine will typically handle the provisioning and de-provisioning based on these dates. If connected integration is set up, it may schedule the activation and deactivation of the access in the target system accordingly.

Other Options:

A. Ask for Start Date while revoking: This setting is related to revoking access, not granting time-bound access.

B. Allow update of Access End Date: This allows modification of the end date after the access has been granted, but it doesn't enforce a time-bound request from the outset.

C. Config JSON for Request Dates: While JSON might be used internally for configuration, this is not the specific setting that directly enables time-bound access requests.

In summary: The "Start Date/End Date while raising a Request" configuration on an Entitlement Type in Saviynt is the key to enforcing time-bound access, ensuring that access is granted only for a specific, pre-defined period.

In Saviynt, Enterprise Roles are specifically designed to encompass entitlements that span multiple applications. This is in contrast to Application Roles, which are limited to entitlements within a single application.

Enterprise Roles: Provide a way to group entitlements across different applications, reflecting a user's overall job function or responsibilities within the organization. This is essential for managing access for users who need permissions in various systems to perform their duties.

Other Role Types:

Application Role: Grants permissions specific to a single application.

Transactional Role: Focuses on granting permissions for specific tasks or transactions within an application.

Enabler Role: Provides supplementary permissions that enhance or support other roles.

Saviynt IGA References:

Saviynt Documentation: The section on Role Management within Saviynt's documentation clearly defines the different role types and their purposes.

Saviynt Training Materials: Saviynt's training courses emphasize the importance of Enterprise Roles in managing cross-application access.

The statement "An Application Owner Campaign can have multiple primary Certifiers and a single secondary Certifier" is generally False in Saviynt. Here's why:

Saviynt's Application Owner Campaign: This campaign type is designed for Application Owners to review and certify access to their applications.

Primary Certifier: There is usually a single designated Application Owner for each application. This is because application ownership is typically a single point of accountability. While it is technically possible to assign multiple owners, it is not considered a best practice.

Secondary Certifiers (Backup/Delegates): Application Owner Campaigns can have multiple secondary certifiers. These are often used as:

Backup: To ensure the campaign can proceed if the primary certifier is unavailable.

Delegates: To allow the primary certifier to delegate some of the certification tasks.

Consultants: Other stakeholders, such as security or compliance teams, who can be consulted during the decision-making process.

Why the Statement Is Generally False: The core principle of application ownership implies a single point of accountability. While multiple secondary certifiers can assist, having multiple primary certifiers can lead to confusion and conflicting decisions.

Possible Exceptions (Less Common):

Highly Customized Configurations: In some very specific scenarios, organizations might customize Saviynt to allow multiple primary certifiers for an application, but this is not a standard or recommended practice.

The connection type best suited to expose Workday reports as a data service in Saviynt is A. Workday-RAAS (Report as a Service). Here's why:

Workday-RAAS: This connection type is specifically designed to integrate with Workday's RaaS functionality. Workday RaaS allows you to expose custom reports created within Workday as web services that can be consumed by external applications like Saviynt.

Data Service for Reports: RaaS essentially turns a Workday report into a data service, making it easy to retrieve the report's data in a structured format (typically XML or JSON).

Saviynt's Integration: Saviynt's Workday-RAAS connection type is built to leverage this capability, allowing you to:

Select Workday Reports: Choose the specific Workday reports you want to integrate with.

Import Data: Import the data from those reports into Saviynt for various purposes (e.g., identity governance, access certification, analytics).

Schedule Imports: Schedule regular data imports to keep Saviynt's data synchronized with Workday.

Why Other Options Are Less Suitable:

B. Workday-REST: While Workday has a REST API, it's more general-purpose and not specifically tailored for exposing reports as data services in the same way as RaaS.

C. Workday-OAuth: OAuth is an authorization protocol, not a connection type for retrieving report data.

D. Workday-SOAP: Workday's SOAP API is being gradually replaced by the REST API and is less focused on report data retrieval than RaaS.

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

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 References:

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.