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

Yes. Identity Attribute Changes are explicitly included among IdentityIQ ' s configurable built-in audit categories. Audit collection is not universally enabled for every possible event because recording large quantities of audit information has storage and performance implications. Administrators therefore select the activities that need to be captured through IdentityIQ ' s Audit Configuration.

SailPoint ' s IdentityIQ documentation lists several categories of auditable actions, including General Actions, Link Attribute Changes, Identity Attribute Changes , Class Actions, and SCIM Resource Actions. The Identity Attribute Changes category includes changes to identity-related information such as assigned roles, capabilities, authorized scopes, controlled scopes, passwords, and potentially configured extended identity attributes. Once the appropriate audit actions are enabled, resulting audit events can be searched through Advanced Analytics using the Audit search type.

This is different from merely enabling general application logging. Audit records provide governance-oriented evidence of defined actions, whereas application/server logging is primarily operational and diagnostic. Consequently, the proposition that built-in IdentityIQ audit functionality supports auditing Identity Attribute Changes is directly supported by the product configuration model.

References/topics: IdentityIQ Engineer — Audit Configuration, Identity Attribute Changes, Audit events, Advanced Analytics Audit search, governance logging.

=======

An Account Group Membership Certification is designed to certify group memberships within accounts, typically focusing on the validation of access within specific account groups (e.g., Active Directory groups).

This type of certification does not directly address the accuracy of role composition or the correctness of entitlements assigned within roles. Since the bank ' s goal is to ensure that all roles include the correct entitlements, an Account Group Membership Certification is not suitable for this purpose.

Thus, the correct answer is B. No.

Placing a QuickLink object directly on a workflow is not a valid step in the development of a custom QuickLink. QuickLinks are used to provide users with easy access to specific tasks or workflows through the IdentityIQ interface, but the QuickLink itself is not embedded within the workflow. Instead, the QuickLink is created as a separate object and associated with the desired workflow or task that it is meant to launch.

The correct approach would involve creating a QuickLink that points to the workflow and then controlling access to the QuickLink by restricting it to a specific QuickLink population (e.g., " Managers " ). Therefore, the correct answer is B. No.

The provided solution does not fulfill the client ' s requirement. Setting " Who can members request for? " to " report to the requester " only limits the request scope to users who directly report to the requester, which does not account for the location attribute. The goal is to restrict requests based on the location attribute, and this specific configuration does not consider that attribute. To achieve the desired behavior, the configuration should include logic that filters users based on the same location as the requester.

Yes. IdentityIQ’s Lifecycle Manager workflows are built from reusable workflow components and subprocesses. Many standard LCM subprocesses can be called from custom workflows, provided the engineer understands the expected input variables, return variables, and control flags. This is a preferred engineering pattern because it avoids rewriting complex provisioning, approval, identity request, policy-checking, or notification logic from scratch. Input variables can alter behavior such as approval routing, provisioning mode, policy checking, notification behavior, target identity, requester, plan handling, and subprocess execution path. However, reuse requires discipline: the custom workflow must pass the correct variables, preserve expected types, and handle returned values correctly. Blindly calling an LCM subprocess without matching its contract can produce broken approvals or provisioning behavior. The proposed statement is therefore true because standard LCM subprocesses are intentionally reusable when controlled through documented workflow variables. References/topics: IdentityIQ Engineer — LCM workflows, subprocess reuse, workflow input variables, provisioning workflows, custom workflow development.

Yes. IdentityIQ role configuration can support conditional role requestability and assignment logic. A role does not have to be universally requestable for every identity. Engineers can restrict role availability through role configuration, assignment logic, population rules, request controls, or related role requirements depending on the implementation design. The proposed solution describes a role that can only be requested if the target user already has a related role. That is a valid access-governance pattern because role models often contain dependency relationships, prerequisites, or related-role structures. For example, a business role may make another IT role or application role meaningful only when the identity already satisfies a prerequisite access condition. This type of restriction prevents users from requesting access that is inappropriate outside a defined role relationship. The important engineering point is that IdentityIQ roles are not just static entitlement containers; they can include assignment rules, profiles, permitted/requestable behavior, and relationships that influence when they are visible or eligible during access requests. References/topics: IdentityIQ Engineer — role model design, requestable roles, role relationships, assignment rules, access-request governance.

Yes. IdentityIQ Debug pages provide administrative access to persisted objects and can support object deletion, including deletion of individual objects and, depending on the view and selection mechanism, bulk deletion of selected objects. This capability is powerful and risky. Engineers must not treat Debug deletion like ordinary UI cleanup because IdentityIQ objects often have dependencies. Deleting a rule, workflow, application, form, task definition, policy, identity, or certification-related object can break references and cause runtime failures. Bulk deletion is especially dangerous because it can remove many objects without the safeguards provided by normal functional pages. The statement is valid from a usability/control perspective, but it should be understood as an administrative capability, not a recommended routine practice. Proper change control, export backups, dependency analysis, and non-production validation are mandatory before deleting objects through Debug. References/topics: IdentityIQ Engineer — Debug-Object page, object deletion, bulk object actions, object dependencies, administrative safeguards.

No. Changing an object’s name and saving it through the Debug pages is not the correct way to create a copy. IdentityIQ objects have internal identifiers, references, metadata, and relationships that are separate from display names or object names. Renaming an object modifies the existing object; it does not create a safe duplicate. For some object types, changing the name can also break references, confuse workflows, disrupt imports, or create governance problems. A proper copy process requires exporting the object XML, removing or regenerating identifiers where appropriate, changing the name intentionally, reviewing object references, and importing it as a new object. Even then, engineers must be careful with dependent objects such as rules, workflows, forms, applications, task definitions, and policies. The Debug pages are powerful but dangerous; they are not a casual object-cloning tool. The proposed method is therefore invalid. References/topics: IdentityIQ Engineer — Debug pages, object XML, object IDs, safe object cloning, configuration migration.

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.

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 is A. Yes.