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

No, this statement is incorrect. When a wait step is encountered in a foreground workflow, it does not cause the user's screen to freeze for the specified number of seconds. Instead, the wait step simply pauses the workflow execution for the specified duration, but this is managed in the background. The user interface remains responsive, and the end-user typically won't notice any freezing or delays caused by the wait step itself.
Reference:
SailPoint IdentityIQ Workflow Guide (Section on Workflow Step Types)
SailPoint IdentityIQ Scripting and Workflow Best Practices

Yes, "Terminate Identity" is a default functionality of the Lifecycle Manager (LCM) module. This functionality is associated with the "Leaver" event, which manages the offboarding process for identities that are leaving the organization. The LCM module includes workflows that handle identity termination by deactivating accounts, removing access, and potentially triggering other actions needed to finalize the termination process.
Therefore, the correct answer is A. Yes.

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).

Yes, the statement is true. When editing a step in the Business Process Editor in SailPoint IdentityIQ, the available step actions are Script, Rule, Subprocess, and Call Method. These actions allow for various types of logic and processing to be embedded within workflows. Each of these actions serves different purposes:
Script: Executes a Beanshell script.
Rule: Calls an existing IdentityIQ rule.
Subprocess: Invokes another workflow as a subprocess.
Call Method: Invokes a method on a specified object.
Reference:
SailPoint IdentityIQ Business Process Editor Guide
SailPoint IdentityIQ Administration Guide (Section on Workflow Management)