Can this be achieved using Rapid Setup user interface configuration options?
Solution: Disable an account on a particular application for one set of users and delete the account for another set of users during administrative Terminations.
The Rapid Setup user interface in SailPoint IdentityIQ is designed to simplify and streamline common configuration tasks, particularly during the initial setup of IdentityIQ environments. However, it has certain limitations in terms of granularity and customization.
In this case, the requirement is to disable an account on a particular application for one set of users and delete the account for another set of users during administrative terminations. The Rapid Setup interface does not provide options to differentiate between user groups for different actions (disable vs. delete) within the same termination event.
This level of specificity---applying different actions based on user group membership---would require a more advanced setup, possibly involving custom rules or workflows rather than using the Rapid Setup options. Therefore, the correct answer is B. No.
Reference: This answer is based on the SailPoint IdentityIQ Rapid Setup Guide, which describes the capabilities and limitations of the Rapid Setup interface. The guide indicates that more complex scenarios require customization beyond what Rapid Setup can offer.
Is this a valid step to take when importing SailPoint XML file objects into IdentitylQ?
Solution: Import the XML object through the IdentitylQ console.
Yes, this is a valid step to take when importing SailPoint XML file objects into IdentityIQ. The IdentityIQ console (iiq console) is a command-line tool used for various administrative tasks, including importing and exporting XML objects.
To import an XML object through the IdentityIQ console, the general procedure involves:
Navigating to the IdentityIQ installation directory.
Running the console with the import command:
iiq console import <filename>.xml
The console will process the XML file, importing the defined objects (roles, policies, identity mappings, etc.) into the IdentityIQ database.
This method is officially documented and is a common practice for importing configuration and objects into SailPoint IdentityIQ. Therefore, the answer is A. Yes.
Reference: This explanation is derived from the SailPoint IdentityIQ Administration Guide, which details how to manage XML imports and exports using the IdentityIQ console tool.
Can the following be achieved via configuration of control variables in the out-of-the-box Lifecycle Manager (LCM) workflows?
Solution: Disable all notifications.
Yes, disabling all notifications can be achieved via configuration of control variables in the out-of-the-box Lifecycle Manager (LCM) workflows. In SailPoint IdentityIQ, most workflows, including those in LCM, use control variables to manage various settings, such as whether notifications should be sent. By setting the appropriate control variable (e.g., disabling email notifications) within the workflow configuration, you can effectively suppress all notifications related to that workflow.
Therefore, the correct answer is A. Yes.
Is the following statement true about out-of-the-box reporting?
Solution: In the Reporting user interface, instances of reports are located on the 'My Reports' tab, and templates are located on the 'Reports' tab.
The statement is true. In the SailPoint IdentityIQ Reporting user interface, report templates are located on the 'Reports' tab. These templates define the structure and parameters of reports but do not contain actual report data. Instances of reports, which are the actual generated reports containing data based on the templates, are located on the 'My Reports' tab. The 'My Reports' tab is used for viewing and managing reports that have been generated for a specific user.
SailPoint IdentityIQ Reporting Guide
SailPoint IdentityIQ Administration Guide (Section on Reporting Interface)
Is this statement correct about writing and executing source mapping rules to populate identity attributes?
Solution: The rule type must be IdentityAttribute.
The statement 'The rule type must be IdentityAttribute' is correct. In SailPoint IdentityIQ, when writing a rule that is intended to map or manipulate identity attributes during the aggregation process, the rule type should be set to 'IdentityAttribute'. This ensures that the rule is recognized and executed in the appropriate context for managing identity attributes.
Therefore, the correct answer is A. Yes.
Enola
4 days agoChau
11 days agoTamera
21 days agoAshanti
28 days agoClaudia
1 month agoKallie
2 months agoLai
2 months agoAnnett
2 months agoTiara
2 months agoMicaela
3 months agoGilma
3 months agoDesmond
3 months agoElenora
3 months agoRossana
4 months agoAmber
4 months agoLeonida
4 months agoErick
4 months agoChauncey
5 months agoTiara
5 months agoCheryl
5 months agoTaryn
5 months agoKyoko
6 months agoShayne
6 months agoVincenza
6 months agoKaycee
6 months agoRikki
7 months agoShalon
7 months agoBritt
7 months agoShala
10 months agoVenita
11 months agoTu
12 months agoKanisha
1 year agoAnnmarie
1 year agoAlease
1 year agoDaren
1 year agoRosamond
1 year agoLatosha
1 year agoLarue
1 year agoLatia
1 year agoElvera
1 year agoSheridan
1 year agoXochitl
1 year agoIrma
1 year agoRikki
2 years agoRodolfo
2 years agoLatrice
2 years agoChau
2 years agoGeoffrey
2 years agoIvette
2 years ago