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

Oracle 1Z0-1084-22 Online Questions & Answers

• Question 11:

  As a cloud-native developer, you have written a web service for your company. You have used Oracle Cloud Infrastructure (OCI) API Gateway service to expose the HTTP backend. However, your security team has suggested that your web

  service should handle Distributed Denial-of-Service (DDoS) attack. You are time-constrained and you need to make sure that this is implemented as soon as possible.

  What should you do in this scenario?

  A. Use OCI virtual cloud network (VCN) segregation to control DDoS.
  B. Use a third party service integration to implement a DDoS attack mitigation,
  C. Use OCI API Gateway service and configure rate limiting.
  D. Re-write your web service and implement rate limiting.
  C. Use OCI API Gateway service and configure rate limiting.

  ---

  Explanation/Reference:

  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 a rate-limiting request policy to an API deployment specification by:

  using the Console editing a JSON file

• Question 12:

  Which header is NOT required when signing GET requests to Oracle Cloud Infrastructure APIs?

  A. date or x-date
  B. (request-target)
  C. content-type
  D. host
  C. content-type

  ---

  Explanation/Reference:

  For GET and DELETE requests (when there's no content in the request body), the signing string must include at least these headers: (request-target) (as described in draft-cavage-http-signatures-08) host date or x-date (if both are included, Oracle uses x-date)

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

• Question 13:

  How do you perform a rolling update in Kubernetes?

  A. kubect1 rolling-update
  B. kubect1 upgrade --image=*image:v2
  C. kubect1 update -c
  D. kubect1 rolling-update --image=image
  A. kubect1 rolling-update

  ---

  Explanation/Reference:

  https://docs.oracle.com/en/cloud/iaas/wercker-cloud/wercm/quickstarts/platforms/kubernetes/

• Question 14:

  You have created a repository in Oracle Cloud Infrastructure Registry in the us-ashburn-1 (iad) region in your tenancy with a namespace called "heyci. Which three are valid tags for an image named "myapp"?

  A. iad.ocir.io/heyoci/myproject/myapp:0.0.1
  B. us-ashburn-l.ocirJo/heyoci/myapp:0.0.2-beta
  C. us-ashburn-l.ocir.io/heyoci/myproject/myapp:0.0.2-beta
  D. us-ashburn-l.ocir.io/myproject/heyoci/myapp:latest
  E. iad.ocir.io/myproject/heyoci/myapprlatest
  F. iad.ocir.io/heyoci/myapp:0.0.2-beta
  G. iad.ocir.io/heyoci/myapp:latest
  A. iad.ocir.io/heyoci/myproject/myapp:0.0.1
  F. iad.ocir.io/heyoci/myapp:0.0.2-beta
  G. iad.ocir.io/heyoci/myapp:latest

  ---

  Explanation/Reference:

  Give a tag to the image that you're going to push to Oracle Cloud Infrastructure Registry by entering:

  docker tag

  where:

  uniquely identifies the image, either using the image's id (for example, 8e0506e14874), or the image's name and tag separated by a colon (for example, acme- web-app:latest).

  is in the format .ocir.io///: where:

  is the key for the Oracle Cloud Infrastructure Registry region you're using. For example, iad. See Availability by Region. ocir.io is the Oracle Cloud Infrastructure Registry name. is the auto-generated

  Object Storage namespace string of the tenancy that owns the repository to which you want to push the image (as shown on the Tenancy Information page). For example, the namespace of the acme-dev tenancy might be ansh81vru1zp.

  Note that for some older tenancies, the namespace string might be the same as the tenancy name in all lower-case letters (for example, acme-dev). Note also that your user must have access to the tenancy.

  (if specified) is the name of a repository to which you want to push the image (for example, project01). Note that specifying a repository is optional (see About Repositories). is the name you want to give the

  image in Oracle Cloud Infrastructure Registry (for example, acme-web-app).

  is an image tag you want to give the image in Oracle Cloud Infrastructure Registry (for example, version2.0.test).

  For example, for convenience you might want to group together multiple versions of the acme-web- app image in the acme-dev tenancy in the Ashburn region into a repository called project01. You do this by including the name of the

  repository in the image name when you push the image, in the format .ocir.io///:. For example, iad.ocir.io/ansh81vru1zp/project01/acme-web-app:4.6.3. Subsequently,

  when you use the docker push command, the presence of the repository in the image's name ensures the image is pushed to the intended repository. If you push an image and include the name of a repository that doesn't already exist, a new

  private repository is created automatically. For example, if you enter a command like docker push iad.ocir.io/ansh81vru1zp/project02/acme-web- app:7.5.2 and the project02 repository doesn't exist, a private repository called project02 is

  created automatically. If you push an image and don't include a repository name, the image's name is used as the name of the repository. For example, if you enter a command like docker push iad.ocir.io/ansh81vru1zp/acme-web-app:7.5.2

  that doesn't contain a repository name, the image's name (acme-web-app) is used as the name of a private repository. https:// docs.cloud.oracle.com/en-us/iaas/Content/Registry/Concepts/registrywhatisarepository.htm

• Question 15:

  Which two "Action Type" options are NOT available in an Oracle Cloud Infrastructure (OCI) Events rule definition?

  A. Notifications
  B. Functions
  C. Streaming
  D. Email
  E. Slack
  D. Email
  E. Slack

  ---

  Explanation/Reference:

  https://docs.cloud.oracle.com/en-us/iaas/Content/Events/Concepts/eventsoverview.htm ACTIONS Event Rules must also specify an action to trigger when the filter finds a matching event. Actions are responses you define for event matches. You set up select Oracle Cloud Infrastructure services that the Events service has established as actions. The resources for these services act as destinations for matching events. When the filter in the rule finds a match, the Events service delivers the matching event to one or more of the destinations you identified in the rule. The destination service that receives the event then processes the event in whatever manner you defined. This delivery provides the automation in your environment. You can only deliver events to certain Oracle Cloud Infrastructure services with a rule. Use the following services to create actions: Notifications Streaming Functions

• Question 16:

  Which two statements accurately describe an Oracle Functions application?

  A. A small block of code invoked in response to an Oracle Cloud Infrastructure (OCI) Events service
  B. A Docker image containing all the functions that share the same configuration
  C. An application based on Oracle Functions, Oracle Cloud Infrastructure (OCI) Events and OCI API Gateway services
  D. A common context to store configuration variables that are available to all functions in the application
  E. A logical group of functions
  D. A common context to store configuration variables that are available to all functions in the application
  E. A logical group of functions

  ---

  Explanation/Reference:

  Applications in the Function services In Oracle Functions, an application is:

  1.

  a logical grouping of functions

  2.

  a common context to store configuration variables that are available to all functions in the application

  When you define an application in Oracle Functions, you specify the subnets in which to run the functions in the application.

• Question 17:

  With the volume of communication that can happen between different components in cloud-native applications, it is vital to not only test functionality, but also service resiliency. Which statement is true with regards to service resiliency?

  A. Resiliency is about recovering from failures without downtime or data loss.
  B. A goal of resiliency is not to bring a service to a functioning state after a failure.
  C. Resiliency testing can be only done in a test environment.
  D. Resiliency is about avoiding failures.
  D. Resiliency is about avoiding failures.

  ---

  Explanation/Reference:

  Resiliency and Availability

  Resiliency and availability refers to the ability of a system to continue operating, despite the failure or sub-optimal performance of some of its components.

  In the case of Oracle Functions:

  The control plane is a set of components that manages function definitions. The data plane is a set of components that executes functions in response to invocation requests. For resiliency and high availability, both the control plane and data plane components are distributed across different availability domains and fault domains in a region. If one of the domains ceases to be available, the components in the remaining domains take over to ensure that function definition management and execution are not disrupted. When functions are invoked, they run in the subnets specified for the application to which the functions belong. For resiliency and high availability, best practice is to specify a regional subnet for an application (or alternatively, multiple AD-specific subnets in different availability domains). If an availability domain specified for an application ceases to be available, Oracle Functions runs functions in an alternative availability domain.

• Question 18:

  Which two handle Oracle Functions authentication automatically?

  A. Oracle Cloud Infrastructure SDK
  B. cURL
  C. Oracle Cloud Infrastructure CLl
  D. Signed HTTP Request
  E. Fn Project CLI
  C. Oracle Cloud Infrastructure CLl
  E. Fn Project CLI

  ---

  Explanation/Reference:

  Fn Project CLI you can create an Fn Project CLI Context to Connect to Oracle Cloud Infrastructure and specify -- provider oracle This option enables Oracle Functions to perform authentication and authorization using Oracle Cloud Infrastructure request signing, private keys, user groups, and policies that grant permissions to those user groups.

• Question 19:

  Which is NOT a valid option to execute a function deployed on Oracle Functions?

  A. Send a signed HTTP requests to the function's invoke endpoint
  B. Invoke from Oracle Cloud Infrastructure CLI
  C. Invoke from Docker CLI
  D. Trigger by an event in Oracle Cloud Infrastructure Events service
  E. Invoke from Fn Project CLI
  C. Invoke from Docker CLI

  ---

  Explanation/Reference:

  You can invoke a function that you've deployed to Oracle Functions in different ways:

  Using the Fn Project CLI.

  Using the Oracle Cloud Infrastructure CLI.

  Using the Oracle Cloud Infrastructure SDKs.

  Making a signed HTTP request to the function's invoke endpoint. Every function has an invoke endpoint.

  Each of the above invokes the function via requests to the API. Any request to the API must be authenticated by including a signature and the OCID of the compartment to which the function belongs in the request header. Such a request is

  referred to as a 'signed' request. The signature includes Oracle Cloud Infrastructure credentials in an encrypted form.

• Question 20:

  You are deploying an API via Oracle Cloud Infrastructure (OCI) API Gateway and you want to implement request policies to control access Which is NOT available in OCI API Gateway?

  A. Limiting the number of requests sent to backend services
  B. Enabling CORS (Cross-Origin Resource Sharing) support
  C. Providing authentication and authorization
  D. Controlling access to OCI resources
  D. Controlling access to OCI resources

  ---

  Explanation/Reference:

  In the API Gateway service, there are two types of policy:

  -

  a request policy describes actions to be performed on an incoming request from a caller before it is sent to a back end

  -

  a response policy describes actions to be performed on a response returned from a back end before it is sent to a caller

  You can use request policies to:

  -limit the number of requests sent to back-end services

  -enable CORS (Cross-Origin Resource Sharing) support

  -provide authentication and authorization