1z0-1084-22 Exam Dumps - Oracle Cloud Infrastructure 2022 Developer Professional

Oracle Cloud Infrastructure provides a number of DevOps tools and plug-ins for working with Oracle Cloud Infrastructure services. These can simplify provisioning and managing infrastructure or enable automated testing and continuous delivery.

A/B Testing

While A/B testing can be combined with either canary orblue-green deployments, it is a very different thing. A/B testing really targets testing the usage behavior of a service or feature and is typically used to validate a hypothesis or to measure two versions of a service or feature and how they stack up against each other in terms of performance, discoverability and usability. A/B testing often leverages feature flags (feature toggles), which allow you to dynamically turn features on and off.

Integration Testing

Integration tests are also known as end-to-end(e2e) tests. These are long-running tests that exercise the system in the way it is intended to be used in production. These are the most valuable tests in demonstrating reliability and thus increasing confidence.

Penetration Testing

Oracle regularly performs penetration and vulnerability testing and security assessments against the Oracle cloud infrastructure, platforms, and applications. These tests are intended to validate and improve the overall security of Oracle Cloud Services.

References:

https://docs.cloud.oracle.com/en-us/iaas/Content/API/Concepts/devopstools.htm

Token-based authentication for the CLI:

Token-based authentication for the CLI allows customers to authenticate their session interactively, then use theCLI for a single session without an API signing key. This enables customers using an identity provider that is not SCIM-supported to use a federated user account with the CLI and SDKs.

Starting a Token-based CLI Session

To use token-based authenticationfor the CLI on a computer with a web browser:

1. In the CLI, run the following command. This will launch a web browser.

oci session authenticate

2. In the browser, enter your user credentials. This authentication information is saved to the .config file.

Validating a Token

To verify that a token is valid, run the following command:

oci session validate --config-file --profile --auth security_token

You should receive a message showing the expiration date for the session.If you receive an error, check your profile settings.

References:

https://docs.cloud.oracle.com/en-us/iaas/Content/API/SDKDocs/clitoken.htm

Having created an API gateway and deployed one or more APIs on it, you'll typically want to limit the rate at which front-end clients can make requests to back-end services. For example, to:

- maintain high availability and fair use of resources by protecting back ends from being overwhelmed by too many requests

- prevent denial-of-service attacks

- constrain costs of resource consumption

- restrict usage of APIs by your customers'users in order to monetize APIs

You apply a rate limit globally to all routes in an API deployment specification.

If a request is denied because the rate limit has been exceeded, the response header specifies when the request can be retried.

You can add arate-limiting request policy to an API deployment specification by:

using the Console

editing a JSON file

{

"requestPolicies": {

"rateLimiting": {

"rateKey": "CLIENT_IP",

"rateInRequestsPerSecond": 10

}

},

"routes":[

{

"path": "/hello",

"methods": ["GET"],

"backend": {

"type": "ORACLE_FUNCTIONS_BACKEND",

"functionId": "ocid1.fnfunc.oc1.phx.aaaaaaaaab______xmq"

}

}

]

}

https://docs.cloud.oracle.com/en-us/iaas/Content/APIGateway/Tasks/apigatewaylimitingbackendaccess.htm

https://docs.cloud.oracle.com/en-us/iaas/Content/ResourceManager/Con cepts/resourcemanager.htm

Following are brief descriptions of key concepts and the main components of Resource Manager.

CONFIGURATION

Information to codify your infrastructure. A Terraform configuration can be either a solution or a file that you write and upload.

JOB

Instructions to perform the actions defined in your configuration. Only one job at a time can run on a given stack; further, you can have only one set of Oracle Cloud Infrastructure resources on a given stack. To provision a different set of resources, you must create a separate stack and use a different configuration.

Resource Manager provides the following job types:

Plan: Parses your Terraform configuration and creates an execution plan for the associated stack. The execution plan lists the sequence of specific actions planned to provision your Oracle Cloud Infrastructure resources. The execution plan is handed off to the apply job, which then executes the instructions.

Apply. Applies the execution plan to theassociated stack to create (or modify) your Oracle Cloud Infrastructure resources. Depending on the number and type of resources specified, a given apply job can take some time. You can check status while the job runs.

Destroy. Releases resources associated with a stack. Released resources are not deleted. For example, terminates a Compute instance controlled by a stack. The stack's job history and state remain after running a destroy job. You can monitor the status and review the results of a destroy job by inspecting the stack's log files.

Import State. Sets the provided Terraform state file as the current state of the stack. Use this job to migrate local Terraform environments to Resource Manager.

STACK

The collection of Oracle Cloud Infrastructure resources corresponding to a given Terraform configuration. Each stack resides in the compartment you specify, in a single region;however, resources on a given stack can be deployed across multiple regions. An OCID is assigned to each stack.

the following steps reference Console instructions

Create a Terraform configuration.

Create a stack.

Run a plan job, which produces an executionplan.

Review the execution plan.

If changes are needed in the execution plan, update the configuration and run a plan job again.

Run an apply job to provision resources.

Review state file and log files, as needed.

You can optionally reapply your configuration, with or without making changes, by running an apply job again.

Optionally, to release the resources running on a stack, run a destroy job.

Kubernetes cluster is a group of nodes. The nodes are the machines running applications. Each node can be a physical machine or a virtual machine. The node'scapacity (its number of CPUs and amount of memory) is defined when the node is created. A cluster comprises:

- one or more master nodes (for high availability, typically there will be a number of master nodes)

- one or more worker nodes (sometimes known asminions)

Connecting to Worker Nodes Using SSH

If you provided a public SSH key when creating the node pool in a cluster, the public key is installed on all worker nodes in the cluster. On UNIX and UNIX-like platforms (including Solaris and Linux), you canthen connect through SSH to the worker nodes using the ssh utility (an SSH client) to perform administrative tasks.

Note the following instructions assume the UNIX machine you use to connect to the worker node:

Has the ssh utility installed.

Has access tothe SSH private key file paired with the SSH public key that was specified when the cluster was created.

How to connect to worker nodes using SSH depends on whether you specified public or private subnets for the worker nodes when defining the node poolsin the cluster.

Connecting to Worker Nodes in Public Subnets Using SSH

Before you can connect to a worker node in a public subnet using SSH, you must define an ingress rule in the subnet's security list to allow SSH access. The ingress rule must allow access to port 22 on worker nodes from source 0.0.0.0/0 and any source port

To connect to a worker node in a public subnet through SSH from a UNIX machine using the ssh utility:

1- Find out the IP address of the worker node to which you want to connect. You can do this in a number of ways:

Using kubectl. If you haven't already done so, follow the steps to set up the cluster's kubeconfig configuration file and (if necessary) set the KUBECONFIG environment variable to point to the file. Note that you must set upyour own kubeconfig file. You cannot access a cluster using a kubeconfig file that a different user set up. See Setting Up Cluster Access. Then in a terminal window, enter kubectl get nodes to see the public IP addresses of worker nodes in node pools in the cluster.

Using the Console. In the Console, display the Cluster List page and then select the cluster to which the worker node belongs. On the Node Pools tab, click the name of the node pool to which the worker node belongs. On the Nodes tab, you see the public IP address of every worker node in the node pool.

Using the REST API. Use the ListNodePools operation to see the public IP addresses of worker nodes in a node pool.

2- In the terminal window, enter ssh opc@ to connect to the worker node, where  isthe IP address of the worker node that you made a note of earlier. For example, you might enter ssh opc@192.0.2.254.

Note that if the SSH private key is not stored in the file or in the path that the ssh utility expects (for example, the ssh utility mightexpect the private key to be stored in ~/.ssh/id_rsa), you must explicitly specify the private key filename and location in one of two ways:

Use the -i option to specify the filename and location of the private key. For example, ssh -i ~/.ssh/my_keys/my_host_key_filename opc@192.0.2.254

Add the private key filename and location to an SSH configuration file, either the client configuration file (~/.ssh/config) if it exists, or the system-wide client configuration file (/etc/ssh/ssh_config). For example, youmight add the following:

Host 192.0.2.254 IdentityFile ~/.ssh/my_keys/my_host_key_filename

For more about the ssh utility’s configuration file, enter man ssh_config

Note also that permissions on the private key file must allow you read/write/execute access, but prevent other users from accessing the file. For example, to set appropriate permissions, you might enter chmod 600 ~/.ssh/my_keys/my_host_key_filename. If permissions are not set correctly and the private key file is accessible to other users, thessh utility will simply ignore the private key file.

References:

https://docs.cloud.oracle.com/en-us/iaas/Content/ContEng/Tasks/conten gconnectingworkernodesusingssh.htm