Can the following IdentitylQ object be extended to store client-specific data by updating the corresponding .HBM file?
Solution: Link
Answer : B
In SailPoint IdentityIQ, certain objects, such as the Link object, cannot be directly extended by updating the corresponding .HBM (Hibernate Mapping) file. Modifying or extending core IdentityIQ objects typically requires a deeper level of customization involving the extension of the application schema and possibly custom Java code. The .HBM files are part of IdentityIQ's internal persistence framework, and altering them is not a supported or recommended method for extending objects in a production environment. Customization should instead be done using SailPoint's supported extension points, such as using ManagedAttributes or CustomAttributes within the IdentityIQ application framework. For guidelines on extending IdentityIQ objects, refer to the SailPoint IdentityIQ Customization Guide and best practices documentation.
Top of Form
Bottom of Form
Can the Provisioning tab under "Administrator Console' be used to do the following task?
Solution: Map the associated WorkflowCase to a particular Provisioning Transaction.
Answer : B
No, the Provisioning tab under the 'Administrator Console' is not used to map the associated WorkflowCase to a particular Provisioning Transaction. The Provisioning tab is primarily for monitoring and managing provisioning operations, not for mapping workflow cases to transactions. Such mappings are typically handled within the workflow configuration itself, not through the Provisioning tab.
SailPoint IdentityIQ Workflow Guide (Handling Workflow and Provisioning Transactions)
SailPoint IdentityIQ Administration Guide (Provisioning Tab Limitations)
Can the Provisioning tab under "Administrator Console' be used to do the following task?
Solution: View the specific operations on each attribute being provisioned.
Answer : A
Yes, the Provisioning tab under the 'Administrator Console' in IdentityIQ can be used to view the specific operations on each attribute being provisioned. This tab provides detailed visibility into the provisioning operations, including which attributes are being modified, created, or removed as part of the provisioning process. This is essential for administrators to monitor and troubleshoot provisioning tasks.
SailPoint IdentityIQ Administration Guide (Provisioning Tab Overview)
SailPoint IdentityIQ Provisioning Guide
Can this action be performed as part of configuring an application definition in IdentitylQ?
Solution: Define account correlation via a rule.
Answer : A
Yes, defining account correlation via a rule is an action that can be performed as part of configuring an application definition in SailPoint IdentityIQ. Account correlation rules are often used to determine how accounts from different sources are linked to identities within IdentityIQ. These rules allow for complex logic to be applied when matching accounts to identities, beyond simple attribute matching.
SailPoint IdentityIQ Administration Guide (Section on Account Correlation)
SailPoint IdentityIQ Application Configuration Guide (Using Rules for Account Correlation)
Can this action be performed as part of configuring an application definition in IdentitylQ?
Solution: Specify which users should be provisioned with a basic account as part of a joiner event.
Answer : A
Yes, this action can be performed as part of configuring an application definition in IdentityIQ. When defining an application, you can specify provisioning policies, including which users should be provisioned with a basic account as part of a joiner event. This is typically done by setting up account creation rules or provisioning policies that trigger when a new user (joiner) is detected, ensuring they receive the necessary basic accounts and entitlements.
Therefore, the correct answer is A. Yes.
Is this an example of a mover lifecycle event?
Solution: An employee quits their job and needs all of their accounts disabled.
Answer : B
This scenario describes an employee quitting their job and needing all of their accounts disabled, which aligns with a leaver lifecycle event rather than a mover event. A leaver event typically involves the deactivation of accounts and removal of access for users who are leaving the organization entirely, whereas a mover event involves changes to roles or access as part of an internal transition (e.g., promotion, transfer).
Therefore, the correct answer is B. No.
Is this an example of a mover lifecycle event?
Solution: A contractor whose contract expired and accounts were disabled has a new contract with the company; the contractor needs all of their previous accounts enabled.
Answer : A
Yes, this is an example of a mover lifecycle event. A mover lifecycle event typically occurs when an individual's role or employment status within the organization changes, requiring updates to their accounts and access rights. In this scenario, a contractor whose accounts were previously disabled due to contract expiration needs those accounts re-enabled upon securing a new contract. This reactivation and adjustment of access rights based on a change in employment status fits the definition of a mover event.
Therefore, the correct answer is A. Yes.