Saviynt Certified IGA Professional Exam (L100) SAVIGA-C01 Exam Questions

Answer : C

The maximum file attachment limit for a request in Saviynt is typically 10. Here's an explanation:

Saviynt's Access Request System (ARS): The ARS allows users to attach files to access requests to provide supporting documentation or justification.

Attachment Limits: To prevent excessive storage usage and potential performance issues, Saviynt imposes limits on the number and size of attachments allowed per request.

Default Limit: The default maximum number of attachments allowed per request in Saviynt is generally 10.

Configuration: While 10 is the common default, it's worth noting that this limit might be configurable within the ARS settings in some Saviynt deployments. However, significantly increasing this limit could impact performance.

File Size Limit: In addition to the number of attachments, there's also usually a limit on the individual file size and the total size of all attachments combined. This is also generally configurable. These file size limits are important for maintain system stability and performance.

Error Handling: If a user attempts to exceed the attachment limit, Saviynt will typically display an error message, preventing them from submitting the request until the number of attachments is reduced.

Answer : A

The formats suitable for downloading an Analytics report in Saviynt typically include A. CSV file and Excel Sheet. Here's an explanation:

Saviynt's Reporting Capabilities: Saviynt provides options for exporting and downloading analytics reports in various formats to facilitate data sharing and further analysis.

Common Export Formats:

CSV (Comma Separated Values): A widely used format for storing tabular data in plain text. It's easily imported into various data analysis tools and spreadsheet programs.

Excel Sheet (e.g., .xlsx): A popular spreadsheet format that allows for data organization, formatting, and calculations.

Why These Formats Are Suitable:

Data Analysis: Both CSV and Excel formats are well-suited for further data analysis and manipulation.

Reporting: They are commonly used for creating reports and sharing data with stakeholders.

Compatibility: Most data analysis and reporting tools support these formats.

Other Less Common Options: While less frequent, Saviynt might offer other export formats like PDF, depending on the specific version and configuration.

B . Text file: Although technically a text file, a raw .txt export might not be as useful for structured data like analytics reports. CSV would be preferred.

In conclusion: CSV and Excel are the most common and practical formats for downloading analytics reports from Saviynt, offering flexibility for data analysis, reporting, and sharing.

Answer : B

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.

Answer : A

The option that cannot be regarded as a Smart Filter in Saviynt's User Manager and Service Account Campaigns is A. User's Assigned Role counts. Here's why:

Saviynt's Smart Filters: Smart Filters are pre-defined filters in Saviynt that help Certifiers quickly focus on specific access patterns or risk indicators during a certification campaign. They are designed to highlight potentially problematic or high-risk access.

Examples of Smart Filters:

B . Access with SoD Violations: This is a Smart Filter because it highlights access that violates Segregation of Duties policies, a significant risk indicator.

C . Out-of-Band Access for Entitlements: This is a Smart Filter as it identifies access that was granted outside of the normal Saviynt processes, potentially indicating a security risk.

D . Risk Level for Accounts: This is a Smart Filter because it allows Certifiers to focus on accounts with high-risk levels, which might require more scrutiny.

Why 'User's Assigned Role counts' Is Not a Smart Filter:

Not a Risk Indicator: Simply knowing the number of roles assigned to a user doesn't inherently indicate a risk or a specific access pattern that requires attention. A user might have many roles legitimately, or they might have few roles but with high-risk access.

Not Actionable: This information alone doesn't provide enough context for a Certifier to make an informed decision about whether to approve or revoke access.

Alternative: While not a 'Smart Filter', the number of roles assigned could be a data point displayed within the campaign, but it wouldn't be considered a pre-defined filter for highlighting risks.

Answer : A

In Saviynt's SSO setup, the 'Max Authentication Session' parameter determines the maximum duration of an SSO session within Saviynt, overriding any longer durations set by the Identity Provider (IdP).

Session Duration Logic: Saviynt's internal session timeout setting takes precedence over the IdP's session timeout. This ensures that Saviynt can enforce its own security policies regarding session lifetimes.

Why other options are incorrect:

B . 10,000 seconds: This is the IdP's session logout value, but Saviynt's 'Max Authentication Session' setting overrides it.

C . 3600 seconds: This is the default value, but the question specifies a configured value of 5000 seconds.

Saviynt IGA Reference:

Saviynt Documentation: The documentation for configuring SSO settings within Saviynt explains the 'Max Authentication Session' parameter and its impact on session duration.

Saviynt Best Practices: Saviynt's best practices for SSO often recommend aligning session timeouts between the IdP and Saviynt to avoid confusion and potential security gaps.

Answer : B

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.

Answer : A

In Saviynt, Endpoints represent the systems or applications that Saviynt manages. Accounts, entitlement types, and entitlement data are all directly associated with these endpoints because they define how access is structured and granted within those specific systems.

Endpoints as the Foundation: Endpoints are the core objects in Saviynt's identity governance framework. They provide the context for managing access, as all entitlements and accounts exist within the context of a specific endpoint (application or system).

Why other options are incorrect:

Roles: Roles are collections of entitlements, but they are not the primary object that accounts and entitlements are directly linked to.

Workflows: Workflows are processes, not the systems or applications themselves.

Security Systems: While related to security, this term is too broad and doesn't specifically refer to the systems being managed.

Saviynt IGA Reference:

Saviynt Documentation: The section on Application Onboarding and Endpoint Management in Saviynt's documentation clarifies the role of endpoints as the central objects for managing access.

Saviynt User Interface: When configuring applications or systems in Saviynt, you define them as endpoints, and all related accounts and entitlements are managed within that endpoint's context.