[2024年09月01日]1z1-076試験ブレーン問題集で学習注釈と理論
合格させるOracle 1z1-076テスト練習テスト問題試験問題集
質問 # 22
On your logical standby database, you specified these rules:
After completion of the weekend batch cycle you attempt to delete the SQL Apply filters:
Which is TRUE regarding the execution of the UNSKIP procedure?
- A. It returns an error because the syntax to delete a SQL Apply filter must specify the same object names as specified when the filter was added.
- B. It succeeds but the SQL Apply filters are not deleted.
- C. It succeeds only if all DML statements executed on the primary have been applied on the logical standby deleting the SQL Apply filter.
- D. It deletes both the SQL Apply filters.
- E. It succeeds only if SQL apply is stopped before deleting the SQL Apply filter.
正解:D
解説:
The execution of the UNSKIP procedure is designed to remove SQL Apply filters that have been previously set up on a logical standby database. Based on the provided statements, the UNSKIP procedure is directed to delete any SQL Apply filters for DML statements associated with objects in the 'HR' schema that start with
'EMP'. Since both SKIP procedures had the same schema name ('HR') and statement type ('DML'), and the UNSKIP procedure uses a wildcard (%) for the object name, it will successfully remove both of the SQL Apply filters for 'EMP_NEW' and 'EMP_OLD', as both object names match the pattern provided in the UNSKIP procedure.
References:Oracle's Data Guard documentation and SQL Language Reference provide insights into managing SQL Apply filters on a logical standby database using the DBMS_LOGSTDBY package. This includes adding and removing filters through SKIP and UNSKIP procedures.
質問 # 23
Which TWO statements correctly describe the behavior of Automatic Block Media Recovery in a Data Guard environment, for a corrupt block in the example tablespace encountered by a session logged in as the SH user?
- A. A corrupt block on the primary database can be automatically recovered, using a block from a standby database with Real-Time Query enabled.
- B. A corrupt block on a standby database with Real-Time Query enabled, is automatically recovered, using flashback logs from the standby database.
- C. A corrupt block on the primary database is automatically recovered, using a block from a flashback log from the primary database.
- D. A corrupt block on the primary database is automatically recovered, using a block from a flashback log from a standby database with Real-Time Query enabled.
- E. A corrupt block on a standby database with Real-Time Query enabled, can be automatically recovered, using a block from the primary database.
正解:A、C
解説:
Automatic Block Media Recovery can be a significant feature for maintaining data integrity within a Data Guard configuration.
* A corrupt block on the primary database can be automatically recovered, using a block from a standby database with Real-Time Query enabled (A): When a corrupted block is encountered on the primary database, Oracle can automatically replace it with a good block from the standby database where Real-Time Query is enabled, leveraging the standby as a source of good data.
* A corrupt block on the primary database is automatically recovered, using a block from a flashback log from the primary database (E): If a good block version is available in the flashback logs of the primary database, Automatic Block Media Recovery can use it to recover the corrupted block on the primary.References:
* Oracle Database Backup and Recovery User's Guide
質問 # 24
Which TWO observations are true about the Far Sync instance?
- A. Receives redo synchronously from the primary database
- B. Includes a standby control file, password file, data files, standby redo logs, and archive logs
- C. Can only be created using a series of SQL commands
- D. Applies redo received
- E. Can be created using the RMAN DUPLICATE command
正解:A、D
解説:
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.
質問 # 25
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. Performing a role change with DGMGRL automatically notifies GDS which in turn activates the appropriate services.
- 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. DGMGRL may be used to add a single database to the Sales configuration even if Sales is a member of the Prod pool.
- E. Adding a database to the Sales configuration with DGMGRL automatically adds the database to the Prod Pool.
正解:A、B、D
解説:
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
質問 # 26
Which TWO are benefits of using Transaction Guard in a Data Guard environment?
- A. It provides application continuity by rolling back uncommitted transactions interrupted by a failover or switchover.
- B. It protects against user errors being replicated to standby databases.
- C. It protects against logical corruptions being replicated to standby databases.
- D. It provides application continuity by replaying transactions interrupted by a failover or a switchover
- E. It protects against recoverable errors during a planned or an unplanned outage of a primary database.
正解:A、E
解説:
Transaction Guard provides benefits in terms of transaction consistency and recovery in a Data Guard environment:
* It provides application continuity by rolling back uncommitted transactions interrupted by a failover or switchover (B): Transaction Guard ensures that any uncommitted transactions at the time of an outage are rolled back consistently, thus preserving the integrity of the application's data and state.
* It protects against recoverable errors during a planned or an unplanned outage of a primary database (D): Transaction Guard offers protection against errors that can occur during outages, allowing applications to resume operations more quickly and reliably after recovery.References:
* Oracle Database High Availability Overview
* Oracle Real Application Clusters Administration and Deployment Guide
質問 # 27
Which two statements are true when using non-rolling release upgrades in a Data Guard environment?
- A. During the upgrade of a logical standby database, standby redo log files must reside on O/S file systems.
- 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. Modifications to the data dictionary on the primary database caused by the upgrade, are applied on a physical standby database.
- E. 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.
正解:D、E
解説:
* 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.
References:
* Oracle Database Upgrade Guide
* Oracle Data Guard Concepts and Administration Guide
質問 # 28
Which three are prerequisites for enabling Fast-Start Failover?
- A. You can specify only one standby database as the fast-start failover target.
- B. Flashback Database must be enabled only on the Fast-Start Failover target standby database.
- C. The configuration must be operating in either Maximum Performance or Maximum Protection mode.
- D. The Data Guard environment must be managed by the Data Guard Broker.
- E. Flashback Database must be enabled on both the primary database and the Fast-Start Failover target standby database.
- F. The maximum protection mode can be used, but with two or more standby databases.
正解:A、D、E
解説:
To enable Fast-Start Failover in a Data Guard environment, the following conditions must be in place:
* The Data Guard environment must be managed by the Data Guard Broker (A): The Broker simplifies management tasks and is required to enable fast-start failover, which is an automatic failover mechanism provided by Data Guard.
* You can specify only one standby database as the fast-start failover target (C): Fast-start failover is designed to fail over to a single, predetermined standby database, known as the target standby.
* Flashback Database must be enabled on both the primary database and the Fast-Start Failover target standby database (F): Flashback Database provides a quick way to revert a database to a point
* in time before a logical or physical corruption or error occurred. It must be enabled on both the primary and target standby databases to allow for the possibility of reinstating the old primary as a standby after a failover.References:
* Oracle Data Guard Concepts and Administration Guide
* Oracle Database High Availability Overview
質問 # 29
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,3,6,1
- B. 4,6,5,2,3,1
- C. 5,2,4,1
- D. 5,2,4,6,3,1
- E. 1,5,2,4,6,3
正解:E
解説:
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
質問 # 30
In Oracle Database 19c, you can set the value of database initialization parameters in a database using the EDIT DATABASE... SET PARAMETER Command:
DGMGRL> EDIT DATABASE 'boston' SET PARAMETER log_archive_trace - 1;
Which THREE statements are TRUE about the command?
- A. The value set using this command is directly applied to the boston database.
- B. The EDIT DATABASE PARAMETER command can be used to set the value of a static parameter in a database.
- C. The edit database parameter command can only be used to modify the value of a dynamic parameter in a database.
- D. The value set using this command is directly stored in the broker configuration file.
- E. The database must be available when the above command is run.
正解:A、C、E
解説:
The EDIT DATABASE...SET PARAMETER command in Data Guard Management (DGMGRL) is used to modify the value of initialization parameters for a database within a Data Guard configuration. This command can be used to modify both static and dynamic parameters, but if a static parameter is changed, the new value will take effect only after the database is restarted. The database must be up and running for the command to execute, and the values set using the command are directly applied to the specified database (in this case,
'boston') .
質問 # 31
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. Enable Active Data Guard in the _ondon database.
- B. Set STANDBY_FILE_MANAGEMENT to auto in the london database.
- C. Open PDBI (remote clone source) in Read Write.
- D. Open PDBI (remote clone source) in Read Only.
- E. Set STANDBY_PDB_SOURCE_FILE_DIRECTORY to <location of the PDB> in the london database.
- F. Set standby_pdb_source_file_dblink to clone_link in the london database.
正解:B、D、E
解説:
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
質問 # 32
Examine the Data Guard configuration: DGMGRL> show configuration;
Configuration - Animals
Protection Mode: MaxPerformance
Databases:
dogs- Primary database
sheep - Physical standby database
cats- Snapshot standby database
Fast-Start Failover: DISABLED
Configuration Status: SUCCESS
You receive an error while attempting to raise the protection mode to Maximum Protection:
DGMGRL> edit configuration set protection mode as maxprotection;
Error: ORA-16627: operation disallowed since no standby databases would remain to support protection mode Failed.
What can you conclude based on this error?
- A. The redo transport mode is set to async for the standby database Sheep.
- B. Cats is a snapshot standby database.
- C. The redo transport mode is set to async for both standby databases.
- D. The redo transport mode is set to asyn: for the standby database Cats.
正解:B
解説:
The error indicates that switching the protection mode to Maximum Protection is not possible due to the presence of a snapshot standby database in the Data Guard configuration, which cannot participate in synchronous redo transport required by the Maximum Protection mode. Therefore, the correct answer is:
* D. Cats is a snapshot standby database.
Comprehensive Detailed Explanation:In an Oracle Data Guard environment, the Maximum Protection mode requires that all redo data be transmitted synchronously to at least one standby database, ensuring no data loss even in the event of a primary database failure. However, a snapshot standby database, by its nature, allows read-write access and is temporarily disconnected from the redo stream, which makes it unable to participate in the synchronous redo transport required by Maximum Protection mode. The presence of a snapshot standby database in the Data Guard configuration thus prevents the activation of Maximum Protection mode, as it cannot guarantee zero data loss without a standby database capable of receiving redo data synchronously.
References:Oracle Data Guard documentation clearly outlines the requirements and restrictions of different protection modes, including the necessity for standby databases to participate in synchronous redo transport to enable Maximum Protection mode. The inability of snapshot standby databases to fulfill this requirement is a key consideration when planning Data Guard configurations and protection levels.
質問 # 33
Which two are true about managing and monitoring Oracle container databases in a Data Guard environment using the broker?
- A. If the primary database is a container database, then a physical standby may be a non-container database.
- B. If the primary database is a container database, then a logical standby may be a non-container database.
- C. After a role change, the broker opens all Pluggable databases (pdbb) on the new primary.
- D. All broker actions execute at the root container for container databases.
- E. If the primary database is not a container database, then a standby may be a container database.
正解:C、D
解説:
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
質問 # 34
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 mounted.
- B. 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.
- C. It will execute successfully on an Oracle 19c physical standby database while Real Time Query is active.
- D. It will execute successfully on an Oracle 19c logical standby database while SQL apply 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. It will execute successfully while an Oracle 19c primary database is open.
正解:A、D、F
解説:
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. References:
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.
質問 # 35
Which THREE statements are TRUE about Global Sequences when connected to a physical standby database with Real-Time Query enabled?
- A. If the CACHE option is set then the size of the cache must be at least 100.
- B. They must have the NOORDEK and CACHE options set.
- C. Their usage may have a performance impact on the physical standby database if the CACHE size is too small.
- D. Their usage will always have a performance impact on the primary database.
- E. Their creation requires that a LOG archive_dest_n parameter be defined in the standby that points back to the primary.
正解:B、C、D
解説:
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.
質問 # 36
Which three types of backups offload ........ with the primary database in a data Guard
- A. Broker configuration files
- B. Archive logs
- C. Password files
- D. Control files
- E. Data files
- F. Online logs
正解:B、D、E
解説:
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.
質問 # 37
Your Data Guard environment has one physical standby database using Real-Time Query. Two sequences have been created by these SQL statements:
Neither sequence has been used since being created.
Session 1 connects to the primary database instance and issues these two SQL statements:
SELECT a.nextval FROM DUAL; SELECT b.nextval FROM DUAL;
Then session 2 connects to the physical standby database instance and issues the same SQL statements. Which output will be seen for session 2?
Then session 2 connects to the physical standby database instance and issues the same SQL statements. Which output will be seen for session 2?
- A.

- B.

- C.

- D.

正解:B
解説:
In Oracle, a sequence created with the GLOBAL keyword is available and can produce values across all sessions and instances. However, a sequence created with the SESSION keyword is only specific to the session it was created in. When the NEXTVAL is called for a sequence, it will increment according to the sequence's properties set during its creation.
Given the sequence creation statements and the actions performed:
* The a sequence is global, which means it is available across the entire database, including the standby database with Real-Time Query enabled. So, when session 2 calls a.nextval, it will get the next value in the sequence, which is 21 since session 1 already retrieved 1.
* The b sequence is session-specific, so when session 2 calls b.nextval, it will get the value 1 because for this new session on the standby, this is the first time the sequence is being accessed.
Therefore, the output for session 2 will be a output as 21 and b output as 1, which corresponds to Option C.
References: The behavior of global vs session-specific sequences is outlined in Oracle's SQL Language Reference under the CREATE SEQUENCE statement documentation.
質問 # 38
Which two are prerequisites for configuring flashback database for Oracle 19c databases, in a Data Guard environment?
- A. A far sync instance must be configured to flash back a standby when the primary has been flashed back.
- B. The database must be in ARCHTVELOG mode.
- C. The Data Guard real-time apply feature must be enabled.
- D. A fast recovery area must be configured.
- E. The data guard broker must be used.
正解:B、D
解説:
* A fast recovery area must be configured (B): Flashback Database requires a fast recovery area to be set up because flashback logs are stored there. The fast recovery area is a unified storage location for all recovery-related files and activities.
* The database must be in ARCHIVELOG mode (C): Flashback Database operation relies on the ability to archive redo logs. Therefore, the database must be running in ARCHIVELOG mode for Flashback Database to be enabled.
References:
* Oracle Database Backup and Recovery User's Guide
* Oracle Data Guard Concepts and Administration Guide
質問 # 39
Which four statements are true regarding SQL Apply filters for a logical standby database?
- A. They can be used to skip ALTE1 STEM and ALTER DATABASE commands.
- B. They can be used to skip all SQL statements executed on a specific pluggable database (PDB) within a standby multitenant container database (CDB).
- C. They can be used to skip CREATE TABLE commands.
- D. They can only be used to skip DML statements on a table.
- E. They can be used to skip execution of DML triggers on a table while allowing the DML to execute.
- F. They can be used to skip ALTER TABLE commands on specific tables.
- G. They can be used to stop SQL apply if it encounters an error.
正解:A、C、E、F
解説:
Based on the Oracle Database 19c documentation, the correct answers about SQL Apply filters for a logical standby database are:A. They can be used to skip execution of DML triggers on a table while allowing the DML to execute.B. They can be used to skip CREATE TABLE commands.C. They can be used to skip ALTER SYSTEM and ALTER DATABASE commands.G. They can be used to skip ALTER TABLE commands on specific tables.
Comprehensive Detailed Explanation:SQL Apply filters in a logical standby database can be set to control which SQL operations are applied to the standby. These filters allow for certain commands to be skipped, ensuring that they do not impact the standby database. For example, filters can be used to skip the execution of DML triggers to prevent them from firing during SQL Apply, while still allowing the underlying DML to be executed on the logical standby database. This is particularly useful when certain triggers are not desired to run in a standby environment. CREATE TABLE, ALTER SYSTEM, ALTER DATABASE, and specific ALTER TABLE commands can also be skipped using SQL Apply filters to prevent unwanted structural changes or administrative operations from affecting the logical standby database. These capabilities provide a level of control to ensure that the logical standby database reflects only the desired state of the primary database.
References:Oracle Database SQL Language Reference and Oracle Data Guard Concepts and Administration guide offer comprehensive details on the use of SQL Apply filters, including the range of SQL statements that can be influenced by these filters in a logical standby database environment.
質問 # 40
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, and 5
- B. 1, 2, 3, 4, 5, 6, and 7
- C. 1, 6, and 7
- D. 1, 2, 3, 6, and 7
- E. 1, 2, 6, and 7
正解:B
解説:
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.
ReferencesOracle 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.
質問 # 41
Which TWO statements are true about Real-Time Query?
- A. Real-Time Query has no limitations regarding the protection level of the Data Guard environment.
- B. Disabling Real-Time Query prevents the automatic start of redo apply when a physical standby databases opened read only.
- C. Real-Time Query sessions can be connected to a Far Sync instance.
- D. A standby database enabled for Real-Time Query cannot be the Fast-Start Failover target of the Data Guard configuration.
- E. Setting standby_max_data_delay=0 requires synchronous redo transport.
正解:B、E
解説:
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
質問 # 42
Examine this validate command:
DGMGRL> VALIDATE DATABASE VERBOSE "<database name>";
Which THREE statements are TRUE?
- A. The command performs a comprehensive set of database checks prior to a role change.
- B. The command can be used for a logical standby database.
- C. The command uses information available in various Oracle Data Guard views as well as the Automatic Diagnostic Repository.
- D. The command performs a comparison of SPFILE entries between the primary database and a specified standby database.
- E. The command performs network connectivity checks between members of a broker configuration.
正解:A、B、E
解説:
* The command performs a comprehensive set of database checks prior to a role change (A): The VALIDATE DATABASE command in Data Guard Manager (DGMGRL) is designed to perform an exhaustive check of a specified database's readiness for a role change, such as a switchover or failover.
* The command performs network connectivity checks between members of a broker configuration (C): One of the checks includes verifying that the necessary network connectivity exists between the databases in a Data Guard Broker configuration.
* The command can be used for a logical standby database (D): The VALIDATE DATABASE command is versatile and can be used for both physical and logical standby databases to ensure their readiness for role changes.
References:
* Oracle Data Guard Broker documentation
* Oracle Data Guard Concepts and Administration Guide
質問 # 43
Which THREE statements are true........ open in real time query mode, which becomes a new.
- A. User sessions can be retained.
- B. User sessions and Current Buffers are maintained by default.
- C. All current buffers can be retained.
- D. Sessions that have long running queries can be retained.
- E. All sessions are disconnected and all
- F. Sessions that are using database links
正解:A、C、E
解説:
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.
References
* Oracle Data Guard Concepts and Administration
* Oracle Database Licensing Information User Manual
* Oracle Data Guard Broker User Manual
質問 # 44
......
厳密検証された1z1-076問題集と解答で1z1-076問題集と正解付き:https://jp.fast2test.com/1z1-076-premium-file.html
ベストOracle Database 19c学習ガイド1z1-076試験:https://drive.google.com/open?id=1V1MzB_OmbC3f1TEK_KRQAbiSixhIVs7g