| A. | DBMS & the Host record |
| B. | Host program and Host record |
| C. | Host program and DBMS |
| D. | Host program and Host language |
|
Option: C Explanation : Click on Discuss to view users comments. |
The maximum number of keys stored in a B-tree of order m and depth d is
| A. | md + 1 - 1 |
| B. | md+1 - 1/(m - 1) |
| C. | (m - 1) (md + 1 - 1) |
| D. | (md - 1) / (m - 1) None of these |
|
Option: D Explanation :
Option A given as right answer in keys provided by UGC =md-1 Click on Discuss to view users comments. |
| A. | LL(I) |
| B. | Canonical LR |
| C. | SLR |
| D. | LALR |
|
Option: B Explanation : Click on Discuss to view users comments. |
| A. | init |
| B. | nice |
| C. | kill |
| D. | PS |
|
Option: B Explanation : Click on Discuss to view users comments. Anuradha said: (5:17pm on Thursday 9th January 2014)
nice becomes useful when several processes are demanding more resources than the CPU can provide. In this state, a higher priority process will get a larger chunk of the CPU time than a lower priority process. If the CPU can deliver more resources than the processes are requesting, then even the lowest priority process can get up to 99% of the CPU. Only the superuser (root) may set the niceness to a smaller (higher priority) value. On Linux it is possible to change /etc/security/limits.conf to allow other users or groups to set low nice values.[1]If a user wanted to compress a large file, but not slow down other processes, they might run the following:$ nice -n 19 tar cvzf archive.tgz largefileThe related renice program can be used to change the priority of a process that is already running.
|
| A. | 5, 7, 15 |
| B. | 10, 12, 14 |
| C. | 5, 6, 7 |
| D. | 20, 12, 14 |
|
Option: B Explanation : Click on Discuss to view users comments. Anuradha said: (5:14pm on Thursday 9th January 2014)
AES supports three key sizes: 128 bits, 192 bits, and 256 bits. The default key size is 128 bits, and all implementations MUST supportthis key size. Implementations MAY also support key sizes of 192 bits and 256 bits.AES uses a different number of rounds for each of the defined key sizes. When a 128-bit key is used, implementations MUST use 10 rounds. When a 192-bit key is used, implementations MUST use 12 rounds. When a 256-bit key is used, implementations MUST use 14 rounds.
|
