Free Practice Questions for SailPoint IdentityIQ-Engineer Exam

Based on the goals and scheduling parameters provided, the tasks should be scheduled in the following order to achieve efficient processing for a 24-hour period:

1st Check Expired Work Items (12:00 AM)

This task runs at midnight to check for expired work items. It’s important to run this first to clean up any pending tasks from the previous day.

1st Perform Identity Request Maintenance (2:00 AM)

This maintenance task is scheduled at 2:00 AM, a time when the system is least likely to be under load.

1st Aggregate Employee Authoritative Application (5:00 AM)

The aggregation for the Employee Authoritative application starts early in the day, at 5:00 AM.

1st Aggregate Contractor Authoritative Application (5:10 AM)

The Contractor Authoritative application aggregation is scheduled 10 minutes after the Employee aggregation, as per the goals.

1st Identity Refresh (5:20 AM)

Active Directory aggregation runs next at 5:20 AM.

2nd Aggregate Employee Authoritative Application (12:00 PM)

The second run for the Employee Authoritative application happens at noon.

2nd Aggregate Contractor Authoritative Application (12:10 PM)

At 12:10 PM, the Contractor Authoritative application runs again for its second aggregation.

2nd Identity Refresh (12:20 PM)

The second aggregation for Active Directory happens at 12:20 PM.

1st Aggregate Finance Authoritative Application (8:00 PM)

The Finance application aggregation is scheduled for 8:00 PM, which aligns with the goal of processing it in the evening.

Comprehensive Detailed Explanation with All IdentityIQ Engineer References

Check Expired Work Items (12:00 AM)

This task is run first to ensure any expired or pending work items from the previous day are cleared out and do not interfere with the new day’s tasks. Running it at midnight ensures that any workflows or approvals with expirations are processed efficiently.

Identity Request Maintenance (2:00 AM)

This is a maintenance task that keeps the system running smoothly by managing identity requests. Scheduling it at 2:00 AM minimizes interference with other key business tasks since it's an off-peak hour.

Authoritative Application Aggregations (Employee/Contractor/Active Directory)

The authoritative applications (Employee, Contractor, Active Directory) need to be processed twice a day: once early in the morning and once at noon. Each aggregation must follow the specified order, as it ensures that the data flow is properly managed from the more critical Employee applications to the less frequent Contractor and Active Directory ones.

Finance Application (8:00 PM)

The Finance application is aggregated once a day, in the evening, after other high-priority applications have been processed. This ensures that financial data is up to date for reporting and compliance purposes, without overlapping with the core workday processes.

Defining an application is not a default functionality of the Lifecycle Manager (LCM) module. Application definitions are typically part of the core IdentityIQ platform and are managed through the IdentityIQ Administration module, not Lifecycle Manager. LCM is primarily focused on managing identity lifecycle events, such as onboarding (Joiner), role changes (Mover), and offboarding (Leaver).

Therefore, the correct answer isB. No.

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)

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 "Delete Entitlement" batch request type isnotdesigned for cleaning up access by correcting or updating entitlements in bulk. Instead, "Delete Entitlement" is used to remove specific entitlements from the system entirely, which may not be what is needed if the goal is to correct incorrect entitlements (e.g., removing excess entitlements while adding missing ones). For the scenario described, where users need their entitlements corrected, other batch processes such as "Update Entitlement," "Revoke Access," or specific role re-assignment processes would be more appropriate.

References:

SailPoint IdentityIQ Batch Request Types Documentation

SailPoint IdentityIQ Administration Guide (Entitlement Management Sections)

Yes, the current version and patch level of IdentityIQ can be found through the Debug-About page. The Debug-About page in SailPoint IdentityIQ provides critical information about the system, including the software version, patch level, and other configuration details. This page is a useful resource for administrators to quickly verify the IdentityIQ version and ensure that the correct patches have been applied.

Therefore, the correct answer isA. Yes.

The statement that workflows can be run directly from the Debug-Object page is incorrect. The Debug-Object page in SailPoint IdentityIQ is primarily used for inspecting and interacting with objects within the system, such as viewing their attributes, relationships, and states. However, running workflows is typically done through the IdentityIQ interface under the appropriate sections for workflow management or through the IdentityIQ Console, not directly from the Debug-Object page.

Therefore, the correct answer isB. No.

The statement that "All certifications include generation, the active period, sign-off, and the end period" istrue. These stages are fundamental to the certification process in SailPoint IdentityIQ:

Generation: This is the initial stage where the certification campaign is created. During this phase, the system generates the list of items (such as access, roles, or entitlements) that need to be reviewed.

Active Period: Once the certification is generated, it enters the active period. During this time, the designated reviewers are responsible for examining the items in the certification, making decisions (such as approving or revoking access), and providing any necessary comments.

Sign-off: After the active period, the certification moves into the sign-off stage. Here, the final approver(s) review the decisions made during the active period and formally approve or reject the certification outcomes.

End Period: Finally, the end period marks the conclusion of the certification campaign. The certification is closed, and the results are archived. Any necessary actions, such as revoking access or triggering workflows based on the certification decisions, are implemented.

These stages are essential to the structured process that ensures all access rights are properly reviewed and either maintained or adjusted according to the organization's policies.

References:

SailPoint IdentityIQ Certification Administrator's Guide

SailPoint IdentityIQ Certification Process Documentation

SailPoint IdentityIQ Administration Guide (Sections on Certification Lifecycle and Workflow)

The provided BeanShell code snippet attempts to filter and print the names ofGroupDefinitionobjects owned by "Randy.Knight." However, the code contains a few issues that prevent it from functioning correctly as written:

Class Import: TheGroupDefinitionclass should be imported explicitly at the beginning of the script, which is missing here.

Query Execution: The use ofcontext.getObjectsByNumber(GroupDefinition.class, i)is incorrect. This method does not exist in this context. The correct approach would be to usecontext.getObjects()to retrieve the list of objects and iterate over them.

Looping Logic: The loop logic also contains a flaw. Instead of using a counter-based loop withcontext.getObjectsByNumber(), the recommended approach is to usecontext.search()to retrieve a list of filtered objects and then iterate through the results.

A corrected version of this code would look something like this:

import sailpoint.object.GroupDefinition;

import sailpoint.object.Filter;

import sailpoint.object.QueryOptions;

Filter filter = Filter.eq("owner.name", "Randy.Knight");

QueryOptions qo = new QueryOptions();

qo.addFilter(filter);

List groupDefinitions = context.getObjects(GroupDefinition.class, qo);

for (GroupDefinition group : groupDefinitions) {

System.out.println(group.getName());

}

In this corrected version:

We explicitly importGroupDefinition.

We retrieve the filtered objects withcontext.getObjects(GroupDefinition.class, qo)instead ofgetObjectsByNumber.

Thus, the original code isnot correctas written. The correct answer isB. No.

The statement suggests moving the XML file intoIIQ_HOME/WEB-INF/databaseas part of the process to import SailPoint XML file objects into IdentityIQ. However, this isnota valid step for importing XML objects.

The correct procedure to import SailPoint XML objects typically involves the following steps:

Use theiiq consolecommand-line tool provided by SailPoint to import the XML file.

The command typically looks like:iiq console import .xml.

The XML file does not need to be moved to any specific directory likeWEB-INF/databasefor the import process.

Moving the XML file into theWEB-INF/databasedirectory does not align with the documented process and does not facilitate the import. The correct answer isB. No.