Autonomous Data Guard enhances high availability for Autonomous Database. The two true statements are:
RPO is 0 minutes for an automatic failover (C): Recovery Point Objective (RPO) measures potential data loss. With Autonomous Data Guard, the standby database is synchronously replicated with the primary, ensuring zero data loss (RPO = 0) during an automatic failover, as all transactions are mirrored in real-time.
RTO is 2 minutes for an automatic failover (E): Recovery Time Objective (RTO) measures downtime during failover. For Autonomous Data Guard, Oracle specifies an RTO of approximately 2 minutes for automatic failovers, reflecting the time to detect failure and promote the standby to primary.
The incorrect options are:
RTO and RPO are adjustable through the OCI console (A): RTO and RPO are fixed by the Autonomous Data Guard architecture and cannot be manually adjusted via the OCI console.
RPO is adjustable, but RTO is always 5 minutes (B): RPO is not adjustable (it's 0 due to synchronous replication), and RTO is not fixed at 5 minutes; it's typically 2 minutes for automatic failover.
RTO and RPO are 0 minutes for manual failovers (D): Manual failovers (switchovers) have an RTO greater than 0 (typically a few minutes) due to manual initiation, though RPO remains 0 with synchronous replication.
These values ensure minimal disruption and data loss.

DBMS_CLOUD.COPY_DATA loads data into Autonomous Database:
Correct Answer (B): "The source files can reside in Oracle Object Storage, Amazon S3 Object Storage, or Azure Blob Storage" is true. The procedure supports these cloud storage services with proper credentials.
Correct Answer (E): "A valid credential must be created prior to running the DBMS_CLOUD.COPY_DATA procedure" is true. Credentials (e.g., via DBMS_CLOUD.CREATE_CREDENTIAL) authenticate access to the source storage.
Incorrect Options:
A: Source files are not automatically removed; deletion requires separate action.
C: The target table must exist; COPY_DATA doesn't create it.
D: Archive Storage isn't supported; only Standard Storage is compatible.
This enables flexible data loading from cloud storage.

Full Detailed In-Depth Explanation:
The Oracle Autonomous JSON Database is a specialized service for managing JSON data with NoSQL-style capabilities. Let's evaluate each statement:
A . It supports NoSQL-style, document-centric applications: True. Autonomous JSON Database is designed for NoSQL workloads, supporting document-based applications via APIs like SODA (Simple Oracle Document Access).
B . There is a 20 GB limit on JSON collection: False. The Oracle documentation does not specify a fixed 20 GB limit on JSON collections. Storage capacity is determined by the overall database size, which can scale dynamically without a specific cap on individual collections. This makes B the false statement.
C . JSON data is stored natively in the database: True. JSON data is stored in a binary format optimized for performance, avoiding the need for parsing or transformation during access.
D . You can promote Autonomous JSON Database to Autonomous Transaction Processing: True. Oracle allows promoting an Autonomous JSON Database to ATP, enabling relational capabilities if application needs evolve.
The false claim about a 20 GB limit likely stems from confusion with other database constraints, but no such restriction exists for JSON collections in Autonomous JSON Database.

Enabling auto scaling on an existing Autonomous Database can be done without unnecessary complexity:
Correct Answer (A): "Click Scale Up/Down and select the Auto Scaling checkbox" is the simplest GUI method. In the OCI Console, navigate to the database, select "Scale Up/Down," and enable the auto scaling option, allowing up to 3x the base OCPUs dynamically.
Correct Answer (C): "Use a REST call to enable Auto Scaling" leverages the OCI REST API to update the database configuration with the isAutoScalingEnabled parameter set to true. This is ideal for programmatic control.
Incorrect Options:
B: Shutting down the instance is unnecessary; auto scaling can be enabled while the database is running.
D: Multiple REST calls, including shutdown and restart, overcomplicate the process when a single API call suffices.
These methods ensure minimal disruption and efficient resource management.

Oracle Autonomous Database Shared Infrastructure offers built-in security features to protect data and ensure compliance. The three correct features are:
Customer Managed Keys (A): This feature allows customers to use their own encryption keys for Transparent Data Encryption (TDE), stored in Oracle Key Vault or OCI Vault. It gives control over key management, enhancing security by ensuring only the customer can decrypt data. For example, a company might generate a key in OCI Vault, link it to their ADB, and rotate it periodically, all managed outside Oracle's default keys.
Database Vault (D): Oracle Database Vault enforces fine-grained access controls, preventing unauthorized access to sensitive data even by privileged users (e.g., DBAs). In ADB shared infrastructure, it's available to restrict operations like SELECT on specific schemas, adding a layer of protection against internal threats. For instance, it could block an admin from viewing customer PII unless explicitly permitted.
Transparent Data Encryption (E): TDE is enabled by default in Autonomous Database, encrypting data at rest (e.g., in tablespaces, backups, and logs) using AES-256. This ensures that if physical storage is compromised, the data remains unreadable without the encryption key. Customers can opt for customer-managed keys (A) or use Oracle-managed keys, but TDE itself is always active.
The incorrect options are:
Audit Vault (B): Oracle Audit Vault is a separate product for centralized audit log management, not a built-in feature of ADB shared infrastructure. While ADB performs auditing, it doesn't include Audit Vault's advanced capabilities natively.
Data Redaction (C): Data Redaction (masking sensitive data in query results) is available in on-premises Oracle Database Enterprise Edition but is not supported in Autonomous Database shared infrastructure. ADB's managed nature limits such custom configurations, relying instead on TDE and Database Vault for security.
These features collectively ensure robust security with minimal customer effort in a shared environment.