The statement that the Debug-Logging page does not have to be reloaded when the log4j file is altered while the application server is running is incorrect. In SailPoint IdentityIQ, if you modify the log4j configuration file while the application is running, you generally need to reload the Debug-Logging page to reflect those changes. Without reloading, the page will not display the updated logging configurations, and the changes will not take effect until the application server or the logging system within the server acknowledges those changes.
Therefore, the correct answer is B. No.
Reference:
This information is based on the SailPoint IdentityIQ Debugging Guide, which explains the procedures for making and reflecting changes to logging configurations, particularly using the Debug-Logging page.

Setting the configuration option "Edit Mode: Read Only" on the account attribute would not meet the requirements as specified. The requirement to "Calculate from: Keystore application, responsibility-code attribute" implies that the attribute needs to be dynamically calculated or updated based on another attribute. If the attribute is set to "Read Only," it cannot be modified, which would prevent it from being calculated or updated as needed. Therefore, "Edit Mode: Read Only" should not be used in this scenario.
Reference:
SailPoint IdentityIQ Administration Guide (Sections on Account Attributes and Attribute Calculation) SailPoint IdentityIQ Configuration Guide (Field Properties and Edit Modes)

The statement "All Identity Mappings must use a rule to set the identity attribute" is incorrect. While source mapping rules can be used to populate identity attributes dynamically, it is not mandatory for all identity mappings to rely on a rule. Identity mappings can also be configured using direct mappings, where attributes from a source are directly mapped to IdentityIQ attributes without any rule-based logic.
Therefore, the correct answer is B. No.

The statement suggests moving the XML file into IIQ_HOME/WEB-INF/database as part of the process to import SailPoint XML file objects into IdentityIQ. However, this is not a valid step for importing XML objects.
The correct procedure to import SailPoint XML objects typically involves the following steps:
Use the iiq console command-line tool provided by SailPoint to import the XML file.
The command typically looks like: iiq console import <filename>.xml.
The XML file does not need to be moved to any specific directory like WEB-INF/database for the import process.
Moving the XML file into the WEB-INF/database directory does not align with the documented process and does not facilitate the import. The correct answer is B. No.
Reference:
This answer is based on the official SailPoint IdentityIQ documentation regarding object import procedures, which clearly states that imports should be performed using the IdentityIQ console or through the user interface (for smaller imports).

The scenario describes triggering a workflow when a "Division" attribute changes from a specific value to "Senior IT," but only when the user is a manager. The proposed solution suggests creating a trigger with an event type of "rule" that checks the previous and new values of the "Division" attribute.
However, this approach has a couple of issues:
Trigger Configuration: In SailPoint IdentityIQ, a lifecycle event trigger typically operates on changes in identity attributes, but it's not standard to define this trigger using a rule that directly inspects the previous and new values. Instead, the lifecycle event would usually be configured in the context of the application or identity to directly listen to specific changes without needing to define the logic in a custom rule.
Condition Validation: The condition of checking if the user is a manager should ideally be integrated within the workflow itself or the lifecycle event configuration, not just as part of a rule in the trigger.
While a rule can be used to define complex conditions, the correct way to implement this in IdentityIQ would involve setting up the lifecycle event trigger specifically for the attribute change and managing any additional conditions (like checking if the user is a manager) within the workflow or using an appropriate script/rule in that context.
Therefore, while partially correct in approach, the described solution is not the best practice or a valid process in IdentityIQ, so the correct answer is B. No.
Reference:
This answer is based on the SailPoint IdentityIQ Lifecycle Manager Guide, which provides best practices for configuring lifecycle events and triggers, as well as proper use of rules and workflow triggers in these scenarios.