Why Study with PlanetCert?
The Latest Questions
Practice questions and exam topics aligned with the current exam objectives.
Detailed Explanations
Go beyond the answer. Master the material with comprehensive learning and professional explanations for every concept.
AI-Powered Insights
Personalized preparation guidance that adapts to your performance and identifies weak spots automatically.
Exam Information
Official specifications published by Red Hat
Exam Format
Registration
Validity
Skills this practice test covers
- Set rate limits and pricing rules on an application plan, then assign the plan to applications.
- Define methods, metrics and mapping rules so that each call counts against the right method.
- Choose API key, App_ID and App_Key pair, or OpenID Connect authentication for an API product.
- Connect the APIcast gateway to a private API, then promote the configuration from staging to production.
- Turn an OpenAPI document into interactive ActiveDocs in the Developer Portal.
- Issue, charge and cancel invoices after setting billing periods and credit card policies.
Explore related topics
EX240 exam content
10 domains · 26 topics · 156 questions
Access Control15 questions
Application plans decide what each consumer application may call, how often and at what price. Candidates create and maintain plans, then add the limits and pricing rules that 3scale enforces.
Skills tested
- Create an application plan and decide whether developers can see and choose it.
- Set a limit on a method or metric for a period, such as calls per day.
- Add pricing rules that charge for calls to a method or metric.
- Switch plan features on or off to tell a free plan from a paid one.
Questions by topic
- Configure limits and pricing rules6
- Create and maintain application plans9
Accounts27 questions
Every API consumer in 3scale is an account that holds users and applications. Candidates manage those accounts, their credentials and invitations, the groups users belong to, and the details that the signup form collects.
Skills tested
- Create and update developer accounts and their users in the 3scale Admin Portal.
- Send user invitations and track whether each one has been accepted.
- Use group memberships to decide which restricted Developer Portal sections an account can open.
- Add custom fields to the signup form and decide which ones are required.
- Move an application between states, such as live and suspended, or change its plan.
Questions by topic
- Create and update user accounts10
- Maintain application states and plans4
- Send user invitations4
- Configure usage rules and information gathered from users3
- Configure user credentials4
- Maintain group memberships2
Analytics13 questions
3scale counts the calls that pass through its gateway and shows the results on its Analytics pages. Candidates read usage, averages and top applications, and they use alerts, traffic and integration errors to find problems.
Skills tested
- Chart the usage of a metric or method over a chosen period.
- Find the top applications for a product and compare their traffic.
- Configure alerts that fire when an application nears or passes its usage limits.
- Use the integration errors list to spot problems such as bad credentials in calls.
Questions by topic
- Analyze alerts, traffic, and integration errors8
- Monitor usage, averages, and top applications5
API Authentication20 questions
This domain is about proving which application makes each call. Candidates choose the authentication mode for a product, from a single API key to an App_ID and App_Key pair or OpenID Connect, and they configure access tokens.
Skills tested
- Explain when an API key, an App_ID and App_Key pair, or OpenID Connect fits best.
- Set where the gateway looks for credentials: in a header or in the query string.
- Link a product to an OpenID Connect identity provider so that APIcast checks each JSON Web Token.
Questions by topic
- Provide access control using OpenID Connect8
- Understand API credentials7
- Configure access tokens5
API Documentation6 questions
Developers need accurate documentation before they call an API. This domain asks candidates to configure ActiveDocs from a document that follows the OpenAPI standard, so that the Developer Portal shows documentation that developers can try out.
Skills tested
- Create an ActiveDocs specification from an OpenAPI document and link it to its product.
- Publish the specification so that developers can send test calls from the Developer Portal.
- Update the specification when the API's paths or parameters change.
Questions by topic
- Configure ActiveDocs using OpenAPI standards6
Billing13 questions
3scale can bill API consumers for the plans and calls they use. Candidates set credit card policies and billing periods, update a user's billing state, add invoice items, and issue, charge or cancel invoices.
Skills tested
- Require a credit card before a developer can use a paid plan.
- Set the billing period and the day on which invoices are charged.
- Add line items to an invoice, then issue it and charge it.
- Cancel an invoice that should not be paid.
Questions by topic
- Configure credit card policies1
- Issue, charge, and cancel invoices4
- Configure billing periods3
- Configure limits and pricing rules3
- Configure billing details and invoice items2
Developer Portal13 questions
The Developer Portal is the public website where API consumers sign up, read documentation and find their keys. Candidates customize its pages and configure its settings.
Skills tested
- Edit portal pages, layouts and partials that are built with Liquid templates.
- Change the portal's CSS and HTML to match a company's style.
- Configure the signup settings and the legal terms that developers must accept.
Questions by topic
- Customize developer portal10
- Configure portal settings3
Service Discovery8 questions
3scale can find APIs that already run as services in the OpenShift cluster beneath it. Candidates add such a service to 3scale straight from the cluster.
Skills tested
- Import a service that runs in the underlying OpenShift cluster into 3scale.
- Check the product and backend that an imported service creates before it goes live.
Questions by topic
- Add services from an underlying OpenShift cluster8
Product Definition20 questions
A product's methods and metrics are what 3scale counts, limits and prices. Candidates configure them, which sets up the units that application plans and analytics depend on.
Skills tested
- Add a method for each API operation under the default Hits metric.
- Create a custom metric when some usage must be counted apart from Hits.
- Write mapping rules that match an HTTP verb and path pattern to a method or metric.
Questions by topic
- Configure methods and metrics20
Service Integration21 questions
This domain connects 3scale to the API it protects. Candidates point the APIcast gateway at a private API, promote the configuration from staging to production, and build custom policies that change how requests are handled.
Skills tested
- Set the private backend address that APIcast forwards approved calls to.
- Test a change on the staging gateway before promoting it to production.
- Add, order and configure policies in the APIcast policy chain.
- Write a custom policy in Lua when no built-in policy does the job.
Questions by topic
- Create and maintain custom service policies8
- Promote API gateway to staging and production7
- Configure API gateway to point to private API6
Requirements
- No formal prerequisites: anyone can book the exam.
- Recommended: the Cloud-native API Administration with Red Hat 3scale API Management course (DO240), or the same work experience.
- Recommended: OpenShift administration knowledge at the level of Red Hat OpenShift Administration II (DO280).
- Recommended: familiarity with testing REST APIs.
About the EX240 exam
EX240 is a hands-on Red Hat exam for developers, administrators and architects who run enterprise APIs on Red Hat 3scale API Management. Instead of multiple-choice questions, candidates complete tasks in a live 3scale environment, and Red Hat checks the finished configuration. The tasks span application plans, developer accounts, API authentication, billing, the Developer Portal and the APIcast gateway. Passing earns the Red Hat Certified Specialist in API Management certification, which counts toward Red Hat Certified Architect (RHCA).
The real exam is a lab, so the PlanetCert practice test checks the knowledge behind each task: what a setting does and when to use it. Accounts has the most practice questions, followed by Service Integration, API Authentication and Product Definition. The explanations separate ideas that are easy to mix up, such as a method versus a metric, or a single API key versus an App_ID and App_Key pair. Flashcard mode helps with the many named settings, such as application states and authentication modes. Brainy AI Assistant can explain how a mapping rule decides which method a call counts against.
How to earn the certification
- Earns
- Red Hat Certified Specialist in API ManagementSpecialist
The certification stays current for three years.
How to prepare for EX240
- 1
Practise in a live 3scale lab
Every EX240 task is done live, so study time belongs in a working 3scale installation on OpenShift. Repeat each objective there until it needs no notes.
- 2
Wire one API from end to end
Define methods and mapping rules, choose an authentication mode, point APIcast at a private API and promote it to production. This one path ties together Product Definition, API Authentication and Service Integration.
- 3
Rehearse accounts and billing chores
Create an account, invite a user, add a signup field and suspend an application. Then take a test account through a billing period and its invoices, because Accounts has the most practice questions.
- 4
Search the offline documentation fast
Red Hat supplies a local copy of the 3scale documentation and no internet access. Practise finding the pages on policies, ActiveDocs and OpenID Connect quickly.
- 5
Close with the EX240 practice test
Take the practice test in Timed Mode once the lab work feels solid. Redo every missed task in the lab, and ask Brainy AI Assistant why the chosen setting was wrong.
Start a timed EX240run
Red Hat's course for this exam is Cloud-native API Administration with Red Hat 3scale API Management (DO240). Red Hat also recommends Red Hat OpenShift Administration II: Operating a Production Kubernetes Cluster (DO280) or the same knowledge.
Who EX240 is for
- Application developers in DevOps roles who publish and secure their company's APIs with 3scale.
- Administrators who run 3scale on OpenShift and keep its gateways, accounts and billing working.
- Architects who plan how an organization exposes, protects and charges for its APIs.
- Holders of RHCE who are adding specialist certifications on the way to RHCA.
Typical job titles: API developer · DevOps engineer · API platform administrator · Integration architect · OpenShift administrator
EX240 glossary
17 terms from the exam objectives and the vendor's official material, each defined in a sentence.
- 3scale Admin Portal
- The web console where an API provider sets up products, application plans, accounts, billing and analytics.
- ActiveDocs
- The 3scale feature that turns an OpenAPI document into interactive documentation in the Developer Portal.
- API Key (user_key)
- A single secret string that both identifies an application and authenticates it, sent by default as user_key.
- APIcast gateway
- The 3scale API gateway that checks each call's credentials and limits before passing the call to the API.
- App_ID and App_Key pair
- An authentication mode in which an application ID names the application and a separate key proves it is genuine.
- Application plans
- Sets of rules that decide what an application may call, how often, and at what price.
- Application states (live, suspended, pending)
- The status of an application in 3scale: live and able to make calls, suspended, or pending approval.
- Custom policies
- Lua modules that change how APIcast handles a request when no built-in policy does the job.
- Developer Portal
- The 3scale website where API consumers sign up, read documentation and get the credentials for their applications.
- Hits metric
- The default 3scale metric that counts every API call, with each method counted beneath it.
- JSON Web Tokens (JWT)
- Signed tokens that carry claims about a user or client; APIcast checks them when a product uses OpenID Connect.
- Liquid templates
- The template language of the Developer Portal, used to build pages that show account data such as keys.
- Mapping rules
- Rules that match a request's HTTP verb and path pattern to a method or metric, so that 3scale counts the call.
- OpenAPI Specification (OAS)
- A standard, machine-readable format that describes an API's paths, parameters and responses.
- OpenID Connect
- An identity layer on top of OAuth 2.0 in which an identity provider issues tokens that the gateway then checks.
- Pricing rules
- Rules on an application plan that set what each call to a method or metric costs.
- Service Discovery
- The 3scale feature that finds API services in the underlying OpenShift cluster so that they can be imported.
Related practice tests
- EX378Red Hat Certified Cloud-native Developer exam
- EX294Red Hat Certified Engineer (RHCE) exam
- EX280Red Hat Certified OpenShift Administrator
- EX288Red Hat Certified OpenShift Application Developer
- EX210Red Hat Certified Specialist in Cloud Infrastructure exam