GoShiken SCAIPリアル試験問題解答は更新された[2026年09月06日]
お手軽に合格させる 最新Saviynt SCAIP問題集には62問があります
Saviynt SCAIP 認定試験の出題範囲：
| トピック | 出題範囲 |
|---|---|
| トピック 1 |
|
| トピック 2 |
|
| トピック 3 |
|
| トピック 4 |
|
| トピック 5 |
|
質問 # 14
Which of the following actions will allow the EIC admin to launch the campaign once the user attributes change?
- A. Schedule a campaign to detect user updates
- B. This cannot be automated and the campaign needs to be launched manually
- C. Configure User Update Rule to trigger the campaign
- D. Configure Trigger Campaign upon update under connection attributes
正解：C
解説：
In Saviynt EIC, automation of campaigns based on identity changes is typically achieved usingUser Update Rules. These rules monitor changes in user attributes (such as department, role, manager, or status) and can trigger predefined actions when conditions are met.
Option A is correct because aUser Update Rule can be configured to trigger a campaignwhen specific attribute changes are detected. This allows organizations to automatically initiate certification campaigns when critical identity attributes change, ensuring continuous compliance and governance without manual intervention.
Option B is incorrect because connection attributes are primarily used for provisioning and integration logic, not for triggering campaigns. Option C is partially valid in a general sense, but scheduled campaigns do not dynamically react to attribute changes-they run on predefined schedules regardless of changes. Option D is incorrect because Saviynt supports automation through rules.
Thus,User Update Rules provide an event-driven mechanismto launch campaigns based on real-time user attribute changes, making Option A the correct answer.
質問 # 15
An EIC Administrator has a requirement to execute provisioning as soon as the user import is completed, what type of job can be configured to achieve this?
- A. WSRetry job
- B. Single Threaded Job
- C. Trigger chain job
- D. Multi threading job
正解：C
解説：
In Saviynt EIC,job orchestration and sequencingare critical for automating identity lifecycle processes such as user import followed by provisioning. To ensure that provisioning starts immediately after user import completes, Saviynt provides the concept of aTrigger Chain Job.
ATrigger Chain Job (Option B)allows administrators to define a sequence of jobs where one job is automatically triggered upon the successful completion of another. In this scenario, once theUser Import Jobfinishes, the system can automatically trigger theProvisioning Job, ensuring seamless and immediate execution without manual intervention or time delays.
Option A (Multi-threading job) relates to performance optimization, not sequencing. Option C (Single Threaded Job) defines execution style but does not control job dependency. Option D (WSRetry job) is used for retrying failed web service calls, not for chaining processes.
Thus,Trigger Chain Jobis the correct approach for automating dependent job execution and is widely used in Saviynt for efficient workflow orchestration.
質問 # 16
What mandatory connection parameters should be configured in order to reconcile accounts using REST Connector? (Multi-Select)
- A. CreateAccountJSON
- B. ConnectionJSON
- C. ImportAccountEntJSON
- D. ImportUserJSON
正解：B、C
解説：
In Saviynt EIC REST connector configuration, account reconciliation (also known as account import or aggregation) requires specific mandatory JSON parameters that define how the system connects to the target application and retrieves account data. The two essential parameters areConnectionJSONandImportAccountEntJSON.
ConnectionJSON (Option A)is mandatory because it contains the core connection details such as base URL, authentication mechanism (OAuth, Basic, etc.), headers, and endpoint configurations. Without this, Saviynt cannot establish communication with the target REST application.
ImportAccountEntJSON (Option B)is also required because it defines the API call used to fetch account (entitlement/account) data from the target system. It includes endpoint URLs, response parsing logic, pagination handling, and mapping rules needed to bring account data into Saviynt.
OptionC (ImportUserJSON)is typically used for identity/user import, not for account reconciliation in REST connectors. OptionD (CreateAccountJSON)is used during provisioning (account creation), not during reconciliation.
Therefore, for account reconciliation using REST connector, the mandatory configurations are ConnectionJSON and ImportAccountEntJSON, as per Saviynt IGA Level 200 connector guidelines.
質問 # 17
Which of the following statements are correct? (Multi-Select)
- A. In the Role mining, if the percentage cut-off = 60%, it would perform mining on only the access which is associated with 100% users
- B. The role mining process discovers relationships between users based on similar access permissions that can logically be grouped to form a role
- C. Duplicate Identity Management can only merge user attributes but not user access
- D. Duplicate Identity Management feature access need to be added to the SAV Role to view the duplicate identity management
正解：B、D
解説：
Statement A is correct becauseRole Miningin Saviynt analyzes user access patterns and identifies relationships between users who share similar entitlements. These patterns are then used to logically group access into roles, enabling efficient role-based access control (RBAC) implementation and reducing manual effort in role creation.
Statement B is incorrect because apercentage cut-off (e.g., 60%)in role mining means that entitlements common to at least 60% of users are considered for role creation-not 100%. The statement incorrectly interprets how threshold-based mining works.
Statement C is correct since access toDuplicate Identity Management (DIM)features is controlled viaSAV Role configurations. Administrators must grant appropriate permissions within SAV roles to allow users to view and manage duplicate identities in the system.
Statement D is incorrect because DIM supports merging not only user attributes but also associated accounts and access depending on configuration. It is not limited to attributes alone.
Thus, the correct answers areA and C.
質問 # 18
What are the different integration options available to integrate Saviynt with ServiceNow?
- A. ServiceNow as a Managed Application
- B. All of the above
- C. ServiceNow as a Ticketing System (ITSM)
- D. ServiceNow as a Request Form
正解：B
解説：
Saviynt EIC provides multiple flexible integration options with ServiceNow to support different business and operational use cases. Therefore,Option D (All of the above)is correct.
ServiceNow as a Managed Application (Option A)allows Saviynt to treat ServiceNow like any other application, enabling account provisioning, deprovisioning, and access governance directly within ServiceNow using REST connectors.
ServiceNow as a Request Form (Option B)enables organizations to leverage ServiceNow's front-end portal for access requests. Users can initiate requests in ServiceNow, which are then processed and fulfilled by Saviynt, ensuring seamless user experience while maintaining governance.
ServiceNow as a Ticketing System (ITSM) (Option C)is another key integration pattern where Saviynt generates tickets (incidents, requests, or tasks) in ServiceNow for approval workflows, provisioning actions, or tracking purposes. This ensures alignment with enterprise ITSM processes.
These multiple integration models provide flexibility, allowing organizations to choose the approach that best fits their operational and governance requirements.
質問 # 19
Schema based account import job failed with Schema definition file not found and No SAV file found. Which of the following could be the possible reasons for the same? (Multi-Select)
- A. SAV file with .sav extension is missing in the File Directory - > SAV files location
- B. datafile (.csv extension) is not present in File Directory - > Data files location
- C. SAV file with .sav extension is missing in the File Directory - > Data files location
- D. SAV file format is incorrect
正解：A、D
解説：
In Saviynt EIC, schema-based account import jobs rely heavily on theSAV file, which acts as the schema definition for interpreting incoming data. The error message"Schema definition file not found and No SAV file found"specifically indicates that Saviynt is unable to locate or process the required SAV file.
Option Ais correct because the SAV file must be placed in the designatedFile Directory # SAV files location.
If the file is missing from this directory, the system cannot read the schema definition, resulting in job failure.
Option Dis also correct because even if the SAV file is present, anincorrectly formatted or corrupted SAV filewill prevent Saviynt from parsing it properly, leading to the same error.
OptionBis incorrect since SAV files are not expected in the Data files directory. OptionCis unrelated to this specific error, as missing CSV files would generate a different error related to missing data, not schema definition.
Thus, the issue is specifically tied to missing or invalid SAV schema files.
質問 # 20
In EIC Service Account Management, when the current owner is terminated, how does EIC identify the new owner?
- A. The new owner is defined in the current owner's user attribute: "Owner On Terminate"
- B. The new owner is identified based on SQL query configured in Global Configuration
- C. The new owner is defined in the Manage Owners Page
- D. The new owner is defined in the Service Account attribute: "Owner On Terminate"
正解：A
解説：
In Saviynt EIC,Service Account Managementincludes mechanisms to ensure continuity of ownership when an account owner leaves the organization. When a user is terminated, the system automatically determines the new owner based on a predefined configuration.
The correct approach is through theuser attribute "Owner On Terminate"(Option B). This attribute is maintained at the user level and specifies who should inherit ownership of service accounts if the current owner is terminated. During the termination process, Saviynt checks this attribute and transfers ownership accordingly, ensuring there is no orphaned service account and maintaining accountability.
Option A is incorrect because SQL queries in Global Configuration are not typically used for ownership reassignment in this context. Option C (Manage Owners Page) is used for manual updates, not automatic reassignment upon termination. Option D is incorrect because the ownership transfer logic is driven by theuser attribute, not a service account attribute.
Thus, using the"Owner On Terminate" user attributeensures automated, policy-driven ownership transitions in Saviynt.
質問 # 21
Which configuration is NOT mandatory when establishing a cascading relationship between two fields in a form?
- A. Set Action String to CHILD###PARENT
- B. Configure Parent Attribute parameter for the child attribute
- C. Ensure that case of Attribute Name of parent field and Parent Attribute of child field should match
- D. Set "What action to perform when Parent attribute changes?" to Mapping
正解：A
解説：
In Saviynt EIC, cascading relationships between form fields are implemented usingDynamic Attributes configuration, where one field (child) depends on the value of another field (parent). Certain configurations are mandatory to ensure proper functionality.
Option A is required because the system must know what action to perform when the parent attribute changes.
Setting it toMappingenables dynamic value population based on parent selection.
Option B is mandatory because theParent Attribute parameterdefines the relationship between parent and child fields. Without this mapping, the system cannot establish dependency.
Option D is also essential since Saviynt configurations arecase-sensitive, and mismatched attribute names will break the cascading logic.
Option C, however, isnot mandatory. TheAction String (CHILD###PARENT)is used in specific advanced scenarios but is not required for standard cascading configurations using mapping and parent attribute settings.
Therefore, the correct answer isC, as it is optional and not required for basic cascading functionality.
質問 # 22
Problem Statement:
Access request approval is not being assigned to the correct approver for a given endpoint.
In this scenario, what configurations will you check? (Multi-Select)
- A. Verify if Delegate is configured for the intended approver
- B. Verify the workflow attached to the corresponding Endpoint to ensure it is correctly configured
- C. Verify the workflow attached to the corresponding Security System to ensure it is correctly configured
- D. Verify the requestor selected the correct approver while submitting the request
正解：A、B、C
解説：
In Saviynt EIC, approval assignment for access requests is primarily controlled throughworkflow configurations, which are associated either at theendpoint level or security system level. Therefore, the first step in troubleshooting incorrect approver assignment is to validate whether the correct workflow is attached and properly configured at both levels (Options A and C). Workflows define approval logic such as manager, owner, or custom approvers, and misconfiguration here often leads to incorrect routing.
Option B is also correct becausedelegation settingscan override the intended approver. If a delegate is configured for an approver, the request may be routed to the delegate instead of the original approver, causing confusion if not validated.
Option D is incorrect because in Saviynt, approvers are typicallysystem-driven based on workflow rules, not manually selected by the requester in most standard configurations. The requester does not usually control approver assignment unless explicitly customized, making this option irrelevant for standard troubleshooting.
質問 # 23
Which option can be used in the REST Connector to perform attribute mapping between target application and EIC?
- A. UpdateAccountJSON
- B. CreateAccountJSON
- C. ImportAccountEntJSON
- D. CreateAccountEntJSON
正解：B
解説：
In Saviynt EIC REST connector configurations,attribute mapping between Saviynt and the target applicationis primarily handled during provisioning operations such as account creation and updates. Among the given options,CreateAccountJSONis the correct configuration where attribute mapping is explicitly defined for provisioning new accounts in the target system.
CreateAccountJSON (Option C)contains the payload structure and field mappings that determine how Saviynt attributes (such as username, email, department, etc.) are translated into the target application's API request format. Administrators define mappings using placeholders and transformation logic to ensure correct data flow from Saviynt to the external system.
OptionA (ImportAccountEntJSON)is used for reconciliation (importing accounts and entitlements), not provisioning. OptionB (CreateAccountEntJSON)is not a standard REST connector configuration in Saviynt.
OptionD (UpdateAccountJSON)is used for modifying existing accounts, but the primary and most commonly referenced mapping configuration for attribute mapping is defined in CreateAccountJSON during initial provisioning.
Thus,CreateAccountJSONis the correct answer for attribute mapping between EIC and the target application.
質問 # 24
For which of the following options duplicate identities can be identified in EIC?
- A. While Importing Users
- B. By running Duplicate Identity Detection Job
- C. All of the above
- D. While Updating Users through Admin > Identity Repository
正解：C
解説：
In Saviynt EIC,Duplicate Identity Management (DIM)supports multiple mechanisms to detect duplicate identities across the identity lifecycle, makingOption D (All of the above)the correct answer.
Firstly, duplicate identities can be detectedduring user import (Option A)when data is ingested from authoritative sources like HR systems. Saviynt can apply matching rules and prevent or flag duplicates at the ingestion stage. Secondly, duplicates can be identified by executing theDuplicate Identity Detection Job (Option B), which is a detective control that scans existing identities in the repository and identifies potential duplicates based on configured correlation rules such as email, username, or employee ID.
Additionally, duplicates may also be identifiedduring manual updates in the Identity Repository (Option C) when administrators modify user attributes. If updated values match existing identities based on defined criteria, Saviynt can flag potential duplicates.
These multiple detection points ensure both proactive and reactive duplicate management, helping maintain identity data accuracy and preventing access risks associated with duplicate identities.
質問 # 25
What are the different actions available while using the Duplicate Identity Management (DIM) feature?
- A. Detect duplicates before importing identities or within existing identities
- B. Perform a side-by-side comparison of ambiguous duplicates
- C. All of the Above
- D. Deactivate the duplicate identity after the merge process
正解：C
解説：
Saviynt'sDuplicate Identity Management (DIM)feature is designed to identify, analyze, and remediate duplicate identities within the Identity Repository, ensuring data integrity and governance. All the listed actions are core capabilities of DIM, makingOption D (All of the Above)the correct answer.
Firstly, DIM enablesduplicate detectionboth during identity import (pre-processing stage) and for already existing identities using detective jobs. This ensures that duplicates are identified proactively and retrospectively. Secondly, DIM provides aside-by-side comparison view, allowing administrators or reviewers to analyze ambiguous duplicate records and decide whether they should be merged. This comparison highlights attribute-level differences for informed decision-making.
Finally, after merging duplicate identities, Saviynt allows administrators todeactivate or retire redundant identities, ensuring only a single authoritative identity remains active. This helps maintain clean identity data and prevents access risks.
Together, these features support identity consolidation, reduce redundancy, and improve overall governance, making DIM a critical component of Saviynt's intelligence and analytics capabilities.
質問 # 26
During a User Import, to define the maximum number of records to be processed in each page, specify the value of the MAX_PAGINATION_SIZE parameter. If this value is not defined, what is the default value?
- A. 0
- B. 1
- C. 2
- D. No default value, it's based on MAX_PAGINATION_SIZE
正解：A
解説：
In Saviynt EIC REST connector configurations, pagination is a critical mechanism used duringuser import (identity reconciliation)to efficiently process large datasets from target systems. The parameterMAX_PAGINATION_SIZEdetermines how many records are fetched and processed per API call (per page).
IfMAX_PAGINATION_SIZEis not explicitly defined, Saviynt uses adefault value of 1000 records per page.
This default is designed to balance performance and system stability. Fetching too many records in a single API call can lead to performance bottlenecks, API timeouts, or memory issues, while too few records can increase the number of API calls and slow down the overall import process.
OptionA (50000)andC (10000)are incorrect because these values are typically too large for default settings and must be explicitly configured if required. OptionBis incorrect because Saviynt does provide a default fallback value rather than leaving it undefined.
Therefore, when MAX_PAGINATION_SIZE is not specified, Saviynt defaults to1000, ensuring efficient and stable data import operations.
質問 # 27
Which among the following are best practices recommended to configure a technical rule in Saviynt Identity Cloud?
- A. Configure Retrofit for all the rules
- B. Use Advanced Configurations
- C. All of the above
- D. Always have user.statuskey = 1 check wherever applicable
正解：C
解説：
In Saviynt EIC,Technical Rulesare essential for automating provisioning, deprovisioning, and enforcing access policies. Following best practices ensures reliability, performance, and governance compliance. Hence, Option D (All of the above)is correct.
Using Advanced Configurations (Option A)allows administrators to implement complex logic, optimize rule execution, and handle sophisticated use cases such as conditional provisioning or attribute-based decisions.
Configuring Retrofit for all rules (Option B)is a recommended practice because it ensures that rules are applied not only to new users but also to existing users. This maintains consistency across the identity repository and prevents access gaps for legacy users.
Including a condition like user.statuskey = 1 (Option C)ensures that rules are applied only to active users.
This avoids unnecessary processing for inactive or terminated users and prevents unintended provisioning actions.
Together, these practices improve rule efficiency, reduce errors, and ensure consistent enforcement of identity governance policies across the organization.
質問 # 28
Which of the following scenarios are True to trigger Technical Rule Execution in EIC? (Multi-Select)
- A. The existing user is updated and satisfies a user update rule with action as Re-run provisioning rules
- B. A new user is registered or created from the UI and the condition in the rule matches
- C. When a user is deleted and the condition in the rule matches
- D. When users are imported through Import Job and the condition in the rule matches
正解：A、B、D
解説：
In Saviynt EIC,Technical Rulesare triggered based on lifecycle events related to user creation, updates, and imports, provided the defined conditions evaluate to true. The correct answers areB, C, and D.
Option Bis correct because duringImport Jobs, when users are brought into Saviynt from authoritative sources, Technical Rules are evaluated, and if conditions match, they are executed. This is a common mechanism for provisioning access during onboarding.
Option Cis also correct since when anew user is created via the UI, Technical Rules can be triggered if the user attributes meet the rule conditions. This ensures consistent provisioning regardless of how users are created.
Option Dis correct because when anexisting user is updated, and a User Update Rule is configured tore-run provisioning rules, it can trigger associated Technical Rules again.
Option Ais incorrect because deletion events typically trigger deprovisioning workflows rather than standard Technical Rule execution.
Thus, Technical Rules are triggered during import, creation, and update events-not deletion.
質問 # 29
In REST connector, under which JSON do you specify the provisioning limit and connection timeout settings?
- A. ConfigJSON
- B. ConnectionJSON
- C. MODIFYUSERDATAJSON
- D. StatusthresholdConfig
正解：B
解説：
In Saviynt EIC REST connector configuration,ConnectionJSONis the central configuration block where all connection-level properties are defined. This includes not only the base URL, authentication details, and headers, but also critical operational parameters such asconnection timeout settingsandprovisioning limits (such as throttling or API limits).
Provisioning activities like account creation, update, and deletion rely on stable connectivity to the target system. Therefore, timeout configurations (for example, connection timeout and read timeout) are defined inConnectionJSONto ensure that API calls do not hang indefinitely and can fail gracefully if the target system is unresponsive. Similarly, provisioning limits-such as maximum records processed or API throttling controls-are configured at this level to manage performance and avoid overloading external systems.
OptionA (ConfigJSON)is not a standard JSON used in REST connector configurations. OptionB (MODIFYUSERDATAJSON)is used specifically for user update operations. OptionD (StatusthresholdConfig) relates to job/status handling rather than connection parameters.
Thus, ConnectionJSON is the correct place for configuring provisioning limits and timeout settings in Saviynt REST connectors.
質問 # 30
......
最新のSCAIP学習ガイド2026年最新の- 提供するのはテストエンジンとPDF：https://www.goshiken.com/Saviynt/SCAIP-mondaishu.html