I85PREP
⌘ K
Cohesity DataProtect study materials
Cohesity DataProtect study resources

Cohesity DataProtect practice questions

One question at a time. Build your Cohesity DataProtect understanding.

First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1Cohesity Data Cloud Platform Fundamentals

In the Cohesity Data Cloud architecture, which component is responsible for storing the protection policy definitions and job metadata rather than the backup data itself?

  1. The external tape library attached to the cluster
  2. The Cohesity cluster's internal metadata and configuration database Correct answer.
  3. The SMB share exported to clients
  4. The backup proxy virtual machine

Explanation

A Cohesity cluster keeps policy definitions, job state, and configuration in its internal metadata store, which is separate from the distributed data store that holds protected data. Policy and job metadata must persist even when no backup data exists yet. External tape and SMB exports are data targets, not the configuration authority.

Question 2Cohesity Data Cloud Platform Fundamentals

What is the primary role of a Cohesity protection policy?

  1. To assign IP addresses to nodes in the cluster
  2. To define the schedule, retention, and replication behavior applied to protected objects Correct answer.
  3. To encrypt the cluster's internal node-to-node traffic
  4. To map LDAP groups to local administrative roles

Explanation

A protection policy bundles the backup schedule, retention period, and optional replication or archival targets that govern how protected objects are captured and kept. Applying the policy to a source ties those rules to that workload. Network addressing, transport encryption, and role mapping are handled elsewhere in the platform.

Question 3Cohesity Data Cloud Platform Fundamentals

A Cohesity cluster uses a distributed file system across its nodes. What benefit does this design provide for backup data?

  1. Data is stored uncompressed to maximize restore speed
  2. Data and metadata are spread across nodes with redundancy so the cluster survives a node failure Correct answer.
  3. Backups are written only to the node that owns the source VM
  4. Each node keeps a complete independent copy of all data, doubling usable capacity

Explanation

Cohesity's distributed architecture stripes data and metadata across nodes with redundancy, so a single node loss does not lose protected data. This also allows capacity and performance to scale as nodes are added. Storing a full copy per node or pinning data to one node would waste capacity and create hotspots.

Question 4Cohesity Data Cloud Platform Fundamentals

Which Cohesity capability reduces storage consumption by identifying and eliminating duplicate data blocks across backups?

  1. Global deduplication Correct answer.
  2. Role-based access control
  3. Multi-factor authentication
  4. Quality of service throttling

Explanation

Global deduplication finds repeated blocks across backups and stores them once, which is a core reason Cohesity can retain many recovery points efficiently. Throttling, MFA, and RBAC address performance and security rather than storage efficiency. Deduplication is distinct from compression, which shrinks individual blocks.

Question 5Cohesity Data Cloud Platform Fundamentals

An administrator wants a protected virtual machine to be copied automatically to a second Cohesity cluster in another region after each backup. Which policy setting accomplishes this?

  1. A higher backup schedule frequency
  2. An archival target pointing to cloud object storage
  3. A snapshot-only policy with zero retention
  4. A replication target configured within the protection policy Correct answer.

Explanation

Replication copies backup snapshots to another cluster, and the target is defined as part of the protection policy so it happens automatically after each run. Archival moves data to long-term external storage instead of another cluster. Increasing frequency or using snapshot-only retention does not create a remote copy.

Question 6Cohesity Data Cloud Platform Fundamentals

What distinguishes a Cohesity physical cluster from a Cohesity virtual cluster?

  1. A physical cluster supports only tape targets, while a virtual cluster supports only cloud targets
  2. A physical cluster runs on dedicated Cohesity hardware, while a virtual cluster runs as virtual machines on supported hypervisors Correct answer.
  3. A physical cluster cannot use protection policies, while a virtual cluster can
  4. A virtual cluster stores no metadata, while a physical cluster stores all metadata

Explanation

Cohesity offers appliance-based physical clusters on dedicated nodes and virtual edition clusters deployed as VMs on supported hypervisors. Both editions use the same Data Cloud software, policies, and targets. The distinction is the underlying compute and storage substrate, not a functional split in policies or metadata.

Question 7Cohesity Data Cloud Platform Fundamentals

In Cohesity terminology, what is a protection source?

  1. The license key that enables replication
  2. An object such as a virtual machine, database, or file share that is registered for protection Correct answer.
  3. The network switch connecting cluster nodes
  4. The physical disk shelf attached to a node

Explanation

A protection source is any workload object, such as a VM, database, or file share, that the cluster registers and can protect under a policy. Sources are organized under registered source registrations like vCenter or a database host. Disk shelves, switches, and licenses are infrastructure, not protectable objects.

Question 8Cohesity Data Cloud Platform Fundamentals

An administrator needs point-in-time recovery of an Oracle database with minimal data loss. Which Cohesity capability should be used?

  1. File-level backup of the Oracle installation directory
  2. Volume-level snapshots taken once per day only
  3. Replication of the database server's operating system disk
  4. Cohesity database-aware protection with log backup for point-in-time recovery Correct answer.

Explanation

Database-aware protection captures the database consistently and can back up transaction logs, enabling restore to a specific point in time. Daily volume snapshots alone limit recovery granularity to the snapshot time. Copying installation files or the OS disk does not capture consistent database state or logs.

Question 9Cohesity Data Cloud Platform Fundamentals

Which statement best describes how Cohesity indexes backup data to enable fast search and recovery?

  1. It relies on the source system to query backups over the network at restore time
  2. It requires restoring each backup to a staging server before searching
  3. It builds a searchable catalog of file and object metadata so items can be located without mounting full backups Correct answer.
  4. It stores a flat text listing of every backup in a single log file

Explanation

Cohesity catalogs metadata from protected data so administrators can search for specific files or objects and restore them directly. This avoids mounting entire backups or restoring to staging just to find content. The index is a structured catalog, not a flat log, and does not depend on live queries to the source.

Question 10Cohesity Data Cloud Platform Fundamentals

What does Cohesity View provide within the Data Cloud platform?

  1. A backup agent installed on protected servers
  2. Scale-out file and object storage services presented to clients as shares and buckets Correct answer.
  3. A reporting dashboard for compliance audits
  4. A network firewall protecting cluster nodes

Explanation

Cohesity View delivers scale-out file and object storage, exposing SMB, NFS, and S3-style access for general file and object workloads on the same platform that protects data. It is a storage service, not an agent, report, or firewall. Consolidating file services with protection is a key platform value.

Question 11Cohesity Data Cloud Platform Fundamentals

A company wants to send long-term retention copies to Amazon S3 while keeping recent backups on the cluster. Which Cohesity feature should be configured?

  1. A snapshot-only retention policy with no external target
  2. An archival target pointing to the S3 bucket, referenced by the protection policy Correct answer.
  3. A higher deduplication ratio setting
  4. A replication target pointing to a second on-premises cluster

Explanation

Archival copies snapshots to external storage such as S3 for long-term retention while recent backups stay local for fast restore. The archival target is referenced by the protection policy so the copy is automatic. Replication targets another cluster, and snapshot-only retention keeps everything local.

Question 12Cohesity Data Cloud Platform Fundamentals

Which Cohesity component enforces that only authorized users can perform restore operations on protected data?

  1. The deduplication engine
  2. The replication scheduler
  3. The compression algorithm
  4. Role-based access control assigning privileges to users and groups Correct answer.

Explanation

Role-based access control assigns roles and privileges to users and groups, determining who may view or restore protected data. Deduplication, replication scheduling, and compression are data-path functions with no bearing on authorization. RBAC is typically combined with directory integration for identity.

Question 13Cohesity Data Cloud Platform Fundamentals

What is the purpose of an SLA-based protection policy in Cohesity?

  1. To guarantee a fixed number of IOPS per protected virtual machine
  2. To express recovery objectives such as retention and frequency that the system maps to underlying backup behavior Correct answer.
  3. To define the physical rack location of each node
  4. To specify which hypervisor version each node runs

Explanation

SLA-based policies let administrators express objectives such as how often data is protected and how long it is retained, and the system translates those into concrete job behavior. This abstracts scheduling details from the operator. IOPS guarantees, rack placement, and hypervisor versions are infrastructure concerns outside a policy.

Question 14Cohesity Data Cloud Platform Fundamentals

Which Cohesity feature allows an administrator to recover an entire virtual machine directly to a vSphere environment without first restoring to a staging datastore?

  1. Tape export, which writes the VM to physical media
  2. Instant recovery, which mounts the backup and runs the VM while data is migrated in the background Correct answer.
  3. Archival to cloud object storage
  4. File-level restore of the VM's configuration files

Explanation

Instant recovery presents a backed-up VM directly to the hypervisor so it can be powered on quickly while its data is migrated to production storage. This minimizes downtime compared with a full restore to staging. Tape export, file-level restore, and archival do not provide this immediate run-from-backup capability.

Question 15Cohesity Data Cloud Platform Fundamentals

What does the Cohesity Helios capability provide for a Data Cloud deployment?

  1. A local disk cache used only during restores
  2. A physical tape library appliance
  3. A cloud-hosted management plane for monitoring and managing clusters across sites Correct answer.
  4. A replacement for the cluster's distributed file system

Explanation

Helios is a SaaS management plane that gives a single view across multiple Cohesity clusters for monitoring, reporting, and management tasks. It complements rather than replaces the on-cluster data services. It is not a disk cache, a file system replacement, or tape hardware.

Question 16Cohesity Data Cloud Platform Fundamentals

An administrator registers a vCenter Server as a source in Cohesity. What does this registration enable?

  1. Automatic creation of new ESXi hosts
  2. Replacement of the cluster's protection policies
  3. Discovery and protection of the virtual machines managed by that vCenter Correct answer.
  4. Direct backup of the vCenter host's physical disk firmware

Explanation

Registering vCenter lets the cluster discover the VMs it manages and protect them under policies, using the hypervisor APIs for consistent snapshots. It does not back up firmware, provision hosts, or alter policies. Source registration is the prerequisite for VM protection.

Question 17Cohesity Data Cloud Platform Fundamentals

Which statement accurately describes how Cohesity handles data reduction across a cluster?

  1. Compression is applied only to metadata, leaving data blocks uncompressed
  2. Deduplication is limited to a single node and never crosses nodes
  3. Data reduction is disabled by default and cannot be enabled
  4. Deduplication and compression are applied to reduce stored footprint while preserving restore fidelity Correct answer.

Explanation

Cohesity applies deduplication and compression to reduce the stored footprint, and the reduction is transparent to restores because the original data is reconstructed on read. Deduplication operates across the cluster rather than being node-local. Data reduction is a core platform capability, not a disabled feature.

Question 18Cohesity Data Cloud Platform Fundamentals

What is the function of a Cohesity clone or copy of a backup used in a test environment?

  1. To re-register the source system with the cluster
  2. To permanently replace the production data with the backup
  3. To provide an isolated, writable instance of backed-up data for development or testing without affecting the source Correct answer.
  4. To delete the original backup after use

Explanation

Cloning creates an isolated, writable instance from a backup so teams can test or develop against realistic data without touching production or the original backup. The source and backup remain intact. A clone is not a replacement for production data and does not modify source registration.

Question 19Cohesity Data Cloud Platform Fundamentals

Which Cohesity capability helps an organization demonstrate that backups meet defined recovery point objectives over time?

  1. Policy compliance and job monitoring reports showing protection status against policy Correct answer.
  2. The compression ratio of the cluster
  3. The hypervisor vendor of the protected hosts
  4. The physical node count in the cluster

Explanation

Compliance and job monitoring reports compare actual protection runs against policy expectations, highlighting objects that are unprotected or out of compliance. This evidence supports audits and internal SLA checks. Compression ratio, node count, and hypervisor vendor do not demonstrate RPO adherence.

Question 20Cohesity Data Cloud Platform Fundamentals

A protected source is configured with a policy that includes both replication and archival. What is the expected behavior after a successful backup?

  1. Only the replica is created; archival is deferred until the replica expires
  2. Both copies are skipped because the source is already protected locally
  3. A replica is created on the peer cluster and an archival copy is sent to the external target according to policy settings Correct answer.
  4. Only the archival copy is created; replication is skipped when archival is present

Explanation

A policy can include multiple copy operations, so a successful backup can trigger replication to a peer cluster and archival to external storage, each governed by its own schedule and retention. The operations are independent and can coexist. Local protection does not suppress configured copies.

Question 21Cohesity Data Cloud Platform Fundamentals

Which consideration most affects sizing a Cohesity cluster for a given protected data set?

  1. The number of administrative users who log in to the UI
  2. The version of the web browser used by operators
  3. The change rate of protected data, retention period, and data reduction ratio determine usable capacity needs Correct answer.
  4. The color scheme of the dashboard

Explanation

Capacity planning depends on how much data is protected, how quickly it changes, how long it is retained, and how much deduplication and compression reduce the footprint. UI users, dashboard appearance, and browser versions have no material effect on storage sizing. Getting these inputs right prevents premature capacity exhaustion.

Question 22Cohesity Data Cloud Platform Fundamentals

What does Cohesity's support for S3-compatible object storage in View enable for application teams?

  1. Applications can read and write objects through S3 APIs on the same platform that protects the data Correct answer.
  2. Applications can only access data through NFS
  3. Applications lose the ability to apply protection policies
  4. Applications must convert objects to tape before storage

Explanation

View's S3-compatible interface lets applications use standard object APIs while the data resides on the Cohesity platform, where it can also be protected. This consolidates file, object, and protection workloads. It does not force tape conversion, remove policy support, or restrict access to NFS only.

Question 23Cohesity Data Cloud Platform Fundamentals

An administrator wants to protect Microsoft 365 data such as Exchange Online mailboxes and OneDrive content. Which approach fits the Cohesity platform?

  1. Rely on the service provider's native retention alone
  2. Back up only the local Outlook client cache on user laptops
  3. Use a SaaS protection capability that connects to Microsoft 365 and backs up cloud workloads to the cluster or cloud target Correct answer.
  4. Install a tape library in the Microsoft datacenter

Explanation

Cohesity provides SaaS workload protection that connects to Microsoft 365 services and backs up mailboxes, OneDrive, and similar content to a controlled target, giving independent retention beyond the provider's defaults. Installing tape in a provider datacenter is not something a customer does, and client caches are not authoritative copies.

Question 24Cohesity Data Cloud Platform Fundamentals

Which statement best explains why Cohesity consolidates backup, file services, and analytics on one platform?

  1. Consolidation is achieved by disabling data reduction for all services
  2. Each service requires its own dedicated physical cluster with no shared storage
  3. A shared distributed data store and metadata layer lets multiple services reuse the same protected data without separate silos Correct answer.
  4. Analytics run only on data copied to external tape

Explanation

Because services share the distributed data store and metadata, protected data can be indexed, searched, and reused for file services or analytics without duplicating it into separate silos. This is the core consolidation benefit. Separate clusters per service, disabled reduction, and tape-only analytics contradict the design.

Question 25Cohesity Data Cloud Platform Fundamentals

What happens to protection jobs when a protection policy's retention period is shortened?

  1. Snapshots older than the new retention window become eligible for expiration according to policy Correct answer.
  2. Retention changes apply only to newly registered sources
  3. The cluster stops taking new backups until old snapshots are manually removed
  4. All existing snapshots are deleted immediately without regard to policy

Explanation

Shortening retention changes when snapshots become eligible for expiration, and the system expires them according to policy rather than deleting everything at once. Existing data is not wiped immediately, and new backups continue. Policy changes apply to the objects using that policy.

Question 26Cohesity Data Cloud Platform Fundamentals

A Cohesity cluster is being deployed as a virtual edition on supported hypervisors. Which statement correctly identifies a primary design characteristic of the virtual edition compared with the physical edition?

  1. The virtual edition runs as a VM on customer-managed hypervisor hosts and uses their compute and storage resources. Correct answer.
  2. The virtual edition requires dedicated Cohesity-certified hardware nodes supplied by Cohesity.
  3. The virtual edition runs only as a cloud-hosted service managed entirely by Cohesity Support.
  4. The virtual edition uses direct-attached SAS disks that must be ordered from Cohesity.

Explanation

The virtual edition is packaged as a virtual machine that runs on supported hypervisors and consumes the host's CPU, memory, and storage, so the customer provides the underlying infrastructure. The physical edition, by contrast, uses Cohesity-certified appliances. This makes the virtual edition suitable for smaller or remote sites and for environments where dedicated hardware is not practical.

Question 27Cohesity Data Cloud Platform Fundamentals

During initial cluster configuration, an administrator must define how the Cohesity cluster will be addressed and discovered on the network. Which setting is configured at this stage to provide a single name that clients and services use to reach the cluster?

  1. A DNS forwarder for external name resolution
  2. A per-node iSCSI IQN for each node
  3. An NTP server pool for time synchronization
  4. A virtual IP (VIP) address assigned to the cluster Correct answer.

Explanation

The cluster VIP gives clients and services one stable address for access even if individual node addresses change. It is configured during cluster setup and is used for management and data service access. The other settings support supporting services but do not provide the cluster's single access name.

Question 28Cohesity Data Cloud Platform Fundamentals

An administrator is reviewing the default behavior of Cohesity data reduction on a cluster. Which statement accurately describes how compression and deduplication are applied to backup data?

  1. Compression is applied globally across the cluster, while deduplication is applied only at the source.
  2. Deduplication is applied globally across the cluster, while compression is applied per data stream or file. Correct answer.
  3. Both deduplication and compression are applied only after data is replicated to a remote cluster.
  4. Deduplication is applied only within a single backup job, and compression is disabled by default.

Explanation

Cohesity performs cluster-wide deduplication so that identical blocks are stored once regardless of which protection job or source produced them. Compression is applied to the data stream, reducing the size of data before or as it is written. Together they reduce storage consumption without requiring source-side agents to perform deduplication.

Question 29Cohesity Data Cloud Platform Fundamentals

A protection policy includes a replication target and an archival target. What is the expected sequence of operations for a backup run that uses this policy?

  1. Replication and archival occur simultaneously with the local backup to minimize total elapsed time.
  2. Replication occurs only after the archival copy has been verified by the remote tier.
  3. Archival occurs before the local backup so that the oldest copy is preserved first.
  4. The local backup completes first, then replication and archival are performed according to their schedules. Correct answer.

Explanation

Cohesity creates the local snapshot first, then runs replication and archival as separate operations governed by the policy's schedules. This ordering ensures a consistent local recovery point exists before copies are made elsewhere. Replication and archival can run concurrently with each other but not before the local backup completes.

Question 30Cohesity Data Cloud Platform Fundamentals

An administrator needs to protect Microsoft 365 Exchange Online mailboxes and OneDrive for Business content. Which Cohesity approach is designed for this requirement?

  1. Register the on-premises Exchange Server as a protection source and rely on mailbox replication.
  2. Install a Cohesity agent on each user's workstation to capture local Outlook data.
  3. Configure a file-based protection job against the Microsoft 365 web endpoints.
  4. Use a cloud-native protection source that connects to Microsoft 365 through Microsoft Graph or equivalent APIs. Correct answer.

Explanation

Cohesity protects Microsoft 365 workloads through a cloud-native integration that uses Microsoft APIs to access Exchange Online, OneDrive, SharePoint Online, and Teams data. This avoids agents on user devices and does not depend on on-premises Exchange. The integration is configured as a protection source within the Cohesity cluster.

Question 31Cohesity Data Cloud Platform Fundamentals

Which Cohesity capability provides a logically isolated copy of backup data that teams can use for development and testing without affecting production backups?

  1. An archival copy written to a cloud object storage tier
  2. A protection policy that includes a longer retention period
  3. A replication of the backup to a remote cluster for disaster recovery
  4. A clone of a backup snapshot presented as a separate view or datastore Correct answer.

Explanation

Cohesity clone technology creates a writable, isolated copy from a backup snapshot, typically exposed as a View or datastore for test and development use. Because it is a separate logical copy, changes made by testers do not alter the original backup. Replication, archival, and retention changes serve different purposes and do not provide an isolated test copy.

Question 32Cohesity Data Cloud Platform Fundamentals

A Cohesity cluster is being sized for a new backup workload. Which factor most directly determines the usable capacity required for the protected data set?

  1. The total source data size combined with the expected change rate and retention period Correct answer.
  2. The number of vCenter Servers that will be registered as protection sources
  3. The number of Cohesity users who will log in to the management interface
  4. The physical rack space available in the data center

Explanation

Sizing depends primarily on how much data is protected, how frequently it changes, and how long it must be retained, because these determine the stored footprint after deduplication and compression. The number of vCenters, users, or rack units does not directly drive capacity requirements. Change rate and retention are especially important because they determine how many unique blocks are kept over time.

Question 33Cohesity Data Cloud Platform Fundamentals

An administrator wants to ensure that a specific protection group retains daily backups for 30 days and monthly backups for 12 months. Which Cohesity construct is designed to express this requirement?

  1. A view with an SMB share and a quota
  2. A protection policy with a retention schedule that defines daily and monthly retention Correct answer.
  3. A storage domain configured with erasure coding
  4. A single protection job with a fixed 30-day retention and no additional copies

Explanation

Cohesity protection policies define retention through schedules that can include multiple tiers, such as daily and monthly. Applying the policy to a protection group enforces those retention rules consistently. A single fixed retention job, a storage domain, or a file share cannot express tiered retention.

Question 34Cohesity Data Cloud Platform Fundamentals

A Cohesity cluster must be able to recover an entire virtual machine directly to a vSphere environment without using an external proxy. Which Cohesity capability supports this?

  1. Archival of the VM backup to a cloud storage tier
  2. File-level restore of individual files from the VM backup
  3. Instant recovery of a VM directly to vSphere using the cluster's native integration Correct answer.
  4. Replication of the backup to a second Cohesity cluster

Explanation

Cohesity supports instant recovery that mounts a backup snapshot and powers on the VM directly in vSphere, avoiding a full data copy before the VM is usable. This relies on native vSphere integration and does not require an external proxy. Archival, replication, and file-level restore do not provide whole-VM recovery to vSphere.

Question 35Cohesity Data Cloud Platform Fundamentals

An administrator is configuring a Cohesity protection job for a vSphere environment and wants to exclude certain VMs from the backup. Which approach is supported for this requirement?

  1. Remove the VMs from vCenter inventory before the backup runs
  2. Disable the Cohesity agent on the excluded VMs
  3. Apply a VM exclusion rule or filter within the protection job definition Correct answer.
  4. Set the excluded VMs to a lower retention tier in the policy

Explanation

Cohesity protection jobs can include or exclude VMs using filters and rules based on names, tags, folders, or other attributes. This allows selective protection without altering the vCenter inventory. Removing VMs from inventory or disabling agents is disruptive or not applicable, and retention tiers do not exclude data from a job.

Question 36Cohesity Data Cloud Platform Fundamentals

A Cohesity cluster is configured to replicate backups to a remote cluster for disaster recovery. Which statement best describes the role of the remote cluster during normal operations?

  1. It actively serves production I/O for the primary cluster to improve performance.
  2. It stores replicated snapshots that can be used for recovery if the primary cluster becomes unavailable. Correct answer.
  3. It performs deduplication only after a failover is declared.
  4. It replaces the need for local backups on the primary cluster.

Explanation

Replication maintains copies of snapshots on a remote Cohesity cluster so that data can be recovered if the primary site is lost. The remote cluster does not serve production I/O for the primary and does not eliminate the need for local backups. Deduplication occurs as data is written, not only after a failover.

Question 37Cohesity Data Cloud Platform Fundamentals

An administrator needs to search backup data for specific content across many backups to support an investigation. Which Cohesity capability is designed for this?

  1. Global search indexing that allows content and metadata queries across protected data Correct answer.
  2. A storage domain policy that controls erasure coding
  3. A view quota that limits how much data can be written
  4. A per-job log file that records backup success and failure

Explanation

Cohesity indexes backup data so that administrators can search content and metadata across snapshots and sources. This supports investigation and recovery workflows without restoring each backup. Log files, storage domain policies, and view quotas do not provide content search across backups.

Question 38Cohesity Data Cloud Platform Fundamentals

A Cohesity administrator wants to delegate restore operations for a specific set of virtual machines to a team while preventing them from modifying protection policies. Which Cohesity mechanism supports this?

  1. A separate Cohesity cluster dedicated to the team
  2. An archival target configured for the team's data
  3. A protection policy that includes only those virtual machines
  4. Role-based access control with scoped roles and permissions Correct answer.

Explanation

Cohesity RBAC lets administrators assign roles with specific permissions and scope them to objects such as protection groups or sources. This allows a team to perform restores without granting policy modification rights. Separate clusters, policies, or archival targets do not by themselves enforce permission boundaries.

Question 39Cohesity Data Cloud Platform Fundamentals

An administrator is evaluating Cohesity Helios for a multi-cluster deployment. Which capability does Helios provide?

  1. Replacement of the cluster's native deduplication engine
  2. Direct execution of backup jobs on user workstations
  3. Local storage capacity expansion by adding disks to a single node
  4. Centralized monitoring and management of multiple Cohesity clusters from a cloud-based console Correct answer.

Explanation

Helios is Cohesity's cloud-based management service that provides a single pane of glass for monitoring and managing multiple clusters. It does not add local storage, replace deduplication, or run backups on workstations. It is especially useful for distributed environments where clusters are in different locations.

Question 40Cohesity Data Cloud Platform Fundamentals

A Cohesity cluster is running low on usable capacity, and the administrator wants to reduce the impact of future backups. Which combination of actions is most appropriate within the platform?

  1. Reduce the number of registered protection sources by unregistering vCenter
  2. Review and adjust retention periods, enable or tune data reduction, and archive older snapshots to a lower-cost tier Correct answer.
  3. Disable deduplication and compression to reduce CPU load on the cluster
  4. Convert all existing views to SMB shares with quotas

Explanation

Capacity pressure is addressed by reducing how much data must be retained locally, improving data reduction, and moving older snapshots to archival storage. These actions directly lower the local footprint while preserving recoverability. Disabling data reduction, unregistering sources, or changing share protocols does not effectively solve capacity constraints.

Question 41Protection Sources and Policy Configuration

In Cohesity DataProtect, which object is the primary container that groups virtual machines, physical servers, and databases for protection?

  1. View
  2. Protection Group
  3. Vault
  4. Protection Source Correct answer.

Explanation

A Protection Source is the registered workload object (such as a vCenter, a physical server, or a database host) that Cohesity discovers and protects. Protection Groups reference these sources to define what gets backed up. Views are logical storage targets, not sources.

Question 42Protection Sources and Policy Configuration

Which Cohesity component must be deployed in a VMware environment before vCenter and its virtual machines can be registered as a protection source?

  1. Cohesity DataProtect agent on each guest OS
  2. Cohesity virtual edition cluster or physical cluster with network access to vCenter Correct answer.
  3. Cohesity Helios connector on the ESXi host
  4. Cohesity SmartFiles instance

Explanation

VMware protection is agentless: the Cohesity cluster communicates with vCenter over the management network using the vCenter API. The cluster can be a physical appliance or a virtual edition, but it must have network reachability and valid vCenter credentials. No per-guest agent is required for image-level backups.

Question 43Protection Sources and Policy Configuration

A backup policy in Cohesity DataProtect is best described as which of the following?

  1. A reusable definition of schedule, retention, and replication/archival targets Correct answer.
  2. A list of individual files selected for backup
  3. A snapshot of the cluster configuration database
  4. A per-server agent configuration file

Explanation

Policies are reusable objects that bundle the backup schedule, retention settings, and optional replication or archival targets. Protection Groups then attach one or more policies to a set of sources. This separation lets administrators apply consistent data protection across many workloads.

Question 44Protection Sources and Policy Configuration

When creating a Protection Group in Cohesity, what is the purpose of assigning a policy to the group?

  1. It defines the backup schedule, retention, and any replication or archival behavior Correct answer.
  2. It configures the cluster's DNS and NTP settings
  3. It sets the IP address range used for source discovery
  4. It determines which users can log in to the protected servers

Explanation

The policy attached to a protection group governs when backups run, how long snapshots are retained, and whether copies are replicated or archived. Source selection and credentials are configured separately on the group. This makes policies the central lever for RPO and RTO design.

Question 45Protection Sources and Policy Configuration

Which Cohesity feature lets an administrator verify that a protected workload can actually boot from a backup without impacting production?

  1. Recover VMs to a temporary isolated network (instant recovery / clone) Correct answer.
  2. Archival to a Vault
  3. Source deregistration
  4. Clone View

Explanation

Cohesity can instantly clone or recover a VM from a snapshot to a temporary, isolated network so administrators can validate bootability and application health. This is often called instant recovery or a validation clone. It uses the snapshot directly rather than a full restore.

Question 46Protection Sources and Policy Configuration

Which statement correctly describes how Cohesity handles application-consistent backups for Microsoft SQL Server?

  1. It only supports full backups and cannot perform log backups
  2. It requires taking the database offline for the duration of the backup
  3. It uses the SQL Server VDI to quiesce databases and truncate logs according to policy Correct answer.
  4. It relies solely on crash-consistent VM snapshots with no application awareness

Explanation

Cohesity integrates with the SQL Server Virtual Device Interface to coordinate with the database engine, producing application-consistent backups and enabling log backup and truncation. This allows point-in-time recovery and log management within the policy. Crash-consistent snapshots alone would risk transaction loss.

Question 47Protection Sources and Policy Configuration

An administrator wants Cohesity to automatically discover new virtual machines added to a vCenter cluster and protect them without manual selection. Which configuration accomplishes this?

  1. Create a separate protection group per VM with a unique policy
  2. Manually add each VM's IP address to a static host list
  3. Enable SmartFiles NFS exports for each VM
  4. Register the vCenter and enable auto-protection on the protection group for the desired container Correct answer.

Explanation

Cohesity supports auto-protection rules where new objects discovered under a registered container (such as a vCenter folder or cluster) are automatically added to a protection group. This eliminates manual per-VM selection as the environment grows. Static host lists and per-VM groups do not scale.

Question 48Protection Sources and Policy Configuration

A protection group is configured with a policy that has a daily backup at 02:00 and a retention of 30 days. What does the retention setting control?

  1. How often the cluster checks for software updates
  2. How long the source credentials remain valid
  3. How long snapshots are kept before being expired and removed Correct answer.
  4. How many concurrent streams are allowed per source

Explanation

Retention defines the lifespan of each snapshot produced by the policy. After the retention period elapses, Cohesity expires the snapshot and reclaims space according to the configured retention type. It does not affect credentials, update checks, or stream concurrency.

Question 49Protection Sources and Policy Configuration

Which Cohesity construct stores backup data locally on the cluster and serves as the target for protection group snapshots?

  1. Policy
  2. Vault
  3. Protection Source
  4. View Correct answer.

Explanation

A View is a logical storage container on the Cohesity cluster that holds snapshot data for protected workloads. Protection groups write snapshots into views, and views can then be replicated or archived. Vaults are external targets, sources are workloads, and policies are rules.

Question 50Protection Sources and Policy Configuration

An administrator registers a physical Linux server as a protection source. Which statement about the required component is correct?

  1. A vCenter plugin must be installed on the server
  2. A Cohesity agent must be installed on the server to capture file-level and application data Correct answer.
  3. No component is needed because physical servers are always protected agentlessly
  4. The server must be converted to a virtual machine first

Explanation

Physical Linux and Windows servers require the Cohesity agent to be installed so that file-level and application-aware backups can be captured. Agentless protection applies to hypervisor-integrated sources such as VMware and Hyper-V. Physical hosts are not virtualized as a prerequisite.