Managing APIs with Apigee u0026 API Gateway Quiz Quiz

Explore key concepts of managing APIs with API gateways, including security, traffic shaping, and developer management. This quiz is designed to assess your understanding of best practices and fundamentals for efficient and secure API operations.

  1. Traffic Quotas Scenario

    When setting up a quota policy on an API, which action best limits each client's requests to 1,000 per day, even if they attempt to exceed this limit with automated scripts?

    1. Using a quota policy with a per-client identifier set to 1,000 per day
    2. Enabling only basic authentication
    3. Setting a per-minute spike arrest for the API
    4. Assigning caching to reduce backend load

    Explanation: A quota policy with a per-client identifier and a daily limit directly enforces a cap of 1,000 requests per client per day, regardless of script usage. Caching helps with performance but does not enforce usage limits. Basic authentication only controls access and does not address request volumes. Spike arrest limits requests in short bursts but does not ensure a firm daily limit.

  2. API Security Choices

    Which approach is most effective for securing an API from unauthorized use when sharing public endpoints?

    1. Using verbose error messages
    2. Reducing payload size in API responses
    3. Optimizing server-side data parsing
    4. Implementing API key verification and validation

    Explanation: API key verification ensures only approved clients can access the API, making it a fundamental security step. Reducing payload size is a performance optimization, not a security measure. Verbose error messages can expose sensitive details and should be avoided. Optimizing data parsing improves efficiency but does not control access.

  3. Versioning Strategies in APIs

    What is the primary benefit of using URL-based versioning such as /v1/products for API endpoints?

    1. It allows both older and newer versions of the API to coexist and be consumed
    2. It automatically increases API response time
    3. It enforces data encryption in transit
    4. It obfuscates endpoint logic from attackers

    Explanation: URL-based versioning helps maintain backward compatibility by allowing clients to access different API versions concurrently. It does not inherently affect response time, which depends on other factors. Obfuscating endpoint logic is not achieved by adding versioning. Data encryption relates to transport protocols, not versioning.

  4. Developer Access Management

    In a scenario where a company wants to manage third-party developer access to its APIs, which feature should be configured to control and track usage for each external developer?

    1. Configuring static IP filtering for all users
    2. Disabling logging for external endpoints
    3. Enabling JSON-only payloads
    4. Assigning individual API keys to developers

    Explanation: Giving unique API keys to each developer allows monitoring and controlling API usage per developer. Disabling logging would reduce visibility and tracking capability. IP filtering controls access based on location but is less flexible for individual developer identity. Enforcing JSON-only payloads addresses data formats, not access or usage control.

  5. API Gateway Monitoring

    Which built-in feature of most API gateways is essential for identifying unusual traffic patterns that might indicate misuse or attacks?

    1. Manual code review of API consumers
    2. Excluding POST requests from endpoints
    3. Traffic analytics and logging
    4. Static error responses only

    Explanation: Traffic analytics and logging help detect anomalies by providing visibility into usage patterns, which is key for security monitoring. Static error responses do not provide insights into traffic behaviors. Manual code review inspects clients but is not practical for real-time monitoring. Excluding POST requests constrains functionality and is not related to monitoring.