IdentityIQ-Engineer Exam Dumps - SailPoint Identity Security Engineer Questions and Answers

Setting the configuration option "Edit Mode: Read Only" on the account attribute wouldnotmeet the requirements as specified. The requirement to "Calculate from: Keystore application, responsibility-code attribute" implies that the attribute needs to be dynamically calculated or updated based on another attribute. If the attribute is set to "Read Only," it cannot be modified, which would prevent it from being calculated or updated as needed. Therefore, "Edit Mode: Read Only" shouldnotbe used in this scenario.

References:

SailPoint IdentityIQ Administration Guide (Sections on Account Attributes and Attribute Calculation)

SailPoint IdentityIQ Configuration Guide (Field Properties and Edit Modes)

The "Name" configuration option isrequiredwhen 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.

References:

SailPoint IdentityIQ SCIM 2.0 Application Configuration Guide

SailPoint IdentityIQ Administration Guide (Application Setup and Naming Conventions)

Yes, this action can be performed as part of configuring an application definition in IdentityIQ. When defining an application, you can specify provisioning policies, including which users should be provisioned with a basic account as part of a joiner event. This is typically done by setting up account creation rules or provisioning policies that trigger when a new user (joiner) is detected, ensuring they receive the necessary basic accounts and entitlements.

Therefore, the correct answer isA. Yes.

The statement isincorrect. The "For Others" option in the quicklink configuration is used to allow users to perform actions on behalf of other identities (e.g., a manager performing an action for a subordinate). However, setting the quicklink to "For Others" does not make it launch a workflow immediately. To have a quicklink launch a workflow immediately when clicked, you would typically need to configure the quicklink to call the workflow directly, without requiring additional user input. "For Others" is more about the context of the action rather than triggering workflows automatically.

References:

SailPoint IdentityIQ Quicklink Development Guide

SailPoint IdentityIQ Administration Guide (Quicklink and Workflow Configuration)

Yes, disabling all notifications can be achieved via configuration of control variables in the out-of-the-box Lifecycle Manager (LCM) workflows. In SailPoint IdentityIQ, most workflows, including those in LCM, use control variables to manage various settings, such as whether notifications should be sent. By setting the appropriate control variable (e.g., disabling email notifications) within the workflow configuration, you can effectively suppress all notifications related to that workflow.

Therefore, the correct answer isA. Yes.

The statement istrue. In the SailPoint IdentityIQ Reporting user interface, reporttemplatesare located on the "Reports" tab. These templates define the structure and parameters of reports but do not contain actual report data.Instancesof reports, which are the actual generated reports containing data based on the templates, are located on the "My Reports" tab. The "My Reports" tab is used for viewing and managing reports that have been generated for a specific user.

References:

SailPoint IdentityIQ Reporting Guide

SailPoint IdentityIQ Administration Guide (Section on Reporting Interface)

In SailPoint IdentityIQ, certain objects are designed to be extended by updating their corresponding Hibernate Mapping (.HBM) files. However, theWorkItemobject is not one of these extendable objects. TheWorkItemis a system object that primarily represents tasks or actions that need to be processed within the workflow. It is not intended to store client-specific data through direct modification of its .HBM file. Instead, client-specific data should be handled using other mechanisms, such as custom attributes or the extension of Identity or Account objects. Attempting to modify theWorkItemobject's HBM file could lead to unexpected behavior and is not supported by SailPoint's best practices.

References:

SailPoint IdentityIQ Customization Guide

SailPoint IdentityIQ Object Model Documentation

Running the commandiiq extendedSchemain theIIQ_Home/WEB-INF/bindirectory iscorrectand one of the standard procedures for generating database scripts to extend Application attributes in the IdentityIQ database. This command processes the schema definitions (including any new attributes) and generates the appropriate SQL scripts to update the database schema. These scripts can then be executed against the database to apply the changes.

References:

SailPoint IdentityIQ Administration Guide (Schema Extension and Database Management Sections)

SailPoint IdentityIQ Configuration Guide (Extended Schema Management)

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 isB. No.

This solution correctly addresses the client's requirement. By setting the membership match list to "All" and configuring "Who can members request for?" as "share attributes with the requester," with the attribute set tolocation, the system ensures that users in the "Management" workgroup can only request roles and entitlements for other users who share the same location. This setup effectively filters based on the location attribute, aligning with the client's needs.

References:

SailPoint IdentityIQ Quicklink Population Configuration Guide

SailPoint IdentityIQ Attribute-Based Access Control Guide