SailPoint IdentityIQ-Engineer - SailPoint Certified IdentityIQ Engineer

Yes. Domain information is a fundamental connection element when configuring IdentityIQ to interact with Active Directory. Active Directory is organized around forests and domains, and the connector must know the domain context in which user, group, membership, authentication, aggregation, and provisioning operations will occur.

In the IdentityIQ Active Directory connector ' s Domain Settings, the engineer configures the relevant forest and enters the Domain along with the required service-account information and authentication settings. The connector then uses this information to bind to the appropriate Active Directory domain controller environment and manage directory objects in the configured scope.

Specific connector releases also provide conveniences such as forest-level domain discovery or “Manage All Domains,” but these mechanisms do not eliminate the underlying Active Directory domain context. The connector still needs to know which domains it manages, whether they are explicitly configured or discovered under a forest configuration.

For the DOMC proposition as stated, Domain is therefore a required core Active Directory configuration concept, rather than an optional role-modeling or cosmetic application property.

References/topics: IdentityIQ Engineer — Active Directory connector, Domain Settings, forests and domains, service account configuration, connector authentication.

=======

Mail Server Certificate is not a universally required IdentityIQ mail setting for successful SMTP communication. IdentityIQ needs the SMTP host/server information, the SMTP port, and, where required by the environment, authentication details such as username and password, plus TLS/SSL-related settings. A mail server certificate may be relevant in environments using encrypted SMTP where the certificate chain must be trusted by the JVM truststore, but that does not make “Mail Server Certificate” a required IdentityIQ configuration field in every SMTP setup. Many SMTP relay configurations work with host and port only, or with host, port, and credentials. The key engineering distinction is between mandatory connection parameters and optional security/trust configuration. If TLS validation fails, certificate trust may need to be configured at the Java/application-server layer, but it is not the baseline required IdentityIQ mail-server setting. References/topics: IdentityIQ Engineer — email notifications, SMTP configuration, mail host, SMTP port, authentication, TLS/SSL trust configuration.

Yes. An Escalation Rule is designed exactly for this type of certification/access-review handling. In IdentityIQ certifications, an escalation process can be configured so that when a reviewer does not complete required certification work within a defined period, the work item can be escalated, reassigned, or otherwise routed according to business logic. The proposed scenario says that if an access review remains incomplete after 7 days, it should be reassigned to the certifier’s manager. That is a valid escalation pattern because the triggering condition is time-based non-completion, and the action is reassignment to another responsible reviewer. The certifier’s manager can be resolved from the identity relationship and used as the new owner or recipient of the escalated work item. The key point is that escalation rules are not used to generate certifications; they are used to control what happens when review work is overdue or requires escalation. References/topics: IdentityIQ Engineer — certification lifecycle, access review work items, escalation rules, reviewer reassignment.

Here’s how the SailPoint IdentityIQ console commands correspond to their respective functions:

connectorDebug: debug the connector to identify issues in the connector.

source: authenticate to IdentityIQ as another user.

list: list objects.

provision: evaluate and execute a provisioning plan.

Comprehensive Detailed Explanation with All IdentityIQ Engineer References

connectorDebug:

SailPoint IdentityIQ Console Guide (section on connector troubleshooting).

source:

This command allows you to authenticate as another user within the IdentityIQ system. It ' s useful for testing user-specific actions or behaviors without logging out and back in.Reference: SailPoint IdentityIQ Admin Guide (section on user authentication and delegation).

list:

This function returns a list of objects or entities within the system. In IdentityIQ, objects could include applications, roles, policies, and more.Reference: SailPoint IdentityIQ Console Reference Guide (list and query commands).

provision:

The provision command evaluates and executes a provisioning plan. This is the actual process that implements changes in user access across connected systems based on the identity lifecycle event.Reference: SailPoint IdentityIQ Provisioning Guide (execution of provisioning plans).

By matching these commands to their respective functions, the detailed functionalities of IdentityIQ’s console tools are properly understood for administrative and troubleshooting purposes.

No. Out-of-the-box LCM workflow control variables govern the runtime behavior of an LCM process , not the population of users authorized to launch the entry point. Control variables can influence processing such as approvals, notifications, policy checking, provisioning behavior, background/foreground execution, templates, and other workflow decisions.

Determining who can launch an LCM operation belongs at the authorization and QuickLink layer. IdentityIQ commonly controls QuickLink availability through QuickLink populations, capabilities, dynamic scopes, and related visibility or access configuration. Once an authorized user launches the operation, the associated LCM workflow executes using its configured control variables.

This architectural distinction matters. A workflow variable can change what happens after invocation, but it should not be confused with the security mechanism that decides whether a particular identity is permitted to invoke that functionality in the first place.

The question bank itself distinguishes this design layer in related LCM propositions: workflow variables control execution behavior, while application or UI eligibility is configured elsewhere.

References/topics: IdentityIQ Engineer — LCM workflow control variables, QuickLinks, QuickLink populations, capabilities, workflow authorization, dynamic scopes.

=======

Yes. Every configured IdentityIQ application requires a Name because the Application object must have a unique logical identifier within IdentityIQ. The Name is not an Active Directory-specific connector parameter such as a domain controller, service account, or forest; it is a fundamental property of the IdentityIQ Application object itself.

IdentityIQ uses the application name throughout the platform when referencing the configured source or target. Application definitions, aggregation tasks, provisioning plans, rules, certifications, policies, reports, ManagedAttributes, Link objects, and workflow logic can all rely on the application identity. Without a usable application name, IdentityIQ could not reliably distinguish one configured Application object from another.

SailPoint ' s application configuration procedure therefore begins with the Details page and requires the engineer to enter the application Name before configuring connector-specific settings. The application type then determines the additional Active Directory configuration fields that become available.

Thus, regardless of the fact that this application uses the Active Directory connector, Name remains a required configuration option.

References/topics: IdentityIQ Engineer — Application object, Application Definition, Name, connector configuration, Active Directory application onboarding.

=======

Yes. Reviewing provisioning transactions and their processing states is a principal purpose of the Provisioning tab in the IdentityIQ Administrator Console. The engineer can use this administrative view to inspect provisioning activity and distinguish transactions according to states such as pending, failed, or completed/successful.

This visibility is particularly important for troubleshooting asynchronous provisioning. A failed transaction may require investigation into connector errors, target-system responses, invalid attribute values, authentication failures, or workflow/provisioning-plan problems. A pending transaction may indicate queued processing or an operation awaiting further execution. Successful transactions provide confirmation and historical visibility into completed processing.

The Provisioning tab is therefore an operational troubleshooting interface for provisioning transactions; it is not merely a configuration page.

This should also be distinguished from another proposition already present in the Word bank: the bank explicitly states that the Provisioning tab can be used to manually retry the provisioning attempt for pending transactions . The video proposition here tests a different capability—viewing transactions across their various states—so it remains a separate DOMC item.

References/topics: IdentityIQ Engineer — Administrator Console, provisioning transactions, failed provisioning, pending transactions, transaction history, provisioning troubleshooting.

=======

No. This proposed lifecycle sequence does not fit the standard Rapid Setup configuration available for a Mover event. A mover represents a change in an existing identity ' s organizational state—for example, a department, location, position, or other employment change—where access typically needs to be recalculated or adjusted rather than handled as terminating access.

The proposed process instead describes a termination-style account lifecycle: immediately disable an account and subsequently delete that account after a 30-day retention period. That pattern is appropriate to Leaver/termination processing, where access is first blocked and an account may subsequently be removed after a configured retention period.

The distinction is reinforced by the question bank. It already contains a different Mover proposition—“Disable an account and remove all its entitlements on a particular application during Mover events”—and marks that Rapid Setup scenario No. The video proposition changes the operation to delayed account deletion, so it remains a distinct DOMC item rather than a duplicate.

Therefore, standard Rapid Setup Mover configuration does not provide the stated disable-then-delete-after-30-days behavior.

References/topics: IdentityIQ Engineer — Rapid Setup, Mover lifecycle events, Leaver lifecycle events, account disablement, delayed account deletion, lifecycle-event configuration.

The statement " The Identity object is passed to the rule " is correct. When writing source mapping rules to populate identity attributes, the Identity object is indeed passed to the rule. This allows the rule to access and modify attributes on the Identity object based on the logic defined within the rule.

Therefore, the correct answer is A. Yes.

Rapid Setup application onboarding is designed to simplify the initial configuration and does not typically provide advanced configuration options like specifying an account attribute and value filter to identify secondary accounts. Such detailed configurations often require custom scripting or detailed adjustments within the standard application setup, outside of the Rapid Setup interface.

SailPoint IdentityIQ Rapid Setup Guide

SailPoint IdentityIQ Administration Guide (Sections on Application Onboarding and Advanced Account Mapping)