DS0-001 CompTIA DataSys+ Certification Exam Questions and Answers

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 correct answer is B. The rule set was configured to allow specific IP addresses. CompTIA DataSys+ materials emphasize the importance of network security controls, particularly firewall rules and access control lists (ACLs), in regulating remote database access. In this scenario, the database server is reachable by users in Brazil but not by users in Canada, which strongly indicates that access is being selectively permitted rather than globally blocked.

Firewall rule sets are often configured using IP-based allowlists, where only approved IP addresses or IP ranges are permitted to establish a connection. If the analyst allowed the IP address range associated with Brazil but did not include the IP range used by Canadian users, connections from Canada would fail while Brazilian users would still have access. This behavior aligns precisely with selective rule-based access control, a common best practice highlighted in DataSys+ for reducing attack surfaces.

Option A is incorrect because if the perimeter network were rejecting remote connections entirely, users in Brazil would also be unable to connect. Option C is incorrect for the same reason: a firewall rule denying all connections would block access from all locations, not just Canada. Option D, server port security being disabled, would typically prevent all inbound connections to the database service, again affecting all users regardless of geography.

CompTIA DataSys+ stresses that troubleshooting connectivity issues requires identifying whether failures are global or location-specific. Location-specific failures are most commonly caused by misconfigured firewall rules, IP filtering, or regional access restrictions. In database environments that support remote access, DBAs must ensure that firewall rules are consistently applied to all authorized networks.

Therefore, the most accurate and verified explanation is that the rule set was configured to allow specific IP addresses, and the Canadian users’ IP range was not included. This makes option B the correct answer.

The instruction that is found on a Linux command-line script and represents a system shell is #!/bin/bash. This instruction is called a shebang or a hashbang, and it indicates the interpreter that should be used to execute the script. In this case, the interpreter is /bin/bash, which is the path to the bash shell, a common system shell for Linux. A system shell is a program that provides an interface for users to interact with the operating system, either through commands or scripts. A system shell can also perform various tasks, such as file management, process control, variable assignment, etc. The other options are either incorrect or not typical for this purpose. For example, /bin/bash is the path to the bash shell, but it does not indicate the interpreter for the script; #/bin/shell is not a valid shebang or a path to a system shell; >/bin/sh is a redirection operator followed by a path to a system shell, but it does not indicate the interpreter for the script. References: CompTIA DataSys+ Course Outline, Domain 2.0 Database Deployment, Objective 2.2 Given a scenario, create database objects using scripting and programming languages.

The correct answer is B. UML. CompTIA DataSys+ identifies Unified Modeling Language (UML) as a standard visual modeling tool used to design, document, and communicate system behavior, structure, and workflows during application development. UML is especially well-suited for creating workflows because it provides multiple diagram types that clearly represent processes, interactions, and control flow within an application.

Common UML diagrams used for workflow modeling include activity diagrams, which show step-by-step business or system processes, and sequence diagrams, which illustrate interactions between system components over time. These diagrams help stakeholders understand how users, systems, and data interact throughout an application’s lifecycle. DataSys+ emphasizes that UML improves collaboration between technical and non-technical stakeholders by providing a clear, standardized visual representation of application logic and flow.

Option A, ERD (Entity Relationship Diagram), is used to model database structure, including entities, attributes, and relationships. While ERDs are essential for schema design, they do not describe application workflows or process logic. Option C, ETL (Extract, Transform, Load), refers to data integration processes used in data warehousing and analytics; it is not a design or modeling tool for application workflows. Option D, ORM (Object-Relational Mapping), is a programming abstraction layer that maps application objects to database tables and does not provide workflow visualization capabilities.

CompTIA DataSys+ highlights the importance of proper planning and design tools during application development. UML enables IT managers to map workflows before implementation, reducing development errors, improving maintainability, and ensuring that business requirements are met.

Therefore, the most appropriate tool for facilitating the creation of a workflow for a new application is UML, making option B the correct and fully verified answer.

The correct answer is D. The continuity of operations policy. CompTIA DataSys+ emphasizes that when an unexpected system failure occurs—especially during critical activities such as database migrations—the primary concern is restoring services, minimizing downtime, and ensuring data availability. The continuity of operations policy (often aligned with business continuity and disaster recovery planning) provides documented guidance on how to respond to system outages and operational disruptions.

A continuity of operations policy outlines procedures, roles, and responsibilities for maintaining or rapidly restoring essential systems after an incident. This includes steps for failover, rollback procedures, recovery prioritization, communication protocols, and escalation paths. During a migration-related crash, administrators rely on this policy to determine whether to restore from backups, revert to a previous database version, activate standby systems, or follow defined recovery time objectives (RTOs) and recovery point objectives (RPOs). DataSys+ highlights these policies as critical for ensuring predictable and coordinated responses during system failures.

Option A, the data retention policy, focuses on how long data must be stored and when it can be archived or deleted. It does not provide operational guidance for handling system crashes. Option B, the access control policy, governs authentication and authorization rules and is unrelated to recovery actions. Option C, the database compliance policy, addresses regulatory and audit requirements but does not define technical recovery procedures during an outage.

CompTIA DataSys+ clearly distinguishes governance and security policies from operational resilience policies. When a database crashes during a migration, the administrator’s priority is service restoration and data integrity, both of which are addressed by continuity of operations planning.

Therefore, the systems administrator should refer to the continuity of operations policy, making option D the correct and fully verified answer.

The correct answer is C. Application high availability. CompTIA DataSys+ describes a multizone region as an architecture that deploys systems across multiple availability zones within the same geographic region to improve availability, fault tolerance, and resilience. Availability zones are physically separate data centers with independent power, cooling, and networking, but they are connected through low-latency links.

A key characteristic of a multizone disaster recovery (DR) design is high availability of applications. By distributing application components and databases across multiple zones, the system can continue operating even if one zone experiences a failure. DataSys+ emphasizes that multizone architectures are primarily designed to protect against localized infrastructure failures, such as power outages or hardware issues within a single zone, while maintaining service continuity.

Option A, three or more availability zones, is incorrect because a multizone region does not require a specific number of zones. Most implementations use two or more zones, and the exact count depends on the cloud provider and design requirements. Option B, a single geographic location, is misleading; while availability zones are within the same broader region, they are still separate physical locations and not a single data center. Option D, active/active deployment on secondary zones, more accurately describes a multi-region or advanced global DR strategy, not a basic multizone regional design. Secondary zones imply geographically separate regions used for regional disaster recovery.

CompTIA DataSys+ clearly distinguishes high availability from disaster recovery. Multizone deployments primarily focus on availability and fault tolerance within a region, while multi-region strategies address large-scale regional outages. In a multizone DR policy, applications are architected to remain available despite zone-level failures.

Therefore, the defining characteristic of a multizone region in a disaster recovery policy is application high availability, making option C the correct and fully verified answer.

A result of an on-path attack on a system is a Wi-Fi network that redirects to clones of legitimate websites. An on-path attack is a type of attack that intercepts and modifies the traffic between two parties without their knowledge or consent. An attacker can use an on-path attack to create a rogue Wi-Fi network that mimics a legitimate one, and then redirect the users to fake websites that look like the ones they intended to visit. The attacker can then steal the users’ personal or financial information, such as usernames, passwords, credit card numbers, or bank account details. The other options are either results of different types of attacks or not related to attacks at all. For example, a website that has crashed and is no longer accessible may be a result of a denial-of-service attack, an email from an unknown source requesting bank account details may be a result of a phishing attack, and a web application that returns the addresses of its customers may be a result of a poor design or a data breach. References: CompTIA DataSys+ Course Outline, Domain 4.0 Data and Database Security, Objective 4.4 Given a scenario, identify common types of attacks against databases.

The correct answer is B. Checkpoints. CompTIA DataSys+ explains that checkpoints play a critical role in database recovery mechanisms by limiting the amount of transaction log data that must be processed during recovery. Log-based recovery relies on transaction logs to restore the database to a consistent state after a failure. If checkpoints are infrequent, the database engine must replay a large portion of the transaction log, which increases recovery time and system overhead.

A checkpoint is a process where the database writes all modified (dirty) pages from memory to disk and records a synchronization point in the transaction log. After a checkpoint completes, the database knows that all changes up to that point are safely stored on disk. During recovery, the system only needs to process log entries that occurred after the most recent checkpoint, significantly reducing recovery workload and time. DataSys+ highlights checkpoints as a key performance and availability feature, especially in systems with high transaction volumes.

Option A, deadlocks, are concurrency issues that occur when two or more transactions block each other indefinitely. While deadlock handling is important for transaction throughput, it does not reduce log-based recovery overhead. Option C, locks, control concurrent access to data and help maintain consistency, but they do not affect how much log data must be replayed during recovery. Option D, indexes, improve query performance but can actually increase logging activity because index changes are also logged.

CompTIA DataSys+ emphasizes that effective recovery planning includes optimizing logging behavior and checkpoint frequency. Properly configured checkpoints strike a balance between runtime performance and recovery efficiency by reducing excessive log replay without causing unnecessary disk I/O.

Therefore, to best mitigate the overhead caused by log-based recoveries, the database manager should use checkpoints, making option B the correct and fully verified answer.

The best suited database engine for this task is MongoDB. MongoDB is a type of non-relational database that stores data as documents in JSON-like format. MongoDB allows administrators to perform quick and simple queries on unstructured data, such as text, images, videos, or social media posts, without requiring a predefined schema or complex joins. MongoDB also supports cloud-based deployment, scalability, and high availability. The other options are either relational databases that require a fixed schema and structure for data, or specialized databases that are designed for specific purposes, such as graph databases for storing and analyzing network data. References: CompTIA DataSys+ Course Outline, Domain 1.0 Database Fundamentals, Objective 1.1 Given a scenario, identify and apply database structure types.

The document that should be used to analyze the database’s structure is an ERD. An ERD, or Entity Relationship Diagram, is a graphical representation of the entities (tables), attributes (columns), and relationships (constraints) in a database. An ERD helps to visualize the structure and design of the database, as well as the dependencies and associations among the tables. An ERD can also help to evaluate the level of normalization of the database, which is a process that organizes data into tables and columns to reduce redundancy and improve consistency. By using an ERD, a database professional can consider denormalizing a database, which is a process that introduces some redundancy or duplication of data to improve performance or simplify queries. The other options are either different types of documents or not related to the database’s structure. For example, an SOP, or Standard Operating Procedure, is a document that describes the steps and procedures for performing a specific task or operation; a data dictionary is a document that describes the metadata (information about data) of a database; a UML diagram is a graphical representation of a software system or its components using the Unified Modeling Language (UML). References: CompTIA DataSys+ Course Outline, Domain 2.0 Database Deployment, Objective 2.2 Given a scenario, create database objects using scripting and programming languages.

The best action for the administrator to take is to create a view. A view is a virtual table that shows a subset of data from one or more tables. The administrator can use a view to provide access to data from two different tables to multiple group users without exposing the restricted columns. The view can also simplify the queries and improve the performance of the reporting process. The other options are either not suitable for this scenario or do not address the requirement of hiding some columns from users. For example, creating a stored procedure would require additional coding and execution, creating a csv export would create a static file that may not reflect the latest data changes, and creating a trigger would perform an action in response to an event rather than provide access to data. References: CompTIA DataSys+ Course Outline, Domain 2.0 Database Deployment, Objective 2.2 Given a scenario, create database objects using scripting and programming languages.

The correct answer is A. Implement a virtual private network (VPN). CompTIA DataSys+ emphasizes secure remote access as a critical requirement for modern database environments, especially when users need to connect from untrusted networks such as home internet connections. A VPN provides a secure, encrypted tunnel between the user’s device and the organization’s internal network, allowing remote users to access database resources as if they were physically on-site.

By using strong encryption and authentication mechanisms, a VPN ensures that data transmitted over public networks cannot be intercepted, read, or altered by unauthorized parties. DataSys+ highlights VPNs as a best practice for protecting data-in-transit and preventing exposure of sensitive database services directly to the internet. VPNs also allow administrators to enforce centralized access controls, logging, and monitoring, further strengthening security.

Option B, implementing strong password policies, is an important security measure but does not by itself enable secure remote connectivity. Password policies address authentication strength, not secure network transport. Option C, configuring and deploying a firewall, is essential for controlling traffic flow, but a firewall alone does not provide secure remote access for home users. It typically blocks or allows connections rather than securely tunneling them. Option D, implementing a perimeter network (DMZ), is designed to host internet-facing services while isolating internal systems. Exposing databases through a perimeter network increases risk and is not recommended for direct user access to internal data.

CompTIA DataSys+ stresses the principle of minimizing attack surface. A VPN supports this principle by avoiding direct exposure of database services while still enabling authorized remote access. It also integrates well with multifactor authentication and identity management systems.

Therefore, the most secure and appropriate method to enable remote access without compromising stored data is to implement a virtual private network, making option A the correct and fully verified answer.

The option that is used to hide data in a database so the data can only be read by a user who has a key is data encryption. Data encryption is a process that transforms data into an unreadable or scrambled form using an algorithm and a key. Data encryption helps protect data from unauthorized access or modification by third parties, such as hackers, eavesdroppers, or interceptors. Data encryption also helps verify the identity and authenticity of the source and destination of the data using digital signatures or certificates. Data encryption can be applied to data at rest (stored in a database) or data in transit (transmitted over a network). To read encrypted data, a user needs to have the corresponding key to decrypt or restore the data to its original form. The other options are either different concepts or not related to hiding data at all. For example, data security is a broad term that encompasses various methods and techniques to protect data from threats or risks; data masking is a technique that replaces sensitive data with fictitious but realistic data to protect its confidentiality or compliance; data protection is a term that refers to the legal or ethical obligations to safeguard personal or sensitive data from misuse or harm. References: CompTIA DataSys+ Course Outline, Domain 4.0 Data and Database Security, Objective 4.2 Given a scenario, implement security controls for databases.

The attack that is being performed is brute-force. A brute-force attack is a type of attack that tries to guess a password or a key by systematically trying all possible combinations of characters or values until the correct one is found. A brute-force attack can use common passwords, such as “123456”, “password”, or “qwerty”, as well as dictionaries, word lists, or patterns to speed up the process. A brute-force attack can target a remote system, such as a web server, an email account, or a network device, and gain unauthorized access to its data or resources. The other options are either different types of attacks or not related to password guessing. For example, a DoS, or Denial-of-Service, attack is a type of attack that floods a system with requests or traffic to overwhelm its capacity and prevent legitimate users from accessing it; an SQL injection attack is a type of attack that inserts malicious SQL statements into an input field or parameter of a web application to manipulate or compromise the underlying database; a phishing attack is a type of attack that sends fraudulent emails or messages that appear to come from a trusted source to trick users into revealing their personal or financial information. References: CompTIA DataSys+ Course Outline, Domain 4.0 Data and Database Security, Objective 4.4 Given a scenario, identify common types of attacks against databases.

The statement that contains an error is option B. This statement is missing the FROM clause, which specifies the table or tables from which to retrieve data. The FROM clause is a mandatory clause in a SELECT statement, unless the statement uses a subquery or a set operator. The correct syntax for option B would be:

SELECT EmpId FROM employee WHERE EmpId=90030 AND DeptId=34

Copy

The other options are either correct or valid SQL statements. For example, option A selects the employee ID from the employee table where the employee ID is equal to 90030; option C selects all columns from the employee table where the employee ID is equal to 90030; option D selects the employee ID from the employee table without any filter condition. 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 correct answer is B. Rights and privileges. CompTIA DataSys+ clearly distinguishes between different categories of security controls, and access to shared resources such as folders is governed primarily by authorization mechanisms, specifically rights and privileges. In this scenario, access is restricted so that only authorized users can view or modify the shared folder, which directly reflects the enforcement of permissions.

Rights and privileges define what actions an authenticated user is allowed to perform on a system or resource. For shared folders, this typically includes read, write, modify, or full control permissions assigned to users or groups. DataSys+ emphasizes the principle of least privilege, which ensures users are granted only the minimum level of access required to perform their job functions. Applying appropriate rights and privileges protects sensitive data from unauthorized access and accidental modification.

Option A, password policies, control how passwords are created and managed, such as complexity, expiration, and reuse rules. While password policies help verify a user’s identity during authentication, they do not determine which resources a user can access after logging in. Option C, service accounts, are specialized non-human accounts used by applications or services and are unrelated to user access to shared folders. Option D, firewall policy, controls network-level traffic and determines which connections are allowed or blocked between systems, not access to files or folders once a connection is established.

CompTIA DataSys+ materials emphasize that security is layered, with authentication confirming identity and authorization enforcing access. In this case, users are already authenticated, and the restriction applies at the resource level. That makes rights and privileges the relevant control.

Therefore, the policy applied to ensure only authorized users can access the shared folder is rights and privileges, making option B the correct and fully verified answer.

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 database structure that is a type of NoSQL database is key-value stores. Key-value stores are databases that store and manage data as pairs of keys and values. Keys are unique identifiers that locate data in the database; values are arbitrary data that can be any type or format. Key-value stores do not use any schema or structure to organize data, but rather use hash tables or indexes to enable fast and simple access to data based on keys. Key-value stores are suitable for storing large amounts of simple or unstructured data that do not require complex queries or relationships. The other options are either different types of databases or not related to database structures at all. For example, hierarchical databases are databases that store and manage data as nodes in a tree-like structure; cloud databases are databases that are hosted and accessed over the internet using cloud computing services; object-oriented databases are databases that store and manage data as objects that have attributes and methods. References: CompTIA DataSys+ Course Outline, Domain 1.0 Database Fundamentals, Objective 1.1 Given a scenario, identify common database types.

The option that is used to write SQL queries in various programming languages is object-relational mapping. Object-relational mapping (ORM) is a technique that maps objects in an object-oriented programming language (such as Java, Python, C#, etc.) to tables in a relational database (such as Oracle, MySQL, SQL Server, etc.). ORM allows users to write SQL queries in their preferred programming language without having to deal with the differences or complexities between the two paradigms. ORM also provides users with various benefits such as code reuse, abstraction, validation, etc. The other options are either not related or not effective for this purpose. For example, indexing is a technique that creates data structures that store the values of one or more columns of a table in a sorted order to speed up queries; Excel is a software application that allows users to organize and manipulate data in rows and columns; normalization is a process that organizes data into tables and columns to reduce redundancy and improve consistency. 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 option that the administrator should implement to ensure high availability of the database is replication. Replication is a process that copies and synchronizes data from one database server (the primary or source) to one or more database servers (the secondary or target). Replication helps ensure high availability of the database by providing redundancy, fault tolerance, and load balancing. If the primary server fails, the secondary server can take over and continue to serve the data without interruption or data loss. The other options are either not related or not suitable for this purpose. For example, ETL is a process that extracts, transforms, and loads data from one source to another for analysis or reporting purposes; database dumping is a process that exports the entire content of a database to a file for backup or migration purposes; backup and restore is a process that copies and recovers data from a backup device or media in case of a disaster or corruption. References: CompTIA DataSys+ Course Outline, Domain 5.0 Business Continuity, Objective 5.3 Given a scenario, implement replication of database management systems.

The two factors that the database administrator should monitor to gauge server health are CPU usage and memory usage. CPU usage is the percentage of time that the processor (CPU) of the server is busy executing instructions or processes. CPU usage indicates how much workload the server can handle and how fast it can process requests. High CPU usage may affect the performance or availability of the server and cause delays or errors. Memory usage is the amount of physical memory (RAM) or virtual memory (swap space) that the server uses to store data or run applications. Memory usage indicates how much space the server has to store temporary or intermediate data or results. High memory usage may affect the performance or availability of the server and cause swapping or paging. The other options are either not relevant or not direct indicators of server health. For example, transaction logs are files that record the changes made by transactions on the database; network sniffer is a tool that captures and analyzes network traffic; domain controllers are servers that manage user authentication and authorization in a network; firewall traffic is the amount of data that passes through a firewall device or software. References: CompTIA DataSys+ Course Outline, Domain 3.0 Database Management and Maintenance, Objective 3.2 Given a scenario, monitor database performance.

The database administrator should mask the sensitive data before giving the developers access to the environment. Data masking is a technique that replaces sensitive data with fictitious but realistic data, such as random numbers or characters, to protect it from unauthorized access or exposure. Data masking preserves the format and structure of the original data, but does not reveal its actual value. This allows developers to work with realistic data without compromising its confidentiality or compliance. The other options are either insufficient or excessive for this scenario. For example, auditing access to tables with sensitive data may help monitor and track who accesses the data, but does not prevent it from being seen; removing sensitive data from tables may compromise the quality or completeness of the data, and may not be feasible if there is a large amount of data; encrypting connections to the development environment may protect the data in transit, but not at rest or in use. References: CompTIA DataSys+ Course Outline, Domain 4.0 Data and Database Security, Objective 4.2 Given a scenario, implement security controls for databases.

The index that stores records in a tabular format is columnstore. A columnstore index is a type of index that stores and compresses data by columns rather than by rows. A columnstore index can improve the performance and efficiency of queries that perform aggregations, calculations, or analysis on large amounts of data, such as data warehouse or business intelligence applications. A columnstore index can also reduce the storage space required for data by applying various compression techniques, such as dictionary encoding, run-length encoding, bit packing, etc. The other options are either different types of indexes or not related to indexes at all. For example, a non-clustered index is a type of index that stores the values of one or more columns in a sorted order along with pointers to the corresponding rows in the table; a unique index is a type of index that enforces uniqueness on one or more columns in a table; a secondary index is an alternative term for a non-clustered index. References: CompTIA DataSys+ Course Outline, Domain 3.0 Database Management and Maintenance, Objective 3.1 Given a scenario, perform common database maintenance tasks.

The document that a company should develop to ensure preparedness for a fire in a data center is a disaster recovery plan. A disaster recovery plan is a document that outlines how an organization will continue its operations in the event of a disaster or disruption, such as fire, flood, earthquake, cyberattack, etc. A disaster recovery plan typically includes the following elements: - The objectives and scope of the plan - The roles and responsibilities of the staff involved - The identification and assessment of the risks and impacts - The strategies and procedures for restoring the critical functions and data - The resources and tools required for the recovery process - The testing and maintenance schedule for the plan A disaster recovery plan helps an organization to minimize the damage and downtime caused by a disaster, as well as to resume normal operations as soon as possible. The other options are either different types of documents or not specific to fire preparedness. For example, a deployment plan is a document that describes how a system or software will be installed or launched; a backup plan is a document that specifies how data will be copied and stored for backup purposes; a data retention policy is a document that defines how long data should be kept and when it should be deleted or archived. References: CompTIA DataSys+ Course Outline, Domain 5.0 Business Continuity, Objective 5.4 Given a scenario, implement disaster recovery methods.

The option that sets the age requirement for data that should be recovered after a major disaster is RPO. RPO, or Recovery Point Objective, is a metric that defines the maximum amount of data that can be lost or acceptable data loss in the event of a disaster or disruption. RPO indicates how frequently the data should be backed up or replicated to minimize the risk of data loss. RPO also sets the age requirement for data that should be recovered after a major disaster, as it determines how far back in time the recovery process should go. For example, if the RPO is one hour, then the data should be backed up or replicated every hour, and the recovery process should restore the data to the state it was in one hour before the disaster. The other options are either different metrics or not related to data recovery at all. For example, MTBF, or Mean Time Between Failures, is a metric that measures the average time that a system or component operates without failure; RTO, or Recovery Time Objective, is a metric that defines the maximum amount of time that can be taken to restore a system or service after a disaster or disruption; MTTF, or Mean Time To Failure, is a metric that measures the average time that a system or component operates until it fails. References: CompTIA DataSys+ Course Outline, Domain 5.0 Business Continuity, Objective 5.3 Given a scenario, implement backup and restoration of data.

The factor that the administrator should measure to analyze a database server’s disk throughput is IOPS. IOPS, or Input/Output Operations Per Second, is a metric that measures the number of read and write operations that a disk can perform in one second. IOPS indicates the performance or speed of a disk and how well it can handle multiple requests or transactions. Higher IOPS means higher disk throughput and lower latency. IOPS can be affected by various factors, such as disk type, size, speed, cache, RAID level, etc. The other options are either not related or not sufficient for this purpose. For example, RPfvl is not a valid acronym or metric; latency is the time delay between a request and a response; reads are the number of read operations performed by a disk. References: CompTIA DataSys+ Course Outline, Domain 3.0 Database Management and Maintenance, Objective 3.2 Given a scenario, monitor database performance.

The query that the administrator should use to create the table is option B. This query uses the CREATE TABLE statement to define a new table named XYZ with three columns: ID, Name, and Age. Each column has a data type and a constraint, such as NOT NULL, PRIMARY KEY, or CHECK. The other options either have syntax errors, use incorrect keywords, or do not specify the table name or columns correctly. References: CompTIA DataSys+ Course Outline, Domain 1.0 Database Fundamentals, Objective 1.1 Given a scenario, identify and apply database structure types.

The SQL syntax that the administrator should use to create an object is option B. This syntax uses the CREATE TABLE statement to define a new table named customer with four columns: customer_id, name, email, and phone. Each column has a data type and a constraint, such as NOT NULL or PRIMARY KEY. The other options either have syntax errors, use incorrect keywords, or do not specify the table name or columns correctly. References: CompTIA DataSys+ Course Outline, Domain 1.0 Database Fundamentals, Objective 1.1 Given a scenario, identify and apply database structure types.

The attack in which an attacker hopes to profit from locking the database software is ransomware. Ransomware is a type of malware that encrypts the data or files on a system or network and demands a ransom from the victim to restore them. Ransomware can target database software and lock its access or functionality until the victim pays the ransom, usually in cryptocurrency. Ransomware can cause serious damage and loss to the victim, as well as expose them to further risks or threats. Ransomware can be delivered through various methods, such as phishing emails, malicious attachments, compromised websites, etc. The other options are either different types of attacks or not related to locking database software at all. For example, spear phishing is a type of phishing attack that targets a specific individual or organization with personalized or customized emails; SQL injection is a type of attack that inserts malicious SQL statements into an input field or parameter of a web application to manipulate or compromise the underlying database; on-path is a type of attack that intercepts and modifies the data in transit between two parties on a network. References: CompTIA DataSys+ Course Outline, Domain 4.0 Data and Database Security, Objective 4.4 Given a scenario, identify common types of attacks against databases

The option that is part of logical database infrastructure security is perimeter network. Perimeter network, also known as DMZ (Demilitarized Zone), is a network segment that lies between an internal network and an external network, such as the internet. Perimeter network provides an additional layer of security for the internal network by isolating and protecting the servers or services that are exposed to the external network, such as web servers, email servers, database servers, etc. Perimeter network also helps prevent unauthorized access or attacks from the external network to the internal network by using firewalls, routers, proxies, etc. The other options are either part of physical database infrastructure security or not related to database infrastructure security at all. For example, surveillance is a method of monitoring and recording physical activities or events in a location or resource; biometric access is a device that uses biological characteristics to control access to a physical location or resource; cooling system is a device or system that regulates the temperature and humidity of a location or resource. References: CompTIA DataSys+ Course Outline, Domain 4.0 Data and Database Security, Objective 4.1 Given a scenario, implement database infrastructure security.

The correct answer is A. Columnstore. According to CompTIA DataSys+, a columnstore index stores data in a column-oriented, tabular structure, where each column of a table is stored separately rather than storing entire rows together. This design is particularly optimized for analytical and reporting workloads, which commonly scan large datasets and perform aggregations on specific columns.

In a columnstore index, data is logically still represented in a table-like (tabular) format, but physically organized by columns instead of rows. This allows the database engine to read only the required columns for a query, significantly reducing disk I/O and improving query performance. DataSys+ highlights columnstore indexes as a best practice for data warehousing, business intelligence, and read-heavy analytical queries.

Option B, a non-clustered index, stores a separate index structure that contains indexed column values and pointers to the underlying table rows. While it improves lookup performance, it does not store data in a tabular columnar format. Option C, a unique index, is a constraint-based index that enforces uniqueness on column values but does not define how data is physically stored. Option D, a secondary index, is a general term for indexes that are not primary and does not specifically describe column-based tabular storage.

Sys+ emphasizes understanding different index types and their appropriate use cases. Columnstore indexes are distinct because they physically reorganize data by columns, compress data efficiently, and support high-performance analytics. This makes them especially effective in scenarios involving large datasets and complex queries.

Therefore, the index type that stores records in a tabular, column-oriented format is the columnstore index, making option A the correct and fully verified answer aligned with CompTIA DataSys+ objectives.

The NoSQL database type that best categorizes MongoDB is document. Document databases are databases that store and manage data as documents, which are collections of fields and values in formats such as JSON (JavaScript Object Notation) or XML (Extensible Markup Language). Document databases do not use any schema or structure to organize data, but rather use identifiers or indexes to enable flexible and dynamic access to data based on fields or values. Document databases are suitable for storing large amounts of complex or unstructured data that have variable attributes or nested structures. MongoDB is an example of a document database that uses JSON-like documents to store and query data. The other options are either different types of NoSQL databases or not related to NoSQL databases at all. For example, column-oriented databases are databases that store and manage data as columns rather than rows; graph databases are databases that store and manage data as nodes and edges that represent entities and relationships; key-value stores are databases that store and manage data as pairs of keys and values. References: CompTIA DataSys+ Course Outline, Domain 1.0 Database Fundamentals, Objective 1.1 Given a scenario, identify common database types.