DO241 Cloud-Native API Administration with Red Hat 3scale API Management with Exam — Lesson 1: 3scale Architecture, Tenants, Products, Backends, Services, and API Discovery

Learning Objectives

• Interpret the architecture, dependencies, and expected behavior of 3scale architecture, tenants, and products.
• Apply backends and API discovery while preserving reviewable technical evidence.
• Recognize and correct the risk where a hidden prerequisite causes the first configuration step to produce an incomplete result.

Detailed Topics

• 3scale architecture: apply the concept to an API platform team publishing and governing enterprise APIs through 3scale, record the relevant settings or decisions, and explain the operational consequence.
• tenants: apply the concept to an API platform team publishing and governing enterprise APIs through 3scale, record the relevant settings or decisions, and explain the operational consequence.
• products: apply the concept to an API platform team publishing and governing enterprise APIs through 3scale, record the relevant settings or decisions, and explain the operational consequence.
• backends: apply the concept to an API platform team publishing and governing enterprise APIs through 3scale, record the relevant settings or decisions, and explain the operational consequence.
• API discovery: apply the concept to an API platform team publishing and governing enterprise APIs through 3scale, record the relevant settings or decisions, and explain the operational consequence.

Instructor Demonstration

The instructor demonstrates 3scale architecture, tenants, products, backends, services, and api discovery by tracing the relevant architecture, commands, configuration, messages, and evidence. The walkthrough highlights how a hidden prerequisite causes the first configuration step to produce an incomplete result and shows how to isolate the cause without masking dependent issues.

Hands-On Exercise

Build a baseline and capture the initial state for 3scale Architecture, Tenants, Products, Backends, Services, and API Discovery. Add verified outcomes to the 3scale API product configuration, policy and security evidence, portal setup, and operations runbook.

1. Confirm the scope, versions, access, dependencies, and success criteria.
2. Perform the workflow while recording commands, settings, output, and platform events.
3. Test one expected case and one controlled exception specific to this lesson.
4. Retest the correction and document ownership, rollback, and follow-up actions.

Scenario Analysis

• Identify which dependency most strongly influences 3scale architecture in the stated scenario.
• Compare two approaches for backends and explain the security, reliability, and support trade-offs.
• Decide what evidence must be retained in the 3scale API product configuration, policy and security evidence, portal setup, and operations runbook before operational acceptance.

Troubleshooting Guidance

Begin with the first observable difference from the expected result. Check architecture, access, dependencies, and starting conditions separately, then correlate logs, events, commands, and configuration history. Do not accept the initial assumption that a hidden prerequisite causes the first configuration step to produce an incomplete result; confirm the cause with a reproducible retest.

Validation Checklist

• The required architecture, access, dependencies, and starting conditions were checked and recorded.
• The normal path and a course-specific exception were tested.
• The 3scale API product configuration, policy and security evidence, portal setup, and operations runbook links conclusions to commands, configuration, logs, or other objective evidence.
• Corrective actions, rollback steps, ownership, and handover notes are complete.

Lesson Outcome

Learners can apply 3scale Architecture, Tenants, Products, Backends, Services, and API Discovery, explain the observed Red Hat platform behavior, and support the result with a reviewable 3scale API product configuration, policy and security evidence, portal setup, and operations runbook.