In Saviynt EIC, automation of campaigns based on identity changes is typically achieved usingUser Update Rules. These rules monitor changes in user attributes (such as department, role, manager, or status) and can trigger predefined actions when conditions are met.
Option A is correct because aUser Update Rule can be configured to trigger a campaignwhen specific attribute changes are detected. This allows organizations to automatically initiate certification campaigns when critical identity attributes change, ensuring continuous compliance and governance without manual intervention.
Option B is incorrect because connection attributes are primarily used for provisioning and integration logic, not for triggering campaigns. Option C is partially valid in a general sense, but scheduled campaigns do not dynamically react to attribute changes-they run on predefined schedules regardless of changes. Option D is incorrect because Saviynt supports automation through rules.
Thus,User Update Rules provide an event-driven mechanismto launch campaigns based on real-time user attribute changes, making Option A the correct answer.

In Saviynt EIC, job scheduling is managed through theJob Control Panel, which provides flexible options to define when and how jobs such asUser Importare executed. The correct options for scheduling areCRON expressionandbuilt-in schedule options, makingA and Bcorrect.
Option A (CRON expression in Job trigger)allows administrators to define precise scheduling using CRON syntax. For example, scheduling a job at exactly 9 AM every day can be achieved using a CRON expression, offering high flexibility and control.
Option B (Schedule option - Hourly, Weekly, Daily, Minutes)provides a user-friendly way to configure job schedules without writing CRON expressions. Administrators can simply select "Daily" and specify 9 AM, making it easier for standard scheduling needs.
OptionC (Global configuration)is not used for scheduling jobs. OptionD (Externalconfig.properties file)is used for system-level configurations, not job scheduling.
Thus, Saviynt supports both CRON-based and UI-based scheduling mechanisms for job execution.

In Saviynt EIC, retrieving reports such as users and their assigned SAV roles can be achieved through multipleanalytics and reporting mechanisms.
Option A is correct because administrators can createAnalytics using SQL queriesand configure them tosend results via email as attachments, which is useful for scheduled reporting and automated distribution.
Option B is also valid since Analytics allows administrators toexport query results into CSV or Excel formats, enabling offline analysis, auditing, and sharing with stakeholders.
Option C is correct becauseData Analyzerprovides a direct interface to execute SQL queries on the Saviynt database, allowing administrators to quickly retrieve required data without creating a formal analytics job.
Option D (Using enhanced query) is not a standard or recognized reporting method within Saviynt for this use case. While advanced queries can be written, "enhanced query" is not a defined feature or module for report extraction.
Thus, the correct answers areA, B, and C, which represent the primary supported methods for reporting in Saviynt.

The correct answer is B. Technical Rule . Saviynt documentation clearly states that a Technical Rule is primarily used to provision birthright access , also referred to as zero-day provisioning , to users joining the organization based on specified conditions. This is one of the most important distinctions in the Rules and Policies section of the Level 200 syllabus. Technical Rules are intended for automated access assignment logic, especially where access must be granted immediately when user attributes match business conditions such as department, location, or cost center.
The other options are not correct for this use case. User Update Rules are generally used to take actions when user records change and can support lifecycle events, but the documentation identifies Technical Rules as the primary mechanism for birthright provisioning. Scan Rules are used for detection and policy-based scanning use cases, not default access assignment. SAV Role controls platform authorization inside Saviynt rather than provisioning target application access. Saviynt also documents that entitlement assignments in a Birthright Rule can be parameterized using user attributes, which reinforces that Technical Rules are the intended framework for this type of zero-day access automation.

Saviynt'sDuplicate Identity Management (DIM)feature is designed to identify, analyze, and remediate duplicate identities within the Identity Repository, ensuring data integrity and governance. All the listed actions are core capabilities of DIM, makingOption D (All of the Above)the correct answer.
Firstly, DIM enablesduplicate detectionboth during identity import (pre-processing stage) and for already existing identities using detective jobs. This ensures that duplicates are identified proactively and retrospectively. Secondly, DIM provides aside-by-side comparison view, allowing administrators or reviewers to analyze ambiguous duplicate records and decide whether they should be merged. This comparison highlights attribute-level differences for informed decision-making.
Finally, after merging duplicate identities, Saviynt allows administrators todeactivate or retire redundant identities, ensuring only a single authoritative identity remains active. This helps maintain clean identity data and prevents access risks.
Together, these features support identity consolidation, reduce redundancy, and improve overall governance, making DIM a critical component of Saviynt's intelligence and analytics capabilities.