IdentityIQ-Engineer Exam Dumps - SailPoint Certified IdentityIQ Engineer

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.

=======

The statement that the application server must be restarted after reloading the logging file through the Debug-Logging page is incorrect. SailPoint IdentityIQ allows you to reload the logging configuration from the Debug-Logging page without restarting the application server. The Debug-Logging page provides a way to dynamically reload the logging settings, including those in the log4j file, so that changes can take effect immediately without the need for a server restart.

Therefore, the correct answer is B. No.

The scenario described involves disabling an account and removing all its entitlements on a particular application during Mover events. The Rapid Setup user interface in SailPoint IdentityIQ primarily handles common configurations like enabling or disabling accounts, assigning or unassigning roles, and triggering certifications during lifecycle events.

However, the combination of disabling an account and removing all its entitlements for a Mover event typically involves more detailed configuration that goes beyond the capabilities of the Rapid Setup interface. Achieving this would generally require creating a custom workflow or a specific rule that handles both disabling the account and removing entitlements based on the Mover event triggers.

Thus, the Rapid Setup UI cannot achieve this level of detailed configuration, making the correct answer B. No.

When upgrading SailPoint IdentityIQ between releases, it is not necessary to install every version in sequential order between the current version and the target version. SailPoint provides upgrade paths that often allow skipping several major versions by directly upgrading to the desired target version from a supported previous version. However, it is crucial to follow the specific upgrade paths and procedures documented by SailPoint, which may involve intermediate steps or specific considerations depending on the versions involved.

Therefore, the correct answer is B. No.

Yes. If a user already has an account on an application and needs the ability to request an additional/new account through Manage User Access, the relevant LCM/QuickLink configuration must permit requesting new accounts. The proposed setting, “Allow requesting new accounts,” is specifically aligned with that requirement. Manage User Access and Manage Accounts behavior is controlled through Lifecycle Manager quicklink and population configuration, which determines what actions are visible and available to eligible users. Without enabling new-account requests for the appropriate QuickLink population, the user may only be able to manage existing account access or request entitlements for current accounts, not initiate a new account request on that application. This setting must also align with the application’s provisioning support and account creation policy. The configuration grants the UI/request capability; successful fulfillment still depends on application schema, create policy, approvals, and provisioning workflow. References/topics: IdentityIQ Engineer — LCM, Manage User Access, Manage Accounts QuickLink, QuickLink population, new account request, provisioning policy.

An Application Owner Certification is primarily used to certify entitlements and roles associated with specific applications. It involves application owners reviewing access within their applications, which is useful for ensuring that access aligns with the intended security policies for that application.

However, in the context of ensuring that roles include the correct entitlements across the entire role model, a more suitable certification type would be a Role Composition Certification. This type specifically focuses on validating the composition of roles, including the entitlements they aggregate.

Therefore, an Application Owner Certification will not fully achieve the goal of ensuring all roles include the correct entitlements. The correct answer is B. No.

Yes. Once the custom audit action and report definition have been created and loaded into IdentityIQ, configuring and scheduling the resulting custom report through Intelligence > Reports is a valid step in completing the reporting solution.

IdentityIQ ' s reporting framework exposes standard and custom report definitions through the Reports UI. A report can be opened and configured with the required filters or parameters, saved as an appropriate report instance, executed immediately, or scheduled for future and recurring execution. SailPoint documents that reports can be scheduled to execute once, hourly, daily, weekly, monthly, quarterly, or annually.

For a custom audit-report implementation, this scheduling step logically follows the underlying development work: the custom AuditAction must first be defined, executable logic must actually create AuditEvent records using that action, and a custom report definition must be created that queries the required audit data. Scheduling the report does not replace any of those earlier implementation steps, but it is a legitimate final operational step once the custom report exists.

Therefore, this proposed solution is one valid step toward accomplishing the stated goal.

References/topics: IdentityIQ Engineer — custom AuditEvent reporting, custom TaskDefinition reports, Intelligence > Reports, report scheduling, recurring compliance reporting.

Syslog can be used to identify the details of a system error presented in the UI. When a system error occurs, IdentityIQ typically logs detailed error messages, stack traces, and other relevant information to Syslog or other logging frameworks configured in the environment. By reviewing these logs, an administrator or engineer can identify and diagnose the specific error that was encountered in the UI.

SailPoint IdentityIQ Logging and Monitoring Guide

SailPoint IdentityIQ Administration Guide (Sections on Error Handling and Troubleshooting)