EX240 Sample Questions

EX240 Sample Questions & Answers

Focuses on two tied leaders: configuring user accounts and credentials, and authenticating APIs through OpenID Connect or API keys, plus application plans, usage analytics, billing policies, the developer portal, service discovery, and gateway integration.

Launch the full EX240 simulator →

Showing 6 of 12 free samples.

  1. Question 1Intermediate

    Analytics · Analyze alerts, traffic, and integration errors

    A financial institution requires strict monitoring of their Payment API. They need an alert to be triggered specifically when the API backend returns '5xx' server errors for more than 5% of requests within a 5-minute window. Where should this specific alert be configured in the 3scale Admin Portal?

    Show answer & explanation

    Correct answer: A

    3scale's built-in alerting system is primarily designed for utilization limits (e.g., reaching 80% of a rate limit). It does not natively support complex logic like 'percentage of 5xx errors' alerts directly in the Admin Portal UI. This type of infrastructure monitoring is handled by external tools like Prometheus (which 3scale/OpenShift integrates with) or Grafana.

  2. Question 2Intermediate

    Developer Portal · Customize developer portal

    Which of the following Liquid drops would you use in a Developer Portal template to display the current logged-in user's account name?

    Show answer & explanation

    Correct answer: B

    The current_account drop accesses the account information of the currently logged-in user. current_account.name renders the name of that account.

  3. Question 3Intermediate

    Service Integration · Create and maintain custom service policies

    A developer is creating a custom policy in 3scale to rewrite the URL of incoming requests. They need to ensure this policy executes after authentication but before the request is sent to the upstream backend. Where should this policy be placed in the policy chain?

    Show answer & explanation

    Correct answer: D

    The 'APIcast' policy is typically the final policy in the chain that handles the actual proxying to the upstream backend. Standard authentication (like API Key or OIDC) usually happens implicitly or via specific policies. To rewrite the URL before it goes upstream, the rewrite policy must be placed before the APIcast policy in the chain.

  4. Question 4Intermediate

    Billing · Configure credit card policies

    You are integrating an external payment gateway (e.g., Stripe) with 3scale to monetize your API. After configuring the payment gateway in the Admin Portal, what is the mandatory next step to ensure that users are actually charged for their usage?

    Show answer & explanation

    Correct answer: A

    Simply configuring the gateway is not enough. You must explicitly enable 'Charging Enabled' in the global Billing settings. Without this, 3scale will generate invoices but will not attempt to charge the credit cards stored in the payment gateway.

  5. Question 5Intermediate

    Service Discovery · Add services from an underlying OpenShift cluster

    A developer needs to import a service into 3scale from an underlying OpenShift cluster using the Service Discovery feature. However, the service is not appearing in the 'Import from OpenShift' list in the 3scale Admin Portal. Which of the following is the most likely cause?

    Show answer & explanation

    Correct answer: C

    For 3scale Service Discovery to detect an OpenShift service, the service must be annotated or labeled correctly. Specifically, it requires the label discovery.3scale.net: 'true' (or similar discovery label configuration depending on version) to be exposed to the 3scale discovery mechanism.

  6. Question 6Intermediate

    Product Definition · Configure methods and metrics

    You are defining the metrics for a REST API in 3scale. You want to track usage of the GET /products endpoint separately from POST /products. Which approach correctly implements this?

    Show answer & explanation

    Correct answer: D

    In 3scale, 'Methods' are used to represent specific operations on the API (like GET vs POST) and are typically nested under the 'Hits' metric. You then use Mapping Rules to link the actual HTTP request (Verb + Path) to these specific Methods. This allows 3scale to increment the specific method count as well as the overall 'Hits' count.

Ready for the real thing?

The full EX240 simulator has every exam-style question, timed mode, and instant scoring.

Go to the EX240 simulator →