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? (Choose the best answer.)
Click on the arrows to vote for the correct answer
A. B. C. D.D.
https://docs.cloud.oracle.com/en-us/iaas/Content/APIGateway/Concepts/apigatewayoverview.htmOCI API Gateway provides several features to control access and implement security policies. In this question, we need to identify the feature that is NOT available in OCI API Gateway.
A. Limiting the number of requests sent to backend services: OCI API Gateway allows you to limit the number of requests sent to backend services. This can be achieved by setting rate limiting policies, which can be defined based on various criteria such as number of requests per second, minute, or hour, IP address, or user agent.
B. Enabling CORS (Cross-Origin Resource Sharing) support: OCI API Gateway allows you to enable CORS support for your APIs. This can be done by setting CORS policies, which allow you to specify which origins, HTTP methods, and headers are allowed to access your API resources.
C. Providing authentication and authorization: OCI API Gateway provides several options for implementing authentication and authorization, including OAuth 2.0, basic authentication, and custom authentication. These options allow you to control access to your APIs and protect your backend services from unauthorized access.
D. Controlling access to OCI resources: OCI API Gateway allows you to control access to OCI resources such as Compute instances, Block Volumes, and Object Storage buckets. This can be achieved by using IAM policies, which allow you to grant or deny access to specific OCI resources based on user or group permissions.
Therefore, based on the above information, it can be concluded that all the features (A, B, C, and D) are available in OCI API Gateway. Therefore, the answer is none of the above, i.e., none of the options are not available in OCI API Gateway.