The statement "The rule type must be IdentityAttribute" is correct. In SailPoint IdentityIQ, when writing a rule that is intended to map or manipulate identity attributes during the aggregation process, the rule type should be set to "IdentityAttribute". This ensures that the rule is recognized and executed in the appropriate context for managing identity attributes.
Therefore, the correct answer is A. Yes.

The proposed solution suggests changing the Email Notification Type to "Redirect to file using FTP protocol" under Global Settings > Configure IdentityIQ Settings > Mail Settings. However, IdentityIQ does not provide an option to redirect emails to a file using the FTP protocol directly through the Global Settings in the application.
Typically, to test generated emails in a non-production environment, you would change the Email Notification Type to "Redirect to File" (if the option is available) or configure an SMTP server with a different setup that captures emails in a file or a specific mailbox designed for testing purposes. The specific steps for testing email generation may vary, but the solution as stated does not align with standard IdentityIQ practices.
Thus, the correct answer is B. No.

A Role Composition Certification is specifically designed to ensure that roles are composed correctly by reviewing the entitlements and other roles they aggregate. This certification allows reviewers to verify whether the roles include the appropriate entitlements based on business needs and compliance requirements.
Given that the bank's objective is to ensure that all roles include the correct entitlements, a Role Composition Certification is the most appropriate tool to achieve this goal. It allows for the comprehensive review and validation of roles and their associated entitlements, ensuring alignment with the overall access governance strategy.
Therefore, the correct answer is A. Yes.

Yes, the current version and patch level of IdentityIQ can be found through the Debug-About page. The Debug-About page in SailPoint IdentityIQ provides critical information about the system, including the software version, patch level, and other configuration details. This page is a useful resource for administrators to quickly verify the IdentityIQ version and ensure that the correct patches have been applied.
Therefore, the correct answer is A. Yes.
Reference:
This answer is based on the SailPoint IdentityIQ Administration Guide, which describes the use and features of the Debug-About page, including how it displays version and patch information.

Yes. Policy checking behavior is one of the areas commonly controlled in LCM request workflows through workflow variables or configuration controlling policy evaluation mode. IdentityIQ can evaluate whether a requested access change would violate configured policies before the request is finalized or provisioned.
Depending on configuration, the system can present policy violations to the requester, block submission, continue with warnings, or require additional approval/mitigation. The proposed behavior - checking whether an access request would violate policies and letting the requester review before submitting - aligns with interactive policy-checking behavior in LCM. This is an execution behavior of the request workflow, not an application schema setting. The engineer must still ensure policies are configured and enabled, but the workflow/control-variable layer can determine how those checks are applied during request submission.
References/topics: IdentityIQ Engineer - LCM workflow control variables, policy checking, request policy violations, interactive policy review, access request governance.