1Z0-997-25 Question 15
Select 2You have developed a serverless function in Oracle Functions that processes orders for your e-commerce application. You want to expose this function securely to external clients via Oracle API Gateway, minimize operational overhead, and allow rolling updates without downtime. Which two approaches would help you achieve these goals?
- A
Configure an API Gateway route with a function backend that references the function� OCID to invoke it securely.
- B
Enable concurrency-limiting settings directly in the Oracle Functions service to prevent overutilization.
- C
Expose the function publicly by retrieving the function invocation endpoint from Oracle Functions and sharing it with clients.
- D
Configure an API Gateway usage plan (for example, requiring an API key or JWT token) to control and secure access.
- E
Create multiple function versions in the same application and then swap traffic between them using the API Gateway routing configuration.
Show answer and explanation
Correct answers: A, D
Explanation
By leveraging an API Gateway route configured with a function backend (referencing the function� OCID) and controlling access with usage plans or token-based authentication, you meet the requirements for secure external access and minimal operational overhead. Oracle� best practices recommend using API Gateway as the front end for serverless deployments to centralize security, logging, and lifecycle management. For rolling updates, you would typically deploy new versions of your function and update the gateway routes, rather than relying on a simple version swap in a single function. For more details, refer to Oracle Functions Official Documentation and API Gateway Best Practices.
- A. Correct.
Correct. When you configure an API Gateway route with a function backend, you specify the function� OCID and other required details. This method securely invokes the function and avoids exposing it directly to the public internet. It also helps centralize access control and logging through the gateway.
- B. Incorrect.
Incorrect. Oracle Functions does not provide direct concurrency-limiting settings in the dashboard for function execution. While Oracle Functions scales automatically, per-function concurrency is not configured by an explicit limit. You typically rely on backend configurations like VCN scaling or policy-based constraints instead.
- C. Incorrect.
Incorrect. Simply exposing the Oracle Functions endpoint publicly without the API Gateway can lead to security gaps and operational overhead, as the function would not benefit from the gateway� routing, API keys, usage plans, or logging features.
- D. Correct.
Correct. With the API Gateway� usage plans or token-based authentication, you can securely manage which clients have the right to invoke your function. This fulfills the requirement of controlling access and ensuring only authorized users can call the function.
- E. Incorrect.
Incorrect. Although you can create function versions, Oracle Functions does not provide a built-in traffic-splitting or canary deployment mechanism at the function version level. While you could deploy new versions in separate Function Apps or with different function names, the correct approach would involve additional configuration (e.g., replicating the function and changing the gateway route). The answer as stated doesn�t fully cover a reliable traffic swap scenario without downtime.