The ORM snippet that would return the ID, state, and country of all customers with the newest customers appearing first is option C. This snippet uses the  select  method to specify the columns to be returned, the  order  method to sort the results by ID in descending order, and the  all  method to fetch all the records. The other options either have syntax errors, use incorrect methods, or do not sort the results correctly. References:  CompTIA DataSys+ Course Outline , Domain 1.0 Database Fundamentals, Objective 1.2 Given a scenario, execute database tasks using scripting and programming languages.

The best action for the administrator to take is to delete all the backup files that are not required by the backup retention policy. This will free up disk space on the server and also comply with the best practices for data backup and recovery. The backup retention policy defines how long the backup files should be kept and when they should be deleted or archived. The other options are either risky, inefficient, or impractical. For example, moving all the backup files to external disks would require additional hardware and time, deleting all the backup files containing data that is rated as classified would compromise data security and compliance, and deleting all the backup files except for the most recent one would limit the recovery options in case of a disaster. 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 option that best describes a collection of data that shares the same properties or attributes is entity set. An entity set is a term used in the entity-relationship (ER) model, which is a conceptual model for designing and representing databases. An entity set is a collection of entities that have the same type or characteristics, such as students, courses, products, etc. An entity is an object or thing that can be identified and distinguished from others, such as a specific student, course, product, etc. An entity set can have one or more attributes that describe the properties or features of the entities, such as name, age, price, etc. An entity set can also have one or more relationships with other entity sets that define how the entities are associated or connected, such as enrolled, taught by, purchased by, etc. The other options are either different terms or not related to the ER model at all. For example, relation set is a term used in the relational model, which is a logical model for implementing and manipulating databases; ER model is a term used to refer to the entity-relationship model itself; tuples are rows or records in a table or relation. References:  CompTIA DataSys+ Course Outline , Domain 1.0 Database Fundamentals, Objective 1.1 Given a scenario, identify common database types.

The correct answer is C. An exact match is not possible in a SELECT statement . CompTIA DataSys+ documentation explains that wildcards are used in SQL primarily within the WHERE clause of a SELECT statement to enable pattern matching rather than exact value matching. Wildcards such as % and _ are commonly used with the LIKE operator to search for partial strings or variable patterns in character-based data.

In practical database usage, wildcards allow analysts and administrators to retrieve records when the full or exact value is unknown or unnecessary. For example, searching for all patient records with last names starting with “Mac%” or all email addresses ending in “@example.com” requires pattern-based matching. In these cases, an exact match is explicitly not required , which is the core purpose of wildcards in SQL queries.

Option A and D incorrectly reference the CREATE statement. Wildcards are not relevant to CREATE statements, which are used for defining database objects such as tables, indexes, or views. These statements require explicit definitions and do not support wildcard-based matching logic. Option B is also incorrect because a SELECT statement does not always require an exact match; this is precisely why wildcards exist and are heavily used in querying operations.

CompTIA DataSys+ emphasizes that understanding query flexibility is essential for data retrieval and reporting. Wildcards enhance query usability and efficiency by allowing broader result sets without complex logic or multiple conditions. They are particularly valuable in analytical, reporting, and troubleshooting scenarios where partial data exploration is required.

Therefore, the best description of the function of a wildcard in the WHERE clause is that it allows queries where an exact match is not required , making option C the correct and fully aligned answer according to CompTIA DataSys+ principles.

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.