Oracle Oracle Certifications 1Z0-1085-22 Questions & Answers

• Question 51:

  Which kind of scaling is supported by virtual machines in Oracle Cloud Infrastructure Compute service?

  A. Only scaling up or down

  B. Only scaling out

  C. Scaling up or down, and scaling in or out

  D. Only scaling in

  Correct Answer: C

  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. Reference: https://medium.com/@abhinavkorpal/scaling-horizontally-and-vertically-for-databases-a2aef778610c

• Question 52:

  You want to migrate mission-critical Oracle E- Business Suite application to Oracle Cloud Infrastructure

  (OCI) with full control and access to the underlying infrastructure.

  Which option meets this requirement?

  A. Replace E-Business Suite with an Oracle SaaS application

  B. OCI Exadata DB Systems and OCI compute instances

  C. OCI Exadata DB Systems and Oracle Functions

  D. Oracle Exadata Cloud at customer, Storage Gateway and API Gateway

  Correct Answer: B

• Question 53:

  Which is NOT a valid business benefit for a customer considering migrating their infrastructure and apps to Oracle Cloud Infrastructure (OCI)?

  A. Faster go-to market

  B. Capital Expenditure to Operational Expenditure conversion

  C. Greater agility

  D. Increased Total Cost of Ownership (TCO)

  Correct Answer: D

  Oracle Cloud Infrastructure is a set of complementary cloud services that enable you to build and run a wide range of applications and services in a highly available hosted environment. Oracle Cloud Infrastructure offers high-performance compute capabilities (as physical hardware instances) and storage capacity in a flexible overlay virtual network that is securely accessible from your on- premises network. Reference: https://docs.cloud.oracle.com/en-us/iaas/Content/GSG/Concepts/baremetalintro.htm One of the major benefits of cloud computing is REDUCED TCO. Therefore, Increased TCO is the incorrect option. https://www.oracle.com/partners/en/partner-with-oracle/develop-solutions/why/increase-value- reducecost-3907933.pdf

• Question 54:

  What characteristics are defined by an Oracle Cloud Infrastructure Compute shape?

  A. Number of vCPU, amount of RAM, bandwidth

  B. Availability Domain and Fault Domain locations

  C. Public or private visibility of the Compute instance

  D. Number of OCPU, amount of RAM, bandwidth

  Correct Answer: D

  Oracle Compute Shape is coming with predefined or customize the number of OCPUs that are allocated to an instance. The amount of memory, network bandwidth, and number of VNICs scale proportionately with the number of OCPUs. Reference: https://docs.cloud.oracle.com/en-us/iaas/Content/Compute/References/computeshapes.htm

• Question 55:

  Which statement accurately describes an Oracle Cloud Infrastructure Region?

  A. Each Availability Domain has a single Fault Domain.

  B. Each Availability Domain has three Fault Domains.

  C. Each Fault Domain has multiple Availability Domains.

  D. Each region has a single Fault Domain.

  Correct Answer: B

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

• Question 56:

  Which three services Integrate with Oracle Cloud Infrastructure (OCI) Key Management?

  A. Functions

  B. Block Volume

  C. Object Storage

  D. Auto Scaling

  E. Identity and Access Management

  F. File Storage

  Correct Answer: BCF

  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.

  Reference:

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

  docs.cloud.oracle.com/en-us/iaas/Content/Object/Concepts/objectstorageoverview.htm https://

  docs.cloud.oracle.com/en-us/iaas/Content/File/Concepts/filestorageoverview.htm

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

  using keys that you control.IAM, Autoscaling and functions cannot be used with Key Management and

  hence are incorrect options.

  Reference:

  https://docs.cloud.oracle.com/en-us/iaas/Content/KeyManagement/Concepts/keyoverview.htm

• Question 57:

  Which should you use to distribute Incoming traffic between a set of web servers?

  A. Load Balances

  B. Internet Gateway

  C. Autoscallng

  D. Dynamic Routing Gateway

  Correct Answer: A

  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 (ADspecific) 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. Reference: https://docs.cloud.oracle.com/en-us/iaas/Content/Balance/Concepts/balanceoverview.htm

• Question 58:

  Which two are enabled by Oracle Cloud Infrastructure Fault Domains?

  A. Protect against unexpected hardware or power supply failures

  B. To meet requirements for legal jurisdictions

  C. To mitigate the risk of large scale events such as earthquakes

  D. Build replicated systems for disaster recovery

  E. Protect against planned hardware maintenance

  Correct Answer: AE

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

  

• Question 59:

  Which Oracle Cloud Infrastructure service leverages Terraform to configure infrastructure as code?

  A. Resource Manager

  B. Events

  C. Compartment Explorer

  D. Oracle Functions

  Correct Answer: A

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

• Question 60:

  Which pricing model is NOT supported by Oracle Cloud Infrastructure?

  A. Reserved Infrastructure

  B. Universal Credits - Monthly Flex

  C. Bring your own license

  D. Pay-as-you-go

  Correct Answer: A

  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:

  1.

  Compute and compute support

  2.

  Automation

  3.

  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:

  1.

  Compute and compute support

  2.

  Automation

  3.

  Customers bring their on-premises license entitlement and get license support via their existing on-premises support contract.

  4.

  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.

  

  Reference: https://www.oracle.com/in/cloud/pricing.html