IDENTITYIQ-ENGINEER practice question 20 of 25

Is this statement true about the Application, Identity, ManageAttribute, Bundle, and Link objects in IdentitylQ? Solution: An Application object is not required to aggregate external user account information into IdentitylQ.

Full set: 121 questions

Domain Onboarding & Correlation

Answer options
A: Yes
B: No Correct answer
Correct Answer:
B. No
Explanation

The statement is false. In SailPoint IdentityIQ, the Application object is a mandatory prerequisite for aggregating account information from any external source. This object serves as the blueprint for the connection, defining the connector type, connection parameters (e.g., host, credentials), and the schema for the data to be imported. The Account Aggregation task, which performs the data loading, must be configured to run against a specific Application object. Without it, IdentityIQ has no knowledge of the target system, how to connect to it, or how to interpret the data it receives.

Why Incorrect

A. Yes: This is incorrect. Aggregation is impossible without an Application object to define the target system and its associated connection and schema details.

References

1. SailPoint IdentityIQ 8.3 Administration Guide, "Chapter 4: Onboarding Applications": This chapter explicitly states, "The first step in bringing data from a new application into IdentityIQ is to define the application in IdentityIQ." This establishes the Application object as the foundational element before any data aggregation can occur.

2. SailPoint IdentityIQ 8.3 Connectors Administration and Configuration Guide, "Introduction to Connectors": The guide explains that a connector is configured within an Application object. It details that "IdentityIQ uses connectors to load (aggregate) data from your native applications into the IdentityIQ repository." This directly links the aggregation process to a configured Application object.

3. SailPoint IdentityIQ 8.3 Technical Whitepaper: The Identity Cube: This document describes the Identity Cube's composition. It explains that Link objects (accounts) are associated with an Application and an Identity. The document's model shows that Links are populated through aggregation from a source system, which is defined in IdentityIQ as an Application. This architectural description confirms the Application object's essential role.

Scroll to Top