Oracle Updated 1z0-1084-26 Exam Questions and Answers by cadi

Explanation

The correct answer is: " read only. " The layers of a Docker image are read-only. Once a layer is created, it cannot be modified. Each layer represents a Dockerfile instruction, and it is stacked on top of the previous layer, forming a stack of immutable layers. These layers are designed to be read-only to ensure consistency and integrity of the image. When a Docker image is built, each instruction in the Dockerfile creates a new layer. Each layer represents the changes made by that instruction relative to the previous layer. The layers are stacked on top of each other to form the complete image. This layer-based approach allows for efficient storage and distribution of Docker images. Because the layers are read-only, any changes or modifications to the image result in the creation of new layers rather than modifying the existing ones. This immutability ensures that each layer remains intact and preserves the integrity of the image. It also enables Docker ' s caching mechanism, where previously built layers can be reused if the corresponding instructions haven ' t changed, speeding up the image build process. The other options mentioned, such as " write only, " " write once, " " movable, " and " read mostly, " do not accurately describe the permission associated with Docker image layers. Docker image layers are specifically designed to be read-only.

The Word source identifiesLongest path matchas the answer, meaning the more specific matching route takes precedence when a request could satisfy multiple path patterns. This is consistent with the general routing principle that more specific path patterns take precedence over broader prefixes. Oracle ' s current OCI API Gateway documentation confirms that deployment routes are defined using URL path patterns and that path parameters and wildcard segments can be used for matching requests to backends. However, the currently published OCI API Gateway pages retrieved for verification do not explicitly state a universal “longest path match” precedence rule for overlapping deployment routes. Therefore, C is the answer recorded in the supplied source, but this particular rule is not stated verbatim in the current OCI API Gateway documentation located during verification.

Oracle ' s documented API Gateway-to-Functions integration uses a dynamic group representing the API Gateway and an IAM policy granting that dynamic group use functions-family in the compartment containing the target Function. The use verb provides the operational permission necessary for invocation without granting unnecessary administrative control. manage functions-family would be excessively privileged because it includes lifecycle management capabilities. The read and inspect verbs are insufficient for executing a Function and, in options C and D, are also scoped to the wrong compartment. Because the authorizer resides in secure-auth-compartment, authorization must apply there. Consequently, A implements the Oracle-documented pattern and satisfies least privilege for API Gateway invocation of the custom authorizer Function.

OCI API Gateway supports the following authentication methods for accessing an API deployment3:

HTTP Basic: The client sends a username and password with each request. The credentials are validated against a user database in Oracle Identity Cloud Service (IDCS).

API Key: The client sends an API key with each request. The API key is validated against a list of keys stored in IDCS or OCI Vault.

OAuth: The client obtains an access token from an authorization server (such as IDCS) and sends it with each request. The access token is validated against the authorization server and optionally checked for required scopes.

JWT Token: The client obtains a JSON Web Token (JWT) from an identity provider (such as IDCS or OCI IAM) and sends it with each request. The JWT is validated against the identity provider’s public key and optionally checked for required claims. SAML Token is not a valid authentication method for accessing an OCI API Gateway deployment. SAML is an XML-based standard for exchanging authentication and authorization data between different parties, such as a service provider and an identity provider4. SAML tokens are typically used for web browser single sign-on (SSO) scenarios, not for API access4.