The CompTIA DataSys+ Certification Exam (DS0-001)

The document that meets these requirements is an SLA. An SLA, or Service Level Agreement, is a contract between a service provider and a customer that defines the scope, quality, and terms of the service delivery. An SLA typically includes the responsibilities, metrics, penalties, and other generalities that a provider would have to fulfill for customers to use its platforms. An SLA also establishes the expectations and obligations of both parties, as well as the methods for measuring and monitoring the service performance. The other options are either different types of documents or not related to service delivery. For example, a DOU, or Data Use Agreement, is a document that governs the sharing and use of data between parties; an MOU, or Memorandum of Understanding, is a document that expresses a mutual agreement or intention between parties; a SOW, or Statement of Work, is a document that describes the specific tasks and deliverables of a project or contract. References:  CompTIA DataSys+ Course Outline , Domain 2.0 Database Deployment, Objective 2.4 Given a scenario, implement service level agreements.

The correct answer is A. High temperatures activated the fire suppression system . According to CompTIA DataSys+ objectives, physical infrastructure protections are a critical component of database and data center reliability. CO₂ fire suppression systems are specifically designed to respond to fire-related conditions , not recovery metrics or cooling system logic. These systems are typically triggered by smoke detectors, heat sensors, or rapid temperature increases that indicate a fire or imminent fire risk following an event such as a power failure.

When a power outage occurs, backup systems such as generators and uninterruptible power supplies may activate. If these systems malfunction or generate excessive heat, temperature thresholds can be exceeded within minutes. DataSys+ materials emphasize that automated environmental controls are designed to protect equipment and data by suppressing fires quickly, often before flames are visible. CO₂ systems work by displacing oxygen, thereby extinguishing fire without damaging sensitive electronic equipment with water or chemical residue.

Options B and D are incorrect because RPO (Recovery Point Objective) and RTO (Recovery Time Objective) are disaster recovery planning metrics. RPO defines acceptable data loss measured in time, while RTO defines acceptable downtime. Neither setting directly triggers physical fire suppression systems. They are planning and policy metrics, not automated environmental controls.

Option C is also incorrect because cooling systems do not activate CO₂ fire suppression. Cooling failures may indirectly contribute to rising temperatures, but the CO₂ system itself is triggered by fire detection mechanisms , not by cooling system logic.

CompTIA DataSys+ clearly distinguishes between environmental controls (fire suppression, HVAC, power) and disaster recovery metrics (RPO, RTO). Therefore, option A best aligns with documented data center operational behavior and exam objectives.

The index that the developer should use to prevent duplicate values from being inserted is unique. A unique index is a type of index that enforces the uniqueness of the values in one or more columns of a table. A unique index ensures that no two rows in the table have the same value or combination of values in the indexed columns. A unique index helps to maintain data integrity and avoid data duplication or inconsistency. The other options are either not related or not effective for this purpose. For example, a single column index is a type of index that involves only one column of a table, but it does not prevent duplicate values unless it is also unique; an implicit index is a type of index that is automatically created by the database system when a constraint or a primary key is defined on a column or columns of a table, but it does not prevent duplicate values unless it is also unique; a composite index is a type of index that involves two or more columns of a table, but it does not prevent duplicate values unless it is also unique. References:  CompTIA DataSys+ Course Outline , Domain 1.0 Database Fundamentals, Objective 1.2 Given a scenario, execute database tasks using scripting and programming languages.

The deployment phase in which a DBA ensures the most recent patches are applied to the new database is upgrading. Upgrading is a process that updates an existing database system or software to a newer version or release that may include new features, enhancements, bug fixes, security patches, etc. Upgrading helps improve the performance, functionality, compatibility, and security of the database system or software. Upgrading can be done manually or automatically using tools or scripts provided by the vendor or developer. Upgrading can also involve testing, backup, migration, or rollback procedures to ensure the quality and reliability of the new version or release. The other options are either different deployment phases or not related to deployment at all. For example, importing is a process that transfers data from one source to another using files or formats; provisioning is a process that allocates resources such as servers, storage, network, etc., for a system or software; modifying is a process that changes existing data or objects in a database using commands or scripts. References:  CompTIA DataSys+ Course Outline , Domain 2.0 Database Deployment, Objective 2.3 Given a scenario, update database systems.

The correct answer is B. 40% . CompTIA DataSys+ explains that Resource Governor is used to manage and allocate CPU and memory resources among multiple workloads or resource pools within a database system. When configuring resource pools, administrators must ensure that the total allocation of minimum resources does not exceed 100% , as all resource pools share the same finite system resources.

In this scenario, the first resource pool has a minimum CPU and memory allocation of 25% , and the second resource pool has a minimum allocation of 35% . Together, these minimum guarantees account for 60% of total available resources . Resource Governor enforces these minimums to ensure that critical workloads always receive their reserved share of system resources, even under heavy load.

The remaining resources are calculated by subtracting the total minimum allocation from 100%.

100% − 60% = 40%

This remaining 40% represents the maximum CPU and memory that can be safely assigned to the third resource pool without violating Resource Governor rules. Assigning a higher value would exceed the total available system resources and would not be permitted under proper configuration guidelines emphasized in DataSys+.

Option A (20%) underutilizes available resources and is unnecessarily restrictive. Option C (60%) and D (100%) are invalid because they would cause the combined minimum allocations to exceed system capacity, leading to misconfiguration or enforcement failures. DataSys+ stresses careful capacity planning when using Resource Governor to balance performance, fairness, and system stability.

Resource Governor is especially useful in multi-tenant or mixed-workload environments, where critical applications must be protected from resource starvation. Proper calculation of minimums and maximums ensures predictable performance and prevents one workload from monopolizing system resources.

Therefore, the correct maximum allocation for the third resource pool is 40% , making option B the correct and fully verified answer aligned with CompTIA DataSys+ guidance.

The cloud storage option that provides users with endpoints to retrieve data via REST API is object. Object storage is a type of cloud storage that stores data as objects, which consist of data, metadata, and a unique identifier. Object storage does not use any hierarchy or structure to organize data, but rather uses flat namespaces that allow users to access data using the unique identifier. Object storage also provides users with endpoints to retrieve data via REST API (Representational State Transfer Application Programming Interface), which is a standard way of communicating with web services using HTTP methods (such as GET, POST, PUT, DELETE) and formats (such as JSON, XML). Object storage is suitable for storing large amounts of unstructured data that do not require frequent changes or complex queries. The other options are either different types of cloud storage or not related to cloud storage at all. For example, network file storage is a type of cloud storage that stores data as files in folders using protocols such as NFS (Network File System) or SMB (Server Message Block); ephemeral storage is a type of temporary storage that stores data only for the duration of a session or process; iBIock is not a valid acronym or type of cloud storage. References:  CompTIA DataSys+ Course Outline , Domain 2.0 Database Deployment, Objective 2.1 Given a scenario, select an appropriate database deployment method.

The statement that the administrator should use to remove inactive customers from a database is option A. This statement uses the  DELETE  command to delete all the rows from the  customer  table where the  status  column is equal to  ' inactive ' . The other options either have syntax errors, use incorrect commands, or do not specify the condition correctly. References:  CompTIA DataSys+ Course Outline , Domain 1.0 Database Fundamentals, Objective 1.2 Given a scenario, execute database tasks using scripting and programming languages.

The join that is most appropriate for the analyst to use to create this database view is option D. This join uses the  LEFT JOIN  clause to combine the  client  table and the  invoice  table based on the matching values in the  Key  column. The  WHERE  clause filters out the rows where the  Invoice.Key  column is not null, meaning that the client has made a purchase. The result is a view that shows only the clients who have not made any purchases yet. The other options either do not produce the desired result or have syntax errors. For example, option A would show only the clients who have made purchases, option B would show only the invoices that do not have a matching client, and option C would show all the clients regardless of their purchase status. References:  CompTIA DataSys+ Course Outline , Domain 1.0 Database Fundamentals, Objective 1.2 Given a scenario, execute database tasks using scripting and programming languages.

The SQL command that the administrator should use to ensure that records from the two tables are not duplicated is option A. This command uses the  UNION  clause to combine the records from the legacy table and the newer table into a single result set. The  UNION  clause also eliminates any duplicate records that may exist in both tables, and sorts the result by default. The other options either do not produce the desired result or have syntax errors. For example, option B would join the records from the two tables based on a common column, but not remove any duplicates; option C would return only the records that are common to both tables, but not the ones that are unique to each table; option D would produce a Cartesian product of the records from the two tables, which would increase the number of duplicates. References:  CompTIA DataSys+ Course Outline , Domain 1.0 Database Fundamentals, Objective 1.2 Given a scenario, execute database tasks using scripting and programming languages.