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-076 Topic 8 Question 26 Discussion

Actual exam question for Oracle's 1Z0-076 exam
Question #: 26
Topic #: 8
[All 1Z0-076 Questions]

Your Data Guard configuration consists of these components and settings:

1. A primary database

2. A remote physical standby database

3. Real-time query is enabled

4. Redo transport mode is synchronous

5. Protection mode is maximum availability

6. The Data Guard broker is used

You notice that the standby destination fails to acknowledge reception of redo within net_timeout period of time.

Which is true in this scenario?

Show Suggested Answer Hide Answer
Suggested Answer: A, B, C, F

The SQL apply lag on a logical standby database can be caused by several factors:

A: An undersized undo tablespace can lead to delays in SQL apply operations as it may not be able to handle the volume of undo records generated by the SQL apply process.

B: SQL apply operations that do full table scans can consume significant system resources, potentially leading to higher apply lag.

C: An increased number of bulk updates on the primary database may generate a large volume of redo data, which can cause apply lag if the logical standby cannot apply the changes quickly enough.

F: An undersized shared pool may affect the parsing and execution of SQL statements by SQL apply, which can contribute to the apply lag.

Option D is less likely to be a direct cause of SQL apply lag compared to bulk updates, as inserts generate new data rather than modifying existing data, which SQL apply can typically handle more efficiently.

Option E is incorrect because the size of the standby redo log files on the primary database impacts redo transport lag, not SQL apply lag.


Contribute your Thoughts:

Sharika
5 days ago
Haha, I bet the Data Guard broker is just going to shut down the whole standby instance. That'll teach it to be late with the redo acknowledgements!
upvoted 0 times
...
Nina
10 days ago
Wait, is the protection mode really going to change to Maximum Performance? That doesn't sound right to me, given the settings mentioned.
upvoted 0 times
...
Leonard
14 days ago
C seems like the most likely option here. If the standby can't acknowledge the redo within the timeout, the synchronous connections would likely be terminated.
upvoted 0 times
Marleen
3 days ago
I agree, option C seems to be the most logical choice in this scenario.
upvoted 0 times
...
...
Lorean
22 days ago
Hmm, this sounds like a tricky one. I'll have to think through the Data Guard settings carefully to figure out the right answer.
upvoted 0 times
Paris
9 days ago
User1: I think the standby destination failing to acknowledge redo is a serious issue.
upvoted 0 times
...
...
Audry
23 days ago
Hmm, that could make sense too. If the standby is not acknowledging redo, maybe it's better to switch to Maximum Performance for better performance.
upvoted 0 times
...
Arlene
24 days ago
I disagree, I believe the answer is B) The protection mode will automatically change to Maximum Performance.
upvoted 0 times
...
Audry
25 days ago
I think the correct answer is A) Real-time query will be disabled on the physical standby.
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