1Z0-076 Exam Guide: Oracle Database 19c Data Guard Administration
Oracle 1Z0-076 validates practical knowledge of administering Oracle Data Guard for high availability and disaster recovery in an Oracle Database 19c environment. It is aimed at database systems administrators responsible for disaster recovery and leads to the Oracle Certified Professional, Oracle Database 19c: Data Guard Administrator credential. This guide helps you decide whether your experience is ready for focused exam preparation, which technical areas need the most attention, and how to build a study sequence around configuration, protection modes, monitoring, recovery, and workload offload.
What does 1Z0-076 validate?
1Z0-076 tests whether you can reason about Oracle Data Guard as an operational high-availability and disaster-recovery solution, not merely recall isolated commands. Oracle associates the exam with Data Guard concepts, configuration, management, optimization, monitoring, data protection, high availability, disaster recovery, and workload-offload capabilities.
The associated credential is Oracle Certified Professional, Oracle Database 19c: Data Guard Administrator, and Oracle places the certification in the High Availability section of its Oracle Database certifications catalog. The exam is validated for Oracle Database 19c.
A useful way to interpret the certification is as a test of decisions made across the Data Guard lifecycle. You need to understand how a configuration is established, how redo is transported and applied, how protection requirements affect primary-database behavior, how administrators monitor health, and how a standby contributes to availability or workload distribution.
The official exam information does not provide domain percentages in the supplied research. Do not assign study time using unofficial percentage charts or compare unsupported weights. Instead, use Oracle’s named knowledge areas as the basis for a balanced plan, then increase practice time for any area in which you cannot explain both the intended configuration and its operational consequences.
Who is the intended candidate?
Oracle describes the certification as intended for database systems administrators responsible for disaster recovery. Its ideal candidate profile lists 4 to 5 years of database-administration experience and 2 to 3 years of Data Guard experience, so candidates should treat this as an administration-focused certification rather than an introductory database exam.
That profile is a useful readiness signal, not a substitute for the official exam requirements. If you have less Data Guard experience, you can still prepare, but you should compensate with structured labs, documentation-based troubleshooting, and repeated explanation of why a particular protection or transport choice fits a stated business requirement.
The strongest candidates can move between three viewpoints. From the business viewpoint, they can identify whether availability, performance, or data protection has priority. From the database viewpoint, they understand the relevant Data Guard configuration and state. From the operations viewpoint, they can recognize a gap, failed transport, lag, or recovery issue and choose a controlled response.
Before scheduling, write down the Data Guard tasks you have actually performed. Separate hands-on work from topics learned only through reading. That inventory will expose whether your main risk is missing terminology, weak command-level understanding, or limited experience interpreting operational conditions.
What are the exam format and planning facts?
The exam is multiple choice, contains 74 questions, allows 120 minutes, and has a listed passing score of 61%. These are the official planning facts supplied for 1Z0-076; confirm the current Oracle exam page for any scheduling or delivery information that may change.
The time allowance makes disciplined reading more valuable than rushing. A candidate who spends too long reconstructing one unfamiliar configuration may lose the opportunity to answer questions that test well-understood concepts. Practice identifying the requirement, the relevant Data Guard mechanism, and the consequence of each option before choosing an answer.
The passing score should not become a target for partial memorization. A practice result near the listed threshold may indicate fragile understanding, especially if it comes from repeated exposure to the same questions. Use practice work to find explanations you cannot produce independently, then return to Oracle documentation and rebuild the reasoning.
The supplied official research confirms the question format, duration, question count, and passing score, but it does not establish current exam pricing, appointment availability, delivery options, languages, prerequisites, or retirement status. Those details should be checked on Oracle’s official certification page before making a booking decision.
Which Data Guard decisions deserve priority?
Protection modes are a central study decision because they express a trade-off among primary-database availability, performance, and data protection. Oracle Data Guard provides maximum availability, maximum performance, and maximum protection; preparation should focus on the behavior and transport requirements of each mode, not on memorizing the names alone.
Maximum availability provides the highest level of data protection possible without compromising primary-database availability. If the primary cannot receive acknowledgement from at least one synchronized standby, it operates as if it were in maximum performance mode so primary availability is preserved until it can write the redo stream to a synchronized standby.
Maximum protection places data protection ahead of allowing the primary to continue. Unlike maximum availability, it shuts the primary down rather than allowing transactions to continue when they are unprotected. Oracle recommends a minimum of two standby databases for a primary running in maximum protection mode so that failure of one standby does not cause the primary to shut down.
Maximum performance provides the highest level of data protection possible without affecting primary performance. Oracle also describes it as offering slightly less data protection than maximum availability while having minimal impact on primary-database performance. Be ready to connect each mode to the failure behavior and business priority it is designed to address.
A practical study exercise is to create three short scenarios: one where the primary must remain available, one where performance is the overriding concern, and one where protection against data loss takes priority. For each, state the appropriate mode, the expected effect when the standby cannot acknowledge redo, and the operational risk accepted by the organization.
How should SYNC, ASYNC, AFFIRM, and NOAFFIRM be understood?
SYNC and ASYNC describe redo transport behavior, while AFFIRM and NOAFFIRM affect what acknowledgement means for standby storage. The important exam skill is connecting these attributes to commit behavior, protection, performance, and possible exposure during failures.
With SYNC/AFFIRM, the primary waits for acknowledgement that redo has been transmitted synchronously to the physical standby and written to disk. Oracle states that this provides no data loss because the data is available on the standby when the system is recovered, while the standby I/O introduces a performance impact.
With SYNC/NOAFFIRM, the primary waits for acknowledgement that data has been received on the standby, not that it has been written to disk. Oracle identifies a performance benefit and potential exposure to data loss in a special case involving multiple simultaneous failures.
The supplied Oracle table lists these redo transport attributes by protection mode: maximum availability uses SYNC with AFFIRM or NOAFFIRM, maximum performance uses ASYNC with NOAFFIRM, and maximum protection uses SYNC with AFFIRM. The same table requires a unique DB_UNIQUE_NAME on the primary and each standby.
Do not reduce this topic to a pair-matching exercise. Ask what event the primary is waiting for, where redo exists at acknowledgement time, and what happens if the primary and standby experience failures before the redo reaches persistent storage. That reasoning is more reliable than memorizing a table without understanding its operational meaning.
What should be practiced with protection-mode configuration?
Oracle’s documented configuration sequence begins by selecting a protection mode that meets availability, performance, and data-protection requirements. Study the prerequisites and state changes around that choice, especially when moving to maximum protection.
The documentation provides an example of setting LOG_ARCHIVE_CONFIG with a DG_CONFIG list: SQL> ALTER SYSTEM SET LOG_ARCHIVE_CONFIG='DG_CONFIG=(CHICAGO,BOSTON)'; Treat the database names in that example as illustrative configuration values from Oracle’s documentation, not as a universal naming convention for your own environment.
Oracle documents the command form SQL> ALTER DATABASE - > SET STANDBY DATABASE TO MAXIMIZE {AVAILABILITY | PERFORMANCE | PROTECTION}; the relevant choice must match the selected operational objective and the configuration’s ability to meet the mode requirements.
The documented restriction is important: maximum protection can be set on an open database only when the current mode is maximum availability and at least one synchronized standby database exists. Build a lab checklist that verifies the standby state before attempting the change.
The official documentation also states that protection-mode settings can be set and changed on an open database when the configuration meets the requirements, including changing from maximum performance to maximum availability. Distinguish that general flexibility from the additional prerequisites for maximum protection.
How should the technical domains be studied?
Study by administration task rather than by a list of disconnected product terms. For each topic, combine a concept explanation, a configuration example, an expected operating state, and a failure or recovery consequence. This approach maps naturally to Oracle’s stated areas of concepts, configuration, management, optimization, monitoring, data protection, high availability, disaster recovery, and workload offload.
Start with architecture and vocabulary. Make sure you can distinguish a primary database, standby database, redo transport, redo application, synchronization, redo gaps, and the role of a standby redo log. The purpose is to create a mental model that makes later troubleshooting steps coherent.
Move next to configuration. Study the relationships among database identity, redo destinations, transport attributes, standby initialization, and the settings needed to establish a valid Data Guard environment. When reading a command, explain what state it changes and which prerequisite makes the command safe or effective.
Then study management and monitoring together. Administration is not complete when a standby is created; you need to recognize whether redo is being transported, whether it is being applied, whether a gap exists, and whether the configuration still satisfies its selected protection mode. Use documentation to link each status or diagnostic action to the problem it helps isolate.
Optimization should be studied as a trade-off, not as a collection of tuning slogans. Compare the effect of synchronous and asynchronous transport, acknowledgement timing, standby storage, apply behavior, and primary workload requirements. Oracle’s discussion of SYNC/AFFIRM versus SYNC/NOAFFIRM is a particularly useful model for this style of analysis.
Finally, cover high availability, disaster recovery, and workload offload as outcomes of administration. Ask what planned or unplanned downtime problem a feature addresses, what assumptions it makes about the standby, and what workload can be moved or supported without weakening the recovery objective. Oracle’s Data Guard Administration Workshop is described as teaching protection against planned and unplanned downtime and is listed with a duration of 21 hours and 45 minutes; use it as a structured learning option, not as proof that course attendance alone establishes exam readiness.
What is a practical preparation sequence?
A reliable sequence is: establish the architecture, learn redo transport and protection modes, build or inspect a configuration, practice monitoring and recovery reasoning, then test workload-offload and high-availability decisions. This order prevents advanced troubleshooting from becoming a memorization exercise detached from the underlying Data Guard state.
First, read the official exam description and turn its named knowledge areas into a checklist. Mark each item as strong, familiar, or untested. Do not assume that general Oracle Database administration automatically covers Data Guard administration; identify the specific tasks and failure conditions you have not encountered.
Second, work through Oracle’s protection-mode documentation carefully. Create a comparison sheet with the business priority, transport behavior, acknowledgement point, primary behavior when the standby is unavailable, and likely operational trade-off for each mode. Keep the official domain label beside every comparison so that maximum availability, maximum performance, and maximum protection are not confused.
Third, use a lab or controlled practice environment to trace a complete change. Begin with the intended requirement, inspect the existing configuration, make one documented adjustment, verify the resulting state, and record how you would reverse or diagnose it. If a full environment is unavailable, use Oracle’s documented examples to practice explaining prerequisites and expected effects without claiming that reading is equivalent to execution.
Fourth, study monitoring through questions rather than passive rereading. For each imagined alert, ask whether the issue concerns transport, apply, synchronization, a redo gap, configuration identity, or protection-mode compliance. Then identify the first evidence you would collect and the least disruptive corrective action you would consider.
Fifth, use practice questions only after the subject review. For every missed answer, record the tested concept, the clue in the scenario, why the selected option was wrong, and the Oracle documentation that resolves the uncertainty. Avoid memorizing answer patterns or relying on question collections that claim to reproduce live exam content.
A four-stage roadmap
Stage one is foundation building. Learn the Data Guard architecture and terminology, then summarize the purpose of high availability and disaster recovery in your own words. The output should be a one-page system model, not a long collection of copied definitions.
Stage two is configuration and protection. Work through database identity, redo destinations, transport attributes, protection modes, synchronization, and the documented prerequisites for changing modes. The output should be a decision matrix and a configuration checklist.
Stage three is operations. Practice monitoring, redo-gap reasoning, apply behavior, recovery decisions, and the effect of an unavailable or unsynchronized standby. Include planned and unplanned downtime scenarios because Oracle’s associated workshop frames Data Guard around both types of interruption.
Stage four is assessment and repair. Complete mixed practice under the official 120-minute limit, review every uncertain response, and return to source documentation for verification. Schedule only when your results remain stable without repeated exposure to identical questions and when you can explain the reasoning behind your answers.
How should study time be allocated?
Because the supplied official research does not provide blueprint percentages, allocate time according to risk rather than invented domain weights. Give priority to topics that combine several knowledge areas, such as selecting a protection mode, configuring its transport requirements, and predicting the primary’s behavior when the standby cannot acknowledge redo.
Use a simple three-column tracker: concept, evidence of competence, and remaining gap. Evidence might be a correct explanation of a protection-mode scenario, a documented lab verification, or a successful diagnosis of a simulated redo-transport problem. A topic should not be marked complete merely because you recognized its terminology.
Candidates with substantial Data Guard experience may spend less time on basic vocabulary and more time validating edge conditions and trade-offs. Candidates with limited hands-on exposure should spend more time building a configuration model and interpreting documentation examples before attempting large practice sets.
Review weak areas in short, repeated sessions. A single long reading session can create familiarity without recall. At the end of each session, close the documentation and write the rule, prerequisite, or failure consequence from memory; then reopen the source and correct the details.
Which mistakes commonly undermine preparation?
The most damaging mistakes are usually reasoning errors: treating protection modes as interchangeable, confusing receipt with disk persistence, ignoring synchronization status, and studying answer recall instead of configuration behavior. Correct these by requiring every answer to include an operational consequence.
Do not treat the listed passing score of 61% as a safe preparation target. It is the official listed threshold, but a practice result at that level may leave little margin for unfamiliar wording or a weak domain. Use it as an exam fact, not as a definition of sufficient mastery.
Do not confuse maximum availability with maximum protection. Maximum availability preserves primary availability when acknowledgement from a synchronized standby is unavailable by operating as maximum performance until the connection is restored. Maximum protection instead shuts down the primary rather than allowing unprotected transactions to continue.
Do not assume that SYNC automatically means the redo has been written to standby disk. The AFFIRM and NOAFFIRM distinction matters. SYNC/AFFIRM waits for the write to disk, whereas SYNC/NOAFFIRM acknowledges receipt and has a different performance and failure trade-off.
Do not overlook identity and configuration prerequisites. Oracle’s documented redo-transport table says DB_UNIQUE_NAME must be set to a unique value on the primary and on each standby. A study answer that ignores database identity is incomplete even if its protection-mode choice sounds plausible.
Do not use dumps, leaked questions, or memorized answer keys as a substitute for learning. They cannot establish that your understanding matches the validated Oracle Database 19c administration skills, and claims about live exam content are not a sound basis for preparation or ethical exam decisions.
Do not build a schedule around unsupported delivery assumptions. The supplied evidence confirms the multiple-choice format and the time and question facts, but not current appointment channels, remote delivery, languages, or other scheduling conditions. Check Oracle directly before booking.
How can you use the official sources effectively?
Use the Oracle exam page to confirm the credential context, candidate profile, validated database version, stated knowledge areas, format, duration, question count, and listed passing score. Use the Data Guard documentation for protection-mode behavior, redo transport attributes, prerequisites, and configuration examples.
Read the protection-mode page with a question in mind: what must be true before this mode is selected, what does the primary wait for, and what happens when the standby is unavailable? This turns documentation into an operational study tool rather than a glossary.
Oracle’s Data Guard Administration Workshop can provide a structured course path for candidates who benefit from guided instruction. The official course description says it teaches use of Data Guard to protect an Oracle database against planned and unplanned downtime. Compare its scope with your gap tracker before committing to it.
The Oracle certification catalog is useful for placing 1Z0-076 in the High Availability context. It should not be used to infer unsupported exam weights, prerequisites, prices, or scheduling details. Keep those distinctions clear in your notes.
What should you do before scheduling?
Schedule after verifying both knowledge readiness and current administrative details. Confirm the official exam page, review the current booking information there, and make sure your preparation is based on Oracle Database 19c Data Guard content rather than a different release or a generic high-availability course.
Use a final readiness review built around explanation. You should be able to describe the purpose of each protection mode, distinguish SYNC/AFFIRM from SYNC/NOAFFIRM, explain why DB_UNIQUE_NAME matters, identify the significance of a synchronized standby, and reason through the consequences of transport or acknowledgement failure.
Complete at least one timed mixed review using the official 120-minute exam duration as your practice constraint. Since the exam contains 74 questions, practice deciding when to make a reasoned selection and move on rather than allowing one uncertain item to consume disproportionate time. This is a preparation recommendation based on the official format facts, not a claim about how the live exam is arranged beyond those facts.
On the day before booking, stop adding unrelated material. Revisit your error log, protection-mode matrix, configuration checklist, and source-backed corrections. If you still rely on recognizing a remembered answer instead of explaining why it is correct, postpone scheduling and repair that gap.
After scheduling, keep the final review narrow: Oracle’s stated domains, the Data Guard protection-mode documentation, your own configuration notes, and the mistakes that remained persistent during practice. The goal is clear technical reasoning under time limits, not accumulation of more unverified question material.
What is the next action for a candidate using this guide?
Start by opening the official 1Z0-076 page and writing a personal gap list against Oracle’s named knowledge areas. Then study the protection modes from the official 19c documentation, build the comparison matrix, and choose a lab or documentation exercise that lets you trace configuration, transport, monitoring, and recovery decisions.
If your background is close to Oracle’s stated ideal profile, use the roadmap to validate breadth and sharpen edge cases rather than assuming experience covers every tested topic. If you are earlier in your Data Guard work, give yourself additional time for architecture, redo transport, synchronization, and failure reasoning before using timed practice.
When your gap list is stable, use the official exam facts to plan the session: multiple-choice questions, 74 questions, 120 minutes, and a listed passing score of 61%. Verify all changeable booking information on Oracle’s current page. Prepare from documented behavior and your own reasoning, not from claims that memorized dumps guarantee a result.
Conclusion
1Z0-076 preparation is strongest when it mirrors the administrator’s real decision process: define the recovery objective, select an appropriate protection mode, configure transport correctly, verify synchronization and apply behavior, monitor the environment, and reason about planned or unplanned failure. Use Oracle’s official exam information to establish scope and logistics, use the 19c Data Guard documentation to verify technical behavior, and let your gap tracker determine what to study next. That combination gives you a defensible scheduling decision without relying on unsupported exam claims or memorized question material.
Related exams
- 1z0-078 exam — Oracle Database 19c: RAC, ASM, and Grid Infrastructure Administration
- 1z0-084 exam — Oracle Database 19c: Performance Management and Tuning
- 1z0-1116-23 exam — Oracle Guided Learning Content Developer Foundations Associate Rel 1
- 1z0-149 exam — Oracle Database 19c: Program with PL/SQL
- 1z0-202 exam — Siebel 8 Consultant Exam
- 1z0-532 exam — Oracle Hyperion Financial Management 11 Essentials
