SailPoint Updated IdentityIQ-Engineer Exam Questions and Answers by arran

Schedule Policy Composition Certification is not a valid action for handling an individual Account Policy violation. A policy violation owner acts on a violation by making a decision about that violation: allow it, remediate it, mitigate it, or route it according to configured compliance processes. A Policy Composition Certification is a separate governance activity used to review the construction or definition of policies; it is not an immediate action available on a single violation record. The proposed solution also mismatches the policy type. The stem concerns an Account Policy violation, which typically relates to account-count or account-condition rules, not policy-composition review. The Word bank separately identifies Account policies as limiting the number of accounts a user can have on a system. Scheduling a certification might help long-term governance hygiene, but it does not dispose of the current policy violation. References/topics: IdentityIQ Engineer — Account Policy violations, violation owner actions, certification types, policy composition certification, compliance remediation workflow.

When upgrading SailPoint IdentityIQ between releases, it is not necessary to install every version in sequential order between the current version and the target version. SailPoint provides upgrade paths that often allow skipping several major versions by directly upgrading to the desired target version from a supported previous version. However, it is crucial to follow the specific upgrade paths and procedures documented by SailPoint, which may involve intermediate steps or specific considerations depending on the versions involved.

Therefore, the correct answer is B. No.

Yes. IdentityIQ workflow steps support several action types, and both Script and Rule actions execute logic implemented with Java BeanShell.

A Script action contains BeanShell code directly within the workflow step. This is useful for workflow-specific logic that is short or tightly coupled to that business process. In workflow XML, the script may appear inline or inside a nested < Script > < Source > ... < /Source > < /Script > block.

A Rule action also executes BeanShell code, but the code is encapsulated in a reusable IdentityIQ Rule object rather than embedded directly in the workflow. This is preferable when logic needs to be reused, separately maintained, or invoked by multiple workflows or other IdentityIQ components.

IdentityIQ distinguishes these action types from Subprocess , which launches another Workflow object, and Call Method , which invokes a compiled Java method exposed through the IdentityIQ workflow library.

SailPoint ' s workflow documentation explicitly describes Script as executing Java BeanShell code and Rule as executing a reusable workflow Rule containing Java BeanShell code. Therefore, the proposed statement accurately characterizes both action types.

References/topics: IdentityIQ Engineer — Workflow Step actions, Script, Rule, BeanShell, Subprocess, Call Method, Business Process Editor.

Yes. Add Entitlement is an explicitly supported IdentityIQ batch request type and directly addresses the portion of this scenario where users are missing required access. Lifecycle Manager batch requests enable administrators to prepare a comma-delimited file containing multiple access operations and submit those operations for bulk processing instead of manually requesting access identity by identity.

SailPoint documents the operation name as AddEntitlement. The batch file identifies the application, entitlement attribute name, entitlement value, and either the target account ' s native identity or the IdentityIQ identity name. Multiple identities can therefore receive the required entitlement through a controlled batch process. This makes the operation particularly suitable for regional reorganizations, migrations, remediation projects, or other situations where the same access change must be applied across a defined population.

The scenario also states that some users possess excess entitlements. Those items require the complementary Remove Entitlement operation rather than Add Entitlement. A complete cleanup might therefore involve separate add and removal records—or separate files if processing order matters. Nevertheless, Add Entitlement is unquestionably one supported batch request type that helps meet the stated goal.

References/topics: IdentityIQ Engineer — Batch Requests, AddEntitlement, bulk access remediation, Lifecycle Manager, entitlement provisioning.

=======