1Z0-076 Oracle Database 19c Data Guard Administration Exam Guide
Oracle 1Z0-076 validates practical knowledge of using Data Guard to support high availability and disaster recovery in an Oracle Database 19c environment. It is aimed particularly 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 subjects need laboratory practice, and how to organize study time around the exam’s documented format and the operational trade-offs among Data Guard protection modes.
What does 1Z0-076 validate?
The exam tests whether you can reason about Data Guard as an availability and disaster-recovery solution, not merely recall isolated commands. Oracle identifies concepts, configuration, management, optimization, monitoring, data protection, high availability, disaster recovery, and workload-offload capabilities as relevant knowledge areas. Source: https://education.oracle.com/oracle-solaris-11-installation-and-configuration-essentials/pexam_1Z0-076
The associated credential is Oracle Certified Professional, Oracle Database 19c: Data Guard Administrator, and Oracle places 1Z0-076 in the High Availability section of its Oracle Database certifications catalog. The exam is validated for Oracle Database 19c. These details make release alignment important: preparation should use 19c terminology and documentation rather than relying on material written for an earlier database release.
The practical scope is broader than failover alone. A capable administrator must connect business requirements to a protection mode, understand how redo is transported and applied, monitor whether a standby remains synchronized, and recognize the operational consequences of a configuration choice. Oracle’s workshop description similarly frames Data Guard as a way to protect a database against planned and unplanned downtime. Source: https://learn.oracle.com/ols/course/oracle-database-19c-data-guard-administration-workshop/84765/116186
Who should take this exam?
1Z0-076 is most suitable for an Oracle database administrator who already works with disaster-recovery responsibilities and wants a credential focused on Data Guard administration. Oracle lists an ideal candidate profile of 4 to 5 years of database-administration experience and 2 to 3 years of Data Guard experience. Those figures describe Oracle’s ideal profile, not a formal prerequisite stated in the supplied evidence. Source: https://education.oracle.com/oracle-solaris-11-installation-and-configuration-essentials/pexam_1Z0-076
Use the profile as a readiness benchmark rather than a gate. If you have less experience but can build, inspect, and troubleshoot a representative 19c Data Guard configuration, targeted preparation may be realistic. If your background is mainly general SQL or application development, begin with Oracle database administration and redo, recovery, and standby concepts before treating exam-focused revision as the next step.
A useful self-check is whether you can explain the consequence of a requirement, not just name a feature. For example, can you explain why synchronous transport may affect primary performance, what a standby acknowledgement means, and why maximum protection can make primary availability subordinate to protection? If those explanations are uncertain, schedule a foundation phase before attempting practice questions.
What are the documented exam facts?
The documented format is multiple choice, with 74 questions, a 120 minutes duration, and a listed passing score of 61%. Oracle states that the exam is validated for Oracle Database 19c. Source: https://education.oracle.com/oracle-solaris-11-installation-and-configuration-essentials/pexam_1Z0-076
These facts support a controlled pacing plan, but they do not predict the difficulty of individual questions or guarantee that a particular preparation method will be sufficient. The official page should remain the authority for registration, delivery arrangements, policies, and any details that may change. The supplied research does not establish a delivery method, language list, price, scheduling window, retake policy, or prerequisite, so do not rely on third-party claims about those items.
For preparation planning, reserve enough time to read the complete scenario, identify the requirement being tested, eliminate options that conflict with the stated protection objective, and review marked questions. A sensible practice exercise is to work under the documented 120 minutes and 74-question structure, but treat that as rehearsal for pacing rather than evidence of the official question wording or content distribution.
The passing score is a threshold, not a target for practice. Build a margin by seeking consistent understanding across all listed knowledge areas. Memorizing answer patterns, using leaked questions, or relying on exam dumps cannot establish that you can administer a Data Guard environment and does not guarantee a pass.
How should you organize the knowledge areas?
Start with the lifecycle of a Data Guard solution: define the availability objective, configure the environment, transport and apply redo, monitor health, manage planned or unplanned transitions, and optimize the result. This sequence gives the listed concepts, configuration, management, optimization, monitoring, data protection, high availability, disaster recovery, and workload offload a practical relationship. Source: https://education.oracle.com/oracle-solaris-11-installation-and-configuration-essentials/pexam_1Z0-076
First establish the vocabulary and architecture. Then study configuration dependencies and the flow of redo from primary to standby. After that, move to administration and monitoring, because operational diagnosis depends on understanding what a healthy configuration is supposed to do. Finish the first pass with protection-mode trade-offs, recovery objectives, planned and unplanned events, and workload-offload decisions.
Do not allocate study time by an invented percentage breakdown. The supplied official research does not provide blueprint weights for the exam domains. Instead, rank topics by two criteria: how directly they affect data protection or availability, and how confidently you can explain or perform them. A topic that is both operationally important and unfamiliar deserves laboratory time before passive reading.
Keep a decision log while studying. For each topic, record the business requirement, the relevant Data Guard behavior, the configuration or command involved, the expected evidence in monitoring, and the failure consequence. This transforms notes into a troubleshooting aid and exposes gaps that flashcards alone may conceal.
How do the three protection modes differ?
Oracle Data Guard provides maximum availability, maximum performance, and maximum protection modes. Choose among them by balancing availability, performance, and data-protection requirements; do not select a mode simply because its name sounds strongest. Source: https://docs.oracle.com/en/database/oracle/oracle-database/19/sbydb/oracle-data-guard-protection-modes.html
Maximum availability provides the highest level of data protection possible without compromising primary availability. Oracle explains that, if the primary cannot receive acknowledgement from at least one synchronized standby, it operates as if it were in maximum performance mode so that primary availability is preserved until it can write to a synchronized standby again. Study this as a conditional behavior, not as a claim that every failure produces identical results.
Maximum performance provides the highest level of data protection possible without affecting primary performance, according to Oracle’s documentation. It offers slightly less data protection than maximum availability and has minimal impact on primary database performance. This is the mode to analyze when the scenario places strong emphasis on primary performance and accepts a different protection trade-off.
Maximum protection is similar to maximum availability but adds protection in the event of multiple failure events. Unlike maximum availability, maximum protection shuts the primary down rather than allowing it to continue processing transactions that are unprotected when the required standby acknowledgement is unavailable. Oracle recommends a minimum of two standby databases for a primary running in maximum protection, to reduce the risk that a single standby failure causes the primary to shut down.
A useful revision method is to write each mode as a requirement-and-consequence pair. For maximum availability, emphasize protection without compromising primary availability. For maximum performance, emphasize minimal primary performance impact. For maximum protection, emphasize refusing to continue unprotected transactions. Then test yourself with failure scenarios instead of memorizing a three-row comparison.
What do SYNC, ASYNC, AFFIRM, and NOAFFIRM change?
Redo transport attributes determine when the primary receives acknowledgement and whether the standby has written redo to disk. Oracle specifically distinguishes SYNC/AFFIRM from SYNC/NOAFFIRM in maximum availability mode because the choice changes the balance between protection and performance. Source: https://docs.oracle.com/en/database/oracle/oracle-database/19/sbydb/oracle-data-guard-protection-modes.html
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 an additional protection benefit at the expense of the performance impact caused by standby redo-log I/O. In the supplied explanation, when the disk write is confirmed, the data is available on the standby during recovery and there is no data loss for that situation.
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 describes a performance benefit, along with potential exposure to data loss in a special case involving multiple simultaneous failures. This distinction is easy to flatten into “synchronous equals no loss,” so make the acknowledgement point explicit in your notes.
Oracle’s table of required redo transport attributes identifies these combinations: 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 DB_UNIQUE_NAME to be set to a unique value on the primary and on each standby. Source: https://docs.oracle.com/en/database/oracle/oracle-database/19/sbydb/oracle-data-guard-protection-modes.html
Practice by translating a scenario into transport requirements. If the prompt prioritizes disk confirmation and protection, investigate SYNC/AFFIRM. If it emphasizes performance and accepts asynchronous transport, investigate the maximum-performance combination. If it describes maximum protection, check both the transport attributes and the stricter consequence when protection cannot be maintained.
Which configuration details deserve laboratory practice?
Use a controlled Oracle 19c practice environment to connect configuration syntax with observable behavior. The most valuable exercises are not command transcription; they are tracing how an initialization parameter, redo destination attribute, protection mode, standby state, and monitoring result fit together. Keep a written before-and-after record so you can explain why each change was made.
The supplied Oracle documentation includes this example for LOG_ARCHIVE_CONFIG: SQL> ALTER SYSTEM SET LOG_ARCHIVE_CONFIG='DG_CONFIG=(CHICAGO,BOSTON)'; Reproduce the syntax only in an appropriate laboratory and substitute values that match your own environment. The point of the exercise is to understand the named database configuration and the need for distinct identities, not to memorize CHICAGO and BOSTON as universal values. Source: https://docs.oracle.com/en/database/oracle/oracle-database/19/sbydb/oracle-data-guard-protection-modes.html
The same documentation gives the form of the protection-mode command: SQL> ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE {AVAILABILITY | PERFORMANCE | PROTECTION}; Treat the alternatives as mutually meaningful decisions. Before changing a mode, verify that the configuration satisfies its requirements. Oracle notes that maximum protection can be set on an open database only when the current mode is maximum availability and at least one standby is synchronized.
Your lab checklist should include identity verification, redo transport settings, standby synchronization, protection-mode changes, and evidence that the resulting state matches the intended requirement. Do not make destructive changes on a production system merely to imitate a study exercise. If you lack a suitable environment, use the official workshop and 19c documentation for conceptual sequencing, while marking hands-on claims as study objectives rather than completed experience.
How can you study monitoring and troubleshooting rather than just configuration?
Study every configuration topic with a corresponding health question: Is redo being transported? Has it reached the standby? Is it written where the selected mode requires? Is it being applied? Is there a redo gap? Is the standby synchronized enough to support the promised protection? Oracle’s protection-mode documentation defines a synchronized standby as one meeting the configured mode’s minimum requirements and having no redo gap. Source: https://docs.oracle.com/en/database/oracle/oracle-database/19/sbydb/oracle-database/19/sbydb/oracle-data-guard-protection-modes.html
Build fault scenarios around missing acknowledgements, delayed apply, transport interruption, and a standby that no longer meets synchronization requirements. For each scenario, identify the protection-mode consequence before choosing a corrective action. This prevents a common mistake: selecting a technically familiar command without first determining whether the primary is currently protected according to the configured objective.
Pay particular attention to the difference between transport and apply. Redo may be transmitted yet not applied at the expected rate, or a standby may be present but not satisfy the protection mode. Your notes should show the evidence that separates those conditions. Include redo gaps in the troubleshooting map, because Oracle explicitly points to gap detection and resolution when defining synchronized standby behavior.
Oracle also states that real-time apply helps the standby apply redo changes as fast as they are received and that Data Guard signals detected corruptions so corrective action can be taken. Use these statements to build questions about operational validation: what should be happening, what evidence would indicate a problem, and which requirement is at risk? Source: https://docs.oracle.com/en/database/oracle/oracle-database/19/sbydb/oracle-data-guard-protection-modes.html
How should workload offload and availability scenarios enter your revision?
Treat workload offload as part of the design objective, not as an unrelated feature list. Oracle associates 1Z0-076 with knowledge of workload-offload capabilities available in Data Guard, while the certification itself is positioned around high availability and disaster recovery. Study when moving suitable work away from the primary supports the overall design without undermining the protection or recovery objective. Source: https://education.oracle.com/oracle-solaris-11-installation-and-configuration-essentials/pexam_1Z0-076
For planned and unplanned downtime, separate the business event from the Data Guard response. A planned operation may focus on maintaining service while roles change; an unplanned event emphasizes protection, recoverability, and the condition of the surviving standby. The supplied sources do not provide a complete command-by-command procedure for every transition, so avoid memorizing unsupported sequences from unofficial summaries.
When reviewing a scenario, ask four questions: what failed or is being maintained, which database should serve the workload, what data could be exposed, and what must be verified before or after the change? This approach makes high availability, disaster recovery, monitoring, and workload offload part of one operational model rather than isolated exam vocabulary.
What is a practical study roadmap?
A staged roadmap works better than repeatedly reading the same overview. Begin with the official scope and 19c terminology, move into protection-mode reasoning, then perform configuration and monitoring exercises, and finish with scenario-based review under timed conditions. Adjust the length of each stage according to your existing administration and Data Guard experience rather than treating the roadmap as an official course requirement.
Stage one: establish the baseline. Read the official 1Z0-076 page and list every named knowledge area. Confirm that your materials are for Oracle Database 19c. Write a short explanation of primary, standby, redo transport, redo apply, synchronization, and the business difference between high availability and disaster recovery. Mark any term you can recognize but cannot explain.
Stage two: master decisions. Create a comparison sheet for maximum availability, maximum performance, and maximum protection. Put the official domain name in every row and include the relevant transport behavior, acknowledgement condition, primary-availability consequence, and failure trade-off. Add SYNC/AFFIRM, SYNC/NOAFFIRM, and the maximum-performance transport combination from Oracle’s documentation.
Stage three: configure and observe. Work through identity and redo-transport exercises in a safe environment. Verify DB_UNIQUE_NAME assumptions, examine how synchronization and redo gaps affect the design, and practice explaining what evidence would confirm that the standby meets the selected protection mode. Use the Oracle Database 19c Data Guard Administration Workshop as a structured learning option; Oracle lists its duration as 21 hours and 45 minutes. Source: https://learn.oracle.com/ols/course/oracle-database-19c-data-guard-administration-workshop/84765/116186
Stage four: troubleshoot scenarios. Rotate through transport interruption, acknowledgement loss, apply delay, synchronization loss, planned downtime, unplanned primary failure, and workload-offload decisions. For each, state the requirement first, then the expected behavior, then the validation step. This is more valuable than collecting command fragments without knowing the condition each command addresses.
Stage five: rehearse the documented format. Use multiple-choice questions from legitimate study sources, but do not assume they reproduce live exam content. Practice reading the entire prompt, identifying the tested objective, eliminating contradictory answers, and recording why the selected answer is correct. Use the official 74-question and 120 minutes structure for pacing practice, while remembering that practice performance is not an official readiness measure.
Which mistakes most often weaken preparation?
The most damaging mistake is treating protection modes as labels instead of operational policies. A candidate who remembers that maximum protection is “strongest” but forgets that the primary can shut down when protection cannot be maintained has not learned the decision. Always pair each mode with its availability consequence and redo-transport requirement.
Another mistake is collapsing SYNC/AFFIRM and SYNC/NOAFFIRM into one idea. Both include synchronous transport, but the standby disk-write acknowledgement differs. Build a small cause-and-effect diagram showing what the primary knows at acknowledgement time and what failure exposure remains. This makes the distinction easier to retrieve in a scenario.
Do not confuse a configured standby with a synchronized standby. Oracle’s definition includes both the mode’s minimum requirements and the absence of a redo gap. A standby that exists but is behind may not provide the protection assumed by the design. Make synchronization and gap status part of every troubleshooting answer.
Avoid studying only administration commands. Oracle’s stated knowledge areas include optimization, monitoring, data protection, high availability, disaster recovery, and workload offload in addition to configuration and management. If your notes contain syntax but no explanation of performance, protection, or failure consequences, rebalance your preparation.
Finally, do not infer exam facts from generic certification sites. The supplied official evidence supports the multiple-choice format, 74 questions, 120 minutes, 61% passing score, 19c validation, and the candidate profile described above. Confirm any registration, delivery, policy, or current-status detail directly on Oracle’s official page before scheduling.
How should you manage time during the exam?
Use the documented 120 minutes as a finite decision-making budget for 74 multiple-choice questions. The official sources establish those figures but do not prescribe a pacing rule. A practical recommendation is to move steadily, mark questions that require deeper analysis, and preserve time to revisit them rather than allowing one ambiguous scenario to consume the session.
Read for the requirement before reading for the technology. Words describing availability, performance, data loss, synchronization, acknowledgement, or multiple failures often determine which protection-mode behavior matters. Then compare each option against that requirement. An answer that sounds operationally familiar is still wrong if it violates the stated business objective.
For configuration questions, check prerequisites and identities before selecting a command. For protection-mode questions, check the transport attributes and the consequence of losing acknowledgement. For monitoring questions, distinguish transport, disk write, apply, synchronization, and redo-gap evidence. These small checks reduce errors caused by recognizing a keyword and answering too quickly.
The listed passing score is 61%, but you should not design a strategy around barely reaching it. Use practice results to identify weak domains, and seek explanations for incorrect answers. The aim is reliable reasoning across the scope, not a memorized score from a narrow question set.
What should you do before scheduling?
Schedule only after you can explain the major Data Guard decisions without notes and can connect configuration, transport, monitoring, and recovery objectives in a single scenario. The official Oracle page should be your final source for current scheduling and policy information, because the supplied evidence does not establish delivery method, price, language, or other administrative details. Source: https://education.oracle.com/oracle-solaris-11-installation-and-configuration-essentials/pexam_1Z0-076
Complete a readiness review with five outputs: a 19c-aligned topic list, a protection-mode decision table, a redo-transport and acknowledgement diagram, a monitoring and redo-gap troubleshooting map, and a record of timed multiple-choice practice. If one of these is missing, decide whether the gap is knowledge, hands-on confidence, or exam technique; each requires a different remedy.
Revisit the official documentation for protection modes immediately before final review. Confirm the three modes, the SYNC/AFFIRM and SYNC/NOAFFIRM distinction, the DB_UNIQUE_NAME requirement, the maximum-protection standby recommendation, and the conditions described for changing modes. Then stop adding disconnected facts and practice applying the model to new scenarios.
On exam day, follow the policies and delivery instructions provided by Oracle at registration. Bring no assumption from an unofficial page about identification, equipment, breaks, or testing location. Your preparation decision is complete when the technical scope is understood and the administrative details have been confirmed from the authoritative source.
Conclusion
1Z0-076 preparation should culminate in operational judgment: selecting a protection mode that fits the requirement, understanding what redo transport confirms, recognizing whether a standby is genuinely synchronized, and predicting the effect of failures or planned changes. Use Oracle’s 19c scope and documented exam facts as the baseline, then reinforce them with safe configuration exercises and scenario-based troubleshooting. Before scheduling, verify current administrative details on Oracle’s official exam page and make sure your readiness rests on understanding rather than memorized or leaked questions.
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
