Evaluation & maintenance

Who is responsible for examining each DBMS before making a decision to purchase a new one?

• System Analyst

• Database Administrator (DBA)

• Project Manager

What can a DBA assign during the DBMS evaluation process?

• A priority level

• A user feedback score

• A numerical ranking or weightage

What is a "runbook" used for in database maintenance?

• Tracking the database’s performance metrics

• Storing user credentials

• Keeping maintenance dates, license keys, and issue resolutions

Before starting a DBMS evaluation, the DBA must:

• Train the users on the new system

• Select a vendor without a formal evaluation

• Create a checklist and determine the weightage

After purchasing the DBMS, the DBA is primarily responsible for:

• Writing user manuals

• Installing and configuring the DBMS

• Training programmers

During the evaluation process, what can a DBA request (from the vendor) to better assess a DBMS?

• Marketing brochures

• Hands-on testing with a trial version

• User guides

Who does the DBA coordinate with to solve database-related problems?

• End-users only

• Marketing teams

• Programmers, users, and software vendors

What type of feedback can a DBA request during the evaluation of a DBMS?

• Statistical analysis reports

• Data security compliance certificates

• User satisfaction surveys from other organizations

Which aspect is crucial for a DBA when preparing for DBMS maintenance?

• Designing the physical data model

• Documenting every configuration change in the runbook

• Writing the SQL queries

What should a DBA do when updating an existing DBMS to a new version?

• Conduct a full reinstallation

• Coordinate the conversion from the old to the new DBMS

• Change the system hardware