Oracle Updated 1z0-1084-22 Exam Questions and Answers by thiago

Resource Manager is an OracleCloud 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.

References:

https://docs.cloud.oracle.com/iaas/Content/ResourceManager/Concepts/resourcemanager.htm

Storing and Viewing Function Logs:

When a function you've deployed to Oracle Functions is invoked, you'll typically want to store the function's logs so that you can review them later. You specify where Oracle Functions storesa function's logs by setting a logging policy for the application containing the function.

You can specify that Oracle Functions:

Stores logs in Oracle Cloud Infrastructure. Until an Oracle Cloud Infrastructure logging service is released, Oracle Functionsstores logs as files in a storage bucket in Oracle Cloud Infrastructure Object Storage.

Note that to view function logs in a storage bucket, the group to which you belong must have been granted access with the following identity policy statements:

Allowgroup to manage object-family in compartment

Allow group to read objectstorage-namespaces in compartment  (Usually created when configuring your tenancy for function development. See Create a Policy to Give Oracle Functions Users Access to Oracle Cloud Infrastructure Registry Repositories.)

Stores logs by exporting them to an external logging destination like Papertrail. Note that to use an external logging destination, you must have set up a VCN with public subnets and an internet gateway (see Create the VCN and Subnets to Use with Oracle Functions, if they don't exist already).

You set application logging policies in the Console.

References:

https://docs.cloud.oracle.com/en-us/iaas/Content/Functions/Tasks/functionsexportingfunctionlogfiles.htm

Overview of Load Balancing:

SHAPE

A template that determines the load balancer's total pre-provisioned maximum capacity (bandwidth) for ingress plus egress traffic. Available shapesinclude 10Mbps, 100 Mbps, 400 Mbps, and 8000 Mbps.

oci-load-balancer-shape: A template that determines the load balancer's total pre-provisioned maximum capacity (bandwidth) for ingress plus egress traffic. Available shapes include 100Mbps, 400Mbps, and8000Mbps. Cannot be modified after load balancer creation.

All annotations are prefixed with service.beta.kubernetes.io/. For example:

kind: Service

apiVersion: v1

metadata:

name: nginx-service

annotations:

service.beta.kubernetes.io/oci-load-balancer-shape: "400Mbps"

service.beta.kubernetes.io/oci-load-balancer-subnet1: "ocid..."

service.beta.kubernetes.io/oci-load-balancer-subnet2: "ocid..."

spec:

References:

https://docs.cloud.oracle.com/en-us/iaas/Content/Balance/Concepts/balanceoverview.htm

https://github.com/oracle/oci-cloud-controller-manager/blob/master/docs/load-balancer-annotations.md