Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Oracle Exam 1Z0-084 Topic 15 Question 11 Discussion

Actual exam question for Oracle's 1Z0-084 exam
Question #: 11
Topic #: 15
[All 1Z0-084 Questions]

Examine these commands, which execute successfully:

Which statement is true?

Show Suggested Answer Hide Answer
Suggested Answer: C, D

Big Table caching is a feature that allows frequently accessed large tables to be cached in memory to improve I/O performance. From the parameter settings provided, Big Table caching is not occurring because DB_BIG_TABLE_CACHE_PERCENT_TARGET is set to 10, which is the minimum threshold for enabling the feature, but the size of the cache is too small for the big tables to be effectively cached.

To enable Big Table caching, one of the following actions could be taken:

C (Correct): Increasing DB_BIG_TABLE_CACHE_PERCENT_TARGET to at least 25. This action would allocate a larger percentage of the buffer cache for storing big tables, which could allow for caching large tables and thus improve I/O performance.

D (Correct): Increasing DB_CACHE_SIZE to 1G. Since the size of the buffer cache is a determining factor for how much data can be cached, increasing this parameter would provide more memory space for big tables to be cached.

Options A, B, E, and F will not enable Big Table caching because:

A: Increasing DB_BIG_TABLE_CACHE_PERCENT_TARGET to 50 without adjusting the overall size of the cache might still not be sufficient if the DB_CACHE_SIZE is not large enough to hold the big tables.

B: Setting DB_KEEP_CACHE_SIZE to at least 50M only specifies a separate buffer pool for objects with the KEEP cache attribute and does not affect Big Table caching.

E: and F: Changing the PARALLEL_DEGREE_POLICY to ADAPTIVE or AUTO influences the behavior of parallel execution but does not directly enable or influence Big Table caching.


Oracle Database Performance Tuning Guide: Big Table Caching

Oracle Database Reference: DB_BIG_TABLE_CACHE_PERCENT_TARGET

Oracle Database Reference: DB_CACHE_SIZE

Contribute your Thoughts:

Nidia
2 days ago
Wait, is this a trick question? I thought AD DM was always enabled, but maybe I'm missing something. I'll have to double-check my notes on that one.
upvoted 0 times
...
Kerrie
7 days ago
Haha, I bet the test writers are trying to trick us with these options. I'm going with C - 60-minute AWR snapshot purges in all pluggable databases. Gotta love that Oracle efficiency!
upvoted 0 times
...
Raelene
14 days ago
Hmm, I'm pretty sure the answer is B. ADDM, AWR, and ASH reports can definitely be purged automatically. Who doesn't love a little database housekeeping?
upvoted 0 times
...
Brandee
15 days ago
Wow, this is a tough one! I thought the correct answer was D, but now I'm not so sure. Maybe I should take a closer look at those commands.
upvoted 0 times
...
Giuseppe
23 days ago
But the question is asking about which statement is true, not what can be done manually. So, I still think it's B.
upvoted 0 times
...
Refugia
24 days ago
I disagree, I believe the answer is D.
upvoted 0 times
...
Giuseppe
27 days ago
I think the answer is B.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77