Machine-translated by Google. Questions are authored in English.
Top

Managing Multiuser Databases Questions and Answers

21.

A point of synchronization between the database and the transaction log is generally referred to as a stop point.

Answer: B

Correct answer: False

A point of synchronisation between the database and its log is a checkpoint. At a checkpoint the buffers are written out and the log records the fact, so recovery need only go back to the last checkpoint rather than to the beginning of the log - which is what keeps recovery time bounded.

Please log in or register to report this question.

22.

Which of the following disallows both dirty reads and nonrepeatable reads, but allows phantom reads?

Answer: C

Correct answer: Repeatable read

Repeatable read holds read locks to the end of the transaction, so a row once read cannot be changed by another transaction and dirty and nonrepeatable reads are both prevented. It does not lock rows that do not yet exist, so another transaction may still insert one and a phantom read remains possible.

Please log in or register to report this question.

23.

Locks placed by the DBMS are explicit locks.

Answer: B

Correct answer: False

Locks placed by the DBMS itself are implicit; explicit locks are those the application requests by command. Getting the pair the right way round matters, because most locking in a well-written application is implicit - the developer declares an isolation level and the DBMS places whatever locks are needed to honour it.

Please log in or register to report this question.

24.

The goal of database security is to ensure that only authorized users can perform authorized activities at authorized times.

Answer: A

Correct answer: True

All three qualifications are needed. Authorised users, so that identity is established; authorised activities, so that a user may read what they may not change; and authorised times, since access appropriate during a shift may not be appropriate outside it. Authentication establishes the first and authorisation the other two.

Please log in or register to report this question.

25.

Which of the following refers to a cursor type where changes of any type and from any source are visible?

Answer: D

Correct answer: Dynamic

A dynamic cursor shows everything: changes, insertions and deletions from any source, made at any time. It is the most current view and correspondingly the most expensive, since the recordset must be re-evaluated as it is traversed. A static cursor is the opposite extreme, showing a snapshot fixed when the cursor was opened.

Please log in or register to report this question.

26.

Resource locking is a process to prevent multiple applications from obtaining copies of the same record when the record is about to be changed.

Answer: A

Correct answer: True

Resource locking is exactly this: preventing two applications from working on their own copies of the same record and each writing back a result computed from a value the other has already superseded. Without it the second write silently overwrites the first, which is the lost update problem.

Please log in or register to report this question.

27.

An exclusive lock locks the item from change but not from read.

Answer: B

Correct answer: False

That describes a shared lock, which permits others to read but not to change. An exclusive lock excludes access of every kind, reading included, which is what a writing transaction requires. Several shared locks may be held on one item at once; an exclusive lock may not coexist with any other.

Please log in or register to report this question.

28.

Which of the following allows dirty reads, nonrepeatable reads and phantom reads to occur?

Answer: B

Correct answer: Read uncommitted

Read uncommitted is the weakest level and prevents nothing: dirty reads, nonrepeatable reads and phantoms are all possible, because the transaction takes no read locks and respects none. It is used only where speed matters more than accuracy - an approximate count over a large table, for instance.

Please log in or register to report this question.

Answer: B

Correct answer: lock granularity.

Granularity is the size of the thing locked - a row, a page, a table, or the whole database. It is a trade: a coarse lock is cheap to manage but blocks many transactions, while a fine one allows far more concurrency at the cost of a great many locks to track. The DBMS may escalate from fine to coarse when the count grows.

Please log in or register to report this question.

30.

In optimistic locking, the assumption is made that conflict will occur.

Answer: B

Correct answer: False

Optimistic locking assumes conflict will not occur: the transaction proceeds without locks and checks at the end whether anything it relied on has changed, rolling back and retrying if so. Pessimistic locking makes the opposite assumption and takes locks before the work begins.

Please log in or register to report this question.

Loading…

Other Subjects

Tags: Managing Multiuser Databases Questions and Answers || Managing Multiuser Databases MCQ Questions and Answers || Managing Multiuser Databases GK Questions and Answers || Managing Multiuser Databases GK MCQ Questions || Managing Multiuser Databases Multiple Choice Questions and Answers || Managing Multiuser Databases GK || GK on Managing Multiuser Databases || Database Questions and Answers || Database MCQ Questions and Answers || Database GK Questions and Answers || GK on Database