CompTIA DS0-001 - CompTIA DataSys+ Certification Exam

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 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 two resources that are best for monitoring potential server issues 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, user connections are the number of users who are connected to a database server at any given time; firewall usage is the amount of data that passes through a firewall device or software; index usage is the frequency or efficiency of using indexes on tables to speed up queries; query execution is the process of running SQL statements on a database server. References: CompTIA DataSys+ Course Outline, Domain 3.0 Database Management and Maintenance, Objective 3.2 Given a scenario, monitor database performance.

The correct answers are D. It can contain more than one data file and F. It can be used to organize data in a database. CompTIA DataSys+ describes a tablespace as a logical storage container used by a database to organize how data is physically stored on disk. Tablespaces provide an abstraction layer between the logical database objects and the physical storage files.

A tablespace can include multiple data files, which allows database administrators to distribute data across different disks or storage systems. This capability supports scalability, performance optimization, and high availability. By adding or resizing data files within a tablespace, administrators can expand storage capacity without restructuring the database schema. DataSys+ highlights this as a key advantage for capacity planning and storage management.

Tablespaces are also used to organize data within a database. Different tablespaces can be created for different purposes, such as separating user data, indexes, temporary data, and system metadata. This organization improves performance tuning, simplifies backup and recovery operations, and enhances manageability. For example, placing indexes in a separate tablespace from table data can reduce I/O contention.

Option A is incorrect because a tablespace belongs to a single database and cannot span multiple databases. Option B is misleading; while tablespaces map to data files, blocks are allocated within files, not mixed arbitrarily across files. Option C is incorrect because segments are allocated in extents, and their sizing behavior is controlled by storage parameters, not defined as a primary purpose of tablespaces. Option E is incorrect because tablespaces represent disk-based storage, not memory-resident structures.

CompTIA DataSys+ emphasizes understanding logical versus physical storage concepts. Tablespaces play a central role in bridging these concepts by organizing data logically while enabling flexible physical storage management. Therefore, the best descriptions of a tablespace are D and F, making them the correct and verified answers.

The script that would set the database recovery model for sys.database is option A. This script uses the ALTER DATABASE statement to modify the recovery model of the sys.database to full with no wait. The other options either have syntax errors, use incorrect keywords, or do not specify the recovery model correctly. References: CompTIA DataSys+ Course Outline, Domain 3.0 Database Management and Maintenance, Objective 3.1 Given a scenario, perform common database maintenance tasks.

The best way for the administrator to accomplish this task is to create a materialized view. A materialized view is a type of view that stores the result of a query on one or more tables as a separate table in the database. A materialized view can aggregate data from multiple tables in a way that does not impact the original tables, and then provide this information to a department as a single source of truth. A materialized view also improves query performance and efficiency by reducing the need to recompute complex queries every time they are executed. The other options are either not suitable or not optimal for this task. For example, creating indexes on those tables may improve query performance on individual tables, but not on aggregated data; creating a new database may require additional resources and maintenance, and may introduce inconsistency or redundancy; creating a function may require additional coding and execution, and may not store the result as a separate table. References: CompTIA DataSys+ Course Outline, Domain 2.0 Database Deployment, Objective 2.2 Given a scenario, create database objects using scripting and programming languages.

A scenario in which a database administrator would use a relational database rather than a non-relational database is when an organization wants to maintain consistency among the data in the database. A relational database is a type of database that organizes data into tables with predefined columns and rows, and enforces rules and constraints to ensure data integrity and accuracy. A relational database also supports transactions, which are sets of operations that must be executed as a whole or not at all, to prevent data corruption or inconsistency. The other options are either not exclusive to relational databases or not relevant to the choice of database type. For example, data encryption can be applied to both relational and non-relational databases, processing complex data sets may require specialized tools or techniques that are not dependent on the database type, and storing a large number of videos, photos, and documents may be better suited for a non-relational database that can handle unstructured or semi-structured data. References: CompTIA DataSys+ Course Outline, Domain 1.0 Database Fundamentals, Objective 1.1 Given a scenario, identify and apply database structure types.

The first thing that the database administrator should examine to troubleshoot the issue is the event log. The event log is a file that records the events and activities that occur on a system, such as database backups, errors, warnings, or failures. By examining the event log, the administrator can identify the cause and time of the backup failure, and also check for any other issues or anomalies that may affect the backup process or the backup quality. The other options are either not relevant or not the first priority for this task. For example, CPU usage, disk space, and OS performance may affect the performance or availability of the system, but not necessarily cause the backup failure; moreover, these factors can be checked after reviewing the event log for more information. References: CompTIA DataSys+ Course Outline, Domain 5.0 Business Continuity, Objective 5.2 Given a scenario, implement backup and restoration of database management systems.

The correct answer is B. Brute-force. CompTIA DataSys+ identifies brute-force attacks as a common authentication-based threat in database and system environments. A brute-force attack involves repeatedly attempting to authenticate to an account by systematically trying different credentials or repeatedly targeting known or default accounts in hopes that one attempt will succeed. The presence of multiple ongoing connection attempts in logs is a key indicator of this attack type.

In this scenario, the attacker is attempting to connect using a default account, even though it has been disabled. Default accounts are well-known targets because attackers are often aware of their usernames and may assume weak or unchanged credentials. DataSys+ emphasizes that attackers frequently attempt brute-force or password-spraying attacks against default or administrative accounts, especially when exposed services are accessible over the network. Even if the account is disabled, repeated attempts still generate log entries and clearly signal brute-force behavior.

Option A, malware, typically involves malicious software executing on a system and does not primarily manifest as repeated login attempts in authentication logs. Option C, on-path (man-in-the-middle) attacks, involve intercepting or altering network traffic between two parties and would not appear as repeated failed authentication attempts from a single source. Option D, SQL injection, targets application input fields and database queries, not authentication mechanisms tied to account logins.

CompTIA DataSys+ stresses the importance of monitoring logs for failed authentication attempts as part of intrusion detection and security auditing. It also highlights defensive controls such as account lockout policies, disabling default accounts, strong authentication mechanisms, and intrusion detection systems to mitigate brute-force attacks.

Because the defining characteristic in the scenario is repeated connection attempts against an account, the activity is best classified as a brute-force attack, making option B the correct and fully verified answer.