Jun-2026 Realistic 1z0-076 Exam Dumps with Accurate & Updated Questions
1z0-076 Exam Dumps - PDF Questions and Testing Engine
Oracle 1z0-076 Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 3 |
|
| Topic 4 |
|
| Topic 5 |
|
| Topic 6 |
|
| Topic 7 |
|
| Topic 8 |
|
| Topic 9 |
|
| Topic 10 |
|
NEW QUESTION # 22
Which TWO statements are true about Real-Time Query?
- A. Setting standby_max_data_delay=0 requires synchronous redo transport.
- B. Disabling Real-Time Query prevents the automatic start of redo apply when a physical standby databases opened read only.
- C. A standby database enabled for Real-Time Query cannot be the Fast-Start Failover target of the Data Guard configuration.
- D. Real-Time Query has no limitations regarding the protection level of the Data Guard environment.
- E. Real-Time Query sessions can be connected to a Far Sync instance.
Answer: A,B
Explanation:
Real-Time Query is a feature that allows queries to be run on a physical standby database while it is applying redo data. The relevant truths about it are:
* Setting standby_max_data_delay=0 requires synchronous redo transport (A): For the real-time apply feature to function with no data delay (zero delay), synchronous redo transport must be used. This setting ensures that the data on the standby database is as current as possible before queries are executed against it.
* Disabling Real-Time Query prevents the automatic start of redo apply when a physical standby database is opened read-only (C): If Real-Time Query is disabled, opening the standby database in read-only mode will not start the redo apply process automatically. Redo apply needs to be manually started to synchronize the standby database with the primary.References:
* Oracle Data Guard Concepts and Administration Guide
NEW QUESTION # 23
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. Increase the size of the buffer cache on the standby database instance.
- B. Reduce I/O latency for the storage used by the primary database.
- C. Increase the network bandwidth between the primary and standby databases.
- D. Change the protection mode to Maximum Performance.
- E. Change the protection mode to Maximum Protection.
- F. Increase the number of standby redo log files on the primary database.
Answer: B,C
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 # 24
Which three are true about using Flashback database through role transitions in a Data Guard environment?
- A. Logical standby databases retain their current role when you flash back through to a point in time before the switchover occurred which caused this database to become a logical standby.
- B. Physical standby databases retain their current role when you flash back to a point in time before the switchover occurred which caused this database to become a physical standby.
- C. Physical standby databases retain their current role when you flash back to a point in time before a reinstate occurred which caused this database to become a physical standby.
- D. Logical standby database roles are reverted to their original role when you flash back to a point in time before the switchover occurred which caused this database to become a logical standby.
- E. Flashback database may not be used to undo a physical standby database activation.
Answer: B,C,E
NEW QUESTION # 25
Examine the Data Guard configuration:
DGMGRL> show configuration;
Configuration - Animals
Protection Mode: MaxAvailability
Databases:
dogs - Primary database
cats - Snapshot standby database
sheep - Snapshot standby database
Fast-Start Failover: DISABLED
Configuration Status:
ORA-01034: ORACLE not available
ORA-16625: cannot reach database "dogs"
DGM-17017: unable to determine configuration status
ou wish to perform a failover to sheep. Which command, or sequence of commands, should you issue to the broker before executing failover to sheep; using the broker?
- A. DGMGRL> convert database sheep to physical standby;
DGMGRL> edit configuration set protection mode as maxperformance;
DGMGRL> convert database sheep to physical standby; - B. DGMGRL> convert database sheep to physical standby;
- C. DGMGRL> convert database cats to physical standby;
- D. DGMGRL> convert database cats to physical standby;
- E. None, because you can directly failover to a Snapshot Standby Database.
Answer: B
NEW QUESTION # 26
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. Configure Oracle Net connectivity on the primary host to the standby database instance.
- C. Put the primary database into archivelog mode.
- D. Establish user equivalence for the database software owner between the primary host and standby host.
- E. Set the DB_UNIQUE_NAME parameter on the primary database to a different value than that of the DB_NAME name parameter.
Answer: A,B,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.References:
* Oracle Database Backup and Recovery User's Guide
* Oracle Data Guard Concepts and Administration
NEW QUESTION # 27
You must configure an Oracle Data..........
1. A primary database
2. A physical standby database
Examine these requirements: 1. Data loss is not permitted.
1. Data loss is not permitted.
2. It should be possible to convert the physical standby database to a snapshot standby database.
3. Under normal operations, transactions should commit when redo is written to disk on the primary database and as soon as it has been received by the standby database instance.
4. The availability of the primary database should not be compromised by the availability of the standby database.
5. It should be possible to convert the physical standby database to a logical standby database
6. It should be possible to deploy Real Application Clusters on the primary database.
7. It should be possible to deploy Real Application Clusters on the physical standby database.
You configure SYNC redo transport mode in combination with Maximum Protection mode.
- A. 1, 2, 6, and 7
- B. 1, 2, 3, 6, and 7
- C. 1, 2, 3, 4, 5, 6, and 7
- D. 1, 2, and 5
- E. 1, 6, and 7
Answer: C
Explanation:
When SYNC redo transport mode is combined with Maximum Protection mode, it ensures that no data loss will occur (requirement 1). The physical standby can be converted to a snapshot standby (requirement 2) and later to a logical standby database (requirement 5), satisfying both transformation requirements. Transactions commit as soon as redo data is received by the standby database (requirement 3). The availability of the primary is not dependent on the standby database in Maximum Protection mode, as the primary database will halt if the standby cannot acknowledge the redo (requirement 4), thus indirectly ensuring its availability. It is also possible to deploy Real Application Clusters on both the primary (requirement 6) and the physical standby database (requirement 7), providing high availability and scalability.
Reference
Oracle Data Guard documentation detailing the requirements for different database roles, protection modes, and redo transport modes, as well as the capabilities and limitations of each configuration.
NEW QUESTION # 28
A Data Guard environment has this configuration and these attributes:
A primary database
A physical standby database named sbdb
The configuration is in maximum availability protection mode.
Then sbdb is converted to a snapshot standby database.
Which two statements are true?
- A. sbdb can still receive redo.
- B. The recovery time objective increases.
- C. The protection mode is lowered to maximum performance.
- D. sbdb can still apply redo.
- E. The recovery point objective increases.
Answer: A,E
NEW QUESTION # 29
Examine the Data Guard configuration:
What happens if you issue "switchover to sheep;" at the DGMGRL prompt?
- A. It results in an error indicating that a switchover is not allowed.
- B. The switchover succeeds and Fast-Start Failover is suspended.
- C. The switchover succeeds and Dogs becomes the new failover target.
- D. The switchover succeeds but Dogs needs to be reinstated.
- E. The switchover succeeds and Cats becomes the new failover target.
Answer: C
Explanation:
When issuing a "switchover to sheep;" command in a Data Guard configuration, the primary database (Dogs) transitions to a standby role, and the target standby database (Sheep) becomes the new primary database.
Fast-Start Failover (FSFO) remains enabled, but its target changes according to the new roles of the databases.
Since Cats is also a physical standby database, it does not become the failover target by default unless it is specified in the broker configuration. After the switchover, the original primary (Dogs) becomes the new standby database and thus the new failover target for FSFO.References:Oracle Data Guard Broker documentation provides detailed procedures and explanations of switchover operations, including how FSFO targets are affected post-switchover. This behavior is consistent across different Oracle Database versions that support Data Guard and FSFO.
NEW QUESTION # 30
Which three are true concerning database states after a successful switchover?
- A. The new primary database will be open read-write.
- B. If the former primary database became a logical standby database it will be open read-write.
- C. If the former primary database became a physical standby database it will always be open readonly.
- D. If the former primary database became a logical standby database it will be in mount state.
- E. The former primary database will always be open.
- F. If the former primary database became a physical standby database it will be in the same state as the former physical standby database.
Answer: A,B,F
Explanation:
After a successful switchover operation in a Data Guard environment, the new primary database (the former standby) will be open read-write (option A). If the former primary database transitions to a logical standby database, it will also be open read-write (option C), allowing it to apply redo data while servicing read-only queries. The former primary, if converted to a physical standby, will adopt the state that the former physical standby database was in prior to the switchover, which can vary based on the configuration prior to the switchover (option D). The state of a physical standby database can range from mounted to open read-only, depending on whether Real-Time Query was enabled. Thus, the exact state will depend on the pre-switchover setup. It's also essential to highlight that options B and E suggest specific states for a former primary turned logical standby, and a former primary turned physical standby, respectively, but these states are not fixed and depend on the configurations set up by the database administrators. Reference: The answers are corroborated by Oracle's documentation on Data Guard switchovers, specifically in the Oracle Data Guard Concepts and Administration guide, which explains the roles and states of databases in a Data Guard configuration before and after switchovers.
NEW QUESTION # 31
Which THREE statements are true about Far Sync instances?
- A. They use an spfMe, a standby controlfile, and standby redo logs.
- B. The Data Guard Broker must be used to deploy and manage Far Sync instances.
- C. A primary database can ship redo directly to multiple Far Sync instances.
- D. They work with any protection level.
- E. They enable standby databases to be configured at remote distances from the primary without impacting performance on the primary.
Answer: B,C,E
Explanation:
Far Sync instances are a feature of Oracle Data Guard designed to support zero data loss protection over long distances:
* The Data Guard Broker must be used to deploy and manage Far Sync instances (A): Data Guard Broker simplifies the deployment and management of Far Sync instances, which are an integral part of zero data loss protection configurations.
* They enable standby databases to be configured at remote distances from the primary without impacting performance on the primary (C): Far Sync instances are designed to receive redo from the primary database and then forward it to a remote standby database, thereby avoiding any performance
* impact on the primary database itself.
* A primary database can ship redo directly to multiple Far Sync instances (E): A primary database can be configured to send redo logs to more than one Far Sync instance, which can then forward the redo to their respective remote standby databases.References:
* Oracle Data Guard Concepts and Administration Guide
* Oracle Database High Availability Overview
NEW QUESTION # 32
Which two are true about managing and monitoring Oracle container databases in a Data Guard environment using the broker?
- A. After a role change, the broker opens all Pluggable databases (pdbb) on the new primary.
- B. If the primary database is a container database, then a physical standby may be a non-container database.
- C. If the primary database is not a container database, then a standby may be a container database.
- D. If the primary database is a container database, then a logical standby may be a non-container database.
- E. All broker actions execute at the root container for container databases.
Answer: A,E
Explanation:
In the context of Oracle Data Guard and container databases (CDBs) managed by Data Guard Broker:
* All broker actions execute at the root container for container databases (D): When using Data Guard Broker to manage a CDB, the actions performed by the broker are executed at the level of the root container. This is because the root container maintains the control and configuration information that applies to the entire CDB, including all of its pluggable databases (PDBs).
* After a role change, the broker opens all Pluggable databases (PDBs) on the new primary (E):
Following a role transition such as a switchover or a failover, Data Guard Broker ensures that all PDBs within the CDB of the new primary database are opened, which is essential to resume operations of the PDBs without manual intervention.References:
* Oracle Data Guard Broker documentation
* Oracle Multitenant Administrator's Guide
NEW QUESTION # 33
Which two statements are true when using non-rolling release upgrades in a Data Guard environment?
- A. The compatible parameter on a standby database that is applying redo, must be equal to or greater than the compatible parameter on the primary that is shipping redo to that standby.
- B. User equivalence must be established for the owner of the Oracle software on the affected hosts prior to the upgrade.
- C. Modifications to the data dictionary on the primary database caused by the upgrade, are applied on a logical standby database.
- D. During the upgrade of a logical standby database, standby redo log files must reside on O/S file systems.
- E. Modifications to the data dictionary on the primary database caused by the upgrade, are applied on a physical standby database.
Answer: A,E
Explanation:
The compatible parameter on a standby database that is applying redo, must be equal to or greater than the compatible parameter on the primary that is shipping redo to that standby (A): This ensures that the standby database can apply redo from the primary, even after the primary has been upgraded. The COMPATIBLE parameter setting on the standby database should not preclude it from understanding the redo it receives.
Modifications to the data dictionary on the primary database caused by the upgrade, are applied on a physical standby database (C): When the primary database undergoes a non-rolling upgrade, any resulting data dictionary changes are transmitted through redo data and applied to the physical standby database.
Reference:
Oracle Database Upgrade Guide
Oracle Data Guard Concepts and Administration Guide
NEW QUESTION # 34
Which three statements are true about redo transport?
- A. With asynchronous redo transport, TTnn processes may read redo from the log buffer or from standby redo logs on the primary database.
- B. An RFS process on a standby database instance may receive redo from an archiver process on the primary database instance to perform archive gap resolution.
- C. Multiple RFS processes may receive redo on one far sync instance.
- D. Multiple RFS processes may receive redo on one standby database instance.
- E. With synchronous redo transport, LGWR ships redo directly to RFS processes on the standby database instances and waits for an acknowledgment.
Answer: B,D,E
NEW QUESTION # 35
You have a Data Guard Broker configuration called 'Somewhere' as shown:
DGMGRL> SHOW CONFIGURATION;
Configuration - Somewhere
Protection Mode: MaxPerformance
Databases:
Nearby - Primary database
FS - Far Sync
Farout - Physical standby database
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS
You then run this command:
DGMGRL> SHOW DATABASE 'Nearby' 'InconsistentProperties';
Which two are true about the output of this DGMGRL command?
- A. It shows all properties whose broker configuration values for database Nearby are inconsistent with the broker configuration values for database Farout.
- B. It shows all properties whose broker configuration values for database Nearby are inconsistent with the values in the corresponding server parameter file or the runtime values for database instance Nearby.
- C. Any inconsistency reported is on an instance-specific basis.
- D. A far sync instance cannot have inconsistent properties because it has no database.
Answer: B,D
NEW QUESTION # 36
Examine this list of possible steps:
1. Raise the compatibility level on both databases.
2. Restart SQL Apply on the upgraded logical standby database.
3. Start SQL Apply on the old primary database.
4. Perform a Switchover to the logical standby database.
5. Upgrade the logical standby database.
6. Upgrade the old primary database.
Which is the minimum number of steps in the correct order, to perform a rolling release upgrade of a data guard environment using an existing logical standby database and to enable the new functionality?
- A. 5,2,4,6,3,1
- B. 5,2,4,3,6,1
- C. 4,6,5,2,3,1
- D. 1,5,2,4,6,3
- E. 5,2,4,1
Answer: D
Explanation:
The process of performing a rolling release upgrade in a Data Guard environment using a logical standby database generally involves these steps:
* Raise the compatibility level on both databases (1): Ensuring both the primary and logical standby databases are operating with the same and correct compatibility level is essential before starting the upgrade process.
* Upgrade the logical standby database (5): Apply the database upgrade to the logical standby first, which allows the primary database to continue serving the workload without interruption.
* Restart SQL Apply on the upgraded logical standby database (2): Once the logical standby has been upgraded, SQL Apply must be restarted to apply the redo data from the primary database, which is still running the earlier version.
* Perform a switchover to the logical standby database (4): After confirming that the logical standby database is successfully applying redo data, perform a switchover to make it the new primary database.
* Upgrade the old primary database (6): With the new primary database now in place, upgrade the old primary database (which is now the new standby) to the new Oracle Database release.
* Start SQL Apply on the old primary database (3): Finally, start SQL Apply on what is now the standby database to synchronize it with the new primary database.References:
* Oracle Data Guard Concepts and Administration Guide
* Oracle Database Upgrade Guide
NEW QUESTION # 37
Which TWO statements are true about configuring Oracle Net Service in a Data Guard environment?
- A. Enterprise Manager does not require static service registration to restart instances during the course of broker operations.
- B. A static service must be registered with the local listener to enable DGMGRL to restart instances during the course of broker operations.
- C. It is necessary to use the failover clause for an address_list with multiple address lists in the tnsnames.ora file.
- D. Installing the oracle-database-preinstall-19c package is NOT sufficient to set up operating system kernel parameters for Oracle Net.
- E. Install the oracle-database-preinstall-19c package to set the kernel parameters for Oracle Net based on the Data Guard best practice guidelines.
Answer: B,D
Explanation:
A static service must be registered with the local listener to enable DGMGRL to restart instances during the course of broker operations (A): For DGMGRL (Data Guard Manager Command-Line Interface) to perform instance management operations, such as restarting instances, a static service registration in the listener is required. This allows the broker to connect to the database instance even when the instance is not fully up and the dynamic service registration is not available.
Installing the oracle-database-preinstall-19c package is NOT sufficient to set up operating system kernel parameters for Oracle Net (C): While the oracle-database-preinstall-19c package automates the setting of several kernel parameters to meet the preinstallation requirements for Oracle Database, it does not specifically tailor all settings for Oracle Net in a Data Guard configuration. Additional manual configuration may be required to optimize Oracle Net services for Data Guard operations.
Reference:
Oracle Data Guard Broker documentation
Oracle Net Services Administrator's Guide
NEW QUESTION # 38
Which FOUR database parameters might be affected by or influence the creation of standby databases?
- A. ARCHIVE_LAG_TARGET
- B. FALSERVER
- C. STANDBY_ARCHIVE_DEST
- D. COMPATIBLE
- E. db_file_name_convert
- F. DB_NAME
Answer: C,D,E,F
Explanation:
* DB_NAME (A): The name of the database, which should remain consistent across the primary and standby databases.
* db_file_name_convert (C): This parameter helps define the mapping of data file names from the primary to the standby database, which is crucial during the creation and operation of a standby database.
* COMPATIBLE (D): The compatibility level can influence the features that can be used on the standby database and must be consistent with or higher than that of the primary database, especially after upgrades.
* STANDBY_ARCHIVE_DEST (F): This parameter specifies the destination of archived redo log files on the standby database, which is important for log transport and apply services.
References:
* Oracle Data Guard Concepts and Administration Guide
* Oracle Database Reference
NEW QUESTION # 39
Which THREE statements are true about snapshot standby databases?
- A. FLASHBACK DATABASE is enabled automatically on a snapshot standby database after converting it from a physical standby database if not already enabled.
- B. A snapshot standby database can have Real-Time apply enabled.
- C. A snapshot standby database may be opened read-write.
- D. A snapshot standby database may be opened read-only.
- E. FLASHBACK DATABASE must be manually enabled on a physical standby database before converting it into a snapshot standby database.
- F. FLASHBACK DATABASE is enabled automatically on a physical standby database as part of the conversion into a snapshot standby database, if not already enabled.
Answer: A,C,F
Explanation:
Snapshot standby databases are a feature of Oracle Data Guard that allows a physical standby database to be temporarily converted into a read-write database for testing or other purposes. The true statements about snapshot standby databases are:
FLASHBACK DATABASE is enabled automatically on a snapshot standby database after converting it from a physical standby database if not already enabled (B): When a physical standby is converted to a snapshot standby, FLASHBACK DATABASE is automatically enabled to allow the database to be easily reverted back to its original state.
FLASHBACK DATABASE is enabled automatically on a physical standby database as part of the conversion into a snapshot standby database, if not already enabled (C): As part of the conversion process, FLASHBACK DATABASE is turned on to ensure that changes made while the database is in snapshot standby mode can be undone.
A snapshot standby database may be opened read-write (E): Once a physical standby is converted to a snapshot standby, it can be opened for read-write operations, allowing for testing and other tasks that require a writable database.
Reference:
Oracle Data Guard Concepts and Administration
Oracle Database Backup and Recovery User's Guide
NEW QUESTION # 40
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. Creating a PDB from the existing PDB within the same CDB
- B. Performing transportable tablespaces
- C. Adding or dropping a redo file group
- D. Adding a data file or creating a tablespace
- E. Renaming a data file in the primary database
Answer: A,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 # 41
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, 2,3,4,6,7
- B. 2,3,5,6,7
- C. 1,3,5,6,7
- D. 1,2,3,4,5,6,7
- E. 2,3,6,7
Answer: A
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.
Reference:
Oracle Database Backup and Recovery User's Guide
Oracle Data Guard Concepts and Administration Guide
NEW QUESTION # 42
Active Data Guard (ADG) databases are widely used to offload reporting or ad hoc query-only jobs from the primary database. Reporting workload profile is different from the primary database and often requires tuning.
Which tool is used to tune SQL workloads running on an ADG database?
- A. Automatic Workload Repository (AWR)
- B. SQL Tuning Advisor
- C. In-Memory Active Session History (ASH)
- D. Automatic Diagnostic Database Monitor (ADDM)
- E. Standby Statspack
Answer: A
Explanation:
AWR collects, processes, and maintains performance statistics for problem detection and self-tuning purposes.
In an Active Data Guard environment, where the physical standby database can be used for read-only workloads, AWR can be instrumental in identifying performance bottlenecks and areas for optimization. It provides detailed reports that include wait events, time model statistics, and active session history, making it an invaluable tool for tuning SQL queries and overall database performance in an ADG setup.
NEW QUESTION # 43
......
Pass Oracle 1z0-076 Exam Quickly With Real4Prep: https://www.real4prep.com/1z0-076-exam.html
1z0-076 Dumps - The Sure Way To Pass Exam: https://drive.google.com/open?id=1VzPTxBFOhnFFRpS5nGdAij8i0aafWFEF