An engineer needs to first create a custom audit event and then set up an associated report. What are four steps to accomplish this goal?
Solution: Create a Data Export task.
Creating a custom audit event and setting up an associated report involves steps such as defining the audit event, modifying the audit configuration, and creating a custom report using the SailPoint IdentityIQ reporting framework. Simply creating a Data Export task does not fulfill these requirements. A Data Export task is used for exporting data from IdentityIQ and is unrelated to the creation of custom audit events or custom reports. Refer to the SailPoint IdentityIQ Reporting Guide and the IdentityIQ Audit Framework documentation for more information on correctly creating and configuring custom audit events and reports.
Can the following action be performed using Rapid Setup application onboarding?
Solution: Specify account correlation using a rule.
Specifying account correlation using a rule cannot be performed using the Rapid Setup application onboarding process. Rapid Setup is designed for straightforward and simplified onboarding processes with a focus on quick configuration, typically using predefined templates and options. However, advanced configurations like custom account correlation rules require more detailed setup, typically done outside of the Rapid Setup UI, involving scripting or detailed configuration within the application definition.
SailPoint IdentityIQ Rapid Setup Guide
SailPoint IdentityIQ Administration Guide (Account Correlation and Application Onboarding Sections)
Is this statement valid regarding the control and usability of the Debug pages in IdentitylQ?
Solution: The application server must be restarted after reloading the logging file through the Debug-Logging page.
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.
Is this a default role type that is available in identitylQ?
Solution: Entitlement Role
In SailPoint IdentityIQ, the concept of a 'role' is fundamental to the identity governance framework. The platform supports several default role types that are pre-configured to help organizations manage access effectively. The default role types include:
Business Role: Represents a collection of entitlements necessary for a specific job function within the organization.
IT Role: Aggregates technical entitlements that are typically assigned together, often linked to specific applications or systems.
Application Role: Tied to a specific application, representing roles within that application's context.
Composite Role: A combination of other roles, either business or IT, to form a higher-level role.
The term 'Entitlement Role' is not recognized as a default role type in SailPoint IdentityIQ. While entitlements can be components of roles, 'Entitlement Role' itself is not a predefined role type in the platform. Therefore, the correct answer is B. No.
Reference: This answer is based on the SailPoint IdentityIQ Role Management Guide, which details the standard role types and their usage within the platform. The guide explicitly lists the supported default role types, and 'Entitlement Role' is not among them.
Is this a default functionality of the Lifecycle Manager (LCM) module?
Solution: Terminate Identity
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.