The principle that addresses this issue is least privilege. Least privilege is a security principle that states that users should only have the minimum level of access or permissions required to perform their tasks or roles.
By applying this principle, the administrator can ensure that users cannot change data unless they have been authorized by the management team through a request approval process. This prevents unauthorized or accidental modifications of data that may compromise its integrity or security. The other options are either opposite or unrelated to this principle. For example, open access means that users have unrestricted access to data; least resistance means that users have the easiest or most convenient access to data; elevated privilege means that users have higher or more permissions than they need. References: CompTIA DataSys+ Course Outline, Domain 4.0 Data and Database Security, Objective 4.1 Given a scenario, apply security principles and best practices for databases.

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 document that the administrator should create to illustrate the interaction between tables is an entity relationship diagram. An entity relationship diagram (ERD) is a graphical representation of the entities (tables), attributes (columns), and relationships (constraints) in a database. An ERD helps the administrator to visualize the structure and design of the database, as well as the dependencies and associations among the tables. The other options are either different types of documents or not related to the interaction between tables. For example, a troubleshooting guide is a document that provides instructions on how to solve common problems or errors in a database; a data dictionary is a document that describes the metadata (information about data) of a database; a database reference manual is a document that provides information on how to use or operate a database. 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 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.

The correct order of the steps in the database deployment process is option C. This order follows the best practices for deploying a database system, which are:
* Confirm prerequisites: Check the system requirements and compatibility of the database software and tools before installation.
* Install: Install the database software and tools on the target server or platform.
* Configure: Configure the database settings and parameters according to the specifications and needs of the application or organization.
* Connect: Connect the database to the network and other systems or applications that will access it.
* Test: Test the functionality and performance of the database system and verify that it meets the expectations and requirements.
* Validate: Validate the data quality and integrity of the database system and ensure that it complies with the standards and regulations.
* Release: Release the database system to production and make it available for use by end-users or customers. The other options do not follow this order and may result in errors, inefficiencies, or security issues. References: CompTIA DataSys+ Course Outline, Domain 2.0 Database Deployment, Objective
2.1 Given a scenario, install and configure database software and tools.