Important SailPoint IdentityIQ-Associate Exam Questions

Answer: B

Explanation:

This is not a standard example of a policy that can be defined in IdentityIQ. IdentityIQ policies are governance controls used to detect inappropriate access, risky access combinations, account conditions, identity conditions, or activity-related violations based on configured policy logic. Common policy examples include separation of duties policies, account policies, identity policies, risk policies, and activity policies. These policies evaluate identities, accounts, roles, entitlements, attributes, and access relationships to determine whether a violation exists.

The wording ''administrator policy'' is not a standard IdentityIQ policy category. IdentityIQ can audit administrative activity and can secure administrative functions through capabilities, scopes, workgroups, permissions, and object-level controls, but that is different from defining an ''administrator policy'' as a governance policy type. Risky actions performed within IdentityIQ itself are generally handled through audit events, administrative security configuration, logging, and operational monitoring rather than a standard policy definition named administrator policy.

Therefore, this statement does not describe a valid common IdentityIQ policy example. Reference topics: Governance --- examples of common policies, policy detection, policy violations; Foundational Concepts --- common objects and components; Identity Modeling --- IdentityCube attributes and access context.

Answer: A

Explanation:

Yes. In SailPoint IdentityIQ, the Active period is the main review window of a certification campaign. During this period, assigned certifiers review the certification items and make access decisions such as approve, revoke, delegate, allow exception, or otherwise act according to the certification configuration. This is the required operational phase in which reviewers complete their access review responsibilities before the certification moves into later lifecycle stages.

The Active period is distinct from other certification timing or processing stages. For example, generation prepares the certification contents, while challenge and remediation periods may occur after reviewer decisions depending on campaign configuration. The Active period specifically represents the time when certification decisions are expected to be made by the responsible reviewers.

Therefore, the definition is accurate because it correctly identifies the Active period as the required review period for certification decision-making. Reference topics: Governance, access reviews, certification lifecycle, Active period, certification decisions, certifier work items, challenge period, remediation, and certification sign-off.

Answer: A

Explanation:

Yes. The Identity Warehouse in SailPoint IdentityIQ is used to display identity-centered information from the IdentityCube and related IdentityIQ object relationships. In addition to core identity attributes, accounts, roles, entitlements, manager relationships, and direct reports, IdentityIQ can show objects for which the identity is designated as the owner. Ownership is an important governance concept because owners may be responsible for approving access, maintaining roles, reviewing entitlements, managing applications, or participating in certification and remediation processes.

An object owner in IdentityIQ may be associated with configurable objects such as roles, applications, managed attributes, policies, or other governance-related items. Displaying owned objects from the identity view helps administrators and governance users understand the responsibilities assigned to that identity, not just the access held by the identity. This distinction matters because IdentityIQ models both ''what access the identity has'' and ''what governance responsibilities the identity owns.''

Therefore, a list of objects the user owns is appropriately displayed in the Identity Warehouse when ownership relationships exist and the viewer has sufficient permission. Reference topics: Identity Modeling, IdentityCube contents, Identity Warehouse, object ownership, manager relationships, and governance responsibility modeling.

Answer: A

Explanation:

Yes. This is a primary use of the entitlement catalog in SailPoint IdentityIQ. Entitlements aggregated from target applications are often technical values, such as group names, permission codes, directory groups, database roles, or application-specific access identifiers. These values may be meaningful to administrators but unclear to business reviewers, requesters, managers, or access approvers. The entitlement catalog enriches those technical access values with governance metadata, including user-friendly display names, descriptions, ownership, classification, requestability, and other attributes used across IdentityIQ.

This enriched entitlement data improves decision quality in access requests, certifications, and reports. During an access request, a requester can search and select understandable access items. During a certification, a reviewer can make better approve-or-revoke decisions because the entitlement is presented with meaningful business context. In reporting, catalog metadata makes access analysis clearer and more usable for audit and compliance teams.

Therefore, providing user-friendly entitlement display names for access requests, reports, and certifications is a correct entitlement catalog function. Reference topics: Access Modeling --- entitlement catalog purpose; Governance --- certifications and review context; User-Driven Requests --- access request display; Applications --- entitlement aggregation from group/account schemas.

Answer: A

Explanation:

Yes. In SailPoint IdentityIQ, an entitlement represents an access right, permission, privilege, group membership, role membership, or similar access-granting value on an application. Entitlements are discovered from application account data during aggregation and are commonly modeled in IdentityIQ through schema attributes marked as entitlement attributes. Once aggregated, these values may appear in the entitlement catalog as managed attributes, where they can be reviewed, requested, certified, governed by policies, and associated with roles.

The definition ''an access right on an application'' is accurate because entitlements describe what an identity's account is allowed to do or access within a connected system. Examples include Active Directory group membership, database roles, application permissions, cloud groups, or other system-specific access values. IdentityIQ uses entitlements as core governance objects for certifications, access requests, policy checks, role modeling, and provisioning.

This definition is intentionally broad because different target systems represent access differently. IdentityIQ normalizes those application-specific access values into entitlement concepts for identity governance.

Reference topics: Access Modeling, entitlement catalog, managed attributes, application schema, entitlement aggregation, certifications, access requests, and provisioning.

'