Free and Premium SailPoint Identity-Security-Administrator Dumps Questions Answers

The statement is incorrect. A SaaS-based application does not inherently require a "cloud-based VA." Identity Security Cloud supports SaaS connectors that can connect supported cloud applications directly without requiring the customer to deploy a Virtual Appliance cluster.

SailPoint explicitly states that organizations can use a SaaS connector when they want to upload data to Identity Security Cloud from a source without a Virtual Appliance cluster . In contrast, VA-based connectors are used when direct connector communication must occur from the customer's controlled environment.

Furthermore, a SailPoint VA is not normally a SailPoint-hosted cloud appliance. SailPoint provides the virtual appliance image, but the VA is deployed on infrastructure procured or controlled by the customer. SailPoint manages and updates the appliance software while the customer provides the hosting environment and network connectivity.

Some cloud-hosted applications can still use VA-based connectors depending on network topology and connector design, but being a SaaS application alone does not impose a VA requirement.

Study Guide Reference: Virtual Appliances — VA-Based versus SaaS Connectors, VA Deployment Architecture and Cloud Application Connectivity.

===============

The statement is incorrect. A source in Identity Security Cloud is not primarily a backup-storage repository. A source represents an enterprise system from which Identity Security Cloud obtains account, identity, and access information or to which it performs supported provisioning operations.

SailPoint defines a source as the Identity Security Cloud representation of a third-party enterprise application, database, or directory-management system that maintains its own accounts or personnel records. Connectors are used to interact with those systems so Identity Security Cloud can aggregate accounts and access rights and associate that information with identities.

Examples include Active Directory, HR applications, databases, SaaS platforms, and flat-file feeds. Depending on connector capabilities and configuration, a source can support account aggregation, entitlement aggregation, account creation and modification, enable/disable operations, password management, and entitlement provisioning.

Backup and disaster-recovery functions are separate concerns. Configuration Hub, for example, backs up supported Identity Security Cloud configuration objects , but that does not redefine enterprise sources as backup systems.

Study Guide Reference: Sources — Source Definitions, Connectors, Account and Entitlement Aggregation, Source Management.

===============

The statement is incorrect. Identity Security Cloud does not automatically transfer a departed reviewer's certification responsibilities to that reviewer's manager merely because of the reporting relationship. Certification ownership is explicitly assigned, and the authorized replacement process is reassignment rather than implicit managerial inheritance.

If the original reviewer cannot finish a certification, an administrator can reassign that pending certification to another qualified identity. Identity Security Cloud validates the reassignment to prevent the new reviewer from certifying their own access. A manager can also configure work reassignment for their team members when that functionality is enabled, but that still establishes an explicit reassignment rather than granting the manager unrestricted authority to enter every certification belonging to the employee.

After a campaign deadline, administrators also have campaign-level options for resolving undecided items, including completing the campaign according to the configured maintain-or-revoke behavior.

Therefore, the correct response to a departed reviewer is to use supported reassignment or campaign-completion procedures, not assume the reviewer's manager automatically acquires all pending certifications.

Study Guide Reference: Supporting Governance — Certification Reassignment, Work Reassignment, Campaign Deadlines and Reviewer Responsibilities.

===============

Certificate-based authentication is a valid authentication mechanism for verifying both user and device identities. It relies on Public Key Infrastructure (PKI), in which a trusted Certificate Authority issues a digital certificate containing the subject's public key and identifying information. During authentication, the certificate holder demonstrates possession of the corresponding private key, and the receiving system validates the certificate's trust chain, validity period, revocation status, intended use, and other policy requirements.

This model can authenticate individual users through certificates stored on smart cards, security tokens, or endpoint certificate stores. The same mechanism can authenticate managed computers, servers, and other devices by issuing device-specific certificates. Because the private key does not need to be transmitted to the authenticating service, certificate-based authentication provides stronger resistance to credential theft than reusable passwords when implemented correctly.

The statement therefore accurately describes a recognized authentication method applicable within broader enterprise identity and access-management architectures.

Study Guide Reference: Access Management — Authentication Methods, Certificate-Based Authentication, PKI and Strong Authentication.

===============

Yes. Checking these mapped attributes is a primary troubleshooting action for an Identity Exception. Identity Security Cloud defines User Name (uid) , Work Email (email) , and Last Name (lastname) as required identity attributes. Every identity profile must contain mappings for these attributes, and none of the resulting identity values can be null. User Name carries the additional requirement of being unique across identities in the tenant.

When an authoritative-source account is missing one or more required values during aggregation, Identity Security Cloud generates an Identity Exception instead of creating the identity normally. A duplicate User Name can also produce an exception. The administrator should therefore inspect the Identity Exceptions report, identify which required attribute is absent or invalid, and verify the corresponding source-account data and identity-profile mappings.

SailPoint's documented remediation is to correct the problematic source information and then aggregate the source again, either manually or through the next scheduled aggregation. If direct mapping cannot generate a required value, a transform or supported rule can derive it.

Study Guide Reference: Identity and Lifecycle Management — Identity Profiles, Required Identity Attributes, Identity Exceptions and Attribute Mappings.

===============

Resetting the source and re-aggregating users is not the appropriate initial remediation. Aggregation is primarily an inbound data collection process: it reads account information from the source into Identity Security Cloud. It does not, by itself, perform the outbound disable operation that should occur when an identity enters the Terminated lifecycle state.

The administrator should first verify that the affected identities actually entered the expected lifecycle state and that the Terminated lifecycle-state configuration specifies that the database source account is to be disabled. SailPoint allows a lifecycle state to enable, disable, or delete accounts on selected sources. The source must also support the required account-disable operation.

The administrator should then review provisioning/account activity for failures and validate that provisioning is enabled and operating correctly for the database connector. Re-aggregation could later be useful to confirm the source's actual account state, but resetting the entire source is unnecessarily disruptive and does not correct the root cause of a failed lifecycle provisioning operation.

Therefore, the proposed troubleshooting action does not directly address why the Terminated lifecycle event failed to disable the account.

Study Guide Reference: Provisioning — Lifecycle-State Provisioning, Account Disable Operations, Provisioning Troubleshooting and Source Aggregation.

===============

The statement correctly describes Identity Security Cloud's default self-approval prevention behavior when the requester is assigned as an individual reviewer . SailPoint does not normally permit a person to approve their own access request. This applies whether the request is submitted directly for themselves or whether the affected access recipient otherwise appears as a reviewer in the approval sequence.

When the requester or recipient is assigned an approval directly as an individual, Identity Security Cloud automatically reassigns that review responsibility to the individual's manager . If a valid manager is unavailable, the system can continue through alternative fallback mechanisms, eventually reaching an administrator when necessary.

There is an important distinction for Governance Groups: if the requester belongs to a Governance Group configured as reviewer, the requester is normally omitted while other group members remain eligible to approve. Only when that user is effectively the group's sole valid reviewer does manager reassignment occur.

An optional API setting can permit auto-approval for individual reviewers, but the default behavior described by the scenario is manager reassignment.

Study Guide Reference: Access Management — Preventing Self-Approval, Approval Reassignment, Manager Review and Access Request Governance.

===============

The statement correctly describes the standard escalation behavior represented by the access-request escalation model. Identity Security Cloud can automatically escalate an approval when the assigned reviewer fails to act within the configured timeframe. This prevents an access request from remaining indefinitely with an unavailable or unresponsive approver.

Under the standard escalation pattern, the first and second escalations can route the request to successive manager levels of the assigned reviewer. The third escalation routes the approval to the configured fallback approver. Administrators control escalation timing, frequency, escalation reviewers, and fallback behavior through approval settings. This mechanism operates alongside reminder notifications and request timeout controls.

The fallback approver is particularly important because it provides a final governance path when ordinary escalation cannot resolve the request. SailPoint's current documentation explicitly describes the first two manager escalations followed by a third escalation to the fallback approver when custom approval settings are not configured.

Study Guide Reference: Access Management — Access Requests, Global Reminder and Escalation Policy, Approval Escalation and Fallback Approvers.

===============

The statement is incorrect because Governance Groups are not restricted to serving only as the primary owner of a Separation of Duties policy. Identity Security Cloud provides multiple ownership and governance assignments within SoD policy configuration.

For the Policy Owner , an administrator can select either an individual identity or a Governance Group. A policy can additionally have up to ten co-owners, and those co-owners may also include individuals or Governance Groups. Furthermore, the Violation Owner —the party responsible for handling violations generated by the policy—can be configured as an individual, an identity's manager, a Governance Group, or no explicitly selected owner, in which case responsibility can fall to the policy owner. SailPoint's current policy configuration documentation explicitly identifies these distinct ownership options.

Governance Groups are also used outside SoD policies. They can participate in access-request approvals, source ownership/governance, certification-related responsibilities, and scoped administration.

Therefore, saying Governance Groups can only be assigned as policy owners incorrectly limits their supported governance functions.

Study Guide Reference: Supporting Governance — Governance Groups, SoD Policy Ownership, Co-Owners and Violation Ownership.

===============

The statement is explicitly incorrect. Identity Security Cloud allows users to hold multiple User Levels in many circumstances, and permissions from compatible User Levels are cumulative. However, SailPoint defines several combinations that cannot be assigned simultaneously because their delegated administrative scopes conflict.

One of the specifically prohibited combinations is Role Admin and Source Sub-Admin . SailPoint's User Level documentation lists this pair among the User Levels that cannot coexist on the same user. Other prohibited combinations include Role Sub-Admin with Source Admin, Role Sub-Admin with Role Admin, and Source Sub-Admin with Source Admin.

The distinction is important. A Role Admin has broad role-management privileges, whereas a Source Sub-Admin receives scoped administrative capabilities based on Governance Group associations with particular sources. Combining certain global and scoped administrative models could create inconsistent authorization behavior, so SailPoint prevents those assignments.

Administrators should therefore consult the User Level compatibility matrix before granting multiple elevated permissions rather than assuming that every User Level can be stacked.

Study Guide Reference: Platform — User Level Permissions, User Level Compatibility, Role Admin and Source Sub-Admin.

===============

The statement is too absolute. Identity Governance and Administration platforms substantially automate and streamline access governance processes, but they do not necessarily eliminate human judgment or fully automate every review, approval, and audit activity.

For example, an IGA platform can automatically generate access certification campaigns, identify the access requiring review, notify reviewers, record their decisions, perform supported remediation, and produce audit evidence. However, designated managers, application owners, source owners, or other certifiers are still commonly required to decide whether individual access should be retained or revoked. SailPoint describes certifications as processes in which designated certifiers review users' access and explicitly approve or revoke it.

Similarly, approval workflows automate routing and enforcement but can still require human authorization. Audit functionality generates searchable events, reports, and evidence, while auditors and compliance professionals still assess whether the organization's controls satisfy applicable requirements.

SailPoint describes IGA as streamlining certification and audit processes by automating reviews, notifications, and audit-ready reporting—not as eliminating every human governance decision.

Study Guide Reference: General knowledge for Identity Security Administrators — Identity Governance and Administration, Access Reviews, Approvals, Audit and Governance Automation.

===============

Yes. Identity Security Cloud identity profiles support stronger verification for password-reset and account-unlock operations. When two-factor authentication is enabled for these functions, users must successfully complete two configured identity-verification methods before Identity Security Cloud permits the password reset operation. SailPoint explicitly documents this behavior under the identity profile's Password Reset and User Unlock settings.

Available verification methods can include a verification code or call to a configured phone number, a verification message delivered to an email address, security questions, Helpdesk-provided codes, or supported external MFA integrations. Administrators must ensure that the underlying identity attributes—such as phone numbers and email addresses—contain valid data when those methods are selected.

This password-reset authentication control should be distinguished from the Multifactor Authentication Sign-In Method , which uses an authenticator application to protect normal Identity Security Cloud sign-in. Both mechanisms strengthen authentication, but they protect different stages of account access.

Study Guide Reference: Access Management — Identity Profile Security Settings, Two-Factor Authentication, Password Reset and User Unlock Methods.

===============

The statement is valid. A Governance Group is intended to provide a collection of identities that can make governance decisions about access. If the group has no valid members, there is nobody within that group who can perform the required approval action.

SailPoint explicitly states that before a Governance Group reviews access, it must be configured and have members . When the Governance Group's turn arrives during an access request or certification, its members receive notification and any eligible member can act on behalf of the group.

Identity Security Cloud has fallback and reassignment mechanisms for situations where reviewers cannot be resolved, but administrators should not design approval configurations around an empty Governance Group. Doing so creates unnecessary routing failures, escalation, or reassignment and weakens the intended ownership model.

The recommended governance model is therefore to create the group, assign appropriate responsible identities as members, maintain membership as organizational responsibilities change, and only then use that group as a reviewer, owner, or governance decision point.

Study Guide Reference: Access Management — Governance Groups, Group Membership, Access Request Reviewers and Approval Configuration.

===============

This is an appropriate diagnostic method within the Search model represented by the course scenario. The query narrows the investigation to events associated with provisioning, filters for events containing errors, constrains the timeframe to the date on which the failure occurred, and associates the result with the affected identity, Clarence.Harper. Opening the corresponding event allows the administrator to investigate the contextual information associated with the failed provisioning operation.

The underlying troubleshooting principle remains central to Identity Security Cloud administration: provisioning failures should be correlated with audit events and account activity rather than evaluated only from the short error message shown in a dashboard. SailPoint Search contains audit-event information and supports filtering against event data. Event records can provide operation details, status, target information, source context, and additional attributes. SailPoint also provides a Provisioning Activity audit-report capability specifically for reviewing provisioning events.

Study Guide Reference: Provisioning — Monitoring Provisioning, Search and Audit Events, Troubleshooting Failed Provisioning Operations.

===============

This is not a valid description of how a canceled access request is handled. A cancellation terminates the request before it completes. Once an access request has entered a concluded Canceled state, it is no longer simply a pending approval waiting for an administrator to substitute a decision for the assigned reviewer.

Approval Management does give administrators powerful controls over pending governance work. Administrators can inspect requests, reassign current approvers, send reminders, cancel requests, and, where supported, overwrite the current approval step. Overwriting an approver is fundamentally different from reversing an already canceled request: the administrator is acting on the current approval step of an active request.

SailPoint documentation explicitly identifies Canceled as a concluded status and defines cancellation as termination of the request. The administrator's overwrite capability applies to an approval step, not to resurrecting a request after cancellation. A new request would normally be required when access is still needed after the original request has been terminated.

Study Guide Reference: Access Management — Approval Management, Access Request Status, Administrative Approval Actions.

===============

The statement correctly describes the relevant Configuration Hub capability, although current SailPoint terminology generally refers to configuration backups, configuration files, and drafts rather than simply "templates." Configuration Hub is specifically designed to manage supported Identity Security Cloud configuration objects through backup, comparison, migration, and deployment operations.

An administrator can back up configuration objects from one tenant, establish a tenant connection, prepare a deployment draft, and migrate configurations into another tenant. This directly supports maintaining consistency between environments such as sandbox/staging and production. SailPoint explicitly documents deploying backups from one connected tenant to another.

Configuration Hub also supports exported sp-config JSON configuration files. Those files can subsequently be uploaded and used to migrate configurations between tenants, including tenants in different domains or regions where supported.

For recovery, Configuration Hub can restore supported configurations from previous automated or manual backups by preparing and deploying a draft. It is a configuration-management mechanism rather than a full business-data backup system.

Study Guide Reference: Platform — Configuration Hub, Configuration Backups, Tenant Connections, Configuration Files and Cross-Tenant Deployment.

===============

The statement is incorrect because Attribute Sync does not synchronize entitlement information from a source into Identity Security Cloud. Its purpose is to keep selected source account attributes synchronized with corresponding identity attributes maintained in Identity Security Cloud.

For example, an organization's authoritative identity data might contain a user's department, title, or other business attribute. If a corresponding account attribute on a connected target source is configured for Attribute Sync, Identity Security Cloud can detect that the account value no longer matches the identity value and provision an update to the source account. SailPoint explicitly states that Attribute Sync uses identity information to keep account data on sources consistent with identity data.

Entitlements are handled through separate aggregation mechanisms. Entitlement aggregation imports entitlement objects and their metadata from external sources into Identity Security Cloud.

Therefore, the proposed statement confuses two distinct processes: Attribute Sync pushes identity-derived account-attribute changes toward target accounts, whereas entitlement aggregation loads entitlement information from governed sources.

Study Guide Reference: Provisioning — Attribute Synchronization, Identity-to-Account Attribute Mapping and Entitlement Aggregation.

===============

This can be a valid reason, depending on the manager-review campaign mechanism being used. In a search-based certification campaign where Manager is selected as the reviewer, Identity Security Cloud determines the reviewer from each identity's manager relationship. If an identity does not have a manager defined, SailPoint documents that the certification is reassigned to the creator of the campaign . If the campaign creator is an administrator, the certification therefore appears assigned to that administrator instead of a manager.

The absence of a manager can originate from authoritative HR data, an incomplete manager attribute mapping, failed manager correlation, or otherwise missing manager information on the identity.

A distinction is important: traditional Manager Campaigns require identities to have managers defined and identities without managers are normally excluded. SailPoint recommends using a Search-based campaign with Manager selected as reviewer when identities without managers must still be included.

Given the scenario explicitly states that the certification was reassigned to an admin, missing manager information is therefore a technically valid explanation for the observed fallback assignment.

Study Guide Reference: Supporting Governance — Certifications, Manager Review, Search-Based Campaigns and Identities Without Managers.

===============

The statement is valid. The Identity Security Cloud Active Directory connector supports substantial identity-lifecycle functionality, including account aggregation, creation, modification, entitlement management, password-related operations, and provisioning. SailPoint documents Active Directory account provisioning and the use of Identity Security Cloud provisioning policies to create and manage accounts on the directory.

Active Directory can also serve as an authentication source through Pass-Through Authentication (PTA) . With PTA configured for an identity profile, users can authenticate to Identity Security Cloud using the network password associated with their Active Directory account. Identity Security Cloud passes the authentication operation through to the configured directory source rather than requiring a separate local SailPoint password.

Therefore, the AD integration is not restricted to account aggregation or read-only identity data. It can participate in both authentication and lifecycle administration, including provisioning users and managing access. Appropriate service-account permissions, VA connectivity, and provisioning configuration are required.

Study Guide Reference: Sources — Active Directory Connector, Pass-Through Authentication, Account Aggregation and Provisioning.

===============

This is not the correct remediation mechanism for the certificate-path error described. Active Directory source configuration allows administrators to enable Transport Layer Security (TLS) for supported connections, but the source's TLS configuration is not simply a certificate-upload repository used to resolve a Java PKIX trust failure.

The underlying problem is that the Virtual Appliance performing the TLS connection cannot validate the certificate chain presented by Active Directory. Trust must therefore exist in the VA's applicable certificate trust location. SailPoint documentation states that when TLS is enabled for a supported source, the applicable certificate should normally be copied automatically to the associated VA cluster. Where manual remediation is required, certificate trust is handled at the VA level rather than by arbitrarily uploading an AD certificate to a source TLS settings page.

Administrators should verify the server certificate, issuing CA chain, hostname correspondence, and the trusted certificates available to the VA. Changing source settings without resolving VA trust will leave the TLS handshake failure unresolved.

Study Guide Reference: Virtual Appliances — TLS Configuration on VAs, Certificate Trust, Active Directory TLS Troubleshooting.

===============

This is not the standard Identity Security Cloud method for configuring role assignment criteria. Role membership can be automatically determined using defined identity or account-based criteria, or administrators can explicitly specify identities through an Identity List depending on the role configuration.

The Identity List mechanism is designed to identify users who should receive the role rather than create a separate universal exclusion list containing identities who must never receive it. When automatic assignment criteria are configured, identities satisfying those criteria can become role members based on the associated identity attributes, account attributes, or other supported conditions.

If a particular identity must not receive a role, administrators should design the role-assignment criteria so that the identity does not satisfy the required conditions or use another appropriate assignment strategy. Introducing an unsupported exclusion mechanism could create incorrect expectations about how role membership is calculated.

Roles are intended to package business-relevant access and automatically assign that access to identities meeting defined organizational criteria.

Study Guide Reference: Access Management — Roles, Role Assignment Criteria, Standard Criteria, Identity Lists.

===============

This proposed API call is not valid for retrieving Virtual Appliance connector logs. The identifier shown in the log entry is a managed-cluster ID , yet the proposed URL incorrectly places that ID under the /v3/sources/ API resource. Managed clusters and sources are separate Identity Security Cloud objects and use different API endpoints.

SailPoint's documented Managed Clusters API provides operations for obtaining cluster details and for retrieving or modifying the cluster's log configuration , such as GET /managed-clusters/{id}/log-config and PUT /managed-clusters/{id}/log-config. It does not document a GET /v3/sources/{managedClusterId}/logs endpoint for exporting VA connector log files.

For connector troubleshooting, enhanced logging can be enabled against the appropriate managed cluster, the problematic operation reproduced, and the resulting VA/connector logs collected through the supported VA troubleshooting process. The administrator must also ensure that the correct cluster associated with the affected source is being investigated.

Therefore, the proposed endpoint confuses a managed cluster with a source and does not represent a supported log-export API.

Study Guide Reference: Virtual Appliances — Managed Clusters, Connector Logging, VA Troubleshooting and SailPoint REST APIs.

===============

The statement does not describe the purpose of a SailPoint Virtual Appliance. A VA is primarily a secure connectivity and connector-execution component . It allows an Identity Security Cloud tenant to communicate with enterprise sources and applications that require connectivity from within the customer's controlled environment.

SailPoint describes a VA as a Linux-based virtual machine that connects the tenant to applications and sources by using SailPoint APIs, connectors, and integrations. The VA continuously makes outbound calls to the SailPoint cloud for operations such as polling its cluster queue, performing data aggregation, executing provisioning operations, and receiving software updates.

The VA architecture does reduce the need to expose internal systems directly to inbound cloud connections, but that is fundamentally different from eliminating databases that contain PII. Enterprise applications, identity repositories, HR systems, directories, and other governed sources may continue to store personally identifiable information according to their own business and regulatory requirements.

Therefore, PII database elimination is neither the VA's purpose nor a consequence of deploying one.

Study Guide Reference: Virtual Appliances — VA Architecture, Secure Source Connectivity, Outbound Communication and Connector Execution.

===============

This is a valid description of Separation of Duties (SoD) as an identity-governance control. SoD policies define combinations of access that should not be held by the same identity because combining those privileges could enable fraud, unauthorized transactions, or circumvention of internal controls. A detective implementation analyzes existing access and identifies identities that already violate a defined policy, allowing administrators to investigate, mitigate, revoke access, or document an approved exception.

Preventive policy evaluation applies the same governance principle before problematic access is granted. During an access-request or provisioning process, the proposed access can be evaluated against policy rules so that a potential conflict is identified before the access change is completed. SailPoint documents SoD policies as conflicting-access definitions and also documents preventive policy evaluation in its governance model. These controls provide measurable evidence that an organization is actively enforcing access-risk policies rather than merely documenting them.

Study Guide Reference: Supporting Governance — Separation of Duties, Policy Rules, Detective and Preventive Controls.

===============

Yes. Removing the @entitlements(name:Manager_Access) portion produces a valid identity-oriented query structure. Identity Search supports the @access(...) nested object because an identity can possess multiple access items. SailPoint specifically documents @access(displayName:...) for identifying identities that possess a named access item and @access(source.name:...) for locating identities whose access originates from a particular source. Nested access queries can be combined with ordinary identity fields by using Boolean operators.

The remaining query therefore applies three conditions correctly: the identity must have been created during the specified 24-hour range, and the identity must satisfy either the New_Hire_Access condition or the Acme_HRMS source-access condition.

The problem with the original expression is the @entitlements(...) nested object. In SailPoint's searchable data models, @entitlements is used when examining objects such as access profiles or roles that contain entitlements; it is not the appropriate nested object for identity-level access searches. Identity-level entitlement holdings are searched through @access(...).

Study Guide Reference: Platform — Search, Nested Queries, Identity Access Fields and Boolean Query Construction.

===============

The statement does not accurately describe how governance-group approval and escalation operate. When a governance group is configured as an approver, the request is associated with the group's members, and a member of that governance group can perform the approval on behalf of the group. The system is not designed to send the request exclusively to the manager of one active group member.

Escalation behavior is also broader than the proposed statement suggests. SailPoint documents that when governance-group approvals are escalated to a manager level, the request can be escalated to each member's manager . If a particular member does not have a manager, that member's approval can remain assigned while other members' assignments are escalated. If none of the members has a manager, the applicable approvals can progress to the configured fallback approver.

Therefore, "only to the manager of an active member" incorrectly reduces a multi-member governance-group escalation process to one manager and does not reflect the documented routing behavior.

Study Guide Reference: Access Management — Governance Group Approvals, Escalation Chains, Access Request Reviewers.

===============

This statement is correct and closely matches SailPoint's official definition of a source. Identity Security Cloud does not treat an external enterprise system itself as being physically contained within the tenant. Instead, it creates a source definition representing that application, database, directory, HR system, or other managed environment.

The source definition supplies the governance context through which Identity Security Cloud interacts with the underlying system. A connector gathers account and access information and associates that data with the source. Identity Security Cloud can then correlate source accounts to identities, aggregate entitlements, model access, perform certifications, support access requests, and—in the case of writable connectors—provision changes back to the external system.

SailPoint's current source-management documentation explicitly defines a source as the Identity Security Cloud representation of a third-party enterprise application, database, or directory-management system maintaining its own user accounts or personnel records.

This distinction between source and connector is important: the source is the governed system representation, while the connector provides the technical mechanism used to communicate with that system.

Study Guide Reference: Sources — Source Definitions, Connector Definitions, Source Accounts and Enterprise System Integration.

===============

The statement accurately describes the cryptographic trust model underlying SAML federation. In a typical SAML configuration, the Identity Provider (IdP) authenticates the user and issues a SAML assertion. The Service Provider (SP) validates the assertion, particularly its digital signature, by using certificate/public-key information associated with the trusted IdP. Private keys remain protected by their owners; the corresponding certificates containing public keys can be exchanged through configuration or SAML metadata.

For Identity Security Cloud operating as a SAML Service Provider, SailPoint requires administrators to obtain the IdP's signing certificate and configure it in Identity Security Cloud. SailPoint also provides Service Provider metadata that can be supplied to the IdP. This establishes the federation relationship and allows the participating systems to validate SAML messages according to the configured trust model. The critical concept is that passwords are not shared between the IdP and SP. Authentication assertions are trusted because they originate from an established federation partner and can be cryptographically validated.

Study Guide Reference: Access Management — Authentication Methods, SAML Federation, Identity Provider and Service Provider Trust.

===============

This approach satisfies the stated provisioning requirements. Identity Security Cloud roles can use identity attributes such as department as assignment criteria. Therefore, a standard role can be configured so that identities whose department equals Finance automatically qualify for the role, regardless of whether their employment type is employee or contractor.

The role can then contain the Office 365 E3 entitlement, either directly or through an appropriate access profile. When an identity satisfies role membership criteria, Identity Security Cloud automatically assigns the role and provisions its associated access to the identity's applicable source account. When the identity ceases to meet the criteria, the role and associated provisioned access can be removed.

This design does not indiscriminately assign a default Office 365 license to contractors throughout the organization. It targets Finance identities and grants the specific E3 access required by the scenario. It also avoids deliberately assigning both the default license and E3 license to the same Finance identity.

Study Guide Reference: Provisioning — Automated Role Assignment, Identity Attribute Criteria, Role-Based Provisioning and Entitlement Assignment.

===============