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 potential issue raised by enterprise database users is the need for concurrent access and multiuser updates. Concurrent access means that multiple users can access the same data at the same time, while multiuser updates mean that multiple users can modify the same data at the same time. These features are essential for enterprise database users who need to share and collaborate on data in real time. However, they also pose challenges such as maintaining data consistency, preventing conflicts or errors, and ensuring transaction isolation and durability. The other options are either not issues or not specific to enterprise database users. For example, the need for multiple views or windows into the same database may be a preference or a convenience, but not an issue; the need to manage long transactions may be a challenge for any database user, not just enterprise ones; the need to manually transfer records to paper may be an outdated or inefficient practice, but not an issue.

The resource that is the best way to lock rows in SQL Server is RID. RID, or Row IDentifier, is an attribute that uniquely identifies each row in a heap table in SQL Server. A heap table is a table that does not have a clustered index, which means that the rows are not stored in any particular order. A RID consists of the file number, page number, and slot number of the row in the database. A RID can be used to lock rows in SQL Server to prevent concurrent access or modification by other transactions or users. A RID lock is a type of lock that locks a single row using its RID. A RID lock can be applied using the HOLDLOCK or XLOCK hints in a SELECT statement. The other options are either not related or not effective for this purpose. For example, TID, or Transaction IDentifier, is an attribute that uniquely identifies each transaction in a database; SID, or Security IDentifier, is an attribute that uniquely identifies each user or group in a Windows system; PID, or Process IDentifier, is an attribute that uniquely identifies each process in an operating system. References: CompTIA DataSys+ Course Outline, Domain 3.0 Database Management and Maintenance, Objective 3.3 Given a scenario, implement database concurrency methods.

The two options that can be used to protect physical database appliances from damage in a server room are fire suppression systems and cooling systems. Fire suppression systems are systems that detect and extinguish fires in a server room using water, gas, foam, or other agents. Fire suppression systems help prevent damage to physical database appliances caused by fire hazards such as overheating, electrical faults, or flammable materials. Cooling systems are systems that regulate the temperature and humidity in a server room using fans, air conditioners, chillers, or other devices. Cooling systems help prevent damage to physical database appliances caused by excessive heat or moisture that may affect their performance or lifespan. The other options are either not related or not effective for this purpose. For example, biometric access systems, camera systems, and key card systems are systems that control the access to a server room using fingerprints, facial recognition, video surveillance, or magnetic cards; these systems help prevent unauthorized entry or theft of physical database appliances, but not damage caused by environmental factors; database control systems are systems that manage the functionality and security of databases using software tools or commands; these systems help protect logical database appliances from errors or attacks, but not physical damage caused by environmental factors. References: CompTIA DataSys+ Course Outline, Domain 5.0 Business Continuity, Objective 5.4 Given a scenario, implement disaster recovery methods.

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.