[2024年08月]更新の1z1-076認定実際の問題を提供します [Q20-Q42]

[2024年08月]更新の1z1-076認定実際の問題を提供します

更新されたのは1z1-076問題集PDFで1z1-076リアル有効なブレーン問題集には72問があります！

質問 # 20
Which TWO are benefits of using Transaction Guard in a Data Guard environment?

• A. It protects against user errors being replicated to standby databases.
• B. It provides application continuity by replaying transactions interrupted by a failover or a switchover
• C. It protects against recoverable errors during a planned or an unplanned outage of a primary database.
• D. It protects against logical corruptions being replicated to standby databases.
• E. It provides application continuity by rolling back uncommitted transactions interrupted by a failover or switchover.

正解：C、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

質問 # 21
Examine this query and its output:

Which two statements are true?

• A. The master observer is not connected to the database on which the query was executed.
• B. The master observer is not running, but should run on ol7.example.com.
• C. The master observer is connected to the database on which the query was executed.
• D. Cats is a bystander database.
• E. The master observer is currently running on ol7.example.com.

正解：A、D

解説：
D: The database role indicated by FS_FAILOVER_STATUS as BYSTANDER implies that the database is a standby database in the Data Guard configuration. This means the database is neither a primary database nor an active failover target.
E: Since the FS_FAILOVER_OBSERVER_HOST column shows cats, it suggests that this is the host on which the observer would run. However, because the FS_FAILOVER_OBSERVER_PRESENT column is not shown, we cannot definitively state if the observer is currently connected or not. If FS_FAILOVER_OBSERVER_PRESENT is 'YES', the observer is connected, if 'NO', then it's not. In the absence of this column's output, the best assumption based on the available data is that the observer is not connected.
The output shows that the FS_FAILOVER_STATUS is BYSTANDER, which indicates that the database in question is not actively involved in a fast-start failover configuration as a primary or standby. It is in a bystander role, meaning that while it is part of a Data Guard configuration, it is neither a target for failover nor actively participating in failover operations. Additionally, FS_FAILOVER_OBSERVER_HOST shows
'cats', which indicates the host where the observer process is expected to run. However, since there is no information about the observer being present, we can infer that although 'cats' is designated for the observer to run, the observer is not currently connected to this database.
ReferencesOracle documentation on Data Guard configurations and the V$DATABASE view which provides information about the fast-start failover status and observer host.

質問 # 22
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 database must be available when the above command is run.
• C. The EDIT DATABASE PARAMETER command can be used to set the value of a static parameter in a database.
• D. The edit database parameter command can only be used to modify the value of a dynamic parameter in a database.
• E. The value set using this command is directly stored in the broker configuration file.

正解：A、B、D

解説：
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') .

質問 # 23
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 only task 5
• B. Execute tasks 1, 3, and 5
• C. Execute tasks 1, 2, 3, 4, and 5
• D. Execute tasks 1 and 5

正解：B

解説：
* 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.

質問 # 24
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. Configure Oracle Net connectivity on the primary host to the standby database instance.
• B. startup nomount the standby database instance.
• C. Set the DB_UNIQUE_NAME parameter on the primary database to a different value than that of the DB_NAME name parameter.
• D. Establish user equivalence for the database software owner between the primary host and standby host.
• E. Put the primary database into archivelog mode.

正解：A、B、D

解説：
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

質問 # 25
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,5,6,7
• B. 1,3,5,6,7
• C. 2,3,5,6,7
• D. 1, 2,3,4,6,7
• E. 2,3,6,7

正解：D

解説：
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

質問 # 26
Which four statements are true regarding SQL Apply filters for a logical standby database?

• A. They can only be used to skip DML statements on a table.
• 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 execution of DML triggers on a table while allowing the DML to execute.
• D. They can be used to stop SQL apply if it encounters an error.
• E. They can be used to skip ALTER TABLE commands on specific tables.
• F. They can be used to skip CREATE TABLE commands.
• G. They can be used to skip ALTE1 STEM and ALTER DATABASE commands.

正解：C、E、F、G

解説：
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.

質問 # 27
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. Modifications to the data dictionary on the primary database caused by the upgrade, are applied on a physical standby database.
• E. During the upgrade of a logical standby database, standby redo log files must reside on O/S file systems.

正解：A、D

解説：
* 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
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

質問 # 29
Which three statements are true about snapshot standby databases?

• A. The switchover TO command allows a switchover operation to a snapshot standby database.
• B. A logical standby database can be converted into a snapshot standby database.
• C. The FATLOVER TO command results in a transition of a snapshot standby database to the primary role.
• D. Tables can be dropped.
• E. Tablespaces can be dropped.
• F. Tablespaces can be created.

正解：D、E、F

解説：
A snapshot standby database is a fully updateable standby database that is created by converting a physical standby database into a snapshot standby database. The main characteristics of a snapshot standby database include:
* B: Tablespaces can indeed be dropped in a snapshot standby database because it is updateable and allows all types of DML and DDL operations that do not conflict with the standby role.
* C: Tablespaces can be created in a snapshot standby database for the same reasons that they can be
* dropped; it supports all operations that do not interfere with its standby nature.
* E: Tables can be dropped in a snapshot standby database, as it is a fully updateable standby.
Options A and D are incorrect because 'FAILOVER TO' and 'SWITCHOVER TO' commands are not used with snapshot standby databases in these contexts. A failover converts a standby database into the primary role after the original primary has become unavailable, and is not a reversible role transition. Switchover is a planned role reversal between the primary database and one of its standby databases and is not applicable to snapshot standby databases in the context provided.
Option F is incorrect because a logical standby database cannot be converted into a snapshot standby database directly. A logical standby is used for different purposes such as reporting and querying with real-time data, and its structure is different from a physical standby which can be converted into a snapshot standby.
References: Oracle Data Guard Concepts and Administration guide details the operations allowed on snapshot standby databases and the processes for transitioning between physical, snapshot, and logical standby databases.

質問 # 30
Your Data Guard environment has a remote physical standby database with real-time query enabled, which is used for reporting, and a logical standby database used for DSS reporting.
Switchovers or failovers are possible due to testing or in case of a disaster.
Clients use local TNSNAMES.ORA files to define connection strings to the database instances.
Which three will prevent clients from connecting to the wrong database instances?

• A. The client applications must use the correct TNS entries when requesting connections to the database instances.
• B. Client TNS entries for the databases use the correct service names for the intended service.
• C. Oracle Net connectivity to the primary database instance must be established on all the standby database instances.
• D. A service name is registered with the local listener of each database instance.
• E. The standby database services must be defined statically with the Listeners running on the standby database hosts.
• F. The DB_NAME and DB_UNIQUE_NAME parameters must be set to the same value for all the databases in the Data Guard environment.
• G. The LOCAL_LISTENER parameter on the primary database instance must always be set.

正解：A、B、E

解説：
Based on Oracle Database 19c: Data Guard Administration documents, the three measures that can prevent clients from connecting to the wrong database instances during switchovers, failovers, or regular operations in a Data Guard environment are:
* B. The standby database services must be defined statically with the Listeners running on the standby database hosts.
* D. The client applications must use the correct TNS entries when requesting connections to the database instances.
* E. Client TNS entries for the databases use the correct service names for the intended service.
* In an Oracle Data Guard configuration, correctly configuring Oracle Net Services (including TNS entries and listeners) is crucial for ensuring that clients connect to the appropriate database instance, whether it's the primary or standby. Defining services on the standby database and associating them with listeners ensures that client applications can connect to the standby when needed, especially useful in a role transition or when the standby is open for read-only access or real-time query. It's essential that TNS entries used by client applications specify the correct service names that correspond to the intended
* database roles, such as primary or standby. This setup facilitates seamless connectivity to the appropriate instance based on the role, especially critical during switchovers and failovers when the roles of the databases change.
* References:Oracle's Data Guard concepts and administration guide provides extensive information on configuring network services for Data Guard environments, ensuring that applications connect to the correct database instance based on the current role of the databases in the Data Guard configuration.

質問 # 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. Open PDBI (remote clone source) in Read Only.
• B. Set STANDBY_PDB_SOURCE_FILE_DIRECTORY to <location of the PDB> in the london database.
• C. Set STANDBY_FILE_MANAGEMENT to auto in the london database.
• D. Set standby_pdb_source_file_dblink to clone_link in the london database.
• E. Open PDBI (remote clone source) in Read Write.
• F. Enable Active Data Guard in the _ondon database.

正解：A、B、C

解説：
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
Which THREE statements are true about snapshot standby databases?

• A. FLASHBACK DATABASE must be manually enabled on a physical standby database before converting it into a snapshot standby database.
• B. A snapshot standby database may be opened read-only.
• C. A snapshot standby database can have Real-Time apply enabled.
• D. FLASHBACK DATABASE is enabled automatically on a snapshot standby database after converting it from a physical standby database if not already enabled.
• E. FLASHBACK DATABASE is enabled automatically on a physical standby database as part of the conversion into a snapshot standby database, if not already enabled.
• F. A snapshot standby database may be opened read-write.

正解：D、E、F

解説：
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.
References:
* Oracle Data Guard Concepts and Administration
* Oracle Database Backup and Recovery User's Guide

質問 # 33
Which two statements are true regarding asynchronous redo transport in a Data Guard

• A. The performance of SQL apply on a logical standby database always improves when using this transport mode.
• B. This transport mode satisfies the minimum requirements for Maximum Availability data protection mode.
• C. Real-time query performance on a physical standby database improves for current read requests when using this transport mode.
• D. A transaction can commit without waiting for redo to be sent to any standby database in the data guard configuration.
• E. This transport mode satisfies the minimum requirements for Maximum Performance data protection mode.

正解：D、E

解説：
Asynchronous redo transport is a method where the primary database does not wait for an acknowledgment from the standby database before committing transactions, which helps in minimizing the impact on the primary database's performance (B). This transport mode is associated with the Maximum Performance data protection mode, which prioritizes performance over synchronicity of data between the primary and standby databases (C). While it provides a level of data protection, there could be some data loss in the event of a primary database failure because redo data may not have been transmitted to the standby database at the time of the failure.
References:Oracle Data Guard Concepts and Administration documentation provides detailed explanations of different redo transport modes and their implications on data protection and performance. Asynchronous transport mode's behavior and association with Maximum Performance mode are outlined explicitly.

質問 # 34
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. All broker actions execute at the root container for container databases.
• D. After a role change, the broker opens all Pluggable databases (pdbb) on the new primary.
• 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

質問 # 35
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. It is necessary to use the failover clause for an address_list with multiple address lists in the tnsnames.ora file.
• C. Install the oracle-database-preinstall-19c package to set the kernel parameters for Oracle Net based on the Data Guard best practice guidelines.
• D. A static service must be registered with the local listener to enable DGMGRL to restart instances during the course of broker operations.
• E. Installing the oracle-database-preinstall-19c package is NOT sufficient to set up operating system kernel parameters for Oracle Net.

正解：D、E

解説：
* 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.
References:
* Oracle Data Guard Broker documentation
* Oracle Net Services Administrator's Guide

質問 # 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. 4,6,5,2,3,1
• B. 5,2,4,3,6,1
• C. 5,2,4,1
• D. 1,5,2,4,6,3
• E. 5,2,4,6,3,1

正解：D

解説：
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

質問 # 37
Which four requirements can be met by deploying a logical standby database?

• A. Support for workloads requiring additional indexes.
• B. It must provide a disaster-recovery solution that protects all data with capability of performing switchovers and failovers.
• C. Support for workloads requiring additional materialized views.
• D. It can be used to create additional schemas.
• E. It must have the same physical structure as the primary database.
• F. It can be used for Real Application Testing without affecting the disaster recovery capabilities.
• G. It can be used to create additional tables.

正解：A、C、F、G

解説：
A logical standby database is part of Oracle Data Guard and allows the standby database to be open for read-write operations, providing additional flexibility. The requirements met by a logical standby database include:
* Support for workloads requiring additional materialized views (A): Logical standby databases can support materialized views, allowing for complex data summarization and reporting workloads.
* It can be used to create additional tables (C): Unlike physical standby databases, logical standby databases allow for the creation of additional tables that do not exist in the primary database, enabling custom workloads and reporting.
* It can be used for Real Application Testing without affecting the disaster recovery capabilities (E):
Logical standby databases can be used to test application changes, patches, and upgrades while still maintaining their role as part of the disaster recovery strategy.
* Support for workloads requiring additional indexes (F): Logical standby databases allow for the creation of additional indexes to optimize query performance for reporting and analytical workloads.
References:
* Oracle Data Guard Concepts and Administration
* Oracle Database High Availability Overview

質問 # 38
Your Data Guard configuration consists of these components and settings:
1. A primary database
2. A remote physical standby database
3. Real-time query is enabled
4. Redo transport mode is synchronous
5. Protection mode is maximum availability
6. The Data Guard broker is used
You notice that the standby destination fails to acknowledge reception of redo within net_timeout period of time.
Which is true in this scenario?

• A. The protection mode will automatically change to Maximum Performance.
• B. The physical standby database instance is shut down by the Data Guard broker.
• C. Synchronous redo transport mode connections to the standby database are terminated.
• D. Real-time query will be disabled on the physical standby.

正解：C

解説：
In a Data Guard configuration where the protection mode is set to Maximum Availability and synchronous redo transport is enabled, if the standby destination fails to acknowledge the reception of redo within the net_timeout period, the primary database will terminate the synchronous redo transport mode connections to the standby database to protect the primary database from hanging (C). The primary database then operates in a Maximum Performance mode until the issue is resolved. This behavior ensures that the primary database can continue to process transactions even when the standby database is temporarily unavailable.
References:The Oracle Data Guard Broker documentation and Oracle Data Guard Concepts and Administration guide detail the behavior of different protection modes and the response to network timeouts, including the fallback to asynchronous redo transport to maintain primary database availability.

質問 # 39
Examine the fast-start failover configuration:

• A. A failover may occur if the observer has lost connectivity to the primary database, even if the Fast-Start Failover target standby database has a good connection to the primary database
• B. If South_Sales develops a problem and cannot be the target of a failover, the broker automatically changes the fast-start failover target to one of the other candidate targets.
• C. You must disable fast-start failover first to change the fast-start failover target to East sales.
• D. The observer will initiate a failover when the primary database is unable to produce local archived redo log files.
• E. The observer is running.

正解：A、D、E

質問 # 40
Which THREE statements are TRUE about the supported workload in Active Data Guard standby databases?

• A. Read-mostly reporting applications that use global temporary tables for storing temporary data can be offloaded.
• B. You might have to use sequences with global temporary tables to support read-mostly applications by using Active Data Guard.
• C. The DML operations on a standby can be transparently redirected to and run on the primary database
• 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. The DDL operations on private temporary tables are transparently redirected to the primary database.

正解：A、B、C

解説：
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.

質問 # 41
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 increased number of bulk inserts on the primary
• B. An undersized undo tablespace on the logical standby
• C. The standby redo log files are undersized on the primary database
• D. Many SQL apply operations do full table scans
• E. An undersized shared pool
• F. An increased number of bulk updates on the primary

正解：B、D、E、F

解説：
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.

質問 # 42
......

あなたをお手軽に1z1-076試験合格させるし100%試験合格保証：https://www.goshiken.com/Oracle/1z1-076-mondaishu.html

100%無料1z1-076試験問題集実際問題を使おうOracle Database 19c問題集：https://drive.google.com/open?id=1Re_Pt3QVkyVLfo8A_IwKHWI0Sc0I75O4