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.

Reference: 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.