Yes, the sets of columns displayed in most tables in the IdentityIQ user interface are controlled by entries in the ColumnConfig elements of the UIConfig object. The UIConfig object in IdentityIQ is responsible for defining various aspects of the user interface, including the configuration of columns that are displayed in tables throughout the application. By modifying the ColumnConfig elements within this object, administrators can customize which columns appear in specific tables, including their order, visibility, and labels.
Therefore, the correct answer is A. Yes.
Reference:
This information is supported by the SailPoint IdentityIQ Configuration Guide, which outlines how UIConfig and ColumnConfig elements are used to control the display of data in the user interface.

In SailPoint IdentityIQ, what users can see and do is indeed partly controlled by their authorized scope. Authorized scopes define the range of objects (such as identities, roles, applications) that a user has access to. Scopes can be applied to limit access based on specific criteria, ensuring that users only interact with the data and functionalities relevant to their role or responsibility within the organization.
For example, a user with access to a specific scope may only view or manage identities within a certain department or geographical location, depending on how the scope is configured.
Therefore, the correct answer is A. Yes.
Reference:
This answer is derived from the SailPoint IdentityIQ Administration Guide, which outlines how scopes are used to manage access control within the platform, influencing both the visibility and actions available to users.

The statement is incorrect. When writing and executing source mapping rules to populate identity attributes, the rule itself does not need to persist the identity attribute to the database. In SailPoint IdentityIQ, once the value for an identity attribute has been calculated by a source mapping rule, IdentityIQ automatically handles the persistence of this attribute to the database as part of the aggregation or provisioning process. The developer does not need to explicitly persist the attribute; this is managed by the system.
Reference:
SailPoint IdentityIQ Source Mapping Guide
SailPoint IdentityIQ Administration Guide (Aggregation and Attribute Mapping Sections)

Syslog is primarily used for logging system events and not for performing complex searches or queries on hierarchical or organizational data like identifying the number of employees that report to a specific person. Such a query would typically require access to the organizational hierarchy or identity data, which is better achieved through IdentityIQ's reporting or search capabilities within the application rather than using Syslog. Syslog captures log events related to system operations, errors, and other activity logs but isn't designed for the type of structured query described in the question.
Reference:
SailPoint IdentityIQ Logging and Monitoring Guide
SailPoint IdentityIQ Administration Guide (Sections on Reporting and Search)

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.
Reference:
SailPoint IdentityIQ Workflow Guide (Handling Workflow and Provisioning Transactions) SailPoint IdentityIQ Administration Guide (Provisioning Tab Limitations)