The statement that the application server must be restarted after reloading the logging file through the Debug-Logging page is incorrect. SailPoint IdentityIQ allows you to reload the logging configuration from the Debug-Logging page without restarting the application server. The Debug-Logging page provides a way to dynamically reload the logging settings, including those in the log4j file, so that changes can take effect immediately without the need for a server restart.
Therefore, the correct answer is B. No.
Reference:
This conclusion is supported by the SailPoint IdentityIQ Administration Guide, which details how to use the Debug-Logging page to manage logging settings dynamically without requiring a server restart.

A Workgroup in SailPoint IdentityIQ is a collection of users or identities grouped together for the purpose of task assignment, workflow approvals, or certifications. Workgroups are not typically used for automatically creating multiple groups based on the values of a single identity attribute. To achieve automatic grouping based on identity attributes, you would need to use dynamic roles or possibly rule-based population. These methods allow for creating roles or groups dynamically by evaluating identity attributes and assigning memberships accordingly.
Reference:
SailPoint IdentityIQ Administration Guide (Sections on Workgroups and Dynamic Roles) SailPoint IdentityIQ Configuration Guide (Role Management)

The "Name" configuration option is required when setting up a SCIM 2.0 application in SailPoint IdentityIQ. The "Name" field is a mandatory identifier for the application within IdentityIQ. This name is used throughout the system to reference the application and is critical for configuration, management, and integration processes. Without specifying a name, IdentityIQ cannot properly identify and interact with the SCIM 2.0 application.
Reference:
SailPoint IdentityIQ SCIM 2.0 Application Configuration Guide
SailPoint IdentityIQ Administration Guide (Application Setup and Naming Conventions)

Yes, specifying which access items may be requested can be achieved via configuration of control variables in the out-of-the-box Lifecycle Manager (LCM) workflows. In IdentityIQ, control variables within LCM workflows allow administrators to define the scope and criteria for access requests, including restricting or specifying which entitlements, roles, or applications can be requested by users. This is part of the request configuration process, where the access items that users can see and request are defined.
Therefore, the correct answer is A. Yes.
Reference: This conclusion is drawn from the SailPoint IdentityIQ Lifecycle Manager Guide and Workflow Guide, which provide details on configuring request workflows, including setting up control variables to limit and specify which access items can be requested.

The statement is incorrect. Email templates in SailPoint IdentityIQ are not restricted to just Identity object attributes or methods. They can access attributes and methods of any object passed to the template through its input arguments, including WorkItems, CertificationItems, and others. The template system allows the use of various objects' properties as long as they are properly referenced within the script or template context.
Reference:
SailPoint IdentityIQ Email Templates Guide
SailPoint IdentityIQ API Reference Documentation