1z0-1105-23 Oracle Cloud Data Management 2023 Foundations Associate Questions and Answers

Oracle Database 19c is the final release supporting the non-CDB architecture. According to the Oracle documentation1, “Starting with Oracle Database 21c, non-CDB architecture is desupported. You must upgrade a non-CDB Oracle Database to a PDB on a CDB.” A CDB is a container database that can host multiple pluggable databases (PDBs) that share the same resources and memory.

ORDS stands for Oracle REST Data Services, which is a Java application that enables developers to access and manipulate data in Oracle Database using RESTful web services. According to the Oracle documentation2, “Oracle REST Data Services (ORDS) bridgesHTTPS and your Oracle Database. A mid-tier Java application, ORDS provides a Database Management REST API, SQL Developer Web, a PL/SQL Gateway, SODA for REST, and the ability to publish RESTful Web Services for interacting with the data and stored procedures in your Oracle Database.”

These are three options that can be selected when using the console to create an autonomous database on an Autonomous Exadata Cloud@Customer. According to the Oracle documentation1, “When you create an Autonomous Database on Autonomous Exadata Cloud@Customer, you specify the following information: Database name, Database display name, Workload type, Admin password, License type, Number of OCPUs, Storage (TB), and Tags (optional).” The workload type can be either transaction processing or data warehouse.

 Exadata Cloud Service and Autonomous Database are two target database environments that provide both high availability (HA) and disaster recovery (DR) options in the cloud. Exadata Cloud Service is a fully managed Oracle Database service that runs on Exadata infrastructure in the cloud. It offers high performance, scalability, availability, security, and reliability for all types of database workloads. It also supports various HA and DR options, such as Oracle Real Application Clusters (RAC), Oracle Data Guard, Oracle Active Data Guard, Oracle GoldenGate, and Oracle Zero Data Loss Recovery Appliance Cloud Service. Autonomous Database is a self-driving, self-securing, and self-repairing cloud database service that automates provisioning, configuring, securing, tuning, scaling, patching, backing up, and repairing of databases without human intervention. It also provides built-in HA and DR features based on Oracle Maximum Availability Architecture (MAA), such as transparent application continuity, automatic failover to standby databases or regions, automatic backups to object storage, point-in-time recovery using restore points or backups.

An Autonomous Database with the workload type Data Warehouse, Transaction Processing, JSON or APEX is a prerequisite of running APEX on an Autonomous Database. According to the Oracle documentation, “Oracle Application Express (APEX) is a low-code development platformthat enables you to build scalable, secure apps with world-class features that can be deployed anywhere. APEX is preconfigured and fully managed in Oracle Autonomous Database (ADB). You can use APEX on any Autonomous Database workload type: Data Warehouse (ADW), Transaction Processing (ATP), JSON (AJD), or APEX (APEX).”

Changing COMPATIBLE after upgrades is one of the scenarios when you should change COMPATIBLE. According to the Oracle blog post7, “COMPATIBLE needs to be adjusted only once after you completed your last database upgrade.” The blog post also explains that changing COMPATIBLE requires a restart of the database and that it should not be changed before upgrades or patching or after downgrades.

Loading data using FTP is not an option in Database Actions to load data into Autonomous Database. According to the Oracle documentation5, “On the Database Actions Data Load pageyou can choose to load data from a file on your local device, from cloud storage, or from a database. You can also choose to explore the data in your Oracle Autonomous Database.” There is no mention of FTP as a source for loading data.

Hadoop clusters cannot be run on Oracle Database 19c. Hadoop is a framework for distributed processing of large data sets across clusters of computers using simple programming models. Oracle Database 19c is a relational database management system that supports SQL and PL/SQL queries and transactions. Hadoop clusters require a different architecture and storage model than Oracle Database 19c. Oracle Database 19c does not support the Hadoop Distributed File System (HDFS) or the MapReduce programming model.

This statement is true about how the Converged Database helps to access data using an API. According to the Oracle documentation5, “Oracle REST Data Services (ORDS) makes it easy to develop modern REST interfaces for relational data in the Oracle Database and the Oracle Database 18c JSON Document Store. A mid-tier Java application, ORDS maps HTTP(S) verbs (GET, POST, PUT, DELETE, etc.) to database transactions and returns any results formatted using JSON.” ORDS can automatically generate RESTful services for tables and views in the database or expose custom REST APIs using SQL or PL/SQL.

This option is the correct way to increase the number of OCPU assigned to an Autonomous Database. According to the Oracle documentation2, “You can scale your Autonomous Database on demand by adding CPU cores or storage. You can also enable auto scaling to allow your Autonomous Database to automatically use up to three times more CPU and IO resources than its allocated CPU core count.” The scaling operation does not require any downtime or affect the availability of the database.

Signing key fingerprint, API signing key, and tenancy OCID are the information required to connect to the NoSQL Database Cloud Service. According to the Oracle documentation, “To connect your application to Oracle NoSQL Database Cloud Service , obtain your credentials such as the client ID, client secret, and the entitlement ID from the Identity Cloud Service console. After obtaining the credentials, pass the credentials to your application and create tables in Oracle NoSQL Database Cloud Service.” The client ID is also known as the signing key fingerprint, and the client secret is also known as the API signing key. The tenancy OCID is a unique identifier for your Oracle Cloud account.

Connect (1Gbps public peering) is not an Always Free resource available for provisioning in your tenancy. According to the Oracle documentation5, “All Oracle Cloud Infrastructure accounts (whether free or paid) have a set of resources that are free of charge for the life of the account.” The list of Always Free resources includes Infrastructure Certificates, Compute VMs, Block Volumes Storage, Object Storage, Resource Manager, OCI Bastions, Databases, NoSQL Database, Observability and Management tools, Flexible Load Balancer, Outbound Data Transfer, Virtual Cloud Networks (VCN), VCN Flow Logs, and Site-to-Site VPN. Connect (1Gbps public peering) is not among these resources.