Oracle 1Z0-1084-20 Online Practice Questions and Exam Preparation

Oracle 1Z0-1084-20 Online Questions & Answers

• Question 41:

  What is the minimum of storage that a persistent volume claim can obtain in Oracle Cloud Infrastructure Container Engine for Kubernetes (OKE)?

  A. 50 GB
  B. 10 GB
  C. 1 GB
  D. 1 TB
  A. 50 GB

  ---

  The minimum amount of persistent storage that a PVC can request is 50 gigabytes. If the request is for less than 50 gigabytes, the request is rounded up to 50 gigabytes. https://docs.cloud.oracle.com/en-us/iaas/Content/ContEng/Tasks/contengcreatingpersistentvolumeclaim.htm

• Question 42:

  Your organization uses a federated identity provider to login to your Oracle Cloud Infrastructure (OCI) environment. As a developer, you are writing a script to automate some operation and want to use OCI CLI to do that. Your security team

  doesn't allow storing private keys on local machines.

  How can you authenticate with OCI CLI?

  A. Run oci setup keys and provide your credentials
  B. Run oci session refresh --profile
  C. Run oci session authenticate and provide your credentials
  D. Run oci setup oci-cli-rc --file path/to/target/file
  C. Run oci session authenticate and provide your credentials

  ---

  Token-based authentication for the CLI allows customers to authenticate their session interactively, then use the CLI 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 authentication for the CLI on a computer with a web browser:

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

  oci session authenticate

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

• Question 43:

  You want to push a new image in the Oracle Cloud Infrastructure (OCI) Registry. Which two actions do you need to perform?

  A. Assign a tag via Docker CLI to the image.
  B. Generate an auth token to complete the authentication via Docker CLI.
  C. Generate an API signing key to complete the authentication via Docker CLI.
  D. Assign an OCI defined tag via OCI CLI to the image.
  E. Generate an OCI tag namespace in your repository.
  A. Assign a tag via Docker CLI to the image.
  B. Generate an auth token to complete the authentication via Docker CLI.

  ---

  You use the Docker CLI to push images to Oracle Cloud Infrastructure Registry. To push an image, you first use the docker tag command to create a copy of the local source image as a new image (the new image is actually just a reference to the existing source image). As a name for the new image, you specify the fully qualified path to the target location in Oracle Cloud Registry where you want to push the image, optionally including the name of a repository. for more details check the below link

  https://docs.cloud.oracle.com/en-us/iaas/Content/Registry/Tasks/registrypushingimagesusingthedockercli.htm

• Question 44:

  Who is responsible for patching, upgrading and maintaining the worker nodes in Oracle Cloud Infrastructure Container Engine for Kubernetes (OKE)?

  A. It Is automated
  B. Independent Software Vendors
  C. Oracle Support
  D. The user
  D. The user

  ---

  After a new version of Kubernetes has been released and when Container Engine for Kubernetes supports the new version, you can use Container Engine for Kubernetes to upgrade master nodes running older versions of Kubernetes. Because Container Engine for Kubernetes distributes the Kubernetes Control Plane on multiple Oracle-managed master nodes (distributed across different availability domains in a region where supported) to ensure high availability, you're able to upgrade the Kubernetes version running on master nodes with zero downtime. Having upgraded master nodes to a new version of Kubernetes, you can subsequently create new node pools running the newer version. Alternatively, you can continue to create new node pools that will run older versions of Kubernetes (providing those older versions are compatible with the Kubernetes version running on the master nodes). Note that you upgrade master nodes by performing an `in-place' upgrade, but you upgrade worker nodes by performing an `out-of-place' upgrade. To upgrade the version of Kubernetes running on worker nodes in a node pool, you replace the original node pool with a new node pool that has new worker nodes running the appropriate Kubernetes version. Having 'drained' existing worker nodes in the original node pool to prevent new pods starting and to delete existing pods, you can then delete the original node pool.

• Question 45:

  You are developing a serverless application with Oracle Functions and Oracle Cloud Infrastructure Object Storage- Your function needs to read a JSON file object from an Object Storage bucket named "input-bucket" in compartment "qacompartment". Your corporate security standards mandate the use of Resource Principals for this use case.

  Which two statements are needed to implement this use case?

  A. Set up a policy with the following statement to grant read access to the bucket:allow dynamic-group read-file-dg to read objects in compartment qa-compartment where target .bucket .name=' input-bucket *
  B. Set up the following dynamic group for your function's OCID: Name: read-file-dg Rule: resource.id = `ocid1.fnfunc.oc1.phx.aaaaaaaakeaobctakezjz5i4ujj7g25q7sx5mvr55pms6f4da'
  C. Set up a policy to grant all functions read access to the bucket:allow all functions in compartment qa-compartment to read objects in target.bucket.name='input-bucket'
  D. Set up a policy to grant your user account read access to the bucket:allow user XYZ to read objects in compartment qa-compartment where target .bucket, name-'input-bucket'
  E. No policies are needed. By default, every function has read access to Object Storage buckets in the tenancy
  A. Set up a policy with the following statement to grant read access to the bucket:allow dynamic-group read-file-dg to read objects in compartment qa-compartment where target .bucket .name=' input-bucket *
  B. Set up the following dynamic group for your function's OCID: Name: read-file-dg Rule: resource.id = `ocid1.fnfunc.oc1.phx.aaaaaaaakeaobctakezjz5i4ujj7g25q7sx5mvr55pms6f4da'

  ---

  When a function you've deployed to Oracle Functions is running, it can access other Oracle Cloud Infrastructure resources. For example:

  -

  You might want a function to get a list of VCNs from the Networking service.

  -

  You might want a function to read data from an Object Storage bucket, perform some operation on the data, and then write the modified data back to the Object Storage bucket. To enable a function to access another Oracle Cloud Infrastructure resource, you have to include the function in a dynamic group, and then create a policy to grant the dynamic group access to that resource. https://docs.cloud.oracle.com/en-us/iaas/Content/Functions/Tasks/functionsaccessingociresources.htm

• Question 46:

  You created a pod called "nginx" and its state is set to Pending. Which command can you run to see the reason why the "nginx" pod is in the pending state?

  A. kubect2 logs pod nginx
  B. kubect2 describe pod nginx
  C. kubect2 get pod nginx
  D. Through the Oracle Cloud Infrastructure Console
  B. kubect2 describe pod nginx

  ---

  Debugging Pods

  The first step in debugging a pod is taking a look at it. Check the current state of the pod and recent events with the following command:

  kubectl describe pods ${POD_NAME}

  Look at the state of the containers in the pod. Are they all Running? Have there been recent restarts? Continue debugging depending on the state of the pods.

  My pod stays pending

  If a pod is stuck in Pending it means that it can not be scheduled onto a node. Generally this is because there are insufficient resources of one type or another that prevent scheduling. Look at the output of the kubectl describe ... command

  above. There should be messages from the scheduler about why it can not schedule your pod.

  https://kubernetes.io/docs/tasks/debug-application-cluster/debug-pod-replication-controller/

• Question 47:

  You are developing a distributed application and you need a call to a path to always return a specific JSON content deploy an Oracle Cloud Infrastructure API Gateway with the below API deployment specification.

  

  What is the correct value for type?

  A. STOCK_RESPONSE_BACKEND
  B. CONSTANT_BACKEND
  C. JSON_BACKEND
  D. HTTP_BACKEND
  A. STOCK_RESPONSE_BACKEND

  ---

  "type": "STOCK_RESPONSE_BACKEND" indicates that the API gateway itself will act as the back end and return the stock response you define (the status code, the header fields and the body content). https://docs.cloud.oracle.com/en-us/iaas/Content/APIGateway/Tasks/apigatewayaddingstockresponses.htm

• Question 48:

  Given a service deployed on Oracle Cloud infrastructure Container Engine for Kubernetes (OKE), which annotation should you add in the sample manifest file to specify a 400 Mbps load balancer?

  

  A. service.beta, kubernetes. lo/oci-load-balancer-kind: 400Mbps
  B. service, beta, kubernetes. lo/oci-load-balancer-value: 4 00Mbps
  C. service . beta. kubernetes . lo/oci-load-balancer-shape: 400Mbps
  D. service . beta . kubernetes . lo/oci-load-balancer-size: 400Mbps
  C. service . beta. kubernetes . lo/oci-load-balancer-shape: 400Mbps

  ---

  The shape of an Oracle Cloud Infrastructure load balancer specifies its maximum total bandwidth (that is, ingress plus egress). By default, load balancers are created with a shape of 100Mbps. Other shapes are available, including 400Mbps

  and 8000Mbps.

  To specify an alternative shape for a load balancer, add the following annotation in the metadata section of the manifest file:

  service.beta.kubernetes.io/oci-load-balancer-shape: where value is the bandwidth of the shape (for example, 100Mbps, 400Mbps, 8000Mbps).

  For example:

  apiVersion: v1

  kind: Service

  metadata:

  name: my-nginx-svc

  labels:

  app: nginx

  annotations:

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

  type: LoadBalancer

  ports:

  -port: 80 selector: app: nginx https://github.com/oracle/oci-cloud-controller-manager/blob/master/docs/load-balancer-annotations.md

• Question 49:

  You are developing a serverless application with Oracle Functions. Your function needs to store state in a database. Your corporate security Standards mandate encryption of secret information like database passwords. As a function developer, which approach should you follow to satisfy this security requirement?

  A. Use the Oracle Cloud Infrastructure Console and enter the password in the function configuration section in the provided input field.
  B. Use Oracle Cloud Infrastructure Key Management to auto-encrypt the password. It will inject the auto-decrypted password inside your function container.
  C. Encrypt the password using Oracle Cloud Infrastructure Key Management. Decrypt this password in your function code with the generated key.
  D. All function configuration variables are automatically encrypted by Oracle Functions.
  A. Use the Oracle Cloud Infrastructure Console and enter the password in the function configuration section in the provided input field.

  ---

  Passing Custom Configuration Parameters to Functions

  he code in functions you deploy to Oracle Functions will typically require values for different parameters. Some pre-defined parameters are available to your functions as environment variables. But you'll often want your functions to use

  parameters that you've defined yourself. For example, you might create a function that reads from and writes to a database. The function will require a database connect string, comprising a username, password, and hostname. You'll

  probably want to define username, password, and hostname as parameters that are passed to the function when it's invoked.

  Using the Console

  To specify custom configuration parameters to pass to functions using the Console:

  Log in to the Console as a functions developer.

  In the Console, open the navigation menu. Under Solutions and Platform, go to Developer Services and click Functions.

  Select the region you are using with Oracle Functions. Oracle recommends that you use the same region as the Docker registry that's specified in the Fn Project CLI context (see 6. Create an Fn Project CLI Context to Connect to Oracle

  Cloud Infrastructure). Select the compartment specified in the Fn Project CLI context (see 6. Create an Fn Project CLI Context to Connect to Oracle Cloud Infrastructure). The Applications page shows the applications defined in the

  compartment. Click the name of the application containing functions to which you want to pass custom configuration parameters:

  To pass one or more custom configuration parameters to every function in the application, click Configuration to see the Configuration section for the application. To pass one or more custom configuration parameters to a particular function,

  click the function's name to see the Configuration section for the function. In the Configuration section, specify details for the first custom configuration parameter:

  Key: The name of the custom configuration parameter. The name must only contain alphanumeric characters and underscores, and must not start with a number. For example, username Value: A value for the custom configuration parameter.

  The value must only contain printable unicode characters. For example, jdoe

  Click the plus button to save the new custom configuration parameter. Oracle Functions combines the key-value pairs for all the custom configuration parameters (both application-wide and function-specific) in the application into a single,

  serially-encoded configuration object with a maximum allowable size of 4Kb. You cannot save the new custom configuration parameter if the size of the serially-encoded configuration object would be greater than 4Kb. (Optional) Enter

  additional custom configuration parameters as required.

• Question 50:

  A pod security policy (PSP) is implemented in your Oracle Cloud Infrastructure Container Engine for Kubernetes cluster Which rule can you use to prevent a container from running as root using PSP?

  A. NoPrivilege
  B. RunOnlyAsUser
  C. MustRunAsNonRoot
  D. forbiddenRoot
  C. MustRunAsNonRoot

  ---

  # Require the container to run without root privileges.

  rule: 'MustRunAsNonRoot'

  Reference: https://kubernetes.io/docs/concepts/policy/pod-security-policy/