Q&A Hero

Design

Q: The task of diagnosing errors due to changes in the database structure is eased by ________. A) formal policies for requesting changes B) database structure change documentation C) rollback analysis D) configuration control
Q: Which of the following is true about making changes to the database structure? A) The DBA need not get input from users on the issue because it is a technical decision. B) Formal policies and procedures for requesting a change are not used because they are too limiting. C) Documentation of when the change was made, how it was made, and why it was made must be created. D) Changes do not produce unexpected results because the DBA will have investigated the change thoroughly before implementing it.
Q: Which of the following is not a database administration responsibility of a DBA? A) Managing the database structure B) Writing the applications C) Managing the DBMS D) Maintaining the data repository
Q: A passive data repository is preferred over an active repository because it requires less human intervention.
Q: A standby data repository is one which requires a person to generate the metadata and place it in the repository.
Q: An active data repository is one in which the metadata is automatically created as the system components are created.
Q: The DBA should periodically analyze run-time statistics of database performance to help manage the DBMS.
Q: Both rollforward and rollback require the use of a log of transaction results.
Q: To support rollforward and rollback recovery, transactions must be written to a script before they are applied to the database.
Q: Rollforward and reprocessing are two different names for the same technique.
Q: Rollforward is a method of database recovery that restores the database save and all valid transactions since the save was reapplied.
Q: Reprocessing is normally the most convenient method for recovery after a system failure.
Q: Copies of each database record or page after it was changed by a transaction that are saved for use in database recovery are called ghost images.
Q: Copies of each database record or page before being changed by a transaction that are saved for use in database recovery are called before images.
Q: A checkpoint is a point of synchronization between the database and the transaction log.
Q: A database save is used to mark the end of a transaction.
Q: The security provided by the DBMS often has to be augmented by additional security features within the application program.
Q: All commercial DBMS products use some version of "username and password" as part of their security features.
Q: Processing rights may be implemented at the DBMS level.
Q: Processing responsibilities should be documented and encoded into manual procedures.
Q: In regard to database security, neither the DBMS nor the database applications can enforce processing responsibilities.
Q: The goal of database security is to ensure that only authorized users can perform authorized activities at authorized times.
Q: A dynamic cursor saves primary key values when the cursor is opened and retrieves the values for each row as the application program accesses it.
Q: A static cursor processes a snapshot of the relation that was taken when the cursor was opened.
Q: According to ANSI SQL, the serializable isolation level will not allow phantom reads, dirty reads, and nonrepeatable reads.
Q: Repeatable Read isolation is the most restrictive level of isolation.
Q: Nonrepeatable reads occur when a transaction rereads data it has previously read and finds modifications or deletions caused by a committed transaction.
Q: A dirty read happens when one transaction reads a changed record that has not been committed to the database.
Q: Transaction level consistency means that all rows impacted by any actions in a transaction are protected from change during the entire transaction.
Q: A durable transaction is one for which all committed changes are permanent.
Q: The transaction boundaries are the essential information that the DBMS needs from the application programs to enforce different locking strategies.
Q: In general, optimistic locking is the preferred technique for Internet databases.
Q: Resources are locked for a shorter amount of time with pessimistic locking because the transaction is pre-processed.
Q: With pessimistic locking, the assumption is made that a conflict will occur.
Q: With optimistic locking, the assumption is made that no conflict will occur.
Q: Requiring all application programs to lock resources in the same order is one way of preventing a deadlock condition.
Q: Resource locking must be carefully planned because most DBMS products cannot detect a deadlock condition.
Q: In two-phase locking, all locks are released during the contracting phase.
Q: In two-phase locking, all locks are obtained during the growing phase.
Q: Two-phased locking has a growing phase and a shrinking phase.
Q: Two-phased locking is a scheme for achieving serializability of transactions.
Q: Locks with large granularity are easy for the DBMS to administer but frequently cause conflicts.
Q: Explicit locks are locks that are placed automatically by the DBMS.
Q: Locks placed automatically by the DBMS are called implicit locks.
Q: Locks placed by a command issued to the DBMS from the application program are called explicit locks.
Q: Resource locking is one remedy to the lost update problem.
Q: An exclusive lock locks the item from change but not from read access.
Q: An exclusive lock locks the item from access of any type.
Q: The size of a lock is referred to as the lock granularity.
Q: A transaction is a group of alternative database actions, from which the database can choose to perform only one of them.
Q: A transaction is a series of actions to be taken on the database such that either all of them are performed successfully or none of them is performed at all.
Q: A transaction is sometimes called atomic because it is performed as a unit.
Q: Concurrency control measures are taken to ensure that one user's work has absolutely no influence on another user's work.
Q: One important reason for documenting changes to the database structure is for diagnosing errors.
Q: The database is most vulnerable to failure after a change to its structure.
Q: Changes in the database structure usually involve only one application.
Q: The DBA is responsible for managing changes to the database structure, but is rarely involved in the original design of the structure.
Q: The DBA has to find a balance between the conflicting goals of maximizing availability of the database to users and protecting the database.
Q: In general, the overall responsibility of the DBA is to facilitate the development and use of the database system.
Q: Database administration is more important but less difficult in multiuser database systems than in single-user database systems.
Q: Database administration tasks have to be performed for single-user, personal databases.
Q: There are several difficulties with increasing cardinalities from 1:1 to 1:N, one of which is preserving the existing relationships.
Q: Depending on the DBMS, when changing the minimum cardinality on the parent side from zero to one, the foreign key constraint that defines the relationship may have to be dropped before the change is made and re-added afterwards.
Q: To change the minimum cardinality on the parent side from zero to one, the foreign key, which would have been NULL, must be changed to NOT NULL.
Q: Converting date, money, or other more specific data types to char or varchar will usually succeed.
Q: To drop a constraint, no preliminary steps are needed and we can simply use the ALTER TABLE DROP CONSTRAINT statement.
Q: To drop a primary key column from a table the primary key constraint must first be dropped, but this does not require that related foreign keys based on the column be dropped.
Q: To drop a foreign key column from a table, no preliminary steps are needed and we can simply use the ALTER TABLE DROP COLUMN statement.
Q: To drop a nonkey column from a table, no preliminary steps are needed and we can simply use the ALTER TABLE DROP COLUMN statement.
Q: To add a NOT NULL column to a table, we first add a NULL column, then we insert values into every row, and finally we change the NULL constraint to NOT NULL.
Q: If a DEFAULT constraint is included when a new column is added to a table, the default value is only applied to new rows and not to the existing rows at the time the new column is added.
Q: To add a NULL column to a table, we simply use the MODIFY TABLE statement.
Q: In order to minimize the need to change table names, some organizations have a policy that no user or application should ever employ the true name of a table, but use views as table aliases instead.
Q: Changing table names is complicated by the fact that constraints and triggers are often associated with the table and will also need to be changed.
Q: SQL Server 2014 contains a system-stored procedure named sp_rename that can be used to change table names.
Q: SQL contains an SQL command RENAME TABLENAME that can be used to change table names.
Q: Even if an organization has a very large database, it will be possible to make a complete backup copy of the operational database prior to making structural changes.
Q: A means must be created to recover all test databases to their original state during the redesign testing process.
Q: Typically, there are at least four different copies of the database schema used in the redesign process.
Q: Dependency graphs are graphical displays like bar charts.
1 2 3 … 68

Subjects

Accounting Anthropology Archaeology Art History Banking Biology & Life Science Business Business Communication Business Development Business Ethics Business Law Chemistry Communication Computer Science Counseling Criminal Law Curriculum & Instruction Design Earth Science Economic Education Engineering Finance History & Theory Humanities Human Resource International Business Investments & Securities Journalism Law Management Marketing Medicine Medicine & Health Science Nursing Philosophy Physic Psychology Real Estate Science Social Science Sociology Special Education Speech Visual Arts