1z0-1085-23 Sample Questions Answers

Resource Manager is an Oracle Cloud Infrastructure service that allows you to automate the process of provisioning your Oracle Cloud Infrastructure resources. Using Terraform, Resource Manager helps you install, configure, and manage resources through the "infrastructure-as-code" model.

A Terraform configuration codifies your infrastructure in declarative configuration files. Resource Manager allows you to share and manage infrastructure configurations and state files across multiple teams and platforms. This infrastructure management can't be done with local Terraform installations and Oracle Terraform modules alone. For more information about the Oracle Cloud Infrastructure Terraform provider, see Terraform Provider. For a general introduction to Terraform and the "infrastructure-as-code" model, see https://www.terraform.io .

DATA ENCRYPTION

Protect customer data at-rest and in-transit in a way that allows customers to meet their security and compliance requirements for cryptographic algorithms and key management

The Oracle Cloud Infrastructure Block Volume service always encrypts all block volumes, boot volumes, and volume backups at rest by using the Advanced Encryption Standard (AES) algorithm with 256-bit encryption. By default all volumes and their backups are encrypted using the Oracle-provided encryption keys. Each time a volume is cloned or restored from a backup the volume is assigned a new unique encryption key.

The File Storage service encrypts all file system and snapshot data at rest. By default all file systems are encrypted using Oracle-managed encryption keys. You have the option to encrypt all of your file systems using the keys that you own and manage using the Vault service.

Object Storage employs 256-bit Advanced Encryption Standard (AES-256) to encrypt object data on the server. Each object is encrypted with its own data encryption key. Data encryption keys are always encrypted with a master encryption key that is assigned to the bucket. Encryption is enabled by default and cannot be turned off. By default, Oracle manages the master encryption key.

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

Explanation

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.

The responsibilities can be divided as:

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.

Customer and Oracle's responsibilities can be divided into the following areas:

Physical Security: Oracle is responsible for protecting the global infrastructure that runs all of the services offered in Oracle Cloud Infrastructure. This infrastructure consists of the hardware, software, networking, and facilities that run Oracle Cloud Infrastructure services.

Identity and Access Management (IAM): As with all Oracle cloud services, you should protect your cloud access credentials and set up individual user accounts. You are responsible for managing and reviewing access for your own employee accounts and for all activities that occur under your tenancy. Oracle is responsible for providing effective IAM services such as identity management, authentication, authorization, and auditing.

Workload Security: You are responsible for protecting and securing the operating system and application layers of your compute instances from attacks and compromises. This protection includes patching applications and operating systems, operating system configuration, and protection against malware and network attacks. Oracle is responsible for providing secure images that are hardened and have the latest patches. Also, Oracle makes it simple for you to bring the same third-party security solutions that you use today.

Data Classification and Compliance: You are responsible for correctly classifying and labeling your data and meeting any compliance obligations. Also, you are responsible for auditing your solutions to ensure that they meet your compliance obligations.

Host Infrastructure Security: You are responsible for securely configuring and managing your compute (virtual hosts, containers), storage (object, local storage, block volumes), and platform (database configuration) services. Oracle has a shared responsibility with you to ensure that the service is optimally configured and secured. This responsibility includes hypervisor security and the configuration of the permissions and network access controls required to ensure that hosts can communicate correctly and that devices are able to attach or mount the correct storage devices.

Network Security: You are responsible for securely configuring network elements such as virtual networking, load balancing, DNS, and gateways. Oracle is responsible for providing a secure network infrastructure.

Client and Endpoint Protection: Your enterprise uses various hardware and software systems, such as mobile devices and browsers, to access your cloud resources. You are responsible for securing all clients and endpoints that you allow to access Oracle Cloud Infrastructure services.

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

• Master encryption keys are keys that are stored and managed by the Vault service. They are used to encrypt or decrypt data encryption keys or other secrets stored in the Vault service7
• Data encryption keys are keys that are generated by the Vault service and used to encrypt or decrypt data outside of the Vault service, such as data in Object Storage or Block Volume. Data encryption keys are themselves encrypted by master encryption keys and returned to the user as ciphertext

The primary goal of the Oracle Cloud Infrastructure shared security model is to ensure a comprehensive security posture by dividing security responsibilities between Oracle and the customer. Security in the cloud is a shared responsibility between you and Oracle. Whereas Oracle ensures the security of cloud infrastructure and operations, your organization must define its own security guidelines. The shared security model helps you understand which security tasks are handled by Oracle and which tasks you must perform3.

Web Application Firewall (WAF) is the Oracle Cloud Infrastructure service that is designed to protect web applications from various types of malicious attacks, such as SQL injection and cross-site scripting. WAF is a cloud-based service that inspects incoming web traffic and blocks any requests that are malicious or do not comply with predefined rules. WAF helps users secure their web applications from common web exploits and application-layer attacks.

Infrastructure as a service (IaaS) is a type of cloud service model in which computing resources are hosted in the cloud. Businesses can use the IaaS model to shift some or all of their use of on-premises or colocated data center infrastructure to the cloud, where it is owned and managed by a cloud provider. These infrastructure elements can include compute, network, and storage hardware as well as other components and software.

How Does IaaS Work?

In a typical IaaS model, a business—which can be of any size—consumes services like compute, storage, and databases from a cloud provider. The cloud provider offers those services by hosting hardware and software in the cloud. The business will no longer need to purchase and manage its own equipment, or space to host the equipment, and the cost will shift to a pay-as-you-go model. When the business needs less, it pays for less. And when it grows, it can provision additional computing resources and other technologies in minutes.

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:

Identity and Access Management (IAM): As with all Oracle cloud services, you should protect your cloud access credentials and set up individual user accounts. You are responsible for managing and reviewing access for your own employee accounts and for all activities that occur under your tenancy. Oracle is responsible for providing effective IAM services such as identity management, authentication, authorization, and auditing.

Workload Security: You are responsible for protecting and securing the operating system and application layers of your compute instances from attacks and compromises. This protection includes patching applications and operating systems, operating system configuration, and protection against malware and network attacks. Oracle is responsible for providing secure images that are hardened and have the latest patches. Also, Oracle makes it simple for you to bring the same third-party security solutions that you use today.

Data Classification and Compliance: You are responsible for correctly classifying and labeling your data and meeting any compliance obligations. Also, you are responsible for auditing your solutions to ensure that they meet your compliance obligations.

Host Infrastructure Security: You are responsible for securely configuring and managing your compute (virtual hosts, containers), storage (object, local storage, block volumes), and platform (database configuration) services. Oracle has a shared responsibility with you to ensure that the service is optimally configured and secured. This responsibility includes hypervisor security and the configuration of the permissions and network access controls required to ensure that hosts can communicate correctly and that devices are able to attach or mount the correct storage devices.

Network Security: You are responsible for securely configuring network elements such as virtual networking, load balancing, DNS, and gateways. Oracle is responsible for providing a secure network infrastructure.

Client and Endpoint Protection: Your enterprise uses various hardware and software systems, such as mobile devices and browsers, to access your cloud resources. You are responsible for securing all clients and endpoints that you allow to access Oracle Cloud Infrastructure services.

Physical Security: Oracle is responsible for protecting the global infrastructure that runs all of the services offered in Oracle Cloud Infrastructure. This infrastructure consists of the hardware, software, networking, and facilities that run Oracle Cloud Infrastructure services.

Exadata DB Systems are not available as part of Oracle Cloud Free Tier. Exadata DB Systems are a premium service that provides the highest levels of performance and availability for Oracle Database workloads. Oracle Cloud Free Tier includes a set of Always Free services that never expire, and a 30-day trial with US$300 of free credit to use on all eligible OCI services1. The Always Free services include two Oracle Autonomous Databases, two AMD Compute VMs, up to four instances of ARM Ampere A1 Compute, and other services1.

https://www.oracle.com/cloud/cloud-infrastructure-compliance/

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.

Autoscaling is an Oracle Cloud Infrastructure (OCI) compute feature that automatically adjusts the number of compute instances in an instance pool based on performance metrics such as CPU utilization. Autoscaling can help you match capacity to demand, while keeping the application up and running, and also saving cost. You can configure autoscaling policies to scale up or down the instance pool based on predefined thresholds or schedules

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 primary purpose of a network security group (NSG) in the Oracle Cloud Infrastructure Networking service is to control traffic flow between specific resources within a VCN. An NSG is a set of virtual firewall rules that can be applied to one or more resources, such as instances, load balancers, or database nodes. NSGs allow users to define granular security policies for different types of resources within a VCN.

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

https://docs.cloud.oracle.com/en-us/iaas/Content/FreeTier/resourceref.htm?Highlight=%20Always%20free

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

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

IAM DYNAMIC GROUP is 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.

Explanation

On an Exadata DB system, all databases share dedicated storage servers which include flash storage. By default, the databases are given equal priority with respect to these resources. The Exadata storage management software uses a first come, first served approach for query processing. If a database executes a major query that overloads I/O resources, overall system performance can be slowed down.

The I/O Resource Management (IORM) allows you to assign priorities to your databases to ensure critical queries are processed first when workloads exceed their resource allocations. You assign priorities by creating directives that specify the number of shares for each database. The number of shares corresponds to a percentage of resources given to that database when I/O resources are stressed.

Directives work together with an overall optimization objective you set for managing the resources. The following objectives are available:

1) Auto - Recommended. IORM determines the optimization objective and continuously and dynamically determines the optimal settings, based on the workloads observed, and resource plans enabled.

2) Balanced - For critical OLTP and DSS workloads. This setting balances low disk latency and high throughput. This setting limits disk utilization of large I/Os to a lesser extent than low latency to achieve a balance between good latency and good throughput.

3) High throughput - For critical DSS workloads that require high throughput.

4) Low latency - For critical OLTP workloads. This setting provides the lowest possible latency by significantly limiting disk utilization.

Components of IAM

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.

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.

Horizontal scaling means that you scale by adding more machines into your pool of resources whereas Vertical scaling means that you scale by adding more power (CPU, RAM) to an existing machine.

An easy way to remember this is to think of a machine on a server rack, we add more machines across the horizontal direction and add more resources to a machine in the vertical direction.

With horizontal-scaling it is often easier to scale dynamically by adding more machines into the existing pool — Vertical-scaling is often limited to the capacity of a single machine, scaling beyond that capacity often involves downtime and comes with an upper limit.

Here is the official list of all industry standards that OCI complies with : https://www.oracle.com/in/cloud/cloud-infrastructure-compliance/

CapEx is Capital expenditures comprise major purchases that will be used in the future.

OpEx Operating expenditures (expenses) represent day-to-day costs that are necessary to keep a business running.

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

Dimensions are defined as qualifiers used for filtering group metric data presented in the OCI Monitoring service. Dimensions are key-value pairs that provide additional information about a metric, such as resource ID, region, availability domain, fault domain, shape, image, etc. Dimensions allow you to narrow down the scope of your metric queries and alarms by specifying which resources or attributes you want to monitor. For example, you can use dimensions to filter the CPU utilization metric by instance ID or shape.

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.

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.

These statements are true regarding OCI regions. A region is a localized geographic area that hosts one or more availability domains. An availability domain is one or more data centers that host OCI resources such as compute instances, block volumes, and subnets. Availability domains are isolated from each other, fault tolerant, and very unlikely to fail simultaneously1

Some regions provide multiple availability domains, while some regions provide a single availability domain. The number of availability domains per region varies depending on the region type and the customer demand. You can check the list of regions and their availability domains here: 2

• Commercial regions: These are the standard regions that are available to all customers and offer a wide range of OCI services and features. Commercial regions can have one, two, or three availability domains per region.
• Government regions: These are the regions that are dedicated to US government customers and meet specific compliance and security requirements. Government regions can have one or two availability domains per region.
• Dedicated regions: These are the regions that are deployed within a customer’s data center and provide a fully managed OCI environment that is consistent with the public cloud regions. Dedicated regions can have one or two availability domains per region.

The other statements are false regarding OCI regions. There is no concept of subregions in OCI. A region is composed of one or more availability domains, not subregions1

Regions do not only provide test/dev environments. Regions can host any type of workload or application, whether it is for production, development, testing, or disaster recovery purposes. Regions offer different performance levels, service levels, and pricing options to suit different customer needs and use cases1

Regions do not provide a single fault domain. A fault domain is a 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. Each availability domain has three fault domains, regardless of the number of availability domains in a region3

A key benefit of using Oracle Cloud Infrastructure Autonomous Database is that it reduces database management overhead by automating tasks such as provisioning, patching, tuning, backup, recovery, and scaling. This allows customers to focus on their core business rather than database administration6

Oracle Data Safe is a unified control center for your Oracle databases which helps you understand the sensitivity of your data, evaluate risks to data, mask sensitive data, implement and monitor security controls, assess user security, monitor user activity, and address data security compliance requirements.

Whether you’re using an Autonomous Database or an Oracle DB system, Oracle Data Safe delivers essential data security capabilities as a service on Oracle Cloud Infrastructure.

Features of Oracle Data Safe:

Oracle Data Safe provides the following set of features for protecting sensitive and regulated data in Oracle Cloud databases, all in a single, easy-to-use management console:

1) Security Assessment helps you assess the security of your cloud database configurations. It analyzes database configurations, user accounts, and security controls, and then reports the findings with recommendations for remediation activities that follow best practices to reduce or mitigate risk.

2) User Assessment helps you assess the security of your database users and identify high risk users. It reviews information about your users in the data dictionary on your target databases, and calculates a risk score for each user. For example, it evaluates the user types, how users are authenticated, the password policies assigned to each user, and how long it has been since each user has changed their password. It also provides a direct link to audit records related to each user. With this information, you can then deploy appropriate security controls and policies.

3) Data Discovery helps you find sensitive data in your cloud databases. You tell Data Discovery what kind of sensitive data to search for, and it inspects the actual data in your database and its data dictionary, and then returns to you a list of sensitive columns. By default, Data Discovery can search for a wide variety of sensitive data pertaining to identification, biographic, IT, financial, healthcare, employment, and academic information.

4) Data Masking provides a way for you to mask sensitive data so that the data is safe for non-production purposes. For example, organizations often need to create copies of their production data to support development and test activities. Simply copying the production data exposes sensitive data to new users. To avoid a security risk, you can use Data Masking to replace the sensitive data with realistic, but fictitious data.

5) Activity Auditing lets you audit user activity on your databases so you can monitor database usage and be alerted of unusual database activities.

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

https://www.oracle.com/cloud/what-is-iaas/

What Is IaaS?

Infrastructure as a service (IaaS) is a type of cloud service model in which computing resources are hosted in the cloud. Businesses can use the IaaS model to shift some or all of their use of on-premises or colocated data center infrastructure to the cloud, where it is owned and managed by a cloud provider. These infrastructure elements can include compute, network, and storage hardware as well as other components and software.

In the IaaS model, the cloud provider owns and operates the hardware and software and also owns or leases the data center. When you have an IaaS solution, you rent the resources like compute or storage, provision them when needed, and pay for the resources your organization consumes. For some resources such as compute, you’ll pay for the resources you use. For others such as storage, you’ll pay for capacity.

How Does IaaS Work?

In a typical IaaS model, a business—which can be of any size—consumes services like compute, storage, and databases from a cloud provider. The cloud provider offers those services by hosting hardware and software in the cloud. The business will no longer need to purchase and manage its own equipment, or space to host the equipment, and the cost will shift to a pay-as-you-go model. When the business needs less, it pays for less. And when it grows, it can provision additional computing resources and other technologies in minutes.

In contrast, in a traditional on-premises scenario, a business manages and maintains its own data center. The business must invest in servers, storage, software, and other technologies, and hire an IT staff or contractors to purchase, manage, and upgrade all the equipment and licenses. The data center has to be built to meet peak demand, even though sometimes workloads decline and those resources stand idle. Conversely, if the business grows quickly, the IT department might struggle to keep up.

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.

https://docs.cloud.oracle.com/en-us/iaas/Content/DataTransfer/Concepts/overview.htm

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.

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

Changing the Shape of an Instance (Horizontal Scaling)

You can change the shape of a virtual machine (VM) instance without having to rebuild your instances or redeploy your applications. This lets you scale up your Compute resources for increased performance, or scale down to reduce cost.

Autoscaling (vertical scaling)

Autoscaling lets you automatically adjust the number of Compute instances in an instance pool based on performance metrics such as CPU utilization. This helps you provide consistent performance for your end users during periods of high demand, and helps you reduce your costs during periods of low demand.

As load increases, instances are automatically provisioned: the instance pool scales out. As load decreases, instances are automatically removed: the instance pool scales in.

https://docs.cloud.oracle.com/en-us/iaas/Content/Compute/Tasks/resizinginstances.htm

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.

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

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