The statement is false. The "Run Rule" feature on the Debug-Object page is not intended for creating, modifying, or deleting SailPoint database objects. Instead, it is used to execute specific rules for testing and debugging purposes. While it allows you to test the logic of a rule by running it in isolation, it does not directly manipulate database objects. For creating, modifying, or deleting database objects, administrators would typically use the appropriate IdentityIQ APIs or database scripts.
Reference:
SailPoint IdentityIQ Administration Guide (Debugging and Rule Management Sections) SailPoint IdentityIQ Developer Guide (Working with Rules and Debugging Tools)

Running the command iiq extendedSchema in the IIQ_Home/WEB-INF/bin directory is correct and one of the standard procedures for generating database scripts to extend Application attributes in the IdentityIQ database. This command processes the schema definitions (including any new attributes) and generates the appropriate SQL scripts to update the database schema. These scripts can then be executed against the database to apply the changes.
Reference:
SailPoint IdentityIQ Administration Guide (Schema Extension and Database Management Sections) SailPoint IdentityIQ Configuration Guide (Extended Schema Management)

Yes, setting the "Source Mappings: Application Rule" configuration on the account attribute is necessary to meet the requirements described. The use case involves flagging privileged accounts based on attributes read from different applications and using these flags in various IdentityIQ features like Advanced Analytics, rule writing, and policy enforcement. By configuring the attribute with a source mapping that uses an Application Rule, you can implement complex logic to derive the attribute's value from multiple sources, such as a financial application and a keystore application, according to the specific requirements.
Therefore, the correct answer is A. Yes.
Reference:
This answer is based on the SailPoint IdentityIQ Implementation Guide, which discusses the use of source mappings and application rules for complex attribute calculations and configurations. The guide explains how to set up attributes that pull data from multiple sources and use this data across various IdentityIQ features.

This solution correctly addresses the client's requirement. By setting the membership match list to "All" and configuring "Who can members request for?" as "share attributes with the requester," with the attribute set to location, the system ensures that users in the "Management" workgroup can only request roles and entitlements for other users who share the same location. This setup effectively filters based on the location attribute, aligning with the client's needs.
Reference:
SailPoint IdentityIQ Quicklink Population Configuration Guide
SailPoint IdentityIQ Attribute-Based Access Control Guide

No, the code snippet provided in the image is incorrect for including a rule library named "Common Rules Library" in a Rule. The correct syntax should reference the sailpoint.object.RuleLibrary class if the intent is to include a Rule Library, as seen in the second image. The first image incorrectly references the sailpoint.object.Rule class, which is not suitable for a rule library inclusion.
Correct Syntax (as shown in the second image):
<ReferenceRules>
<Reference class="sailpoint.object.RuleLibrary" name="Common Rules Library"/>
</ReferenceRules>
Reference:
SailPoint IdentityIQ Rule Library Documentation
SailPoint IdentityIQ Configuration Guide (Rule and Rule Library Management)