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

Oracle Native Network Encryption and TDE are security measures that are implemented out-of-the-box, and are included if you are not using BYOL licensing with Exadata Cloud@Customer. According to the Oracle documentation5, “Oracle Native Network Encryption encrypts all data sent over the network between database clients and servers using industry-standard encryption algorithms.” Additionally, according to the Oracle documentation6, “Transparent Data Encryption (TDE) enables you to encrypt sensitive data, such as credit card numbers, stored in tables and tablespaces.”

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).”

Graph, relational, and spatial are three typical data types/models that are covered by Oracle’s Converged Database. A converged database is a multi-model, multitenant, multi-workload database that supports the data model and access method each development team wants, without unneeded functionality getting in the way. A graph data model represents data as nodes and edges, and enables complex queries based on relationships and patterns. A relational data model organizes data into tables with rows and columns, and supports SQL queries and transactions. A spatial data model stores and manipulates geometric and geographic data, such as points, lines, polygons, and raster images.

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.

Regulations that prevent moving data into the public cloud and putting data in the cloud would break data residency rules are two typical reasons why customers cannot move their database into the public cloud. Some organizations may have legal, compliance, or business policy requirements that restrict where their data can be stored or processed. For example, some regulations may require that data be stored within a certain country or region, or that data be encrypted or anonymized before being transferred to the cloud. Moving data to the public cloud may violate these regulations or introduce additional risks or costs for the customers.

Security and support compliance are two important reasons to upgrade and patch your Oracle Database. According to the Oracle blog3, “Security is one of the most important reasons to patch your database. Every quarter Oracle releases security patches as part of the Critical Patch Update (CPU) program. These patches fix vulnerabilities in the database software that could be exploited by malicious attackers.” Additionally, according to the Oracle blog4, “Support compliance is another reason to patch your database. Oracle provides different levels of support for different versions of the database software. To be eligible for certain support services, such as Extended Support or Sustaining Support, you need to apply the latest patches available for your version.”

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.

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.

Object Storage (standard) is the OCI storage service that can be used to store application backups which can be stored for months, but retrieved immediately based on business needs. According to the Oracle documentation1, “Object Storage is a highly scalable, durable, and available cloud-based storage service that provides a cost-effective way to store and manage large amounts of unstructured data such as images, videos, and log files. Object Storage supports standard HTTP operations such as GET, PUT, and DELETE, as well as advanced features such as encryption, data replication, lifecycle policies, and pre-authenticated requests.” Object Storage (standard) offers high performance and low latency for frequent data access.

SODA (Simple Oracle Document Access) is the set of NoSQL-style APIs that can be used in Autonomous JSON Database. According to the Oracle documentation, “SODA provides a set of APIs for various application-development languages and for RESTful web services that let you create and store collections of JSON documents in an Oracle Database without needing any knowledge of SQL or how the data is stored in the database.”

These are two benefits that the partnership and interconnect between Oracle Cloud and Microsoft Azure provide. According to the Oracle website1, the partnership enables the following benefits:

• A secure intercloud connection that bypasses the public internet
• High availability and reliability through redundant 10-Gbps physical connections
• Predictable cross-cloud network performance
• One time setup without the need for any intermediate network provider
• Unified identity and access management platform that leads to cost savings

The unified identity and access management platform allows customers to use a single identity provider to access resources in both clouds, simplifying the authentication and authorization process. The low latency is achieved by the direct interconnection between the two clouds, which provides less than two seconds of latency for superior multicloud network performance2.

Customers are responsible for managing databases and customer VMs when they are using the Exadata Cloud Service. According to the Oracle documentation7, “Customers have full control over their databases running on Exadata Cloud Service, including root access for database servers.” Additionally, according to the Oracle documentation8, “Customers can create customer VMs on Exadata Cloud Service database servers for their own use.”

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.

Focuses on creation of indexes and optimized for response time are two characteristics of Autonomous Transaction Processing (ATP). According to the Oracle documentation,“Autonomous Transaction Processing is a database service that is optimized for transaction processing or mixed workloads. It delivers the best experience for mission-critical applications that require high performance, high concurrency, and low latency. Autonomous Transaction Processing automatically creates indexes, materialized views, and partitions based on the workload.” Additionally, according to the Oracle documentation, “Autonomous Transaction Processing is optimized for response time. It uses a combination of caching, in-memory columnar format, and result set caching to deliver fast response times.”