Identity-Security-Administrator SailPoint Certified Identity Security Administrator Questions and Answers

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.

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

Yes, when the user's application access is governed through attribute-driven role assignment, a department change can trigger deprovisioning of access that is no longer appropriate. Identity Security Cloud roles can use mapped identity attributes such as Department as membership criteria. During identity processing, SailPoint evaluates whether the identity continues to satisfy those criteria.

If the user moves to another department and consequently ceases to satisfy the role's assignment criteria, the identity is removed from the role. SailPoint explicitly documents that when identities are removed from roles because of assignment-criteria changes, access assigned by those roles is removed or deprovisioned , unless the same access is independently provided through another role or assignment.

This implements birthright and role-based lifecycle governance: business changes such as department transfers should automatically cause obsolete access to be removed while new access appropriate to the destination department can be provisioned. SailPoint even provides a workflow template specifically addressing identity department changes and reassessment of old versus new access.

Thus, a department change is a valid deprovisioning trigger when the former application's access derives from criteria that the identity no longer satisfies.

Study Guide Reference: Provisioning — Automated Role Assignment, Attribute Changes, Role Deprovisioning and Department-Based Access Lifecycle.

The statement is valid in the Identity Security Cloud source model. A source represents an external enterprise system that maintains accounts or personnel records. Those source accounts are aggregated into Identity Security Cloud so they can be correlated with identities and governed.

SailPoint's official definition states that a source represents a third-party enterprise application, database, or directory-management system maintaining its own set of user accounts or personnel records. For example, an Active Directory source can contain directory user accounts, while a database source might expose database accounts and a SaaS source might contain application-specific user objects.

This distinction between an identity and a source account is fundamental. One Identity Security Cloud identity can be correlated to accounts across multiple sources. The identity represents the person or governed entity, whereas each source account represents that identity's presence in a particular external system.

During aggregation, Identity Security Cloud loads account attributes and associated access from the source, correlates those accounts to identities, and uses the resulting relationships for provisioning, access modeling, certifications, and governance.

Study Guide Reference: Sources — Sources and Connectors, Source Accounts, Account Aggregation and Identity Correlation.

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

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.

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

This is a valid troubleshooting action. Identity Security Cloud depends on the source's entitlement schema to understand what entitlement objects and attributes should be collected. If the schema or entitlement-type configuration is incorrect, a newly created entitlement might not be recognized correctly during aggregation.

In the current Identity Security Cloud interface, this functionality is represented under Entitlement Management > Entitlement Types and Schemas . Each entitlement type has a schema that defines attributes such as its identifier, name, display name, description, and other source-specific properties. The account schema also identifies which account attributes represent entitlements. Consequently, schema configuration directly affects how source entitlement information is interpreted and linked to accounts.

Administrators should therefore confirm that the expected entitlement type exists, verify that its entitlement ID and entitlement-name attributes are mapped correctly, and then perform an entitlement aggregation. SailPoint specifically recommends examining and correcting entitlement schema mappings when entitlement information is not being aggregated correctly.

Study Guide Reference: Sources — Entitlement Types and Schemas, Entitlement Aggregation, Source Entitlement Configuration.

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

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.

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

The proposed sequence is incorrect because the administrator should not first apply the Identity Profile's Block Access From settings before defining the underlying network and geography restrictions.

Identity Security Cloud tenant restrictions are configured in two logical stages. First, the organization defines the networks and geographic rules that determine what locations are trusted or untrusted. Network restrictions are based on configured IP address ranges, while geographic restrictions can use trusted or blocked-country definitions. After these global security definitions exist, restrictions are applied to specific user populations through their Identity Profiles.

The Identity Profile does indeed contain Block Access From options such as Off Network and Untrusted Geography, so that part of the statement identifies a real configuration location. However, SailPoint explicitly warns that enabling Off Network without first defining an applicable network can block all users associated with that identity profile from accessing Identity Security Cloud.

Therefore, selecting Block Access From is a required application step, but describing it as the first configuration action makes the proposed solution invalid.

Study Guide Reference: Access Management — Restricting Tenant Access, Network Definitions, Geographic Restrictions and Identity Profile Security.

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

This is a valid troubleshooting action because the error explicitly identifies an invalid email-address value during provisioning. When Identity Security Cloud creates an account on a source, the Create Account configuration determines which account attributes are populated and how their values are calculated.

SailPoint allows each Create Account attribute to derive its value from an identity attribute, generator, static value, or other supported provisioning configuration. For example, the source's email account attribute can be mapped directly to the identity's Work Email value. If that mapping references the wrong identity attribute, produces an incorrectly formatted value, or uses a defective generator or transformation, the target source can reject the provisioning operation.

The administrator should therefore inspect Admin > Connections > Sources > Account Management > Create Account , locate the email-related source attribute, validate its mapping, and inspect the affected identity's source value. The conflicting-action portion of the error should also be reviewed in Account Activity, but the explicit email validation failure makes the account-creation mapping a direct troubleshooting target.

Study Guide Reference: Provisioning — Create Account Configuration, Account Attribute Mappings, Provisioning Validation and Provisioning Troubleshooting.

Yes. Identity Security Cloud's Account Activity view is designed to provide administrators with a chronological operational view of provisioning actions. SailPoint documents that account activities are displayed by default in descending order of Last Modified date , which places the most recently updated provisioning activity first. This is useful during troubleshooting because current or recently failed operations are immediately visible.

The activity table exposes operational fields such as Status, Action, Requester, Recipient, Sources, Last Modified, and Stage. Administrators can use the tabular controls to reorganize the displayed information for analysis, including changing sort direction on sortable columns. This makes it possible to investigate provisioning operations from perspectives other than chronological order—for example, grouping similar requesters, recipients, sources, statuses, or actions.

Selecting an individual activity exposes additional request information, including provisioning errors and the progression of the request through its processing stages. This capability is important when determining whether an account create, modify, enable, disable, or entitlement operation completed successfully or stalled.

Study Guide Reference: Provisioning — Monitoring Provisioning, Account Activity, Last Modified Sorting and Provisioning Troubleshooting.

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

The statement is false. Identity Security Cloud distinguishes between defining an identity attribute for the tenant and mapping that attribute within a specific identity profile. When an administrator creates a new custom identity attribute from the mappings configuration of an identity profile, the attribute itself becomes available across all identity profiles in the tenant .

SailPoint explicitly states that any identity attribute added under any identity profile appears in all identity profiles. However, administrators do not have to map or use that attribute in every profile. Each identity profile can define its own mapping because different identity populations can obtain attribute values from different authoritative or secondary sources.

For example, a custom Employee Region attribute could be mapped from an HR source for employees while being mapped from Active Directory for contractors—or left unmapped in a profile where it is unnecessary. This distinction is essential: the attribute definition is tenant-wide, whereas the mapping and resulting value are identity-profile-specific.

Therefore, claiming that the custom attribute applies only to the identity profile where it was created is incorrect.

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

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

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.

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

This is a valid troubleshooting approach. An Active Directory provisioning failure such as "There is no such object on the server" indicates that the connector attempted an operation against an object or directory reference that Active Directory could not resolve. Potential causes include an account or group being deleted or moved, an outdated distinguished name, an invalid entitlement reference, replication timing, or a provisioning operation targeting an object that no longer exists.

Searching SailPoint's technical knowledge and community resources for the exact connector error is therefore useful because connector-specific errors often have previously documented causes, configuration considerations, and remediation patterns. This should complement—not replace—tenant-side investigation. An administrator should correlate the error with provisioning activity, source information, account state, and the target system. Identity Security Cloud provides Search and audit information for investigating provisioning activity, while SailPoint technical resources provide additional connector-specific context. Current SailPoint documentation explicitly identifies provisioning activity as auditable and searchable.

Study Guide Reference: Provisioning — Troubleshooting Provisioning Errors, Active Directory Connector Operations, SailPoint Support Resources.

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

The statement is incorrect. Purchasing or using an IGA platform that maintains security certifications or demonstrates alignment with regulatory frameworks does not automatically make the customer organization compliant with those requirements.

Regulatory compliance depends on the organization's own controls, processes, system configurations, access-governance practices, data-handling procedures, evidence collection, risk-management activities, and remediation processes. Identity Security Cloud provides capabilities that can support compliance obligations, but organizations must configure and operate those controls appropriately.

For example, Separation of Duties policies can detect conflicting access combinations. Certification campaigns enable managers, application owners, and other reviewers to validate whether users should retain particular access. Audit data provides evidence of governance decisions, access changes, and administrative actions. These features can materially support compliance assessments and audits.

However, the organization's auditors still evaluate whether applicable legal, regulatory, and internal-control requirements have actually been implemented and continuously maintained. Vendor certifications are supporting evidence, not blanket proof of customer compliance.

Study Guide Reference: Supporting Governance — Separation of Duties, Certifications, Audit Evidence, Governance and Regulatory Compliance.

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

This is an appropriate corrective action for a PKIX certification-path failure. When the Active Directory connector communicates with a domain controller using TLS, the Virtual Appliance must trust the certificate presented by that server. A PKIX path validation failed or unable to find valid certification path to requested target error indicates that Java cannot construct a trusted certificate chain from the server certificate to a trusted certification authority.

Consequently, verifying that the correct CA or server certificate is available to the VA is a fundamental troubleshooting step. SailPoint supports TLS between Virtual Appliances and compatible sources and documents certificate management on the VA for situations where trusted certificates need to be added manually. Current configuration also attempts to copy supported TLS certificates automatically to the VA cluster, but administrators must still validate certificate trust when TLS handshakes fail.

The certificate chain, expiration, hostname, and issuing CA should also be checked. Once the VA trusts the appropriate chain, the TLS handshake can complete successfully.

Study Guide Reference: Virtual Appliances — TLS Configuration, Certificate Trust, Active Directory Secure Connectivity and PKIX Troubleshooting.

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

The statement is correct. Identity Security Cloud workflows consist of triggers, actions, operators, and control-flow relationships. Each workflow action requires a name that uniquely identifies the step within that workflow. The name is operationally significant because subsequent steps and conditional logic reference workflow actions by their names.

SailPoint specifically documents that every workflow action has a name and that the action name must be unique within the workflow so it can be referenced correctly in next-step definitions and conditional logic. The workflow builder can automatically generate the initial name based on the action type, but administrators can rename steps where clearer naming improves workflow readability.

If two workflow actions shared the same underlying step name, references could become ambiguous and workflow execution could not reliably determine which action's output or transition was intended. This is particularly important because action output becomes part of the workflow data flow and can be referenced by later steps.

Therefore, uniqueness is a functional requirement rather than merely a user-interface naming preference.

Study Guide Reference: Platform — Workflows, Workflow Actions, Step Names, Data Flow and Conditional Logic.

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

This is a valid network-isolation troubleshooting step. Virtual Appliances depend on continuous outbound network connectivity to Identity Security Cloud. A VPN, firewall, proxy, routing policy, or network-security device positioned in the communication path can prevent the VA from reaching required SailPoint endpoints even when the VA itself is otherwise healthy.

Testing connectivity with and without the VPN helps determine whether the VPN path, its routing tables, security policies, DNS handling, or tunnel configuration is responsible for the failure. SailPoint requires VA outbound connectivity, including HTTPS communication over TCP port 443, and documents network connectivity as a primary dependency for proper VA operation. Network connectivity errors should therefore be investigated by validating the path between the appliance and required endpoints.

This does not mean permanently bypassing required enterprise security controls. The objective is diagnostic isolation: establish whether connectivity succeeds when the suspected network component is removed from the path, then correct the underlying VPN or routing configuration.

Study Guide Reference: Virtual Appliances — VA Network Troubleshooting, Outbound Connectivity, VPN and Firewall Configuration.

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

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.

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

The proposed description is correct. Identity Security Cloud Search supports field-specific queries that allow administrators to search identity attributes directly. The expression attributes.location restricts the search to the location identity attribute rather than searching across all indexed identity fields.

The quotation marks around "sao paulo" indicate that the search engine should evaluate the value as a phrase. This means the query is intended to identify identities whose location attribute contains the phrase Sao Paulo rather than independently searching for the words sao and paulo in unrelated positions.

Field qualification is important when administrators need precise search results. Without the attributes.location prefix, a general search could potentially return matches from other searchable attributes or indexed properties. Combining the specific identity attribute with a quoted phrase produces a more targeted search result.

Therefore, the query accurately retrieves identities whose location information matches the Sao Paulo phrase.

Study Guide Reference: Platform — Identity Security Cloud Search, Building Search Queries, Identity Attribute Searches.

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

This statement is incorrect. When a role uses Identity List as its assignment type, Identity Security Cloud expects administrators to explicitly search for and select individual identities that should receive the role. SailPoint's documented procedure is to select Identity List, search for a specific identity in Add Identities , add that identity, and repeat the process for additional identities. Identity List therefore functions as an explicit membership list rather than a pattern-based membership rule.

Wildcards such as * and ? are valid in Identity Security Cloud Search queries for supported text fields. For example, Search can use patterns to find records whose names match a particular character sequence. However, that Search capability must not be confused with role Identity List assignment criteria.

If dynamic membership is required, administrators should use Standard Criteria , where identity attributes, account attributes, or entitlements can be evaluated through supported comparison operators. Identity List is appropriate when named identities are deliberately selected.

Study Guide Reference: Access Management — Roles, Automated Role Assignment, Identity List, Standard Criteria and Search Wildcards.

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

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 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.

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

This statement is correct. An uncorrelated account is a source account that Identity Security Cloud has been unable to associate with an existing identity by using the configured account-correlation criteria. SailPoint provides a supported manual-correlation process for resolving these accounts.

From the source's Uncorrelated Accounts area, an administrator can select Download Correlation File to obtain a CSV containing the uncorrelated accounts. The administrator then adds the appropriate identity Account IDs to the designated userName column beside each account that needs to be correlated. After saving the modified CSV, it can be uploaded back through the Uncorrelated Accounts page. Identity Security Cloud processes the file and creates permanent manual associations between the specified source accounts and identities.

Manual correlation differs from ordinary correlation rules because a manually correlated account remains attached to that identity even if source attributes later change. To associate it with another identity, the manual correlation must first be removed or explicitly changed.

Therefore, the download-edit-upload procedure described in the proposed statement is an officially supported method.

Study Guide Reference: Identity and Lifecycle Management — Account Correlation, Uncorrelated Accounts, Manual Correlation and Identity Assignment.

The statement is correct. Identity Security Cloud normally uses optimized aggregation , which retrieves records from the source but can skip further processing for an account when the account already exists and no relevant data changes are detected. In that situation, account correlation and manager correlation do not need to be recalculated for unchanged accounts.

Disabling aggregation optimization causes an unoptimized aggregation . SailPoint explicitly states that this mode reprocesses every record regardless of whether the underlying account data has changed. It also reevaluates account-correlation and manager-correlation logic for those accounts.

This is particularly important after changing account-correlation configuration. If an account's attributes have not changed, an optimized aggregation might otherwise skip the account, leaving it uncorrelated despite the newly corrected correlation rules. SailPoint therefore recommends running an aggregation with optimization disabled when correlation logic has been modified on an already-aggregated source.

Unoptimized processing requires more resources and can take longer on large sources, so it should be used deliberately when full reevaluation is necessary rather than as the default aggregation mode.

Study Guide Reference: Sources — Account Aggregation, Optimized and Unoptimized Aggregations, Account Correlation.

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

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.

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

This is a valid and specifically documented cause of missing entitlements during flat-file aggregation. When multiple rows represent different entitlements belonging to the same account, Identity Security Cloud expects the rows for that account to be grouped together according to the account identifier.

SailPoint's aggregation troubleshooting documentation explicitly addresses the condition in which only one or an incomplete set of entitlements is aggregated for accounts from a delimited file. The documented remediation is to ensure that the file is sorted by account ID . SailPoint's Generic Flat File prerequisites similarly state that all accounts and entitlements must be sorted by the account name so that all entitlement rows for an account appear together.

This requirement matters because the aggregation parser must correctly recognize consecutive records as belonging to the same logical account while assembling its multi-valued entitlement attributes. If the same account appears in separated regions of the file, the complete entitlement set may not be assembled as expected.

Therefore, sorting and grouping all rows for each account together is a fundamental preprocessing requirement when supplying multi-valued entitlement information through flat files.

Study Guide Reference: Sources — Flat File Aggregation, Delimited Files, Multi-Valued Entitlements and Aggregation Troubleshooting.

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

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.

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