최신SailPoint Certified IdentityIQ Engineer - IdentityIQ-Engineer무료샘플문제
Can the following IdentitylQ object be extended to store client-specific data by updating the corresponding .
HBM file?
Solution: Link
Is this statement valid regarding the control and usability of the Debug pages in IdentityIQ?
Proposed Solution:
Changing an object ' s name and saving the object is the correct way to create a new copy of the object.
An engineer needs to trigger a workflow when a Division attribute changes from IT to Senior IT, but only when the user is a manager.
Is this a valid process that the engineer could use to launch a workflow for a lifecycle event?
Proposed Solution:
Create a trigger with an event type of create.
Can the search type in Identity be used to accomplish this result?
Proposed Solution:
Identifying the number of employees that report to a specific person
Is the following statement true about out-of-the-box reporting?
Proposed Solution:
All out-of-the-box reports in IdentityIQ are stored as TaskDefinition objects.
A customer wants to make changes in their IdentitylQ user interface. Consider branding and other IdentitylQ Ul changes. Is this statement valid?
Solution: The sets of columns displayed in most tables in the IdentitylQ user interface are controlled by entries in the ColumnConfig elements of the UlConfig object.
An engineer is assigned to configure an account attribute. The requirements are:
Purpose: Flag privileged accounts
Read from: Financial application, privileged attribute
Calculate from: Keystore application, responsibility-code attribute
Usage 1: Display as option in Advanced Analytics
Usage 2: Use when writing rules
Usage 3: Include in policies
Does the engineer need to set this configuration option on the account attribute to meet the requirements?
Solution: Edit Mode: Read Only
Is this configuration option required when an engineer sets up any application?
Proposed Solution:
Create Policy
How should an engineer schedule the tasks to most efficiently achieve the following goals?
Goals:
* Process the Employee Authoritative application at 5:00 AM and 12:00 PM.
* Process the Contractor Authoritative application at 5:10 AM and 12:10 PM.
* Process the Active Directory application at 5:20 AM and 12:20 PM.
* Process the Finance application at 8:00 PM.
* Check for expired work items at 12:00 AM.
* Perform identity request maintenance at 2:00 AM.
Schedule parameters:
* Each application aggregation takes anywhere between 30 minutes and 2 hours.
* The run schedule is for a 24-hour period, which begins at 12:00 AM.
Instructions:
* Drag the required tasks from the left into the answer area on the right, and place them in the correct order, starting at 12:00 AM.
* Ordinal numbers (such as 1st, 2nd, and 3rd) in the options indicate which run of the day it is for the task type.
* There will be unused task options.


Explanation:
Based on the goals and scheduling parameters provided, the tasks should be scheduled in the following order to achieve efficient processing for a 24-hour period:
* 1st Check Expired Work Items (12:00 AM)
* This task runs at midnight to check for expired work items. It's important to run this first to clean up any pending tasks from the previous day.
* 1st Perform Identity Request Maintenance (2:00 AM)
* This maintenance task is scheduled at 2:00 AM, a time when the system is least likely to be under load.
* 1st Aggregate Employee Authoritative Application (5:00 AM)
* The aggregation for the Employee Authoritative application starts early in the day, at 5:00 AM.
* 1st Aggregate Contractor Authoritative Application (5:10 AM)
* The Contractor Authoritative application aggregation is scheduled 10 minutes after the Employee aggregation, as per the goals.
* 1st Identity Refresh (5:20 AM)
* Active Directory aggregation runs next at 5:20 AM.
* 2nd Aggregate Employee Authoritative Application (12:00 PM)
* The second run for the Employee Authoritative application happens at noon.
* 2nd Aggregate Contractor Authoritative Application (12:10 PM)
* At 12:10 PM, the Contractor Authoritative application runs again for its second aggregation.
* 2nd Identity Refresh (12:20 PM)
* The second aggregation for Active Directory happens at 12:20 PM.
* 1st Aggregate Finance Authoritative Application (8:00 PM)
* The Finance application aggregation is scheduled for 8:00 PM, which aligns with the goal of processing it in the evening.
Comprehensive Detailed Explanation with All IdentityIQ Engineer References
* Check Expired Work Items (12:00 AM)
* This task is run first to ensure any expired or pending work items from the previous day are cleared out and do not interfere with the new day's tasks. Running it at midnight ensures that any workflows or approvals with expirations are processed efficiently.
* Identity Request Maintenance (2:00 AM)
* This is a maintenance task that keeps the system running smoothly by managing identity requests.
Scheduling it at 2:00 AM minimizes interference with other key business tasks since it ' s an off- peak hour.
* Authoritative Application Aggregations (Employee/Contractor/Active Directory)
* The authoritative applications (Employee, Contractor, Active Directory) need to be processed twice a day: once early in the morning and once at noon. Each aggregation must follow the specified order, as it ensures that the data flow is properly managed from the more critical Employee applications to the less frequent Contractor and Active Directory ones.
* Finance Application (8:00 PM)
* The Finance application is aggregated once a day, in the evening, after other high-priority applications have been processed. This ensures that financial data is up to date for reporting and compliance purposes, without overlapping with the core workday processes.
SailPoint IdentityIQ Scheduler Documentation (section on task scheduling and run-time configuration).
Is this a valid step to take when importing SailPoint XML file objects into IdentitylQ?
Solution: Import the XML object through the IdentitylQ console.