CyberArk Guardian Exam Questions and Answers
How can a Secondary PTA server be promoted to a Primary PTA Server?
Options:
A manual procedure.
Automatically using the PTA Network Sensors.
This is not possible.
Automatically using a BASH script.
Answer:
AExplanation:
CyberArk Privileged Threat Analytics (PTA) provides security analytics for privileged account activity, identifying suspicious behavior, anomalous access patterns, and potential credential misuse.
In the traditional PTA disaster recovery architecture, the Primary PTA server processes incoming security events and performs the active analytics functions. A Secondary PTA server maintains replicated information and provides a recovery capability if the Primary PTA becomes unavailable.
Promoting the Secondary server requires an administrator-controlled failover procedure. The administrator must confirm the failure, assess replication consistency, activate the secondary environment according to the supported recovery procedure, and ensure that relevant integrations direct their traffic to the newly active server.
PTA Network Sensors collect network authentication information for analytics. They do not independently manage PTA server promotion or provide automatic high-availability orchestration.
Although Linux shell scripts may be involved in PTA disaster recovery configuration and recovery operations, the presence of such scripts does not mean that unattended automatic promotion is supported.
Manual promotion provides operational control over recovery and helps prevent inconsistent analytics environments or an unintended simultaneous-primary condition.
The following message appears in a log: PSMSV1230E: Vault files download completed with errors. Some of the files may be missing.
On which system would you most likely see this message?
Options:
PSM for SSH
CPM
PSM
Vault
Answer:
CExplanation:
CyberArk components use distinct message prefixes to identify the originating service or subsystem. These identifiers help administrators determine where a problem occurred and which diagnostic records should be examined.
The message PSMSV1230E belongs to the Privileged Session Manager service message family.
Privileged Session Manager (PSM) establishes and controls privileged sessions, isolates credentials from users, and supports monitoring and recording of administrative activity.
During initialization and normal operations, PSM communicates with the Digital Vault to obtain configuration data and other files required by its services.
The error indicates that a Vault file download operation completed unsuccessfully and that some expected files may not have been retrieved.
Potential causes include Vault connectivity problems, insufficient Safe permissions, unavailable objects, authentication failures, or incomplete component configuration.
Administrators should investigate the corresponding PSM service logs and correlate the event with Vault connectivity and authentication records.
PSM for SSH uses a different service architecture and message families, while CPM primarily produces password-management and credential-processing diagnostics.
Although the underlying communication involves the Digital Vault, the PSMSV prefix identifies the PSM component as the expected logging source.
Match the Conjur services and options:

Options:
Answer:

Explanation:
Original description / order
Correct match
Added and fetched in OpenSSH format
Public Keys
Manage policies and maintain consistency
Host Factory — intended by elimination
Immutable permission events and records across entire infrastructure
Audit
Engine to manage users, groups, hosts, and layers
Directory
CyberArk Conjur includes services for managing machine identities, authorization policies, cryptographic public keys, and security audit information.
The Public Keys service manages public keys associated with Conjur identities. These keys can support SSH-based authentication and are commonly represented in OpenSSH format.
The Directory service organizes identity resources, including users, groups, hosts, and layers. These resources provide the foundation for policy-based authorization and controlled secrets retrieval.
The Audit service records security-relevant activities, including authentication and authorization events. Such records support operational investigation, accountability, and security monitoring. Audit durability depends on the deployment and protected log-storage configuration.
Host Factory enables automated creation and enrollment of host identities. It uses policy-controlled, time-limited enrollment tokens to allow newly provisioned workloads to become members of authorized Conjur layers without granting broad administrative permissions.
The second description in the exhibit is technically imprecise. Host Factory is not the general mechanism for maintaining Conjur policies. Policy files and Conjur's policy-management interfaces govern authorization definitions.
Nevertheless, Host Factory is the intended remaining match among the four supplied choices.
Technical warning / qualification: The second description should be rewritten to Automates the creation and enrollment of host identities using policy-controlled tokens.
In most cases, why should a failed CPM verification followed by a reconciliation action be considered a security incident?
Options:
The secret may have been changed outside of CyberArk and is compromised.
The secret is not configured for automatic reconciliation.
The CPM should not be performing automatic reconciliation actions.
The secret was rotated outside of an approved change-control window.
Answer:
AExplanation:
CyberArk Central Policy Manager (CPM) manages privileged credentials through automated password verification, rotation, and reconciliation.
During verification, CPM attempts to authenticate to the managed target using the credential stored in the Digital Vault. Successful verification demonstrates that the vaulted credential remains consistent with the target system.
If verification fails because the target password no longer matches the stored password, this may indicate an unauthorized password change outside CyberArk's approved management process.
A subsequent reconciliation operation uses an appropriately privileged reconciliation account to reset the target credential and restore control.
The need for reconciliation therefore raises a security concern: an administrator, application, attacker, or uncontrolled automation process may have modified the credential independently.
Such activity can indicate compromised credentials, unauthorized administrative access, or a breakdown in password governance.
However, verification failures may also result from network problems, unavailable targets, account restrictions, or incorrect plugin configurations. A failed verification alone does not conclusively establish compromise.
The event should trigger investigation, including examination of CPM logs, Vault audit events, target-system authentication records, and authorized change activity.
Option A correctly identifies the principal security concern, while the other options either assume unsupported facts or misunderstand reconciliation behavior.
What type of attack can CyberArk mitigate?
Options:
Pass-the-Hash
SQL Injection
DDOS
Phishing
Answer:
AExplanation:
Pass-the-Hash is an authentication attack in which an adversary obtains an NTLM password hash and uses it to authenticate without knowing the corresponding plaintext password.
The technique is particularly dangerous in Windows environments where privileged credentials or reusable authentication material are exposed across multiple systems.
CyberArk mitigates this risk through privileged credential protection, controlled session initiation, endpoint privilege management, and restrictions on local administrative privileges.
CyberArk PAM helps reduce credential exposure by rotating privileged account passwords, maintaining unique credentials where applicable, and isolating administrative sessions through Privileged Session Manager.
CyberArk Endpoint Privilege Manager complements these protections by restricting unnecessary administrative access and implementing endpoint controls designed to reduce credential-theft and lateral-movement opportunities.
These safeguards make it more difficult for attackers to obtain and reuse privileged authentication material.
However, password rotation alone does not guarantee prevention of Pass-the-Hash attacks. Effective protection also depends on endpoint configuration, authentication mechanisms, credential isolation, and Windows security controls.
SQL Injection primarily concerns weaknesses in application input handling. DDoS targets service availability, while phishing involves social engineering. CyberArk offers identity-related defenses relevant to some phishing scenarios, but Pass-the-Hash is the specific attack most directly aligned with the controls tested here.
A customer has a policy that denies all direct RDP access from their workstation network security zone to the server network security zone. Only HTTPS is permitted into the server network security zone.
What recommendation would you give the customer?
Options:
Do not use the PSM. Allow end users to use the Show/Copy feature.
Request an exception to allow RDP access from the workstation network zone to the network security zone.
Provide to virtual desktop to each user. Users will access the PSM from the virtual desktop that sits within the server network security zone.
Deploy an HTML5 gateway in the server network security zone.
Answer:
DExplanation:
CyberArk Privileged Session Manager provides controlled access to privileged systems while isolating credentials and recording administrative sessions.
In a conventional RDP-based PSM connection, the user's workstation establishes an RDP session to the PSM infrastructure. This normally requires TCP port 3389 connectivity.
The customer's network segmentation policy specifically prevents direct RDP traffic from workstation networks into the server security zone.
Deploying an HTML5 Gateway addresses this restriction by allowing users to establish PSM sessions through a supported web browser over HTTPS.
The browser communicates with the HTML5 Gateway through TCP port 443, using encrypted web communications. The Gateway subsequently brokers the session to the appropriate PSM infrastructure.
As a result, the administrator can interact with target systems without establishing a direct RDP connection from the workstation network.
The internal PSM-to-target communication must still use the relevant protocols and permitted firewall rules.
Option A removes important credential-isolation protections. Option B conflicts with the customer's security policy. Option C introduces unnecessary virtual desktop infrastructure.
The HTML5 Gateway is therefore the appropriate solution because it maintains the existing segmentation model while preserving controlled privileged-session access.
Communication is an integral component of any PAM program and includes these two elements.
Choose two
Options:
Getting buy-in from leadership and communicating this from the first stakeholder meeting.
Allowing each level to develop their own messaging so that we can build a specific message catered to each group's goals: leadership, management, different organizations, IT Administrators, etc..
Developing a PAM sponsor to evangelize the project goals with the CTO and the entire technology organization.
"One and Done" communication so we don't overwhelm users.
Developing all training materials in Stage 2 of the program so that we can include 'lessons learned'.
Answer:
A, CExplanation:
Successful Privileged Access Management implementation requires organizational commitment in addition to technology deployment. PAM initiatives affect administrators, application owners, operations teams, business stakeholders, and executive leadership.
Establishing leadership buy-in from the beginning is essential because privileged-access controls can change established administrative procedures and introduce new approval, authentication, and session-management requirements.
Communicating executive support during initial stakeholder engagement establishes a clear organizational mandate and reduces uncertainty regarding the program's importance.
A dedicated PAM sponsor provides continuing executive advocacy. This individual communicates objectives to senior technology leadership, helps resolve organizational barriers, and ensures the program receives the necessary operational support.
Options A and C therefore describe complementary elements: executive commitment and sustained sponsorship.
Option B introduces an important distinction. Communication should be tailored to different audiences, but allowing every organizational level to independently define its own message can create conflicting expectations. A centrally coordinated communication strategy is preferable.
Option D is incorrect because adoption requires continuous engagement rather than a single announcement. Option E is also unsuitable because enablement and training preparation should begin before the second stage.
A customer must retain all privileged-access records for 7 years. The environment has approximately 2000 users who create nearly 100 GB of session recordings each day.
How should CyberArk PAS be designed to meet this requirement for PSM recordings?
Options:
Set a low PSM Recording Retention period and use Secure Replicate to offload recordings for archival storage.
Connect Vault servers to SAN storage and increase disk size whenever free disk space monitoring sends an alert.
Connect external storage to PSM servers to more evenly distribute the storage requirements.
Set Audit Retention Master Policy and PSMRecording Safe object retention to 2555 days (365 days * 7 years).
Answer:
AExplanation:
CyberArk Privileged Session Manager records administrative sessions and stores completed recordings in designated Recording Safes within the Digital Vault.
At approximately 100 GB per day, retaining seven years of recordings requires substantial storage capacity.
The estimated volume is:
100 GB × 365 × 7 = 255,500 GB
This represents approximately 255.5 TB before accounting for filesystem overhead, additional metadata, growth, and redundancy.
Retaining this entire volume within the operational Digital Vault would introduce considerable storage, backup, and recovery requirements.
The more appropriate approach is to establish a shorter operational recording-retention period and use CyberArk replication or supported archival processes to transfer recordings into secure long-term storage.
Secure Replicate can support the transfer of Vault data into an external backup environment, reducing dependence on continuously expanding primary Vault storage.
However, the archival solution must independently enforce the required seven-year retention period, integrity protection, recoverability, and audit requirements. A backup copy alone does not automatically establish regulatory compliance.
Option B relies on reactive storage expansion. Option C incorrectly treats PSM servers as the permanent recording archive. Option D does not address practical capacity management and incorrectly combines different retention mechanisms.
A financial institution uses CyberArk Privileged Session Manager (PSM) to monitor privileged access to production servers.
The security team requires authorized auditors to terminate suspicious privileged sessions immediately when potentially malicious administrative activity is detected.
An auditor can view active sessions in PVWA but cannot terminate them. The administrator confirms that session monitoring is enabled and the PSM infrastructure is functioning correctly.
What configuration should be implemented to allow the auditor to terminate active privileged sessions?
Options:
Add the auditor to the Vault Administrators group and grant full administrative access to all Recording Safes.
Enable the Require Dual Control Password Access Approval rule in the Master Policy and assign the auditor as an approver.
Add the auditor to the PSMLiveSessionTerminators group and ensure that this group has the required membership in the Safes containing the managed accounts.
Assign the auditor the Retrieve Accounts permission on the relevant Safes and enable automatic password reconciliation.
Answer:
CExplanation:
CyberArk Privileged Session Manager provides real-time monitoring and control of privileged sessions, enabling security teams to investigate potentially dangerous activity and intervene when necessary.
Session monitoring and session termination are distinct authorization capabilities. Being able to view an active privileged session does not automatically grant permission to terminate it.
In CyberArk PAM Self-Hosted, the PSMLiveSessionTerminators group provides the authorization framework for terminating active PSM sessions.
To enable this capability, the administrator must add the designated auditor to the PSMLiveSessionTerminators group.
Additionally, this group must have the necessary membership in the Safes containing the account objects associated with the sessions that the auditor is authorized to terminate.
Both requirements are important because session termination authorization must respect the organization's privileged-account access boundaries.
Where PSM uses RDP over SSL, additional connection-component configuration may be required for the monitoring and termination functions to operate correctly.
Granting broad Vault Administrator privileges would violate least-privilege principles. Dual Control regulates password-access approvals rather than active-session termination.
Similarly, credential retrieval and password reconciliation permissions do not independently authorize session termination.
This configuration enables controlled security intervention without unnecessarily exposing privileged credentials or granting unrestricted Vault administration.
ClientABC is building a PSM farm with 2 servers. They plan to use a physical load balancer configured for least connections.
What else is required as part of this configuration?
Options:
Deploy the PSM Healthcheck integration on 1 of the 2 PSM servers. This acts as a centralized healthcheck for both servers.
Deploy the PSM Healthcheck integration on both of the 2 PSM servers. Ensure the load balancer uses this URL.
This is not a supported configuration, PSM only supports round robin load balancing.
Deploy the PSM Healthcheck, however without the load balancer, CyberArk is able to load balance the PSMs internally.
Answer:
BExplanation:
CyberArk Privileged Session Manager supports horizontally scaled deployments in which multiple PSM servers operate behind a load balancer. This architecture distributes privileged sessions across available servers and increases service availability.
When implementing a PSM farm with a physical load balancer, each PSM server must independently expose its health status. The PSM Health Check integration provides an application-level mechanism for determining whether the individual PSM instance is operational.
The health-check service should be installed and configured on both PSM servers. The load balancer must query each server's health-check endpoint rather than relying exclusively on network connectivity.
A typical endpoint is /psm/api/health , subject to the deployed PSM Health Check version.
The least-connections algorithm distributes new connections toward the server handling fewer active connections. This is useful because privileged sessions can have substantially different durations.
If a PSM instance becomes unavailable, health monitoring allows the load balancer to exclude it from new session assignments.
A single health-check deployment cannot reliably report the independent application status of both servers. Furthermore, PSM supports external load-balancing solutions and is not restricted to round-robin distribution.
You need to safeguard secrets used by an application hosted on AWS with Docker. The application has high activity volumes around the clock.
The application accepts customer information and captured images, uploads them to storage, and reads and writes metadata to and from a database service.
Select the option that secures the privileged credentials used in these transactions.
Options:
Central Credential Provider
Credential Provider
Application Server Credential Provider
Conjur
Answer:
DExplanation:
CyberArk Conjur is designed to protect secrets used by cloud-native applications, containerized workloads, DevOps pipelines, and automated services.
The application described in this scenario runs in Docker containers on AWS and requires privileged credentials to access storage and database resources.
Embedding these credentials in container images, application configuration files, or environment variables can expose them through compromised containers, source repositories, diagnostic logs, or deployment artifacts.
Conjur addresses this risk by centralizing secrets management and enforcing policy-based authorization for application identities.
Containerized applications authenticate through an appropriate supported authenticator and obtain the secrets they are explicitly authorized to retrieve.
This design enables credentials to be managed independently of application code and container images.
Conjur also supports scalable architectures suitable for workloads that generate continuous and substantial transaction volumes.
A properly designed deployment should include high-availability secrets delivery, secure workload authentication, credential rotation, and appropriate application-side handling of temporary secrets-service interruptions.
Although Central Credential Provider and conventional Credential Provider solutions can serve application credential requests, Conjur is the strongest architectural fit for cloud-native Docker workloads.
The ‘LogRetention’ parameter in the DBParm.ini file specifies how long log records are retained.
When are the expired logs cleared?
Options:
It needs to be cleared manually.
It will not be cleared automatically. It will show warning.
Whenever the Server is stopped.
Whenever the Server is started.
Answer:
DExplanation:
The CyberArk Digital Vault uses the DBParm.ini configuration file to define operational parameters affecting the Vault Server, including logging, communication, and service behavior.
The LogRetention parameter specifies how long relevant Vault log records are retained before they become eligible for removal.
According to the behavior described by this legacy parameter, expired log records are cleared during the Vault Server startup process. At startup, the server can evaluate retention settings and perform the corresponding cleanup operations.
This means the retention period defines the eligibility threshold for removing records, while the server lifecycle determines when the cleanup operation is performed.
Stopping the service does not independently execute the startup cleanup operation. Additionally, an administrator is not ordinarily required to perform individual manual deletions of expired records governed by this mechanism.
It is important to distinguish operational log retention from other CyberArk retention controls. Vault audit records, external SIEM archives, privileged session recordings, and disaster recovery replicas may have separate retention requirements.
Administrators should therefore validate the relevant logging configuration and applicable audit obligations before modifying retention settings.
A customer needs to implement CyberArk with the lowest possible recovery time objective for a Vault server failure in both the primary and secondary datacenters.
Which architecture is most suitable for this?
Options:
Deploy a multi cloud, multi region Architecture with 4 vaults. 2 vaults per public cloud across different regions.
Deploy both Primary and DR vault clusters in primary and secondary datacenters.
Deploy Distributed vaults. 1 Primary vault and 1 satellite vault in the primary datacenter and 2 satellite vaults in the secondary datacenter.
Deploy Primary and DR standalone vaults in a single public cloud environment within the same region across different availability zones.
Answer:
BExplanation:
Recovery Time Objective (RTO) defines the maximum acceptable duration of service interruption following a failure.
For a CyberArk deployment requiring minimal recovery time from individual Vault server failures in both datacenters, high-availability Vault clusters provide an appropriate architecture.
A CyberArk Vault cluster consists of two Vault nodes configured to operate as a single logical Vault service. The Cluster Vault Manager coordinates availability and failover between the active and passive nodes.
If the active node fails, the surviving cluster node can assume operations through the supported failover mechanism, minimizing interruption without requiring a full datacenter disaster recovery procedure.
Deploying a Primary Vault cluster in the primary datacenter and a DR Vault cluster in the secondary datacenter combines local high availability with geographic disaster recovery.
This design protects against individual server failures at either location while retaining a standby recovery environment if the primary datacenter becomes unavailable.
The distinction is important: automatic cluster-node failover does not necessarily mean instantaneous disaster recovery promotion between geographically separated Vault clusters.
Option B directly addresses the customer's requirement for local server-failure resilience at both locations.
Which type of approach is most important for driving the adoption and transformation of a successful Identity Security program?
Options:
Risk based approach
Security based approach
Top-down approach
Bottom up approach
Answer:
CExplanation:
A successful Identity Security program requires executive commitment, enterprise-wide alignment, and coordinated implementation across organizational boundaries.
A top-down approach establishes these conditions by securing sponsorship from executive leadership and translating strategic security objectives into operational requirements.
Senior management provides the authority required to establish identity security standards, allocate appropriate resources, and enforce consistent privileged-access controls across business units.
This is particularly important because PAM adoption frequently changes established administrative practices. Administrators may be required to use privileged session management, request approval before accessing sensitive accounts, and comply with automated password rotation.
Without visible executive sponsorship, individual teams may resist these changes, creating inconsistent security coverage and unmanaged privileged-access exceptions.
A top-down strategy also establishes accountability through governance structures, clearly defined responsibilities, measurable implementation milestones, and periodic reporting.
Risk-based prioritization remains essential for determining which privileged identities and systems should be secured first. However, risk assessment alone does not provide the organizational authority needed to execute a substantial identity security transformation.
Bottom-up technical initiatives can deliver localized improvements, but they may struggle to establish enterprise-wide standards.
Therefore, the top-down approach is the most appropriate answer when evaluating organizational adoption and transformation.
A customer wants to identify which accounts in CyberArk are past due for a password change.
Which PVWA report would be most suitable for this information?
Options:
Entitlement Report
Privileged Accounts Compliance Status
Applications Inventory
Privileged Accounts Inventory
Answer:
BExplanation:
CyberArk Password Vault Web Access provides built-in reports for monitoring privileged accounts, reviewing access permissions, and assessing compliance with password-management policies.
The Privileged Accounts Compliance Status report is specifically designed to evaluate whether managed privileged accounts comply with their assigned platform policies.
It provides account-management information such as CPM management status, password compliance, and scheduled password-management operations.
This enables administrators to identify accounts whose credentials have exceeded the required password-change interval or whose scheduled password-management operations have not completed successfully.
For example, if a platform requires password rotation every 30 days, an account that has passed its scheduled rotation date without completing a successful change may appear as noncompliant.
The report helps administrators distinguish actively managed credentials from accounts requiring corrective action.
The Privileged Accounts Inventory report provides information about stored accounts and associated properties, but it is primarily intended for inventory analysis.
The Entitlement Report focuses on user access rights, while Applications Inventory provides information about application identities configured for credential retrieval.
Therefore, the Privileged Accounts Compliance Status report is the most appropriate choice for identifying overdue password changes.
Put the events in the correct order for the PSM for SSH MFA Caching authentication workflow, available beginning with v12.1.

Options:
Answer:

Explanation:
See correct matching / sequence below.
Original description / order
Correct match
1
Access the PVWA and select the required authentication method to logon.
2
Navigate to PSM for SSH MFA caching page.
3
Generate an SSH key with preconfigured validity period download the SSH private key in the correct format.
4
Open up your SSH client and browse to the SSH private key.
5
Using the regular PSMP syntax, connect to the target via the PSMP server.
6
You are automatically authenticated through PSMP and logged onto the target Linux server.
CyberArk PSM for SSH MFA Caching enables administrators to authenticate through supported PVWA authentication mechanisms and subsequently establish SSH sessions without repeating the complete multifactor authentication process for every connection.
The workflow begins when the user authenticates to PVWA using the required authentication method.
After successful authentication, the user navigates to the PSM for SSH MFA Caching interface and generates a temporary SSH authentication key.
The key is issued with a configured validity period and downloaded in a format supported by the user's SSH client.
The administrator then configures the SSH client to use the generated private key.
Using the standard PSM for SSH connection syntax, the user establishes an SSH connection through the PSMP server.
PSM for SSH validates the presented authentication material and applicable cached authentication context before initiating the authorized target connection.
This architecture allows organizations to retain multifactor authentication requirements while improving usability for administrators who establish frequent SSH sessions.
The private key must remain protected because it represents temporary authentication material. Expiration, revocation, and endpoint security controls remain essential.
Your customer has used CyberArk PAS for more than five years and has successfully onboarded over 35 local built-in administrator accounts.
A new CISO has assumed responsibility and wants to rapidly broaden privileged access management across the organization. Based on the use cases provided, prioritize them according to CyberArk's Blueprint methodology, from most critical first to least critical last.
Drag & Drop
Original drag-and-drop exhibit (answer area unselected)

Options:
Answer:

Explanation:
Original description / order
Correct match
1
Domain Administrators
2
Server built-in Administrators
3
Workstation built-in Administrators
4
Database Built-in Administrators
The CyberArk Blueprint prioritizes privileged identities according to their potential impact on enterprise security, particularly their ability to facilitate credential theft, lateral movement, and privilege escalation.
Domain Administrator accounts receive the highest priority because their compromise can provide extensive control over Active Directory, including authentication infrastructure, domain controllers, and other domain-managed resources. These identities represent a substantial enterprise-wide risk.
Server built-in Administrator accounts follow because they provide powerful local privileges on infrastructure that frequently hosts sensitive applications, databases, and business services. Securing these accounts reduces opportunities for attackers to establish persistence or move between critical servers.
Workstation built-in Administrator accounts are subsequently prioritized because shared or poorly managed endpoint credentials can facilitate credential reuse and lateral movement across large workstation populations.
Database built-in Administrator accounts remain important because they can provide extensive control over business-critical information. Within the Blueprint sequence represented by this question, these identities are addressed in a later stage of enterprise security expansion.
This ordering reflects CyberArk's staged implementation model rather than an assertion that every database credential is inherently less sensitive than every workstation credential. Actual onboarding priorities should additionally consider privilege scope, asset criticality, and business impact.
You are installing the Digital Vault on AWS.
When does hardening occur?
Options:
After the initial installation is completed.
It is not recommended to harden the Vault in AWS.
During the installation procedure.
Before the installation starts by running script.
Answer:
AExplanation:
CyberArk Digital Vault hardening establishes the security controls required to protect the Vault operating system and minimize exposure to unauthorized access.
These controls include restrictive network communication, operating-system configuration, service hardening, and the removal or disabling of unnecessary system functionality.
In the AWS deployment procedure referenced by this question, the standard Vault installation and hardening sequence differs from the conventional installation process.
During the initial Vault installation, the administrator selects the option to skip automatic machine hardening.
After completing the initial installation, the applicable AWS-specific hardening procedure is performed.
This sequence accounts for cloud infrastructure requirements, including instance configuration, virtual networking, supported access mechanisms, and cloud-specific operating-system dependencies.
Skipping hardening during the initial installation does not mean that hardening is optional.
The final deployed Vault must still satisfy CyberArk's supported security requirements before being placed into production.
Option B is incorrect because a cloud-hosted Vault requires appropriate hardening. Option C describes the conventional installation sequence rather than the specific AWS procedure presented. Option D does not reflect the documented sequence for this deployment method.
Technical warning / qualification: This answer applies to the AWS installation procedure represented by the Guardian source. CyberArk-provided cloud images and automated deployment scripts may implement hardening differently in newer releases.