View Full CompTIA DataSys+ DS0-001 Exam Dumps and Practice Test Dumps

 

Question 361.

A database administrator is preparing a highly available database cluster for a planned maintenance event. What should be verified FIRST before taking the active node offline?

1. The standby node is healthy, synchronized, and capable of supporting the production workload
2. All historical backups have been deleted
3. The application password has been changed
4. Every index has been rebuilt

Correct Answer: 1. The standby node is healthy, synchronized, and capable of supporting the production workload

Explanation:

Before intentionally taking an active database node offline, the administrator should confirm that the standby or secondary node is healthy and ready to assume production responsibilities. This includes verifying replication status, synchronization, available CPU and memory, storage capacity, network connectivity, database consistency, required services, security configuration, and application connectivity. The team should also confirm that failover procedures are documented and that monitoring remains active during the transition. If the standby is significantly behind or lacks sufficient capacity, a planned maintenance event could turn into an outage or create data-loss risk. Deleting backups or rebuilding indexes is not inherently required before failover. A controlled maintenance process should include readiness checks, change approval, application coordination, failover validation, and a defined method for returning to the preferred topology after maintenance is complete.

Question 362.

A database cluster automatically moves service from a failed primary node to a healthy secondary node without manual administrator intervention. Which capability is being used?

1. Manual recovery
2. Automatic failover
3. Data masking
4. Table normalization

Correct Answer: 2. Automatic failover

Explanation:

Automatic failover allows a high-availability system to detect that the active database node is unavailable and transfer service to another healthy node without waiting for an administrator to initiate the process. This can significantly reduce downtime and help organizations meet aggressive recovery time objectives. The cluster generally uses health checks, quorum or voting logic, replication status, and service monitoring to determine whether failover should occur. Automatic failover must be designed carefully because incorrect failure detection can cause unnecessary role changes or split-brain conditions. Administrators should test failover behavior under realistic scenarios, including network loss, storage failure, service crashes, and node outages. Automatic failover supports availability but does not replace backups, disaster recovery planning, or application-level retry logic. Normalization and masking solve unrelated database design and security problems.

Question 363.

A company needs a database architecture that can continue operating even if an entire availability zone fails. Which design is MOST appropriate?

1. Place all database instances and storage in one availability zone
2. Keep only one database server with a larger CPU
3. Deploy redundant database resources across separate failure domains or availability zones
4. Disable replication to reduce complexity

Correct Answer: 3. Deploy redundant database resources across separate failure domains or availability zones

Explanation:

If all database resources are located within one failure domain, an outage affecting that location can make every component unavailable at the same time. Distributing database nodes, storage, and supporting services across independent availability zones or failure domains reduces the chance that one local infrastructure failure removes the entire service. The database platform may use synchronous or asynchronous replication depending on latency, consistency, and recovery requirements. Administrators should also verify that networking, load balancing, monitoring, credentials, and application routing can survive the same zone failure. Merely adding CPU to a single server does not address location-level risk. Disabling replication would weaken resilience. Multi-zone designs should be tested regularly because architecture diagrams alone do not prove that applications can reconnect or that failover meets the required RTO and RPO.

Question 364.

A database service remains available after a server failure, but users lose the last several seconds of committed transactions. Which design characteristic MOST likely explains this behavior?

1. Data compression
2. Synchronous replication with zero lag
3. Table partitioning
4. Asynchronous replication to the failover target**

Correct Answer: 4. Asynchronous replication to the failover target

Explanation:

Asynchronous replication allows the primary database to acknowledge transactions before the secondary has fully received or applied those changes. This reduces transaction latency, especially when the replica is geographically distant, but it creates a window in which the primary may contain newer committed data than the secondary. If the primary fails during that window, the failover target may be missing the most recent transactions. This behavior directly affects the achievable recovery point objective. Administrators should monitor replication lag and confirm that the potential loss window remains acceptable to the business. Synchronous replication generally reduces this risk because acknowledgment waits for the required replica confirmation, though it may increase latency. Compression and partitioning do not explain missing recent transactions after failover.

Question 365.

A company requires that no acknowledged transaction be lost if the primary database node fails. Which replication approach BEST supports this requirement when latency is acceptable?

1. Synchronous replication
2. Weekly full backup only
3. Manual CSV export
4. Read-only caching

Correct Answer: 1. Synchronous replication

Explanation:

Synchronous replication is designed to ensure that required transaction information reaches another protected location before the primary confirms success to the client. This can support a near-zero or zero data-loss objective for certain failure scenarios, depending on the implementation and failure model. The trade-off is additional transaction latency because the primary must wait for network communication and replica acknowledgment. Geographic distance can therefore make synchronous replication impractical for some workloads. Administrators must also consider quorum, storage behavior, replica health, and application retry logic because replication alone cannot eliminate every failure mode. Weekly backups provide historical recovery but cannot protect every committed transaction between backup events. Read-only caches and CSV exports do not provide transactional durability across a primary-node failure.

Question 366.

A database administrator notices that a standby server has been disconnected from the primary for several hours. Which concern should be addressed FIRST?

1. The standby’s table names may differ
2. The standby may no longer meet the required recovery point objective
3. All user passwords must be reset
4. The primary key values will automatically change

Correct Answer: 2. The standby may no longer meet the required recovery point objective

Explanation:

A disconnected standby cannot receive current database changes, so the gap between primary and secondary continues to grow. If the primary fails before replication catches up, the organization could lose more data than the documented RPO allows. The administrator should determine when replication stopped, why connectivity failed, whether transaction logs or change records needed for resynchronization are still available, and how long catch-up will take. Monitoring should alert on replication interruption or lag before the problem becomes severe. If the secondary is also part of the disaster recovery strategy, prolonged disconnection may require escalation because the organization effectively has reduced resilience. User passwords and primary keys do not automatically change because replication is interrupted. The key operational issue is whether the standby remains a valid and sufficiently current recovery target.

Question 367.

A database administrator wants to determine whether the recovery environment can handle the same workload as production after failover. Which test is MOST appropriate?

1. Run representative workload and capacity testing in the recovery environment
2. Verify only that the database service starts
3. Check the recovery server’s hostname
4. Confirm that one administrator can log in

Correct Answer: 1. Run representative workload and capacity testing in the recovery environment

Explanation:

A disaster recovery environment can be technically available yet still lack the resources needed to support real production demand. Representative workload testing evaluates whether CPU, memory, storage, network capacity, connection limits, query performance, and application throughput remain acceptable after failover. Testing should simulate realistic transaction rates, reporting demand, batch jobs, and concurrent users where practical. A standby that merely starts successfully may fail under normal production volume. Organizations sometimes size recovery systems smaller to reduce cost, but this trade-off must be understood and aligned with business expectations. Capacity testing should also verify dependencies such as authentication, application servers, integration services, and monitoring. The objective is to demonstrate that recovered service is not only online but usable at the required performance level.

Question 368.

A database failover succeeds, but applications continue attempting to connect to the failed primary server. Which component was MOST likely not configured correctly?

1. Table normalization
2. Backup retention
3. Query statistics
4. Client connection routing, service endpoint, or failover-aware configuration**

Correct Answer: 4. Client connection routing, service endpoint, or failover-aware configuration

Explanation:

High availability requires more than moving the database role from one server to another. Applications must also know how to locate the new active instance. This may be handled through a virtual endpoint, listener, load balancer, DNS mechanism, connection-string option, service discovery system, or database-driver failover capability. If clients continue targeting the failed server directly, the database failover itself does not restore usable application service. Administrators should test connection behavior during planned failover and verify that applications retry appropriately rather than caching obsolete endpoints indefinitely. DNS time-to-live values, load balancer health checks, firewall rules, and connection pools may all influence reconnection time. Normalization, statistics, and backup retention do not determine where an application sends new database connections.

Question 369.

A database cluster experiences repeated failovers between two nodes even though neither node has a permanent hardware failure. What should the administrator investigate FIRST?

1. Health-check thresholds, network stability, resource exhaustion, and cluster logs
2. Data classification labels
3. Backup filenames
4. Number of columns in each table

Correct Answer: 1. Health-check thresholds, network stability, resource exhaustion, and cluster logs

Explanation:

Repeated unplanned role changes, sometimes called failover flapping, often indicate unstable health detection rather than a permanent node failure. Intermittent network loss, storage pauses, CPU exhaustion, long garbage-collection events, overloaded virtual hosts, or overly sensitive health-check thresholds can cause a cluster to incorrectly conclude that a node is unavailable. Administrators should review cluster logs, node health history, network metrics, storage latency, operating-system events, and failover reasons. Simply forcing the database back to the preferred node without identifying the trigger may allow the cycle to continue. Health checks should detect genuine failures quickly without reacting to harmless short delays. Backup naming and table design are unrelated to cluster instability. The goal is to identify whether the problem is infrastructure, configuration, workload, or cluster logic.

Question 370.

A company wants database services in two regions, but only one region should accept writes at a time. Which architecture BEST fits this requirement?

1. Multi-primary write architecture
2. Cross-region active-passive architecture
3. Single-server local database only
4. Standalone spreadsheet replication

Correct Answer: 2. Cross-region active-passive architecture

Explanation:

A cross-region active-passive architecture uses one region as the active production location while another region maintains a synchronized standby environment. During a regional outage or planned transition, the passive region can be promoted to serve the workload. This approach avoids the write-conflict complexity of multi-primary designs while providing geographic resilience. Replication between distant regions is often asynchronous because synchronous round-trip latency can significantly slow transactions, although the exact design depends on the database platform and business requirements. Administrators should define how applications are redirected, how replication is monitored, how failover is authorized, and how failback occurs later. The architecture should also account for regional dependencies such as identity, secrets, DNS, application servers, and network connectivity. A single local database does not protect against regional failure.

Question 371.

A database administrator is evaluating whether to use active-active database architecture. Which challenge is MOST important to consider?

1. Conflict detection and consistency when multiple locations accept writes
2. The font used in database diagrams
3. Whether backups use lowercase filenames
4. The number of comments in SQL scripts

Correct Answer: 1. Conflict detection and consistency when multiple locations accept writes

Explanation:

Active-active architectures can improve availability and distribute workload, but allowing multiple sites or nodes to accept writes creates complex consistency challenges. Two locations may update the same record concurrently, create identifiers independently, or make conflicting business decisions before replication completes. The database must therefore provide a defined conflict-resolution model, distributed transaction behavior, ownership strategy, or application-level rules. Network partitions are particularly important because both sides may remain operational while unable to communicate. Administrators must understand whether the platform favors availability, consistency, or specific conflict semantics under these conditions. Active-active designs also complicate monitoring, backup, schema changes, and incident response. The architecture should be chosen only when business requirements justify the additional complexity rather than because it appears more redundant on a diagram.

Question 372.

A database administrator must verify that a failover did not create two writable primary nodes simultaneously. Which condition is the administrator checking for?

1. Cache warming
2. Data compression
3. Index fragmentation
4. Split brain**

Correct Answer: 4. Split brain

Explanation:

Split brain occurs when multiple nodes believe they are authorized to act as primary and may independently accept writes. This can happen during network partitions, quorum failures, incorrect fencing, or poorly designed failover mechanisms. Conflicting writes may cause divergent datasets that are difficult to reconcile automatically. Administrators should use quorum, witness services, fencing, lease mechanisms, or other platform-supported controls to ensure that only the valid primary remains writable. After a failover event, cluster status and application routing should be checked to confirm that no isolated former primary is still accepting transactions. Split-brain prevention is critical in high-availability systems because preserving service while allowing uncontrolled divergence can be more damaging than a short outage. Compression and index maintenance are unrelated to primary-role ownership.

Question 373.

A database administrator wants to minimize recovery time after a complete server loss. Which preparation is MOST effective?

1. Maintain a ready standby with current data and tested failover procedures
2. Keep only printed copies of database schemas
3. Perform no recovery testing to avoid production risk
4. Store all backups on the failed server’s local disk

Correct Answer: 1. Maintain a ready standby with current data and tested failover procedures

Explanation:

A ready standby can substantially reduce recovery time because the database software, configuration, schema, and most or all data are already present before the incident occurs. The recovery process may require only promotion, service routing, validation, and application reconnection rather than provisioning a server and restoring large backups from scratch. The standby should be continuously monitored to ensure it remains synchronized and healthy. Planned failover exercises validate that the documented procedure actually works and reveal missing dependencies or permissions. Backups remain essential because a standby can replicate logical corruption or accidental deletion, but local-only backups on the failed server are insufficient. Printed schemas do not provide data recovery. Recovery architecture should be selected according to business RTO, RPO, cost, complexity, and required level of availability.

Question 374.

A company operates a hot disaster recovery site. Which description BEST matches a hot site?

1. An empty facility with no computing equipment
2. A fully or nearly fully prepared environment capable of rapid production recovery
3. A location used only to store paper documentation
4. A site that contains backups but no usable infrastructure

Correct Answer: 2. A fully or nearly fully prepared environment capable of rapid production recovery

Explanation:

A hot site is designed for rapid recovery and typically contains functioning infrastructure, networking, software, and current or nearly current copies of required data. It may continuously receive replicated changes and be ready for applications to fail over with relatively little configuration. This level of readiness can support a short RTO but generally costs more than warm or cold alternatives. A warm site contains more preparation than a cold site but may require additional configuration or data synchronization before becoming operational. A cold site usually provides facilities and perhaps basic infrastructure but requires much more recovery work. Organizations should select a site type based on business impact, recovery objectives, cost, regulatory requirements, and the complexity of dependent services rather than assuming every database requires the most expensive option.

Question 375.

A low-priority database can tolerate three days of downtime and can be rebuilt from archived backups. Which recovery strategy is MOST cost-effective?

1. A lower-cost cold recovery site with documented restore procedures
2. Synchronous multi-region active-active deployment
3. Multiple continuously writable primary databases
4. Zero-downtime automatic failover across three regions

Correct Answer: 1. A lower-cost cold recovery site with documented restore procedures

Explanation:

Recovery architecture should match business requirements rather than use the highest level of redundancy for every system. If a database can tolerate several days of downtime and can be restored reliably from archives, a cold site or other lower-cost recovery arrangement may be sufficient. This approach reduces infrastructure expense because resources do not need to remain fully provisioned and synchronized at all times. The trade-off is a longer recovery process involving provisioning, software setup, restoration, validation, and application reconnection. Administrators should still maintain tested backups, documentation, key material, and clear recovery responsibilities. Expensive multi-region synchronous or active-active architectures are more appropriate for systems where business impact justifies very short RTO and RPO. Cost optimization is strongest when recovery investment is aligned with business criticality.

Question 376.

A disaster recovery test shows that the database restores within 20 minutes, but application users cannot log in for another 90 minutes because an identity service was unavailable. What does this demonstrate?

1. Database recovery alone does not determine end-to-end service recovery time
2. The database backup is invalid
3. The application requires more indexes
4. Transaction logging should be disabled

Correct Answer: 1. Database recovery alone does not determine end-to-end service recovery time

Explanation:

Business services usually depend on more than the database. Authentication, DNS, network routes, certificates, application servers, message queues, APIs, storage services, secrets management, and other components may all be required before users can complete real transactions. An RTO should therefore be measured from the perspective of restored usable service rather than only the database restore duration. In this scenario, a 20-minute database recovery does not satisfy a 30-minute service RTO if users cannot authenticate for 90 additional minutes. Disaster recovery exercises should identify these cross-system dependencies and coordinate their recovery order. The database backup may be perfectly valid. Adding indexes or disabling logging would not address the identity-service dependency. End-to-end testing is necessary because isolated component tests can produce an unrealistic picture of true recoverability.

Question 377.

A database administrator wants to reduce the possibility that one administrator accidentally initiates an unnecessary regional failover. Which control BEST supports this requirement?

1. Require documented approval or dual control for high-impact failover actions
2. Give every user failover privileges
3. Disable audit logging
4. Use one shared administrator account

Correct Answer: 1. Require documented approval or dual control for high-impact failover actions

Explanation:

Regional failover is a high-impact action that can affect availability, data consistency, application routing, and recovery state. Requiring approval, peer verification, or dual control helps prevent accidental or unauthorized execution. Privileged access management systems can provide time-limited permissions, approval workflows, and detailed audit trails. Emergency procedures should still allow rapid action when a genuine disaster occurs, but the authorization model should be defined before the incident. Shared administrator accounts weaken accountability, and giving everyone failover rights increases operational risk. Audit logging should remain enabled so the organization can reconstruct who initiated a change and why. Separation of duties and controlled elevation are especially useful for actions that can change primary database ownership across regions or data centers.

Question 378.

During failover testing, a database administrator finds that the secondary server has the data but does not contain a required application login. Which issue does this reveal?

1. Data compression failure
2. Incomplete recovery of non-data dependencies and security configuration
3. Incorrect normalization
4. Excessive indexing

Correct Answer: 2. Incomplete recovery of non-data dependencies and security configuration

Explanation:

Database recovery must include more than user tables. Logins, roles, permissions, certificates, encryption keys, jobs, linked services, extensions, server-level objects, and configuration settings may exist outside the database or may not replicate automatically. A secondary server can therefore contain current application data yet still fail to support production because required security principals or dependencies are missing. Recovery planning should inventory these objects and define how they are replicated, recreated, or restored. Testing should verify application authentication and authorization rather than stopping after confirming database synchronization. Excessive indexes and normalization do not explain a missing login. The scenario demonstrates why disaster recovery must be validated at the application-service level and not merely by checking that database files exist on the standby.

Question 379.

A database administrator wants to ensure that the disaster recovery environment uses the same critical configuration as production. Which practice is BEST?

1. Use controlled configuration management and periodically compare the recovery environment against the production baseline
2. Configure the recovery site manually from memory during an outage
3. Avoid documenting configuration differences
4. Disable version control for deployment files

Correct Answer: 1. Use controlled configuration management and periodically compare the recovery environment against the production baseline

Explanation:

Configuration drift can make a disaster recovery environment fail at the moment it is needed. Critical differences in database parameters, extensions, certificates, firewall rules, operating-system settings, storage paths, or application credentials may prevent successful failover or cause unexpected performance problems. Configuration management tools, version-controlled deployment artifacts, infrastructure automation, and periodic comparison against an approved baseline can reduce this risk. Some differences between production and recovery may be intentional, such as smaller capacity at a warm site, but those differences should be documented and tested. Rebuilding configuration from memory during an outage is slow and error-prone. Disaster recovery systems should be treated as actively managed environments rather than forgotten infrastructure that is checked only after a major incident.

Question 380.

Which statement BEST describes a comprehensive database high-availability and disaster recovery strategy?

1. High availability and disaster recovery are identical and require only replication
2. A standby database eliminates the need for backups and recovery testing
3. Disaster recovery is needed only for hardware failures
4. A comprehensive strategy combines redundancy, replication, backups, quorum, failover, geographic recovery, monitoring, dependency planning, security, documentation, and regular testing**

Correct Answer: 4. A comprehensive strategy combines redundancy, replication, backups, quorum, failover, geographic recovery, monitoring, dependency planning, security, documentation, and regular testing

Explanation:

High availability and disaster recovery address related but distinct risks. High availability focuses primarily on keeping services operating through local component failures by using redundancy, clustering, health checks, replication, and failover. Disaster recovery addresses larger disruptions such as regional outages, severe corruption, ransomware, or loss of an entire production environment. A mature strategy combines multiple controls because no single technology handles every failure mode. Replication supports current copies but can propagate logical damage, so historical backups remain necessary. Quorum and fencing protect clustered consistency, monitoring detects degradation, and geographic recovery reduces location-level risk. Recovery plans must also include application, identity, network, certificate, and security dependencies. Documentation and regular exercises verify that people can execute the design successfully. Effective resilience therefore combines architecture, operations, governance, testing, and continuous improvement around clearly defined RTO and RPO targets.