SailPoint Updated IdentityIQ-Engineer Exam Questions and Answers by liya

Yes. This is the classic joiner lifecycle event. The person has not previously been with the company, has now been hired, and needs new access and new accounts. In IdentityIQ Lifecycle Manager terms, a joiner process usually starts from an authoritative-source change such as a new HR record. The process may create or activate the Identity Cube, assign birthright roles, request or automatically provision accounts, calculate policies, trigger approvals, and send notifications. Unlike rehire or reinstatement scenarios, there are no existing disabled accounts to restore. The access model should be built from onboarding rules, role assignment logic, provisioning policies, application create policies, and approval workflows. This is exactly why joiner workflows exist: to standardize new-person onboarding and ensure access is created consistently, securely, and audibly. References/topics: IdentityIQ Engineer — joiner lifecycle event, LCM onboarding, birthright access, account creation, provisioning policy, role assignment.

This statement is correct. The IdentityIQ rule editor is designed to assist engineers when writing BeanShell rules by exposing rule-context information, including available arguments/input variables for the selected rule type. In the editor, variables shown in the arguments list are not decorative; they represent objects or values IdentityIQ makes available to the rule at runtime. Being able to insert an input variable by interacting with the argument list is consistent with the purpose of the rule editor: helping the developer use the correct variable names and avoid spelling or context mistakes. This is especially important because rule arguments differ by rule type. A correlation rule, provisioning rule, workflow rule, and certification rule may each expose different variables. The proposed solution is therefore valid because the Rule Editor can use the rule registry metadata to present available arguments and support insertion into the BeanShell source. References/topics: IdentityIQ Engineer — BeanShell Rule Editor, rule arguments, Rule Registry, input variables, rule development tooling.

Yes, an Escalation Rule can be used to handle the scenario of automatically reassigning parts of an access review to a different certifier. In SailPoint IdentityIQ, Escalation Rules are often employed within certification campaigns to manage situations where a primary certifier has not completed their review within a specified timeframe. The rule can trigger actions such as reassigning the review items to a different certifier, thus ensuring that the certification process continues smoothly without delays.

Therefore, the correct answer is A. Yes.

This is a valid implementation pattern. The workflow requirement has three routing outcomes, and the proposed solution expresses them as three explicit transition elements. The first transition routes to Stop when the approval flag is false, which corresponds to the Reject or back action. The second transition routes to Audit when the comment variable is not null or empty, using sailpoint.tools.Util.isNotNullOrEmpty(comment). That satisfies the condition that the Approve action was used and the returned form field has a value. The final transition to Provision has no condition, making it the default fallback when the prior transition conditions are not satisfied. This is the correct style for workflow routing because the destination steps are explicitly declared through the to attribute, and the conditional routing is attached to each transition rather than relying on an invalid free-form return block. References/topics: IdentityIQ Engineer — workflow transitions, when conditions, script expressions, form approval routing, default workflow transition behavior.