This solution correctly addresses the client ' s requirement. By setting the membership match list to " All " and configuring " Who can members request for? " as " share attributes with the requester, " with the attribute set to location, the system ensures that users in the " Management " workgroup can only request roles and entitlements for other users who share the same location. This setup effectively filters based on the location attribute, aligning with the client ' s needs.

Not all Application objects in SailPoint IdentityIQ must have an Identity object as the owner. While it is common practice to assign an owner to an Application object for governance and administration purposes, it is not a strict requirement. Applications can exist without a direct association to an Identity object. The ownership concept in IdentityIQ is more of a best practice for accountability rather than a mandatory attribute. Refer to the SailPoint IdentityIQ Application Definition Guide for more information on the configuration and management of Application objects.

The statement that " All certifications include generation, the active period, sign-off, and the end period " is true. 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.

SailPoint IdentityIQ Certification Administrator ' s Guide

SailPoint IdentityIQ Certification Process Documentation

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

No. Create Entitlement is not one of the standard IdentityIQ Lifecycle Manager batch request operation types used for bulk access cleanup. The requirement concerns modifying users ' access: some identities need entitlements added while others need excessive access removed. IdentityIQ provides specific batch operations for those tasks.

SailPoint ' s supported batch request operations include Create Identity, Modify Identity, Create Account, Delete Account, Enable/Disable Account, Unlock Account, Add Role, Remove Role, Add Entitlement , Remove Entitlement , and Change Password. “Create Entitlement” does not appear as a standard batch request operation in this list. The distinction is fundamental: an entitlement is a governed access value represented through the application schema and usually as a ManagedAttribute in the Entitlement Catalog. Creating or maintaining that entitlement definition is different from granting an existing entitlement to identities.

For the described regional cleanup, Add Entitlement can repair missing access and Remove Entitlement can revoke excessive access. Therefore, “Create Entitlement” does not represent the appropriate supported batch request type and the proposed solution is false.

References/topics: IdentityIQ Engineer — Lifecycle Manager Batch Requests, AddEntitlement, RemoveEntitlement, ManagedAttribute versus entitlement assignment, bulk remediation.

=======

Yes. CertificationItem is one of the IdentityIQ object areas that can be extended to store client-specific data through the supported extended-object/Hibernate mapping approach. The purpose of updating a corresponding .hbm file is to introduce persistent custom columns or mapped properties into the IdentityIQ database model. For certification use cases, client-specific data may need to be stored with review items, such as additional context, classification values, remediation metadata, or custom review attributes. The extension process must not stop at editing the mapping file. The Word bank’s schema-extension process describes the broader pattern: update the Hibernate mapping, generate the schema update script, apply the script to the IdentityIQ database while the application server is stopped, then start the application server and update the corresponding ObjectConfig. Therefore, CertificationItem is a valid object for this proposed extension approach, provided the engineer follows the full supported schema-extension process. References/topics: IdentityIQ Engineer — object extension, CertificationItem, Hibernate mapping, extended schema, ObjectConfig.

Yes. The IdentityIQ version is essential information when setting up a new sandbox environment. Version affects installation steps, supported Java versions, supported application servers, database compatibility, connector behavior, patch requirements, schema scripts, upgrade paths, and available product features. A sandbox is usually intended to mirror or safely test changes for another environment, so the engineer must know which IdentityIQ version the sandbox should run. Without the version, the engineer could deploy the wrong WAR file, apply incompatible patches, use the wrong schema scripts, or test behavior that does not match production. Version also matters for customizations such as rules, workflows, Quicklinks, UI branding, extended attributes, and connector configuration because APIs and supported patterns can differ between releases. Therefore, IdentityIQ version is not optional background information; it is a core environment-planning input. References/topics: IdentityIQ Engineer — sandbox setup, installation planning, version compatibility, patching, environment parity.

Yes, the text on the login page of IdentityIQ is set through message keys in the message catalog. The message catalog in IdentityIQ contains localized text strings that are used throughout the user interface, including on the login page. By modifying the appropriate message keys in the catalog, you can customize the text that appears on the login page to match the organization ' s branding or messaging requirements.

Therefore, the correct answer is A. Yes.

This implementation is not correct. The requirement is to return all account names for an identity on the application MagicBox, but the code retrieves only a single Link by calling service.getLink(identity, " MagicBox " ). Even worse, the while (link != null) loop never changes the link variable, so if a link is found, the loop becomes infinite and repeatedly adds the same native identity. A correct implementation must retrieve the application object, obtain all matching Link objects for the identity and application, iterate over that list, and add each link’s native identity once. There is also no visible import for ArrayList or List, although BeanShell environments may sometimes tolerate imports differently. The fatal issue remains the flawed loop and single-link retrieval. IdentityIQ account data is represented by Link objects, and multiple accounts may exist for the same identity on the same application depending on connector and policy design. References/topics: IdentityIQ Engineer — IdentityService, Link objects, native identity, BeanShell API usage, account lookup logic.

Yes. This is exactly what the Managed property on an application schema attribute is designed to accomplish. During application configuration, an engineer can mark an account attribute as Managed. When IdentityIQ subsequently aggregates accounts, the distinct values of that attribute can be promoted into ManagedAttribute objects. Those objects are the records represented and governed through the Entitlement Catalog.

SailPoint documentation explicitly states that attributes designated as Managed can be viewed and managed from the Entitlement Catalog . Managed attributes can also receive governance metadata such as an owner, description, display name, and requestable status, and can participate in policies and risk calculations. For example, if an account attribute such as memberOf or groups is managed, the aggregated group values can become individual ManagedAttribute records.

The Entitlement flag and the Managed flag are related but distinct. Entitlement indicates that the attribute represents access that IdentityIQ should track. Managed promotes its values into first-class managed objects and makes them available through the Entitlement Catalog. Therefore the proposed action is valid application-definition configuration.

References/topics: IdentityIQ Engineer — Application Schema, Managed attributes, ManagedAttribute object, Entitlement Catalog, account aggregation.

=======

Yes. When a new IdentityIQ object is created and persisted correctly through the application layer, IdentityIQ can generate the internal object ID upon save. The object ID is the persistent identifier used by the platform and database, while the object name is a separate logical or display identifier. This distinction is important when engineers create or import objects through Debug. A new object should not reuse the ID of an existing object, because that would update or conflict with the existing object rather than create a clean new record. Automatic ID generation is one reason object XML is often edited before import or creation: copied XML must have old IDs removed so IdentityIQ can assign a fresh identifier. The statement is therefore valid, but engineers must still ensure required fields, class type, name uniqueness, and object references are correct before saving. References/topics: IdentityIQ Engineer — Debug-Object page, object persistence, automatic ID generation, object name versus ID, XML import safety.