Oracle 1z0-1085-23 Oracle Cloud Infrastructure 2023 Foundations Associate Exam Practice Test

The MySQL Database Service HeatWave Configuration in OCI is a distributed in-memory query accelerator that enables customers to run analytics queries on their MySQL databases up to 400 times faster than without HeatWave. It also eliminates the need to move data to a separate analytics database5

A fault domain is a grouping of hardware and infrastructure within an availability domain. Each availability domain contains three fault domains. Fault domains provide anti-affinity: they let you distribute your instances so that the instances are not on the same physical hardware within a single availability domain. A hardware failure or Compute hardware maintenance event that affects one fault domain does not affect instances in other fault domains. In addition, the physical hardware in a fault domain has independent and redundant power supplies, which prevents a failure in the power supply hardware within one fault domain from affecting other fault domains.

Usually fault domains to do the following things:

1) Protect against unexpected hardware failures or power supply failures.

2) Protect against planned outages because of Compute hardware maintenance.

Cloud Horizontal Scaling refers to provisioning additional servers to meet your needs, often splitting workloads between servers to limit the number of requests any individual server is getting. In a cloud-based environment, this would mean adding additional instances instead of moving to a larger instance size.

Cloud Vertical Scaling refers to adding more CPU or memory to an existing server, or replacing one server with a more powerful server.

Low performance is not a performance level available in the Oracle Cloud Infrastructure Block Volume service. The Block Volume service offers four performance levels for block volumes: higher performance, balanced, lower cost, and ultra high performance. Each performance level has different characteristics in terms of throughput, IOPS, latency, and cost.

Round robin is a type of load balancing policy supported by Oracle Cloud Infrastructure Load Balancer. Round robin distributes incoming traffic evenly across all healthy backend servers in a backend set. Round robin ensures that each server receives an equal number of requests over time.

Compartments do not provide a way to store and manage encryption keys and secrets in Oracle Cloud Infrastructure. Compartments are logical containers that help users organize and isolate their cloud resources. Compartments can be nested to create a hierarchy that reflects the structure of an organization or project. To store and manage encryption keys and secrets, users can use the Oracle Cloud Infrastructure Vault service, which is a fully managed service that provides centralized management of encryption keys, secrets, and certificates.

OCI leverages advanced encryption that leads to fast performance, OCI does not over subscribe CPU, but only memory, and OCI hypervisor provides industry leading performance are WRONG.

However, OCI does back claims with SLAs and offers predictable pricing for all services.

The cost of running a virtual machine instance in Oracle Cloud Infrastructure depends on several factors, such as the size, shape, region, and operating system of the instance. The number of virtual machines running does not impact the cost of each individual instance1

Oracle Cloud Infrastructure File Storage service provides a durable, scalable, secure, enterprise-grade network file system. You can connect to a File Storage service file system from any bare metal, virtual machine, or container instance in your Virtual Cloud Network (VCN).

You can control the access of the file system from FSS by applying some security rules and others but the services it self not related to security but it related to shared storage

You can think of a Dynamic Routing Gateway (DRG) as a virtual router that provides a path for private traffic (that is, traffic that uses private IPv4 addresses) between your VCN and networks outside the VCN's region.

For example, if you use an IPSec VPN or Oracle Cloud Infrastructure FastConnect (or both) to connect your on-premises network to your VCN, that private IPv4 address traffic goes through a DRG that you create and attach to your VCN. For scenarios for using a DRG to connect a VCN to your on-premises network, see Networking Scenarios. For important details about routing to your on-premises network, see Routing Details for Connections to Your On-Premises Network.

Also, if you decide to peer your VCN with a VCN in another region, your VCN's DRG routes traffic to the other VCN over a private backbone that connects the regions (without traffic traversing the internet). For information about connecting VCNs in different regions, see Remote VCN Peering (Across Regions).

OCI logs are encrypted in three ways: in-flight, disk-level, and archive. OCI logs are encrypted in-flight, that is, while they are in the process of being ingested into OCI Logging; after the logs are in the system, they are encrypted with disk-level encryption for commercial environments; and logs are also encrypted when they are archived, and while in storage

You can filter Costs Analysis Tools by following three ways

To filter costs by dates

To filter costs by tags

To filter costs by compartments

VCN peering is the process of connecting multiple virtual cloud networks (VCNs) so that their resources can communicate using private IP addresses. There are four types of VCN peering: 1

• Local VCN peering: This is the process of connecting two VCNs in the same region and tenancy. This type of peering uses local peering gateways (LPGs) in each VCN to establish a logical connection.
• Remote VCN peering: This is the process of connecting two VCNs in different regions, either in the same tenancy or different tenancies. This type of peering uses remote peering gateways (RPGs) in each VCN to establish a logical connection.
• Peering VCNs in the same region through a dynamic routing gateway (DRG): This is the process of connecting multiple VCNs in the same region and tenancy by attaching them to a common DRG. A DRG is a virtual router that provides a path for private network traffic between your VCN and other networks.
• Peering VCNs in different regions through a DRG: This is the process of connecting multiple VCNs in different regions and tenancies by attaching them to a common DRG and using IPSec VPN or FastConnect to connect the DRGs across regions.

Peered VCNs cannot have overlapping CIDRs, as this would cause routing conflicts and ambiguity. Peered VCNs need to have unique CIDRs that do not overlap with each other or with any other network that they need to communicate with1

A VCN peering connection is not a VPN-based connection. A VPN-based connection is a secure and encrypted connection between your on-premises network and your OCI VCN over the public internet by using IPSec VPN or FastConnect. A VPN-based connection requires an internet gateway or a DRG in your VCN and a customer-premises equipment (CPE) device in your on-premises network2

Peered VCNs do not need to be part of the same OCI tenancy, as long as they are in different regions. Remote VCN peering supports cross-tenancy connections, meaning that you can peer a VCN in one tenancy with a VCN in another tenancy, as long as they are subscribed to the same regions and have proper IAM policies to allow peering. Local VCN peering and peering through a DRG only support intra-tenancy connections, meaning that you can only peer VCNs within the same tenancy1

The primary use case for using Web Application Firewall (WAF) in OCI is to filter malicious web traffic and protect internet-facing and internal applications from attacks. WAF is a cloud-based, PCI-compliant, global web application firewall service that monitors and controls access to web applications based on predefined rules and threat intelligence. WAF can block common web application attacks such as cross-site scripting (XSS), SQL injection, remote file inclusion, etc., as well as bot traffic, geographic restrictions, rate limiting, etc. WAF can protect any internet-facing endpoint or internal application by attaching WAF policies to enforcement points such as load balancers or web application domain names10

Oracle Functions is a fully managed, multi-tenant, highly scalable, on-demand, Functions-as-a-Service platform. It is built on enterprise-grade Oracle Cloud Infrastructure and powered by the Fn Project open source engine. Use Oracle Functions (sometimes abbreviated to just Functions) when you want to focus on writing code to meet business needs.

The serverless and elastic architecture of Oracle Functions means there's no infrastructure administration or software administration for you to perform. You don't provision or maintain compute instances, and operating system software patches and upgrades are applied automatically. Oracle Functions simply ensures your app is highly-available, scalable, secure, and monitored. With Oracle Functions, you can write code in Java, Python, Node, Go, and Ruby (and for advanced use cases, bring your own Dockerfile, and Graal VM). You can then deploy your code, call it directly or trigger it in response to events, and get billed only for the resources consumed during the execution.

Oracle Functions is based on Fn Project. Fn Project is an open source, container native, serverless platform that can be run anywhere - any cloud or on-premises. Fn Project is easy to use, extensible, and performant. You can download and install the open source distribution of Fn Project, develop and test a function locally, and then use the same tooling to deploy that function to Oracle Functions.

You can access Oracle Functions using the Console, a CLI, and a REST API. You can invoke the functions you deploy to Oracle Functions using the CLI or by making signed HTTP requests.

Visual Logs is not a valid log type supported by the Oracle Cloud Infrastructure (OCI) Logging service. The Logging service supports three kinds of logs: Audit logs, Service logs, and Custom logs5

• Audit logs are logs related to events emitted by the OCI Audit service, such as API calls or console actions performed by users or services in your tenancy. Audit logs are automatically enabled and available for viewing or searching in the Logging service5
• Service logs are logs emitted by OCI native services, such as API Gateway, Events, Functions, Load Balancer, Object Storage, and VCN Flow Logs. Each of these supported services has predefined logging categories that you can enable or disable on your respective resources. For example, you can enable read and write access events for Object Storage buckets, or ingress and egress traffic for VCN subnets5
• Custom logs are logs that contain diagnostic information from custom applications, other cloud providers, or an on-premises environment. Custom logs can be ingested through the API, or by configuring the Unified Monitoring Agent. For example, you can send logs from Apache web servers, Oracle databases, or Kubernetes clusters to the Logging service for analysis and monitoring5

Monitoring is the Oracle Cloud Infrastructure (OCI) service that can be configured to send you an alert for high CPU usage. Monitoring service collects metrics from various OCI resources and allows you to create alarms based on performance thresholds or anomalies. You can use Monitoring service to monitor the CPU utilization of your compute instances, databases, functions, load balancers, and other resources that emit metrics to Monitoring service6

Network File System (NFS) is the file protocol that Oracle Cloud Infrastructure File Storage Service uses to enable file sharing across instances. NFS is a distributed file system protocol that allows a user on a client computer to access files over a network in a manner similar to how local storage is accessed. The File Storage service supports the NFS version 3.0 protocol with Network Lock Manager (NLM) for file locking functionality2.

Oracle Cloud Infrastructure Container Engine for Kubernetes is a fully-managed, scalable, and highly available service that you can use to deploy your containerized applications to the cloud. Use Container Engine for Kubernetes (sometimes abbreviated to just OKE) when your development team wants to reliably build, deploy, and manage cloud-native applications. You specify the compute resources that your applications require, and Container Engine for Kubernetes provisions them on Oracle Cloud Infrastructure in an existing OCI tenancy.

Container Engine for Kubernetes uses Kubernetes - the open-source system for automating deployment, scaling, and management of containerized applications across clusters of hosts. Kubernetes groups the containers that make up an application into logical units (called pods) for easy management and discovery.

You can access Container Engine for Kubernetes to define and create Kubernetes clusters using the Console and the REST API. You can access the clusters you create using the Kubernetes command line (kubectl), the Kubernetes Dashboard, and the Kubernetes API.

Container Engine for Kubernetes is integrated with Oracle Cloud Infrastructure Identity and Access Management (IAM), which provides easy authentication with native Oracle Cloud Infrastructure identity functionality.

Budget is the OCI capability that allows you to set up alerts to notify you if a budget forecast exceeds or spending surpasses a certain amount. You can create budget alerts based on actual spending or forecasted spending, and specify the percentage or amount of the budget that triggers the alert. You can also choose how to receive the alert notifications, such as email or OCI Notifications service.

Setting up your application across multiple fault domains is a way to configure high availability for an application in an OCI region with a single availability domain. A fault domain is a logical grouping of hardware and infrastructure within an availability domain that is designed to be isolated from failures in other fault domains. Fault domains let you distribute your instances so that they are not on the same physical hardware within a single availability domain. This reduces the impact of hardware failures, power outages, or network issues on your application availability and performance. Each availability domain has three fault domains, regardless of the number of availability domains in a region1

Fault domains are the feature that the Oracle Cloud Infrastructure Compute service leverages for ensuring high availability of applications. A fault domain is a grouping of hardware and infrastructure within an availability domain that is isolated from other fault domains. Fault domains provide protection from unexpected hardware failures or power interruptions within an availability domain.

You can open a support service request with Oracle Support

To create a service request:

Go to My Oracle Support and sign in.

If you are not signed in to Oracle Cloud Support, click Switch to Cloud Support at the top of the page.

Click Create Service Request.

Select the following from the displayed menus:

Service Type: Select Oracle Cloud Infrastructure from the list.

Service Name: Select the appropriate option for your organization.

Problem Type: Select your problem type from the list.

Enter your contact information.

Enter a Description, and then enter the required fields specific to your issue. For most Oracle Cloud Infrastructure issues you need to include the OCID (Oracle Cloud Identifier) for each resource you need help with. See Locating Oracle Cloud Infrastructure IDs for instructions on locating these.

Oracle Cloud Infrastructure Compute lets you provision and manage compute hosts, known as instances

You can launch instances as needed to meet your compute and application requirements. After you launch an instance, you can access it securely from your computer, restart it, attach and detach volumes, and terminate it when you're done with it. Any changes made to the instance's local drives are lost when you terminate it. Any saved changes to volumes attached to the instance are retained.

Oracle Cloud Infrastructure offers both bare metal and virtual machine instances:

1) Bare Metal: A bare metal compute instance gives you dedicated physical server access for highest performance and strong isolation.

2) Virtual Machine: A virtual machine (VM) is an independent computing environment that runs on top of physical bare metal hardware. The virtualization makes it possible to run multiple VMs that are isolated from each other. VMs are ideal for running applications that do not require the performance and resources (CPU, memory, network bandwidth, storage) of an entire physical machine.

An Oracle Cloud Infrastructure VM compute instance runs on the same hardware as a bare metal instance, leveraging the same cloud-optimized hardware, firmware, software stack, and networking infrastructure.

Components of IAM

IAM uses the components described in this section. To better understand how the components fit together, see Example Scenario.

RESOURCE

The cloud objects that your company's employees create and use when interacting with Oracle Cloud Infrastructure. For example: compute instances, block storage volumes, virtual cloud networks (VCNs), subnets, route tables, etc.

USER

An individual employee or system that needs to manage or use your company's Oracle Cloud Infrastructure resources. Users might need to launch instances, manage remote disks, work with your virtual cloud network, etc. End users of your application are not typically IAM users. Users have one or more IAM credentials (see User Credentials).

GROUP

A collection of users who all need the same type of access to a particular set of resources or compartment.

DYNAMIC GROUP

A special type of group that contains resources (such as compute instances) that match rules that you define (thus the membership can change dynamically as matching resources are created or deleted). These instances act as "principal" actors and can make API calls to services according to policies that you write for the dynamic group.

NETWORK SOURCE

A group of IP addresses that are allowed to access resources in your tenancy. The IP addresses can be public IP addresses or IP addresses from a VCN within your tenancy. After you create the network source, you use policy to restrict access to only requests that originate from the IPs in the network source.

COMPARTMENT

A collection of related resources. Compartments are a fundamental component of Oracle Cloud Infrastructure for organizing and isolating your cloud resources. You use them to clearly separate resources for the purposes of measuring usage and billing, access (through the use of policies), and isolation (separating the resources for one project or business unit from another). A common approach is to create a compartment for each major part of your organization. For more information, see Setting Up Your Tenancy.

TENANCY

The root compartment that contains all of your organization's Oracle Cloud Infrastructure resources. Oracle automatically creates your company's tenancy for you. Directly within the tenancy are your IAM entities (users, groups, compartments, and some policies; you can also put policies into compartments inside the tenancy). You place the other types of cloud resources (e.g., instances, virtual networks, block storage volumes, etc.) inside the compartments that you create.

POLICY

A document that specifies who can access which resources, and how. Access is granted at the group and compartment level, which means you can write a policy that gives a group a specific type of access within a specific compartment, or to the tenancy itself. If you give a group access to the tenancy, the group automatically gets the same type of access to all the compartments inside the tenancy. For more information, see Example Scenario and How Policies Work. The word "policy" is used by people in different ways: to mean an individual statement written in the policy language; to mean a collection of statements in a single, named "policy" document (which has an Oracle Cloud ID (OCID) assigned to it); and to mean the overall body of policies your organization uses to control access to resources.

HOME REGION

The region where your IAM resources reside. All IAM resources are global and available across all regions, but the master set of definitions reside in a single region, the home region. You must make changes to your IAM resources in your home region. The changes will be automatically propagated to all regions. For more information, see Managing Regions.

FEDERATION

A relationship that an administrator configures between an identity provider and a service provider. When you federate Oracle Cloud Infrastructure with an identity provider, you manage users and groups in the identity provider. You manage authorization in Oracle Cloud Infrastructure's IAM service. Oracle Cloud Infrastructure tenancies are federated with Oracle Identity Cloud Service by default.

You can set up a single IPSec VPN with a simple layout that you might use for a proof of concept (POC).

Oracle Cloud Infrastructure Key Management is a managed service that enables you to encrypt your data using keys that you control.

Oracle Functions is the OCI service that can be used for running serverless applications. Oracle Functions is a fully managed, multi-tenant, highly scalable, on-demand, Functions-as-a-Service platform. It is built on enterprise-grade Oracle Cloud Infrastructure and powered by the Fn Project open source engine4.

The Oracle Cloud Infrastructure Load Balancing service provides automated traffic distribution from one entry point to multiple servers reachable from your virtual cloud network (VCN). The service offers a load balancer with your choice of a public or private IP address, and provisioned bandwidth.

A load balancer improves resource utilization, facilitates scaling, and helps ensure high availability. You can configure multiple load balancing policies and application-specific health checks

to ensure that the load balancer directs traffic only to healthy instances. The load balancer can reduce your maintenance window by draining traffic from an unhealthy application server before you remove it from service for maintenance.

HOW LOAD BALANCING WORKS:

The Load Balancing service enables you to create a public or private load balancer within your VCN. A public load balancer has a public IP address that is accessible from the internet. A private load balancer has an IP address from the hosting subnet, which is visible only within your VCN. You can configure multiple listeners

for an IP address to load balance transport Layer 4 and Layer 7 (TCP and HTTP) traffic. Both public and private load balancers can route data traffic to any backend server that is reachable from the VCN.

1) Public Load Balancer

To accept traffic from the internet, you create a public load balancer. The service assigns it a public IP address that serves as the entry point for incoming traffic. You can associate the public IP address with a friendly DNS name through any DNS vendor.

A public load balancer is regional in scope. If your region includes multiple availability domains, a public load balancer requires either a regional subnet (recommended) or two availability domain-specific (AD-specific) subnets, each in a separate availability domain. With a regional subnet, the Load Balancing service creates a primary load balancer and a standby load balancer, each in a different availability domain, to ensure accessibility even during an availability domain outage. If you create a load balancer in two AD-specific subnets, one subnet hosts the primary load balancer and the other hosts a standby load balancer. If the primary load balancer fails, the public IP address switches to the secondary load balancer. The service treats the two load balancers as equivalent and you cannot specify which one is "primary".

Whether you use regional or AD-specific subnets, each load balancer requires one private IP address from its host subnet. The Load Balancing service supplies a floating public IP address to the primary load balancer. The floating public IP address does not come from your backend subnets.

If your region includes only one availability domain, the service requires just one subnet, either regional or AD-specific, to host both the primary and standby load balancers. The primary and standby load balancers each require a private IP address from the host subnet, in addition to the assigned floating public IP address. If there is an availability domain outage, the load balancer has no failover.

2) Private Load Balancer

To isolate your load balancer from the internet and simplify your security posture, you can create a private load balancer. The Load Balancing service assigns it a private IP address that serves as the entry point for incoming traffic.

When you create a private load balancer, the service requires only one subnet to host both the primary and standby load balancers. The load balancer can be regional or AD-specific, depending on the scope of the host subnet. The load balancer is accessible only from within the VCN that contains the host subnet, or as further restricted by your security rules.

The assigned floating private IP address is local to the host subnet. The primary and standby load balancers each require an extra private IP address from the host subnet.

If there is an availability domain outage, a private load balancer created in a regional subnet within a multi-AD region provides failover capability. A private load balancer created in an AD-specific subnet, or in a regional subnet within a single availability domain region, has no failover capability in response to an availability domain outage.

Network Security Groups (NSGs) and Security Lists (SLs) are two virtual firewall features that can be used for controlling traffic in an OCI Virtual Cloud Network (VCN). NSGs and SLs allow you to create stateful network filtering rules that allow or deny network traffic based on source and destination IP addresses, ports, and protocols5

NSGs are a subsequent feature designed for application components that have different security postures. NSGs are a set of security rules that you can apply to a set of VNICs in a VCN. NSGs are associated with VNICs, not subnets. You can use NSGs to implement a network security policy at the level of individual VNICs or a group of VNICs. For example, you can use NSGs to control traffic between tiers of an application deployed in a VCN5

SLs are the original virtual firewall feature from the Networking service. SLs are a set of security rules that you apply to a subnet in a VCN. SLs are associated with subnets, not VNICs. You can use SLs to implement a network security policy at the level of the subnet. For example, you can use SLs to control traffic between subnets in a VCN5

When you sign up for Oracle Cloud Infrastructure, Oracle creates a tenancy for you in one region. This is your home region. Your home region is where your IAM resources are defined. When you subscribe to another region, your IAM resources are available in the new region, however, the master definitions reside in your home region and can only be changed there.

When you subscribe your tenancy to a new region, all the policies from your home region are enforced in the new region. If you want to limit access for groups of users to specific regions, you can write policies to grant access to specific regions only.

A fault domain is a grouping of hardware and infrastructure within an availability domain. Each availability domain contains three fault domains. Fault domains provide anti-affinity: they let you distribute your instances so that the instances are not on the same physical hardware within a single availability domain. A hardware failure or Compute hardware maintenance event that affects one fault domain does not affect instances in other fault domains. In addition, the physical hardware in a fault domain has independent and redundant power supplies, which prevents a failure in the power supply hardware within one fault domain from affecting other fault domains.

To control the placement of your compute instances, bare metal DB system instances, or virtual machine DB system instances, you can optionally specify the fault domain for a new instance or instance pool at launch time. If you don't specify the fault domain, the system selects one for you. Oracle Cloud Infrastructure makes a best-effort anti-affinity placement across different fault domains, while optimizing for available capacity in the availability domain. To change the fault domain for an instance, terminate it and launch a new instance in the preferred fault domain.

Use fault domains to do the following things:

Protect against unexpected hardware failures or power supply failures.

Protect against planned outages because of Compute hardware maintenance.

We can use fault domains to do the following things:

1) Protect against unexpected hardware failures or power supply failures.

2) Protect against planned outages because of Compute hardware maintenance

Budgets can be used to set thresholds for your Oracle Cloud Infrastructure spending. You can set alerts on your budget to let you know when you might exceed your budget, and you can view all of your budgets and spending from one single place in the Oracle Cloud Infrastructure console.

Explanation

A shape is a template that determines the number of CPUs, amount of memory, and other resources that are allocated to an instance.

Standard shapes don't incur costs in a STOPPED state.

Users are not a component of the OCI Identity domains, but rather a resource within an identity domain. An identity domain is a container for managing users and roles, federating and provisioning of users, secure application integration through Oracle Single Sign-On (SSO) configuration, and SAML/OAuth based Identity Provider administration1.

Oracle Cloud Infrastructure offers two distinct storage class tiers to address the need for both performant, frequently accessed "hot" storage, and less frequently accessed "cold" storage. Storage tiers help you maximize performance where appropriate and minimize costs where possible.

Use Object Storage for data to which you need fast, immediate, and frequent access. Data accessibility and performance justifies a higher price to store data in the Object Storage tier.

Use Archive Storage for data to which you seldom or rarely access, but that must be retained and preserved for long periods of time. The cost efficiency of the Archive Storage tier offsets the long lead time required to access the data.

Unlike Object Storage, Archive Storage data retrieval is not instantaneous.

In Oracle Cloud Infrastructure, you can set up email alerts to receive notifications when budget thresholds are reached. Email alerts are sent to users who are subscribed to a budget alert rule, which specifies the percentage or amount of budget consumption that triggers the alert. Email alerts help users monitor and control their cloud spending.

An availability domain is a part of a region. A region is a localized geographic area composed of one or more availability domains. An availability domain is one or more data centers located within a region that have fault-tolerant power and network connectivity. Availability domains are isolated from each other within a region, which provides protection from failures that affect multiple data centers at once.

Oracle’s mission is to build cloud infrastructure and platform services for your business to have effective and manageable security to run your mission-critical workloads and store your data with confidence.

Oracle Cloud Infrastructure offers best-in-class security technology and operational processes to secure its enterprise cloud services. However, for you to securely run your workloads in Oracle Cloud Infrastructure, you must be aware of your security and compliance responsibilities. By design, Oracle provides security of cloud infrastructure and operations (cloud operator access controls, infrastructure security patching, and so on), and you are responsible for securely configuring your cloud resources. Security in the cloud is a shared responsibility between you and Oracle.

In a shared, multi-tenant compute environment, Oracle is responsible for the security of the underlying cloud infrastructure (such as data-center facilities, and hardware and software systems) and you are responsible for securing your workloads and configuring your services (such as compute, network, storage, and database) securely.

In a fully isolated, single-tenant, bare metal server with no Oracle software on it, your responsibility increases as you bring the entire software stack (operating systems and above) on which you deploy your applications. In this environment, you are responsible for securing your workloads, and configuring your services (compute, network, storage, database) securely, and ensuring that the software components that you run on the bare metal servers are configured, deployed, and managed securely.

More specifically, your and Oracle's responsibilities can be divided into the following areas:

For more information on Always Free Resources refer below official documentation page

OCI FastConnect is not offered as part of the Free tier:

The following are capabilities of the OCI Data Catalog service:

• It provides a repository of searchable metadata. Data Catalog harvests metadata from data sources across the OCI ecosystem and on-premises to create an inventory of data assets. This helps data consumers easily find the data they need for analytics4.
• It enables enrichment of the metadata. Data Catalog allows users to add business metadata such as business terms, tags, custom properties, and annotations to data assets. This helps provide more insight and context into the data5.
• It can automate harvesting of data. Data Catalog supports on-demand or schedule-based automatic harvesting to ensure the data catalog always has up-to-date information4.

APPLIANCE-BASED DATA TRANSFER

You send your data as files on secure, high-capacity, Oracle-supplied storage appliances to an Oracle transfer site. Operators at the Oracle transfer site upload the data into your designated Object Storage bucket in your tenancy.

This solution supports data transfer when you are migrating a large volume of data and when using disks is not a practical alternative. You do not need to write any code or purchase any hardware. Oracle supplies the transfer appliance and software required to manage the transfer.

Oracle Cloud Infrastructure Data Transfer Appliance securely moves terabytes or petabytes data between on-premise data centers and the cloud. The service reduces data migration times from weeks or months to just hours and is available for data import to the cloud and data export from the cloud.

Creating a manual cluster of compute instances, and Writing custom scripts that will monitor your solution are not valid ways to ensure fault tolerance at all. Also, Performing Data Integrity check when using OCI File Storage Service is not valid since OCI takes care of it.

Therefore, we are left with:

1) Using multiple OCI Availibility Domains (AD), where available, to deploy your solution - Which is excellent because we have multiple AD's so that if one fails, we have a backup AD!

2) Ensuring your solution components are distributed across OCI Fault Domains - So that we can protect our deployment against unexpected power failures, AD failure etc.

The Ultra High Performance level is the only OCI Block Volume performance level that can meet the requirement of at least 105 IOPS/GB and 100,000 IOPS per volume. The Ultra High Performance level is recommended for workloads with the highest I/O requirements, requiring the best possible performance. With this option, you can purchase between 30 – 120 VPUs (volume performance units) per GB/month. The VPUs determine the baseline performance of the volume, as well as the maximum burst performance. The Ultra High Performance level offers the following performance characteristics: 1

• Baseline IOPS/GB: 75
• Maximum IOPS/GB: 300
• Maximum IOPS per volume: 480,000
• Baseline throughput/GB: 0.6 MB/s
• Maximum throughput/GB: 2.4 MB/s
• Maximum throughput per volume: 3,680 MB/s

To achieve the requirement of at least 105 IOPS/GB, you need to purchase at least 45 VPUs/GB. To achieve the requirement of 100,000 IOPS per volume, you need to have a volume size of at least 334 GB. Therefore, the Ultra High Performance level can satisfy both requirements with a minimum volume size of 334 GB and a minimum VPUs/GB of 45.

The other performance levels (Balanced, Higher Performance, and Lower Cost) cannot meet the requirement of at least 105 IOPS/GB and 100,000 IOPS per volume. The Balanced level offers 10 VPUs/GB, with a baseline of 60 IOPS/GB and a maximum of 75 IOPS/GB. The Higher Performance level offers 20 VPUs/GB, with a baseline of 75 IOPS/GB and a maximum of 150 IOPS/GB. The Lower Cost level offers 2 VPUs/GB, with a baseline of 2 IOPS/GB and a maximum of 10 IOPS/GB. None of these levels can provide the required performance for the workload1

Archive storage is the most cost effective for archive data

The Universal Credits pricing model allows customers to use prepaid credits for any eligible cloud service. This gives customers the flexibility to switch between services or regions as needed without having to renegotiate contracts2

A NAT gateway gives cloud resources without public IP addresses access to the internet without exposing those resources to incoming internet connections.

- OCI offers consistent performance with a predictable pricing model - is the best suited answer.

- Only bare metal workloads are supported in OCI - False, since you can work with VMs etc too

- With OCI, you can run cloud native workloads - False, since you can work with on-premise by connecting it to OCI too.

- With OCI, you can only run Java based workloads on bare metal - False since Java is not the only  programming language supported by OCI.