今の多士済々な社会の中で、IT専門人士はとても人気がありますが、競争も大きいです。だからいろいろな方は試験を借って、自分の社会の地位を固めたいです。IdentityIQ-Associate認定試験はSailPointの中に重要な認証試験の一つですが、CertShikenにIT業界のエリートのグループがあって、彼達は自分の経験と専門知識を使ってSailPoint IdentityIQ-Associate「SailPoint Certified IdentityIQ Associate Exam」認証試験に参加する方に対して問題集を研究続けています。
| Certification Vendor: | SailPoint |
|---|---|
| Exam Name: | SailPoint Certified IdentityIQ Associate Exam |
| Exam Number: | IdentityIQ-Associate |
| Exam Duration: | 90 minutes |
| Exam Price: | $300 USD |
| Available Languages: | English |
| Certificate Validity Period: | 2 years |
| Related Certifications: | SailPoint Certified IdentityIQ Professional |
| Real Exam Qty: | 60 - 80 |
| Passing Score: | 70% |
| Exam Format: | Multiple Choice, Multiple Select |
| Recommended Training: | IdentityIQ Essentials IdentityIQ Introduction |
| Exam Registration: | SailPoint Identity University |
| Sample Questions: | SailPoint IdentityIQ-Associate Sample Questions |
| Exam Way: | Online proctored exam, available globally |
| Pre Condition: | Recommended completion of 'IdentityIQ Introduction' and 'IdentityIQ Essentials' training courses; no mandatory prerequisites |
| Official Syllabus URL: | https://university.sailpoint.com/sailpoint-certified-identityiq-associate |
>> IdentityIQ-Associate資格試験 <<
SailPointのIdentityIQ-Associate試験に合格することは容易なことではなくて、良い訓練ツールは成功の保証でCertShikenは君の試験の問題を準備してしまいました。君の初めての合格を目標にします。
| トピック | 出題範囲 |
|---|---|
| トピック 1 |
|
| トピック 2 |
|
| トピック 3 |
|
質問 # 40
Is this statement true about group factories and/or populations?
New groups are created as a result of executing a task.
正解：B
解説：
The statement is true. In SailPoint IdentityIQ, group factories are used to generate identity groups dynamically based on identity attribute values or configured grouping logic. A group factory defines the rule or attribute basis for grouping identities, but the actual creation or refresh of the resulting groups occurs when the appropriate task is executed. For example, a group factory might be configured to create groups by department, location, cost center, or business unit. When the task runs, IdentityIQ evaluates identities against the factory definition and creates or updates the corresponding groups.
This differs from populations, which are typically defined sets of identities used for targeting, filtering, reporting, or governance scoping. Group factories are more generation-oriented because they can produce multiple group objects from identity data. The task execution step is important because it materializes the groups so they can be used in IdentityIQ operations.
Therefore, new groups can be created as a result of executing a task tied to group factory processing.
Reference topics: Identity Modeling - groups and populations, group factories, identity grouping, and task- driven group creation.
質問 # 41
Is this statement true for IdentityIQ application definitions?
Correlation logic can be specified for authoritative applications.
正解：B
解説：
Yes. In SailPoint IdentityIQ, correlation logic can be specified for authoritative applications. An authoritative application is commonly used as a trusted source for identity data, such as HR or another system of record. During aggregation, IdentityIQ reads account or source records from the application and uses correlation logic to determine whether each record should be linked to an existing IdentityCube or used in identity creation and update processing.
Correlation logic may be configured using account attributes, identity attributes, or correlation rules. For example, an authoritative source may correlate records by employee ID, user name, email address, or another unique identifier. This ensures that incoming authoritative data updates the correct identity instead of creating duplicates or leaving records uncorrelated.
The authoritative nature of the application does not eliminate the need for correlation. It defines the trust level and identity-data role of the source, while correlation defines how records from that source are matched to identities in IdentityIQ.
Reference topics: Applications, authoritative applications, correlation options, account aggregation, IdentityCube creation, identity attribute mapping, and uncorrelated account resolution.
質問 # 42
Is this a valid reason to grant an identity an IdentityIQ capability?
To give them elevated permissions on a connected application
正解：B
解説：
No. IdentityIQ capabilities are used to control what a user can do inside SailPoint IdentityIQ, not to grant elevated permissions on a connected target application. A capability defines access to IdentityIQ functions such as administration, reporting, certification management, policy management, role management, access request functions, or other internal product features. Capabilities are part of IdentityIQ's internal authorization model and determine which menus, pages, actions, and administrative operations a logged-in IdentityIQ user may perform.
Elevated permissions on a connected application must be granted through governed access, such as requesting or provisioning an account, entitlement, role, or permission on that target system. That process is handled through access requests, approval workflows, provisioning plans, connector operations, and application- specific provisioning policies. For example, adding a privileged group in Active Directory or assigning an administrative application role would be modeled as target-system access, not as an IdentityIQ capability.
Therefore, granting an IdentityIQ capability is appropriate when the user needs additional permissions within IdentityIQ itself, not when they need elevated access on an external connected application. Reference topics:
Identity Modeling - how IdentityIQ access is granted to users; User-Driven Requests - access requests; Provisioning - target application access fulfillment.
質問 # 43
Is this an accurate statement about preventive policy checking in IdentityIQ?
Preventive policy checking can only stop self-service requests.
正解：B
解説：
The statement is false. Preventive policy checking in SailPoint IdentityIQ is not limited only to self-service requests. Preventive policy evaluation is used to identify policy violations before access changes are completed. This can occur during access request processing, provisioning-related activity, or other configured request paths where IdentityIQ evaluates proposed changes against defined policies before allowing the transaction to proceed.
A self-service request is only one possible entry point. IdentityIQ access requests may be submitted by an end user, a manager, an administrator, or another authorized requester depending on QuickLink Population rules, request configuration, and access-request permissions. Preventive policy checking evaluates the requested access change itself, not merely the fact that the request was self-initiated. If the proposed access would violate a separation-of-duty, risk, or other governance policy, IdentityIQ can warn, require additional handling, or block the request depending on policy and workflow configuration.
Therefore, the word "only" makes the statement incorrect. Preventive policy checking is a governance control applied to configured access-change activity, not exclusively to self-service actions. Reference topics:
Governance, policy detection, preventive policy checking, access request policy evaluation, User-Driven Requests, and provisioning request control.
質問 # 44
Does this statement accurately describe how roles are acquired by users in the default role model configuration?
Business roles can only be requested by managers.
正解：B
解説：
No. This statement does not accurately describe role acquisition in IdentityIQ. Business roles are not restricted to being requested only by managers. In IdentityIQ, roles may be acquired through role assignment logic, role detection, access requests, or administrative action, depending on the role configuration and the organization's request model.
A business role commonly represents access associated with a business function, job, department, location, or organizational responsibility. Users may receive business roles automatically when their identity attributes satisfy configured role profiles or assignment rules, typically recalculated during Identity Refresh. Separately, roles may be made requestable through Lifecycle Manager and exposed through QuickLinks, where request eligibility is controlled by QuickLink Populations, request configuration, and workflow rules.
Managers may be allowed to request roles for direct reports, but that is only one possible configuration.
IdentityIQ can also allow users to request roles for themselves, allow delegated requesters to request for others, or restrict requests to specific populations.
Therefore, "only requested by managers" is too narrow and incorrect. Reference topics: Access Modeling, business roles, role assignment, role detection, Identity Refresh, User-Driven Requests, QuickLink Populations, and role request configuration.
質問 # 45
......
IdentityIQ-Associateオンライン試験: https://www.certshiken.com/IdentityIQ-Associate-shiken.html