1z0-076 Exam Info and Free Practice Test Professional Quiz Study Materials
Accurate Hot Selling 1z0-076 Exam Dumps 2026 Newly Released
Oracle 1z0-076 Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
| Topic 6 |
|
| Topic 8 |
|
| Topic 9 |
|
| Topic 10 |
|
| Topic 11 |
|
| Topic 12 |
|
| Topic 13 |
|
NEW QUESTION # 54
Which three actions are performed by the START PLAN procedure of the DBMS ROLLING package?
- A. switching the primary database to the logical standby role
- B. creating a guaranteed restore point on the primary database
- C. creating a guaranteed restore point on the standby databases
- D. starting media recovery on all the Leading Group Standby databases
- E. converting the designated physical standby database into a logical standby database
- F. building a LogMiner dictionary on the primary database instance
Answer: B,C,F
Explanation:
The DBMS_ROLLING package facilitates a rolling upgrade process across a Data Guard configuration. The START PLAN procedure in particular handles several critical actions, including:
Creating a guaranteed restore point on the standby databases (B): This ensures that the standby databases can be reverted to their state before the rolling upgrade process in case of any issues.
Building a LogMiner dictionary on the primary database instance (C): This is necessary for logical standby databases to interpret redo data during the SQL Apply process.
Creating a guaranteed restore point on the primary database (D): Similar to the standby databases, this ensures that the primary database can be reverted to a known good state if necessary.
Reference:
Oracle Database PL/SQL Packages and Types Reference
Oracle Data Guard Concepts and Administration Guide
NEW QUESTION # 55
Examine the following parameter settings of the physical standby database:
* STANDBY_FILE_MANAGEMENT=AUTO
* ENABLED_PDBS_ON_STANDBY=<null>
During which TWO tasks are files automatically created in the physical standby database after structure changes on the primary database?
- A. Renaming a data file in the primary database
- B. Performing transportable tablespaces
- C. Adding a data file or creating a tablespace
- D. Creating a PDB from the existing PDB within the same CDB
- E. Adding or dropping a redo file group
Answer: C,D
Explanation:
When STANDBY_FILE_MANAGEMENT is set to AUTO, the Oracle Data Guard automatically creates, deletes, and renames files on the standby database to match the changes made on the primary database. The tasks that lead to the automatic creation of files on the standby include:
Adding a data file or creating a tablespace (C): When a new tablespace is created or a new data file is added on the primary database, the standby database automatically replicates this action, maintaining structural consistency with the primary database.
Creating a PDB from the existing PDB within the same CDB (D): Creating a new Pluggable Database (PDB) within a Multitenant Container Database (CDB) on the primary database triggers an automatic creation of the corresponding PDB within the standby CDB.
Reference:
Oracle Data Guard Concepts and Administration Guide
NEW QUESTION # 56
The Oracle database 19c Observer is currently running on host1 and you wish to have it running on host2.
Examine this list of possible steps:
1) Stop the observer on host1
2) Disable Fast-Start Failover
3) Update the broker configuration with the new observer hostname
4) Enable Fast-Start Failover
5) Start the Observer on host2
Which contains the minimum required steps to move the observer to host2?
- A. Execute tasks 1, 2, 3, 4, and 5
- B. Execute only task 5
- C. Execute tasks 1, 3, and 5
- D. Execute tasks 1 and 5
Answer: C
Explanation:
* Stop the Observer on host1 to ensure that there are no conflicts between the instances of the Observer running on different hosts.
* Update the Data Guard Broker configuration with the new hostname for the Observer. This step is crucial to redirect the Data Guard Broker to communicate with the Observer on the new host.
* Start the Observer on host2 to resume its operations in the new environment.
Disabling and re-enabling Fast-Start Failover (steps 2 and 4) are not strictly necessary for moving the Observer to a new host. These steps would be more relevant if changes to the configuration of Fast-Start Failover itself were required, which is not the case when simply relocating the Observer.
NEW QUESTION # 57
A customer has these requirements for their proposed Data Guard implementation:
1. Zero data loss must still be guaranteed through the loss of any one configuration component.
2. The primary database must be protected against a regional disaster.
3. Performance overheads on the primary should be minimized as much as possible given these requirements.
4. Downtime on the primary database for any reason must be kept to a minimum.
Components referred to in the broker commands are:
- A.
- B.
- C.
- D.
Answer: B
Explanation:
According to the requirements stated:
Zero data loss must be guaranteed despite the loss of any one component: This necessitates synchronous redo transport to at least one standby database (for no data loss).
The primary database must be protected against a regional disaster: This implies that there must be a standby database in a different region.
Performance overhead on the primary should be minimized: This suggests that asynchronous transport should be used where possible to reduce the performance impact on the primary.
Downtime on the primary for any reason must be kept to a minimum: This is indicative of a requirement for a fast failover mechanism, possibly with a fast-start failover (FSFO) and high availability.
Given these requirements, the appropriate option that fulfills all these is:
Option C, where 'prima' is the primary database, 'fs1' is the Far Sync instance in the primary region, and 'physt' and 'physt2' are physical standby databases in the primary and remote regions, respectively. In this configuration:
'prima' is set to send redo to 'fs1' using SYNC to guarantee zero data loss.
'fs1' is set to send redo to 'physt' (local standby) using FASTSYNC, which is a low-latency synchronous transport that is optimized for performance.
The Data Guard configuration's protection mode is set to MAXAVAILABILITY to provide the highest level of data protection that is possible without compromising the availability of the primary database.
This configuration ensures that there is zero data loss even if the primary region is completely lost, maintains performance by limiting the synchronous transport to the local region with a Far Sync instance, and has a remote standby database in a separate region for disaster recovery purposes.
Reference:
Oracle Data Guard Concepts and Administration
Oracle Data Guard Broker documentation
NEW QUESTION # 58
Which THREE are true about using flashback database in a Data Guard environment?
- A. It may not be used to flash back a primary database after a failover to a physical standby.
- B. When a flashback database operation is performed on a primary database, a physical standby database is also flashed back automatically.
- C. It may be used to flash back a physical standby that receives redo from a far sync instance.
- D. When a flashback database operation is performed on a primary database, a logical standby database is also flashed back automatically.
- E. You can use it when real-time apply is enabled in case the physical standby suffers from logical corruption.
- F. You can use it when real-time apply is enabled in case the phylt may not be used to flash back a primary database after a failover to a logical standby.
Answer: A,C,E
Explanation:
Flashback Database is a feature that allows reverting a database to a previous point in time, which is extremely useful in various Data Guard configurations:
It may be used to flash back a physical standby that receives redo from a far sync instance (C): Flashback Database can be used on a physical standby database to revert it to a past point in time, even when it is receiving redo data from a far sync instance. This can be particularly useful to recover from logical corruptions or unwanted changes.
You can use it when real-time apply is enabled in case the physical standby suffers from logical corruption (D): Even when real-time apply is enabled, which allows redo data to be applied to the standby database as soon as it is received, Flashback Database can be used to revert the physical standby database to a point in time before the logical corruption occurred.
It may not be used to flash back a primary database after a failover to a physical standby (E): After a failover has occurred from a primary to a physical standby database, making the standby the new primary, Flashback Database cannot be used to revert the old primary database to a state before the failover because the failover operation makes irreversible changes to the database role and configuration.
Reference:
Oracle Database Backup and Recovery User's Guide
Oracle Data Guard Concepts and Administration
NEW QUESTION # 59
Which THREE statements are TRUE about Global Sequences when connected to a physical standby database with Real-Time Query enabled?
- A. Their usage may have a performance impact on the physical standby database if the CACHE size is too small.
- B. Their usage will always have a performance impact on the primary database.
- C. Their creation requires that a LOG archive_dest_n parameter be defined in the standby that points back to the primary.
- D. If the CACHE option is set then the size of the cache must be at least 100.
- E. They must have the NOORDEK and CACHE options set.
Answer: A,B,E
Explanation:
Global Sequences are Oracle sequences that generate unique values across multiple instances in an Oracle RAC or a Data Guard configuration. Regarding their behavior and performance when connected to a physical standby database with Real-Time Query enabled:
* A: The usage of Global Sequences can indeed have a performance impact on the primary database due to the need to generate unique values that are consistent across both primary and standby databases.
* D: The performance impact on the physical standby database may occur if the CACHE size is too small. This is because the standby database will frequently have to access the primary database to replenish the cache, which can increase the load and potentially lead to performance degradation.
* E: Global Sequences should have the NOORDER and CACHE options set. The NOORDER option ensures that sequence numbers are provided without guaranteeing sequence order, thus improving scalability and performance. The CACHE option is used to specify how many sequence values will be held in memory for faster access.
Option B is incorrect as the LOG_ARCHIVE_DEST_n parameter's definition for standbys pointing back to the primary does not directly pertain to the creation of sequences.
Option C is incorrect because there is no requirement that the size of the cache for a sequence must be at least
100. The CACHE size can be set to a different number based on specific use cases or performance considerations.
References: Oracle's documentation on sequences and their behavior in a Data Guard environment provides insights into the performance considerations and best practices for using sequences, particularly in a Real-Time Query context.
NEW QUESTION # 60
Which two are true about database roles in an Oracle Data Guard configuration?
- A. A Physical Standby Database can be converted into a Logical Standby Database.
- B. A Logical Standby Database can cascade redo to a terminal destination.
- C. A Logical Standby Database can be converted to a Snapshot Standby Database.
- D. A Snapshot Standby Database can be a fast-start failover target.
- E. A configuration consisting only of a primary and one or more physical standby databases can support a rolling release upgrade.
Answer: A,E
Explanation:
A Physical Standby Database can indeed be converted into a Logical Standby Database, providing flexibility in a Data Guard configuration. This allows for the database to switch roles and supports SQL apply operations, enabling more granular control over the data and transactions being replicated and applied. Additionally, having a configuration with a primary database and one or more physical standby databases allows for rolling upgrades to be performed. This means that each database in the Data Guard configuration can be upgraded in a phased manner, minimizing downtime and ensuring high availability during the upgrade process.
NEW QUESTION # 61
You must configure flashback database for your Oracle 19c databases that will be part of a Data Guard Broker configuration.
The databases are all in ARCHIVELOG mode.
You will execute the SQL statement:
ALTER DATABASE FLASHBACK ON;
Which three are true concerning this command?
- A. It will execute successfully while an Oracle 19c primary database is open.
- B. It will execute successfully on an Oracle 19c logical standby database while SQL apply is active.
- C. It will execute successfully while an Oracle 19c primary database is mounted.
- D. It will execute successfully on an Oracle 19c physical standby database while Real Time Query is active.
- E. If executed successfully on an Oracle 19c primary database, flashback will also be enabled on all physical standby databases that are part of the configuration.
- F. If executed successfully on an Oracle 19c primary database, flashback will also be enabled on all logical standby databases that are part of the configuration.
Answer: A,B,C
Explanation:
The command ALTER DATABASE FLASHBACK ON; enables the Flashback Database feature, which provides a way to quickly revert an entire Oracle database back to a previous point in time. This command can be executed while an Oracle 19c primary database is either open (option A) or mounted (option B). It is also applicable to an Oracle 19c logical standby database while SQL Apply is active (option E). However, it's important to note that enabling Flashback Database on the primary does not automatically enable it on all associated standby databases, whether they are physical or logical. Each database in a Data Guard configuration must have Flashback Database explicitly enabled if desired. Real Time Query being active on a physical standby does not directly relate to the ability to execute this command on the standby. Reference: The explanation is based on Oracle's concepts for Flashback Technology and Data Guard configurations as detailed in the Oracle Database Backup and Recovery User's Guide and the Oracle Data Guard Concepts and Administration guide.
NEW QUESTION # 62
You detected an unrecoverable archive gap in your data guard environment. So, you need to roll standby.
forward in time without applying a large number of archive log files using this command:
RMAN> RECOVER STANDBY DATABASE FROM SERVICE-<primary database name>;
When running this command, which of the following steps can be performed automatically?
1. Remember all data file names on the standby.
2. Restart standby in nomount.
3. Restore controlfile from primary.
4. Mount standby database.
5. Rename data files from stored standby names.
6. Restore new data files to new names.
7. Recover standby.
- A. 1,3,5,6,7
- B. 2,3,5,6,7
- C. 1, 2,3,4,6,7
- D. 1,2,3,4,5,6,7
- E. 2,3,6,7
Answer: C
Explanation:
The RECOVER STANDBY DATABASE FROM SERVICE command in RMAN is designed to automate various steps required to recover the standby database, especially when dealing with an archive gap. When this command is executed, the following actions can occur automatically:
* Remember all data file names on the standby (1): RMAN has the capability to recall the names and paths of all data files associated with the standby database.
* Restart standby in nomount (2): The standby database can be automatically restarted in the NOMOUNT state, allowing recovery operations to proceed without the database being open.
* Restore controlfile from primary (3): RMAN can restore the control file from the primary database to the standby system, ensuring that the standby has the most up-to-date control file.
* Mount standby database (4): After restoring the control file, the standby database is mounted to prepare for data file recovery.
* Rename data files from stored standby names (5): Not typically done automatically by this command.
* Restore new data files to new names (6): New data files added to the primary since the last synchronization can be restored to the standby with their correct names.
* Recover standby (7): Finally, RMAN will apply any necessary redo logs to bring the standby database up to date with the primary.
While some steps, such as renaming data files (5), typically require manual intervention or scripting, most of the recovery process can be handled by RMAN automatically, streamlining the recovery of the standby database.
References:
* Oracle Database Backup and Recovery User's Guide
* Oracle Data Guard Concepts and Administration Guide
NEW QUESTION # 63
Which THREE statements are TRUE about the supported workload in Active Data Guard standby databases?
- A. The DDL operations on private temporary tables are transparently redirected to the primary database.
- B. The DML operations on a standby can be transparently redirected to and run on the primary database
- C. You might have to use sequences with global temporary tables to support read-mostly applications by using Active Data Guard.
- D. PL/SQL blocks that you run on Active Data Guard standby databases can be always redirected to and run on the primary database.
- E. Read-mostly reporting applications that use global temporary tables for storing temporary data can be offloaded.
Answer: B,C,E
Explanation:
In an Oracle Active Data Guard environment:
B: Read-mostly reporting applications that utilize global temporary tables to store session-specific data can be effectively offloaded to an Active Data Guard standby database, reducing the load on the primary database.
C: Sequences can be used with global temporary tables on an Active Data Guard standby database to support certain types of read-mostly applications, though some restrictions on sequence use may apply.
E: In Oracle Database 19c and later, DML redirection allows DML operations performed on an Active Data Guard standby database to be transparently redirected to the primary database. This is part of the DML Redirection feature.
Option A is incorrect because not all PL/SQL blocks run on an Active Data Guard standby database can be redirected to the primary database. Some PL/SQL executions, specifically those that would attempt to make changes to the database, are not supported on the standby.
Option D is incorrect because DDL operations on private temporary tables are not redirected; instead, private temporary tables are session-specific and are not persisted on disk, so they do not generate redo and are not applicable to an Active Data Guard standby.
NEW QUESTION # 64
There are currently 6 applief. and 6 pfepafef processes running and no idle applier processes on y logical standby database.
The max_SERVERS SQL apply parameter and number of archiver processes are both set to 12.
Identify two changes, each of which would allow you to increase the number of applier processes.
- A. Decrease the number of archiver processes on the standby database.
- B. Increase the RECOVERY_PARALLEL initialization parameter.
- C. Increase the value for the MAX_SERVERS SQL apply parameter.
- D. Increase the parallel_max_server initialization parameter.
- E. Increase the processes initialization parameter. D Decrease the number of FREPARER processes.
Answer: C,D
Explanation:
To increase the number of applier processes on a logical standby database, the following changes can be made:
C: Increasing the value for the MAX_SERVERS SQL apply parameter would allow for more applier processes to be initiated, assuming that system resources permit.
D: Increasing the PARALLEL_MAX_SERVERS initialization parameter would allow for more parallel execution processes, which can be used by SQL apply to increase the number of applier processes.
Option A is incorrect as decreasing the number of archiver processes will not necessarily increase the number of applier processes; these are unrelated components.
Option B is incorrect because the 'FREPARER' processes do not exist, it seems to be a typographical error, and the 'REPARER' is not a valid Oracle process or parameter.
Option E is incorrect because the RECOVERY_PARALLELISM parameter controls the number of processes used for instance recovery and media recovery, not for SQL apply.
NEW QUESTION # 65
Examine the Data Guard configuration after an accidental switchover to Sheep:
DGMGRL> show configuration;
Configuration - Animals
Protection Mode: MaxAvailability
Databases:
sheep - Primary database
dogs - Logical standby database
cats - Physical standby database (disabled)
ORA-16795: the standby database needs to be re-created
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS
Which three statements will be true after a switchover to Dogs?
- A. Cats will be an enabled physical standby database.
- B. Sheep will be a disabled logical standby database.
- C. Sheep will be an enabled logical standby database.
- D. Dogs will be the primary database.
- E. Cats will be a disabled physical standby database that can be manually enabled.
Answer: C,D,E
NEW QUESTION # 66
You are using Data Guard in conjunction with Global Database Services.
You have a Data Guard Broker configuration called Sales and a GDS pool called Prod.
Which three are true concerning the management of the broker configuration when using GDS?
- A. DGMGRL may be used to add a single database to the Sales configuration even if Sales is a member of the Prod pool.
- B. DGMGRL may be used to add the Sales configuration to the Prod pool in gds.
- C. Adding a database to the Sales configuration with DGMGRL requires that the Sales configuration be disabled first. It must then be enabled after the new database is added to the configuration.
- D. Performing a role change with DGMGRL automatically notifies GDS which in turn activates the appropriate services.
- E. Adding a database to the Sales configuration with DGMGRL automatically adds the database to the Prod Pool.
Answer: A,B,D
Explanation:
In the context of Oracle Data Guard and Global Database Services (GDS):
* DGMGRL may be used to add the Sales configuration to the Prod pool in gds (A): Data Guard Broker's command-line interface DGMGRL can be utilized to manage configurations with GDS, allowing the addition of Data Guard Broker configurations to GDS pools.
* Performing a role change with DGMGRL automatically notifies GDS which in turn activates the appropriate services (B): When a role change is executed using DGMGRL, GDS is automatically notified, and it then activates the services that are appropriate for the new database roles.
* DGMGRL may be used to add a single database to the Sales configuration even if Sales is a member of the Prod pool (C): DGMGRL provides the capability to manage individual databases within a broker configuration, including adding databases to a configuration that is already part of a GDS pool.References:
* Oracle Data Guard Broker documentation
* Oracle Global Data Services documentation
NEW QUESTION # 67
Your Data Guard environment consists of these components and settings:
1. A primary database
2. A remote physical standby database
3. Real-time query is enabled.
4. The redo transport mode is set to SYNC.
5. The protection mode is set to Maximum Availability.
You notice that queries executed on the physical standby database receive errors: ORA-03172: STANDBY_MAX_DATA_DELAY of 15 seconds exceeded. Which two would you recommend to avoid this error?
- A. Change the protection mode to Maximum Performance.
- B. Increase the network bandwidth between the primary and standby databases.
- C. Change the protection mode to Maximum Protection.
- D. Reduce I/O latency for the storage used by the primary database.
- E. Increase the size of the buffer cache on the standby database instance.
- F. Increase the number of standby redo log files on the primary database.
Answer: B,D
Explanation:
The ORA-03172: STANDBY_MAX_DATA_DELAY error indicates that the real-time query on the physical standby database is experiencing delays beyond the specified maximum data delay threshold. Increasing the network bandwidth (Option E) can enhance the speed at which redo data is transferred from the primary to the standby database, thereby reducing the likelihood of exceeding the STANDBY_MAX_DATA_DELAY threshold. Reducing I/O latency on the primary database's storage (Option B) ensures that redo data is generated and shipped more efficiently, further mitigating the risk of delay. These actions, focused on optimizing data transfer and processing speed, address the root causes of the ORA-03172 error in a synchronous Data Guard configuration operating in Maximum Availability mode.
NEW QUESTION # 68
Which three types of backups offload ........ with the primary database in a data Guard
- A. Data files
- B. Online logs
- C. Password files
- D. Broker configuration files
- E. Control files
- F. Archive logs
Answer: A,E,F
Explanation:
In a Data Guard environment, you can offload the backups of certain database components to a physical standby database. Incremental backups of a standby database are interchangeable with the primary database, meaning you can apply a backup taken on a standby database to a primary database and vice versa. This includes control files, data files, and archive logs. Backups of control files and nonstandby control files are interchangeable. You can restore a standby control file on a primary database and a primary control file on a physical standby database, demonstrating their interchangeability and the ability to offload control file backups to one database in a Data Guard environment.
NEW QUESTION # 69
Which THREE are true about using flashback database in a Data Guard environment?
- A. It may not be used to flash back a primary database after a failover to a physical standby.
- B. When a flashback database operation is performed on a primary database, a physical standby database is also flashed back automatically.
- C. It may be used to flash back a physical standby that receives redo from a far sync instance.
- D. When a flashback database operation is performed on a primary database, a logical standby database is also flashed back automatically.
- E. You can use it when real-time apply is enabled in case the physical standby suffers from logical corruption.
- F. You can use it when real-time apply is enabled in case the phylt may not be used to flash back a primary database after a failover to a logical standby.
Answer: A,C,E
NEW QUESTION # 70
You notice that the SQL apply lag on your logical standby database has increased but the redo transport lag has not.
Which four could be reasons for the increase in SQL apply lag?
- A. An undersized undo tablespace on the logical standby
- B. An increased number of bulk inserts on the primary
- C. An increased number of bulk updates on the primary
- D. The standby redo log files are undersized on the primary database
- E. Many SQL apply operations do full table scans
- F. An undersized shared pool
Answer: A,C,E,F
Explanation:
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.
References: Oracle Database High Availability Overview and Oracle Data Guard Concepts and Administration guide provide insights into the factors affecting SQL apply performance on logical standby databases.
NEW QUESTION # 71
Which THREE steps are prerequisites for the creation of a physical standby database on a separate server using the RMAN active database duplication method?
- A. startup nomount the standby database instance.
- B. Set the DB_UNIQUE_NAME parameter on the primary database to a different value than that of the DB_NAME name parameter.
- C. Configure Oracle Net connectivity on the primary host to the standby database instance.
- D. Establish user equivalence for the database software owner between the primary host and standby host.
- E. Put the primary database into archivelog mode.
Answer: A,C,D
Explanation:
Creating a physical standby database using RMAN active database duplication requires certain prerequisites to ensure a successful and seamless operation:
Configure Oracle Net connectivity on the primary host to the standby database instance (A): Proper Oracle Net connectivity between the primary and standby servers is essential for communication and data transfer during the duplication process. Oracle Net services provide the network foundation for Oracle Database, Oracle Net Listener, and Oracle applications.
Establish user equivalence for the database software owner between the primary host and standby host (B): User equivalence ensures that the user who owns the Oracle Database software on the primary server has the same privileges on the standby server. This is crucial for RMAN to perform operations on both servers without encountering permission issues.
Startup nomount the standby database instance (C): The standby database instance needs to be started in the NOMOUNT stage before the duplication can begin. This prepares the environment for creating the control file and restoring the database without mounting it, which is a necessary step in the RMAN duplication process.
Reference:
Oracle Database Backup and Recovery User's Guide
Oracle Data Guard Concepts and Administration
NEW QUESTION # 72
Which THREE statements are true........ open in real time query mode, which becomes a new.
- A. User sessions and Current Buffers are maintained by default.
- B. All current buffers can be retained.
- C. Sessions that have long running queries can be retained.
- D. All sessions are disconnected and all
- E. Sessions that are using database links
- F. User sessions can be retained.
Answer: B,D,F
Explanation:
When a physical standby database is opened in real-time query mode, which may be referred to as real-time apply when using Active Data Guard, certain operations can disrupt ongoing sessions. However, with features like Application Continuity and the proper configuration of initialization parameters such as STANDBY_DB_PRESERVE_STATES, user sessions and current buffers may be preserved during role transitions such as a switchover or failover. Specifically, the STANDBY_DB_PRESERVE_STATES parameter can be set to preserve none, all, or only user sessions during such transitions. This ensures that in-flight transactions are not lost and that users do not experience disruptions during the role transitions of a physical standby database.
Reference
Oracle Data Guard Concepts and Administration
Oracle Database Licensing Information User Manual
Oracle Data Guard Broker User Manual
NEW QUESTION # 73
Which THREE statements are true about snapshot standby databases?
- A. A snapshot standby database can be the only standby database in a Maximum Protection Oracle Data Guard configuration.
- B. If datafiles grow while a database is a snapshot standby database, then they shrink when converted back to a physical standby database.
- C. A guaranteed restore point is created automatically when a physical standby database is converted into a snapshot standby database.
- D. A snapshot standby database must be opened at least once in read-write mode before it can be converted into a physical standby database.
- E. Snapshot standby databases may be used for rolling database upgrades.
Answer: C,D,E
NEW QUESTION # 74
Which TWO observations are true about the Far Sync instance?
- A. Can only be created using a series of SQL commands
- B. Receives redo synchronously from the primary database
- C. Can be created using the RMAN DUPLICATE command
- D. Includes a standby control file, password file, data files, standby redo logs, and archive logs
- E. Applies redo received
Answer: B,E
Explanation:
A Far Sync instance is a special kind of Oracle Data Guard configuration that allows synchronous redo transport from a primary database to a remote standby database with minimum impact on the primary database's performance. The Far Sync instance receives redo data synchronously from the primary database (A), then ships it asynchronously to the remote standby database, thus extending zero data loss protection over longer distances and higher network latency environments than would be practical with a synchronous standby alone. The Far Sync instance does not apply the redo data; it just receives and ships it (E). A Far Sync instance does not have data files, and it cannot apply redo to stay synchronized with the primary database.
References:Oracle Database High Availability Overview and Oracle Data Guard Concepts and Administration documentation detail the role and configuration of Far Sync instances, including how they contribute to achieving zero data loss disaster recovery over long distances.
NEW QUESTION # 75
Suppose that you manage the following databases in your environment:
* boston: Primary database with a single PDB called DEVI
* london: Physical standby database protecting the PDB called DEVI
* orcl: Stand-alone database with a single PDB called PDB1 as a remote clone source You are planning to run the following command to create a remote clone in the primary database (boston) using pdbi in orcl:
Which are the THREE prerequisites for automating instantiation of the PDB in the standby database (london)?
- A. Set STANDBY_PDB_SOURCE_FILE_DIRECTORY to <location of the PDB> in the london database.
- B. Open PDBI (remote clone source) in Read Only.
- C. Set standby_pdb_source_file_dblink to clone_link in the london database.
- D. Enable Active Data Guard in the _ondon database.
- E. Set STANDBY_FILE_MANAGEMENT to auto in the london database.
- F. Open PDBI (remote clone source) in Read Write.
Answer: A,B,E
Explanation:
To automate the instantiation of a PDB in the standby database after creating a remote clone in the primary database, certain conditions must be met:
* Open PDBI (remote clone source) in Read Only (A): The source PDB from which the clone is created must be open in read-only mode to ensure a consistent state during cloning.
* Set STANDBY_PDB_SOURCE_FILE_DIRECTORY to <location of the PDB> in the london database (C): This parameter specifies the location on the standby database where the files from the source PDB should be placed.
* Set STANDBY_FILE_MANAGEMENT to auto in the london database (F): This parameter automates the management of file changes on the standby database when structural changes occur on the primary database, ensuring that the clone operation is reflected automatically on the standby.
References:
* Oracle Multitenant Administrator's Guide
* Oracle Data Guard Broker documentation
NEW QUESTION # 76
Which THREE statements are TRUE about the supported workload in Active Data Guard standby databases?
- A. The DDL operations on private temporary tables are transparently redirected to the primary database.
- B. The DML operations on a standby can be transparently redirected to and run on the primary database
- C. You might have to use sequences with global temporary tables to support read-mostly applications by using Active Data Guard.
- D. PL/SQL blocks that you run on Active Data Guard standby databases can be always redirected to and run on the primary database.
- E. Read-mostly reporting applications that use global temporary tables for storing temporary data can be offloaded.
Answer: B,C,E
Explanation:
In an Oracle Active Data Guard environment:
* B: Read-mostly reporting applications that utilize global temporary tables to store session-specific data can be effectively offloaded to an Active Data Guard standby database, reducing the load on the primary database.
* C: Sequences can be used with global temporary tables on an Active Data Guard standby database to support certain types of read-mostly applications, though some restrictions on sequence use may apply.
* E: In Oracle Database 19c and later, DML redirection allows DML operations performed on an Active Data Guard standby database to be transparently redirected to the primary database. This is part of the DML Redirection feature.
Option A is incorrect because not all PL/SQL blocks run on an Active Data Guard standby database can be redirected to the primary database. Some PL/SQL executions, specifically those that would attempt to make changes to the database, are not supported on the standby.
Option D is incorrect because DDL operations on private temporary tables are not redirected; instead, private temporary tables are session-specific and are not persisted on disk, so they do not generate redo and are not applicable to an Active Data Guard standby.
References: The behavior and capabilities of Active Data Guard standby databases are documented in the Oracle Data Guard Concepts and Administration guide and the Active Data Guard documentation.
NEW QUESTION # 77
......
Get 100% Authentic Oracle 1z0-076 Dumps with Correct Answers: https://www.testkingfree.com/Oracle/1z0-076-practice-exam-dumps.html
New Training Course 1z0-076 Tutorial Preparation Guide: https://drive.google.com/open?id=1yfb9lWE5q2MvO981ZmE6dZOqA4R6PSN3