[Sep 21, 2023] 1z0-1085-22 Exam Dumps, 1z0-1085-22 Practice Test Questions [Q33-Q52]

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.
Reference:
https://www.oracle.com/a/ocom/docs/oracle-cloud-infrastructure-security-architecture.pdf

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.

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.
Reference:
https://docs.cloud.oracle.com/en-us/iaas/Content/Billing/Concepts/billingoverview.htm A budget can be used to set soft limits on 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.
How Budgets Work:
Budgets are set on cost-tracking tags or on compartments (including the root compartment) to track all spending in that cost-tracking tag or for that compartment and its children.
All budgets alerts are evaluated every 15 minutes. To see the last time a budget was evaluated, open the details for a budget. You will see fields that show the current spend, the forecast and the “Spent in period” field which shows you the time period over which the budget was evaluated. When a budget alert fires, the email recipients configured in the budget alert receive an email.

Oracle Cloud Infrastructure is hosted in regions and availability domains. A region is a localized geographic area, and an availability domain is one or more data centers located within a region. A region is composed of one or more availability domains. Most Oracle Cloud Infrastructure resources are either region-specific, such as a virtual cloud network, or availability domain-specific, such as a compute instance. Traffic between availability domains and between regions is encrypted. Availability domains are isolated from each other, fault tolerant, and very unlikely to fail simultaneously. Because availability domains do not share infrastructure such as power or cooling, or the internal availability domain network, a failure at one availability domain within a region is unlikely to impact the availability of the others within the same region.
The availability domains within the same region are connected to each other by a low latency, high bandwidth network, which makes it possible for you to provide high-availability connectivity to the internet and on-premises, and to build replicated systems in multiple availability domains for both high-availability and disaster recovery.
Oracle is adding multiple cloud regions around the world to provide local access to cloud resources for our customers. To accomplish this quickly, we’ve chosen to launch regions in new geographies with one availability domain.
As regions require expansion, we have the option to add capacity to existing availability domains, to add additional availability domains to an existing region, or to build a new region. The expansion approach in a particular scenario is based on customer requirements as well as considerations of regional demand patterns and resource availability.
For any region with one availability domain, a second availability domain or region in the same country or geo-political area will be made available within a year to enable further options for disaster recovery that support customer requirements for data residency where they exist.

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.
Reference:
https://oracledbwr.com/oracle-cloud-infrastructure-object-storage-service/

The available purchase models are:
Pay As You Go (PAYG): Billed in arrears based on consumption. Recommended for organizations who are trying new services, rapid prototyping, or for elastic scaling.
Monthly Flex: Billed in advance with a 12-month minimum. Use monthly or forfeit that month’s credits. Recommended for customers with predictable production workloads or large long-running applications, such as HR, payroll, analytics, and more. Monthly Flex maximizes cost reduction with predictable monthly spend, similar to your monthly phone plan. Delivers faster time to market by offering customers the choice of using any IaaS and PaaS services.
Oracle’s current PaaS offering is “license-included PaaS.” It includes:
* Compute and compute support
* Automation
* License entitlement and license support
Bring your own license
BYOL stands for “bring your own license.” Previously, you could bring your own licenses to Oracle IaaS, but to get the benefits of PaaS automation, you couldn’t leverage existing licenses. This has been changed. We’re offering Oracle BYOL to PaaS, enabling our customers to leverage their investment in existing on-premises licenses in their journey to the cloud.
Oracle BYOL to PaaS includes:
* Compute and compute support
* Automation
* Customers bring their on-premises license entitlement and get license support via their existing on-premises support contract.
* As customers leverage their existing on-premises license entitlement, they can move to the cloud at a lower cost.
Reference:
https://www.oracle.com/in/cloud/bring-your-own-license/faq/universal-credit-pricing.html OCI doesn’t offer Reserved instances.
Enterprise users and technology vendors alike require cost predictability to plan their budgets and run their business. The cost for running applications, databases, and large workloads in the cloud can be extremely difficult to forecast leading to unforeseen expenses. Not with Oracle Cloud. Oracle has simple rate structures that eliminate the cost surprises associated with hard-to-estimate usage elements like data egress and storage performance. Oracle also charges the same rates for all regions, so going global on Oracle Cloud means no hidden cost variances. Thus, Oracle’s cloud will provide you with industry leading price-performance and tremendous business value.

To design a high availability architecture, three key elements should be considered- redundancy, monitoring, and failover:
1) Redundancy means that multiple components can perform the same task. The problem of a single point of failure is eliminated because redundant components can take over a task performed by a component that has failed.
2) Monitoring means checking whether or not a component is working properly.
3) Failover is the process by which a secondary component becomes primary when the primary component fails.
The best practices introduced here focus on these three key elements. Although high availability can be achieved at many different levels, including the application level and the cloud infrastructure level, here we will focus on the cloud infrastructure level.
An Oracle Cloud Infrastructure region is a localized geographic area composed of one or more availability domains, each composed of three fault domains. High availability is ensured by a redundancy of fault domains within the availability domains.
An availability domain is one or more data centers located within a region. Availability domains are isolated from each other, fault tolerant, and unlikely to fail simultaneously. Because availability domains do not share physical infrastructure, such as power or cooling, or the internal availability domain network, a failure that impacts one availability domain is unlikely to impact the availability of others.
A fault domain is a grouping of hardware and infrastructure within an availability domain. Each availability domain contains three fault domains. Fault domains let you distribute your instances so that they are not on the same physical hardware within a single availability domain. As a result, an unexpected hardware failure or a Compute hardware maintenance that affects one fault domain does not affect instances in other fault domains. You can optionally specify the fault domain for a new instance at launch time, or you can let the system select one for you.
All the availability domains in a region are connected to each other by a low-latency, high bandwidth network. This predictable, encrypted interconnection between availability domains provides the building blocks for both high availability and disaster recovery.

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 Reference:
https://docs.cloud.oracle.com/en-us/iaas/Content/File/Concepts/filestorageoverview.htm

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.