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.

* 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.

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

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.

To view the Entitlements Query used in a previously launched Campaign in Saviynt, a Campaign Owner can use the C. Campaign Summary. Here's why:
* Saviynt's Campaign Summary: The Campaign Summary provides a detailed overview of a campaign's configuration, including:
* Campaign Scope: The users, applications, or entitlements included in the campaign.
* Filters and Queries: Any filters or queries used to define the campaign scope, including the Entitlements Query.
* Certifier Information: Details about the assigned certifiers.
* Schedule: The campaign's start and end dates.
* Status: The current status of the campaign (e.g., Active, Completed, Expired).
* Accessing the Entitlements Query: The Campaign Summary typically includes a section that displays the exact query used to select the entitlements included in the campaign.
* Why Other Options Are Less Suitable:
* A. Reconfigure option: While you might be able to see the query by going into the reconfiguration, it's not the most direct way. The Campaign Summary is designed to provide this information readily.
* B. Campaign Export: Exporting the campaign data might include the list of entitlements but not necessarily the original query used to select them.
* D. Export option at the top right corner of the page, next to the Refresh Progress option:
This option typically exports the current view of the campaign data, not the underlying configuration details like the Entitlements Query.
In conclusion: The Campaign Summary in Saviynt is the most direct and convenient place for a Campaign Owner to review the detailed configuration of a campaign, including the Entitlements Query used to define the campaign's scope.