• ホーム
  • ブログ
  • [2025年05月06日] 365日更新、有効なSAVIGA-C01知能問題集 [Q16-Q35]

[2025年05月06日] 365日更新、有効なSAVIGA-C01知能問題集 [Q16-Q35]

Share

[2025年05月06日] 365日更新、有効なSAVIGA-C01知能問題集

ベスト品質のSAVIGA-C01試験問題集でSaviyntテスト高得点を目指そう

質問 # 16
Which of the following Access Request configurations can be set up as either optional or mandatory, based on business requirements?

  • A. Approval comments
  • B. Business justification at Request level
  • C. Add Attachment
  • D. None of the above

正解：A

解説：
In Saviynt's Access Request configurations, the following can be set up as either optional or mandatory based on business requirements:
* A. Approval comments: When an approver approves or rejects a request, they can be required to provide comments, or it can be made optional.
* B. Add Attachment: Requesters can be allowed or required to attach supporting documentation to their access requests.
* C. Business justification at Request level: Requesters can be obligated to provide a business justification for their access request, or it can be made optional.
Here's a breakdown with Saviynt IGA references:
* Saviynt's Access Request System (ARS) Configuration: Saviynt provides granular control over the ARS's behavior, allowing administrators to customize various aspects of the request process, including data validation and required fields.
* Mandatory vs. Optional Fields: Many fields and actions within the ARS can be configured as either mandatory or optional. This allows organizations to tailor the request process to their specific needs and compliance requirements.
* Configuration Locations: These settings are typically found within the ARS configuration section of Saviynt's administrative interface.
* Approval Comments: Often configurable within the workflow definition, at the approval step level. You can define whether comments are required for approval, rejection, or both.
* Add Attachment: Generally found under general ARS settings, allowing you to enable or disable attachments and potentially set them as mandatory.
* Business Justification: Also found within the ARS settings, allowing you to toggle the requirement for a business justification at the request level or even at the individual entitlement level.
* Business Rationale: The flexibility to make these elements optional or mandatory allows organizations to balance the need for information with the desire for a streamlined user experience. For example, high- risk access requests might require detailed justification and attachments, while low-risk requests might not.
* Saviynt's Audit Trail: Regardless of whether these fields are mandatory or optional, Saviynt's audit trail will capture the information provided, ensuring a complete record of the request and approval process.
In summary: Saviynt's ARS allows administrators to configure approval comments, attachments, and business justifications as either optional or mandatory, providing the flexibility to adapt the access request process to meet diverse organizational needs and compliance requirements.


質問 # 17
Which of the following actions is appropriate if the data displayed in the Campaign Preview mode does not meet the requirement?

  • A. Export Campaign
  • B. Activate Campaign
  • C. Check Summary
  • D. Re-configure Campaign

正解：D

解説：
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.


質問 # 18
Jane was managing an AD Group; however, she had to decommission this group and revoke access for all the users.
Which of the following options should be used to perform the above task?

  • A. Entitlement Update Rule
  • B. Mitigation Control
  • C. Entitlement Owner Certification
  • D. Segregation of Duties

正解：C

解説：
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.


質問 # 19
How can a single report be configured to display the account attributes of all the accounts to Application Owners?

  • A. V2 Analytics using SQL Query with Allowed Action
  • B. Use Elasticsearch Query
  • C. V2 Analytics using SQL Query with External Connection
  • D. V2 Analytics using SQL Query with User Context

正解：D

解説：
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.


質問 # 20
Which of the following Account statuses is not considered in a User Manager Campaign certification?

  • A. Manually Provisioned
  • B. Inactive
  • C. Suspended from Import Service
  • D. Manually Suspended

正解：A

解説：
The Account status that is not typically considered in a User Manager Campaign certification in Saviynt is D.
Manually Provisioned. Here's why:
* Saviynt's User Manager Campaign Focus: User Manager Campaigns primarily focus on reviewing and certifying access that is actively managed and tracked within Saviynt.
* Account Statuses and Their Relevance:
* A. Manually Suspended: Indicates an account that has been intentionally disabled within Saviynt. These accounts are often included in reviews to ensure the suspension is still valid.
* B. Inactive: Indicates an account that has not been used for a certain period. These accounts are often included in reviews to determine if they should be disabled or removed.
* C. Suspended from Import Service: Indicates an account that has been suspended due to issues during an import process. These accounts are typically reviewed to resolve the import problem and determine the appropriate account status.
* Manually Provisioned Accounts: These accounts are created directly in the target system, bypassing Saviynt's provisioning processes. As such, they might not be fully tracked or managed within Saviynt.
* Out-of-Band Access: Manually provisioned accounts represent a form of out-of-band access, which is often excluded from standard User Manager Campaigns.
* Separate Review Process: Organizations might have separate processes for reviewing manually provisioned accounts, such as using the RevokeOutOfBandAccessJob or a different type of campaign.
In conclusion: While other account statuses like Manually Suspended, Inactive, and Suspended from Import Service are relevant to access management within Saviynt and are often included in User Manager Campaigns, Manually Provisioned accounts might be excluded because they represent access granted outside of Saviynt's control and might require a different review process.


質問 # 21
Given that an Admin launched a Role Ownership Campaign for you, which of the following options can you not certify?

  • A. Associated Entitlements
  • B. User membership of the Role
  • C. Role Ownership
  • D. Delete Role

正解：C

解説：
Given that an Admin launched a Role Ownership Campaign for you in Saviynt, the option you can not certify is A. Role Ownership. Here's why:
* Saviynt's Role Ownership Campaign: This type of campaign is specifically designed for reviewing and certifying the ownership of roles, not the other aspects of a role.
* Your Role as Certifier: In this scenario, you are the designated reviewer for role ownership. This means you are responsible for confirming who should be the owner of specific roles.
* What You Can Certify in a Role Ownership Campaign:
* Confirm or Change Role Owner: You can confirm that the current role owner is correct or assign a new owner.
* What You Cannot Certify in This Campaign:
* A. Role Ownership: You are the one certifying role ownership, so you cannot certify your own action of assigning an owner. It would be a circular process.
* B. User membership of the Role: This is typically reviewed in a User Access Campaign or a Role Membership Campaign.
* C. Delete Role: Role deletion is an administrative action, not typically part of a Role Ownership Campaign.
* D. Associated Entitlements: Entitlement certification is usually handled in an Entitlement Owner Campaign or as part of a broader User Access Campaign.
In essence: A Role Ownership Campaign focuses solely on validating and assigning role owners. Other aspects of role management, such as user membership or associated entitlements, are handled in different campaign types or through separate administrative actions. As the certifier in this specific campaign, you cannot certify the very action you are performing, which is assigning role ownership.


質問 # 22
________ filters the requestable applications under "Request New Access."

  • A. Access Add Workflow
  • B. Provisioning Connection
  • C. Whom to Request
  • D. Access Query

正解：D

解説：
The component that filters the requestable applications under "Request New Access" in Saviynt is the Access Query. Here's a detailed explanation:
* Saviynt's Access Request System (ARS): As the front end for requesting access, the ARS needs a mechanism to determine which applications (and entitlements) should be displayed to a user as requestable.
* Access Query: This is a powerful feature within Saviynt that allows administrators to define specific criteria to control the visibility of applications and entitlements in the ARS. Think of it as a filter that determines what a user can see and request.
* How Access Queries Work:
* Defined on Applications/Entitlements: Access Queries are configured on individual applications or entitlements within Saviynt.
* Based on User Attributes: They use user attributes (e.g., department, location, job title, group memberships) and other criteria (e.g., risk level) to determine if a user should see a particular application or entitlement.
* Dynamic Filtering: When a user accesses the "Request New Access" section, Saviynt evaluates the Access Queries associated with each application and entitlement in real-time. Based on the user's attributes, the system dynamically filters the list, showing only the applications and entitlements that match the query conditions.
* Saviynt's Security Model: Access Queries are a fundamental part of Saviynt's security model. They ensure that users are only presented with access options that are relevant and appropriate for their role and context, preventing accidental over-provisioning and reducing the attack surface.
* Other Options:
* Access Add Workflow: While essential for processing access requests, the workflow itself doesn't filter which applications are initially displayed.
* Provisioning Connection: This relates to how Saviynt connects to target systems for automated provisioning. It doesn't control the initial visibility of applications in the ARS.
* Whom to Request: This setting might determine the available approvers, but it doesn't filter the list of requestable applications.
In essence: Access Queries act as a dynamic filter, leveraging user attributes and defined criteria to determine which applications and entitlements are presented to a user within Saviynt's "Request New Access" interface, ensuring a personalized and secure access request experience.


質問 # 23
The Max Authentication Session parameter in Single Sign-On settings specifies the maximum duration, in seconds, for which an SSO session will remain valid. The default value is 3600 seconds. If the session logout value defined in IDP is 10,000 seconds and Max Authentication Session in Saviynt SSO is 5000 seconds, how long will the session last?

  • A. 10,000 seconds
  • B. 3600 seconds
  • C. None of the above
  • D. 5000 seconds

正解：D

解説：
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.


質問 # 24
Which of the following bulk operations is not a supported feature?

  • A. Disabling multiple users and their access
  • B. Bulk Request Access Request for multiple users in a single request
  • C. Bulk Approval - Single-click approval for multiple entitlements in a single request
  • D. Deleting multiple users

正解：C

解説：
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.


質問 # 25
The process of Attestation or Certification can be best described as:

  • A. Application Onboarding
  • B. Segregation of Duties
  • C. Access Reviews
  • D. Access Request

正解：C

解説：
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.


質問 # 26
Where can an Admin get the details of a successfully executed Rule?

  • A. Action Trail
  • B. Archived Application Logs
  • C. Current Rule Trail
  • D. Archived Rule Trail

正解：C

解説：
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.


質問 # 27
Which of the following options is part of the Saviynt Identity Repository?

  • A. Users, Accounts, Entitlements, Workflows
  • B. Users, Identity Rules, Workflows, Roles
  • C. Users, User Groups, Workflows, SAV Roles
  • D. Users, Accounts, Entitlements, Roles

正解：D

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


質問 # 28
Which of the following formats is suitable for downloading an Analytics report? (Select all that apply)

  • A. CSV file and Excel Sheet
  • B. Text file
  • C. CSV file only

正解：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.


質問 # 29
A Campaign Owner can create various types of a User Manager Campaign to save different settings for various categories of Manager Access Reviews.

  • A. Campaign Previews
  • B. Campaign Templates
  • C. Campaign Types
  • D. Global Configurations

正解：B

解説：
To save different settings for various categories of Manager Access Reviews within User Manager Campaigns, a Campaign Owner can create C. Campaign Templates. Here's why:
* Saviynt's Campaign Templates: Templates allow you to pre-configure various settings for a campaign and save them as a reusable template. This includes settings related to:
* Campaign Scope: Defining which users, applications, or entitlements are included.
* Certifier Selection: Specifying the type of certifiers (e.g., Managers, Application Owners).
* Scheduling and Notifications: Setting up the campaign schedule and email notifications.
* Advanced Configurations: Including filters, risk scores, and other advanced settings.
* Multiple Templates for Different Categories: A Campaign Owner can create multiple templates, each tailored to a specific category of Manager Access Review. For example:
* Template 1: For high-risk applications, with stricter filters and more frequent reviews.
* Template 2: For low-risk applications, with broader scope and less frequent reviews.
* Template 3: For specific departments or business units, with customized certifier selection.
* Benefits of Using Templates:
* Consistency: Ensures that similar types of reviews are conducted consistently.
* Efficiency: Saves time by eliminating the need to configure each campaign from scratch.
* Reduced Errors: Minimizes the risk of manual configuration errors.
* Why Other Options Are Less Suitable:
* A. Global Configurations: Global configurations apply to all campaigns, not to specific categories of reviews.
* B. Campaign Types: Campaign types (e.g., User Manager, Entitlement Owner) define the overall purpose of the campaign, not the specific settings for different categories within a campaign type.
* D. Campaign Previews: Previews are for reviewing the campaign data before launch, not for saving different configurations.
In conclusion: Campaign Templates in Saviynt provide a powerful way to save and reuse different configurations for various categories of Manager Access Reviews, promoting consistency, efficiency, and accuracy in the certification process.


質問 # 30
Multiple indices can be selected while creating Analytics using the Elasticsearch Query.

  • A. False
  • B. True

正解：B

解説：
It is True that multiple indices can be selected while creating Analytics using the Elasticsearch Query in Saviynt. Here's why:
* Saviynt's Analytics and Elasticsearch: Saviynt's analytics capabilities are often built on top of Elasticsearch, a powerful search and analytics engine.
* Indices in Elasticsearch: In Elasticsearch, an index is like a database table. It's a collection of documents with similar characteristics. Saviynt uses indices to store various types of data, such as user data, account data, entitlement data, and event logs.
* Multi-Index Queries: Elasticsearch allows you to query across multiple indices simultaneously. This is a fundamental feature of the search engine.
* Saviynt's Interface: When creating analytics in Saviynt using Elasticsearch queries, the interface typically allows you to select multiple indices as the data source for your analysis.
* Use Cases: This capability is essential for creating comprehensive analytics that span different data domains. For example, you might want to analyze user access patterns (from one index) in conjunction with application usage data (from another index).
In conclusion: The ability to select multiple indices is a core feature of Elasticsearch and is supported within Saviynt's analytics interface,


質問 # 31
Which of the following objects is available in the User Update Rule to configure Rule conditions?

  • A. Users
  • B. Roles
  • C. Entitlements
  • D. Accounts

正解：A

解説：
The object that is available in the User Update Rule to configure Rule conditions in Saviynt is A. Users.
Here's an explanation:
* User Update Rule Purpose: As mentioned before, User Update Rules are used to automatically update user attributes based on certain conditions.
* Condition Based on User Attributes: The conditions for triggering a User Update Rule are primarily based on attributes of the User object itself.
* Examples of User Attributes: These attributes can include:
* User Status: (e.g., Active, Inactive, Disabled)
* Department:
* Location:
* Job Title:
* Manager:
* Custom Attributes: Any custom attributes defined for users in your Saviynt environment.
* Triggering the Rule: When a user's attributes change, and those changes match the conditions defined in a User Update Rule, the rule is triggered.
* Other Options:
* B. Accounts: While account attributes can be updated as an action of a User Update Rule, the conditions for triggering the rule are typically based on user attributes, not account attributes.
* C. Roles: Similar to accounts, roles can be assigned or removed as an action of a User Update Rule, but the triggering conditions are usually based on user attributes.
* D. Entitlements: Entitlements are also typically managed as an action of a User Update Rule, not as part of the triggering condition.
In conclusion: The User object and its attributes are the primary focus for defining conditions within a Saviynt User Update Rule. Changes to user attributes trigger the rule, which can then perform actions such as updating other user attributes, accounts, roles, or entitlements.


質問 # 32
What is the purpose of a Custom Assignment Workflow block?

  • A. Request must be approved based on any attribute of a user or account, or a custom condition
  • B. Request must be approved by the Application Owner
  • C. None of the above
  • D. Request must be approved by the Role Owner

正解：A

解説：
The purpose of a Custom Assignment Workflow block in Saviynt is A. Request must be approved based on any attribute of a user or account, or a custom condition. Here's a detailed explanation:
* Saviynt's Workflow Flexibility: Saviynt's workflow engine is designed to be highly flexible, allowing organizations to create complex approval processes tailored to their specific needs.
* Standard Approver Types: While Saviynt provides standard approver types like Manager, Role Owner, and Application Owner, there are often scenarios where the approval needs to be routed based on more dynamic or complex criteria.
* Custom Assignment Block: This is where the "Custom Assignment" block comes in. It allows you to define custom logic to determine the approver(s) for a request.
* Attribute-Based Approvals: You can use attributes of the requester, the beneficiary (if different), or even attributes of the requested resource (e.g., application, entitlement) to determine the approver. For example:
* Requests from users in a specific department could be routed to a particular security officer.
* Requests for access to a high-risk application could be routed to a specific risk management team.
* Custom Conditions: You can also define custom conditions using scripting or other logic within the Custom Assignment block. This allows for even greater flexibility in defining the approval routing.
* Example: You might have a condition that checks if the requested entitlement has a certain risk level and, if so, routes the approval to a specific compliance officer.
* Other Options:
* B. Request must be approved by the Role Owner: This is handled by a standard "TASK Access Approve" activity assigned to the Role Owner.
* C. Request must be approved by the Application Owner: Similar to the above, this is a standard approver type.
* D. None of the above: Option A accurately describes the purpose of the Custom Assignment block.
RULES & POLICIES


質問 # 33
ABC Company intends to implement a workflow that involves Saviynt User Group's approval. Which of the following Workflow blocks is appropriate for this implementation?

  • A. TASK Custom Assignment
  • B. CONDITION IF Else
  • C. TASK Access Approve
  • D. Action Prompt

正解：C

解説：
To implement a workflow involving a Saviynt User Group's approval, the appropriate workflow block is B.
TASK Access Approve. Here's an explanation:
* Saviynt's Workflow Engine: Saviynt's workflow engine allows for the creation of complex approval processes using various building blocks or activities.
* TASK Access Approve: This specific activity is designed to handle approval steps within a workflow.
It allows you to define who the approver(s) should be and how the approval should be processed.
* User Group Approval: To implement approval by a Saviynt User Group, you would configure the
"TASK Access Approve" activity as follows:
* Approver Type: You would select "User Group" as the approver type.
* User Group Selection: You would then specify the particular Saviynt User Group that should be responsible for the approval.
* Approval Logic: You can define whether all members of the group must approve, or if a certain number or percentage of approvals is sufficient.
* Saviynt User Groups: User Groups in Saviynt are collections of users, often based on department, role, or other criteria. They are useful for managing access and approvals at a group level.
* Other Options:
* A. CONDITION IF Else: This block is used for branching logic in a workflow, not specifically for assigning approvals to user groups.
* C. Action Prompt: This might be used for displaying information or collecting input, but not for defining an approval step.
* D. TASK Custom Assignment: While you could potentially use custom assignment with scripting to achieve user group approval, the "TASK Access Approve" activity provides a more straightforward and built-in way to do it.
In conclusion: The "TASK Access Approve" workflow block in Saviynt, configured with a User Group as the approver type, is the most appropriate and direct way to implement a workflow that requires approval from a specific Saviynt User Group.


質問 # 34
Accounts, Entitlement types, and Entitlement data of an application are directly associated with:

  • A. Workflows
  • B. Roles
  • C. Security Systems
  • D. Endpoints

正解：D

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


質問 # 35
......

注目すべき時短になるSAVIGA-C01オールインワン試験ガイド：https://www.passtest.jp/Saviynt/SAVIGA-C01-shiken.html

検証された材料は決まってこれ！SAVIGA-C01：https://drive.google.com/open?id=13ZQDWXZ0b2w0suSwZJKIEIc668eJMRAD

関するブログ

もっと
SAVIGA-C01 無料問題集