Explanation
In the given scenario, the developer should use the approach of creating an authorizer function using token-based authorization. Token-based authorization is a commonly used approach for authenticating API requests. It involves generating and issuing tokens to API callers, which they can then include in the requests they make to the API. The tokens serve as proof of authentication and are validated by the server to ensure the caller's identity and access rights. By creating an authorizer function using token-based authorization, the developer can implement a custom scheme that accepts string-based parameters from the API caller. This allows the developer to define their own authentication logic and validate the provided tokens according to their requirements. The authorizer function can be configured in the OCI API Gateway to be invoked before forwarding the request to the web application. It will perform the necessary token validation and authenticationchecks, allowing only authorized requests to access the protected resources of the web application.

The correct answer is: "Multiple microservices can run in one process." The statement that is FALSE about microservices is: "Multiple microservices can run in one process." Microservices are designed to be independent and autonomous services that can be deployed, scaled, and managed separately. Each microservice typically runs as its own separate process. This separation allows for loose coupling and independent scalability of individual services. Running multiple microservices in a single process would violate the fundamental principle of microservices architecture, which emphasizes the isolation and independence of services. Combining multiple microservices into a single process would tightly couple them, making it difficult to independently manage, scale, and update each service. The other statements provided are true about microservices: It is fairly common for microservices to communicate with HTTP: Microservices often communicate with each other using lightweight protocols like HTTP/REST. This allows for interoperability, flexibility, and ease of communication between microservices. Microservices are typically designed around business capabilities: Microservices architecture advocates designing services based on specific business capabilities or functionalities. Each microservice focuses on a specific business domain or task, enabling modular and scalable development. They are independently deployable: Microservices are designed to be independently deployable units. This means that each microservice can be developed, tested, deployed, and updated separately without affecting other services. This flexibility allows for faster development cycles and more efficient scalability.

Explanation
Fn Project is the open source engine that is used by OCI to power Oracle Functions1. Fn Project is an open source, container native, serverless platform that can be run anywhere - any cloud or on-premises1. Fn Project is easy to use, extensible, and performant. You can download and install the open source distribution of Fn Project, develop and test a function locally, and then use the same tooling to deploy that function to Oracle Functions1.Verified References: Overview of Functions

Visibility timeout is the concept in OCI Queue that is responsible for hiding a message from other consumers for a predefined amount of time after it has been delivered to a consumer1. The visibility timeout can be set at the queue level when creating a queue, or it can be specified when consuming or updating messages1. If a consumer is having difficulty successfully processing a message, it can update the message to extend its invisibility1. If a message's visibility timeout is not extended, and the consumer does not delete the message, it returns to the queue1. Verified Reference: Overview of Queue

Explanation
Idle-timeout is the parameter that is used to configure the time period during which an idle function will remain in memory before Oracle Functions removes its container image from memory2. The idle-timeout parameter is specified in seconds and can be set when creating or updating a function2. The default value for idle-timeout is 30 seconds and the maximum value is 900 seconds (15 minutes)2. If a function has the
--provisioned-concurrency option enabled, the idle-timeout parameter is ignored and the function instances are always kept in memory3.Verified References: Creating Functions, Provisioned Concurrency