Prepare and test your skills

Prepare and test your skills

Security, Governance, and Operational Visibility describes how Apigee gives a business one control point for protecting APIs, controlling access, and understanding API use. Apigee API Management (opens in a new tab) is Google Cloud's native platform for building, managing, and securing APIs. It places an API proxy (opens in a new tab) layer between backend services and client apps, so traffic from internal or external clients passes through Apigee's runtime services. Apigee consists of Apigee services (opens in a new tab) for creating, managing, and deploying proxies, and an Apigee runtime of containerized services in a Google-maintained Kubernetes cluster. Google Cloud supplies identity management, logging, analytics, metrics, and project management, while backend services supply runtime data to the proxies. This structure supports REST, gRPC, SOAP, and GraphQL APIs from one place.
Security at the API proxy layer means clients call a public proxy instead of calling the backend service directly. The API proxy maps a public HTTP endpoint to a backend service, and Apigee handles the security and authorization tasks that protect that service. Policies attached to the proxy can add security, rate limiting, quotas, data mediation, extensions, custom code, conditional logic, fault handling, and caching without changing the backend. Apigee also provides keystore management so a team can configure the keystore and truststore for TLS handshakes between Apigee and the backend.
Apigee comes in two deployment flavors that change where security boundaries sit:
| Apigee flavor | Where runtime runs | Where management runs | Data boundary |
|---|---|---|---|
| Apigee | Hosted by Apigee in the cloud | Apigee maintains the environment | Cloud-hosted |
| Apigee hybrid | On-premises or a cloud provider of choice | Apigee's cloud | API traffic and data stay within enterprise-approved boundaries |
In a private architecture, Apigee is provisioned in a Google Cloud project, and its runtime is peered in a tenant project using VPC Network Peering. Instead of sending data over the internet, Apigee can use a private connection to a data center through Cloud Interconnect, forward requests to GKE backends through internal IP addresses, and send requests to third-party services through Apigee NAT IP address provisioning.
Governance with API products and developer portals is how Apigee controls which developers can use which APIs. An API product is a bundle of one or more API proxies plus a service plan, and that service plan can set access limits, provide security, allow monitoring and analytics, and add other features. API products are the central mechanism Apigee uses for authorization and access control. Multiple API products can share the same API proxy, so different audiences can receive different levels of access.
An Euler diagram showing three API products (A, B, and C) as overlapping regions over four API proxies. All three products include API proxy 3, product A also includes proxy 1, and product C also includes proxies 2 and 4, illustrating that multiple API products can share the same proxy.
The main governance building blocks are:
For example, a customer mobile app might be allowed only to perform a POST operation on /v1/payments, while a staff call-center app might be allowed to perform PUT or DELETE operations on /payments to reverse payments. Because developers call the API proxy, they need only the proxy URL, request parameters, authentication credentials, and response format. They do not need to know the backend implementation. This isolation lets the producer change the backend database, host, or implementation while keeping the public API consistent.
Exam tip: API products are the central mechanism for authorization and access control in Apigee; individual API proxies are typically grouped into products rather than exposed directly.
Layered security with Cloud Armor (opens in a new tab), reCAPTCHA, and WAAP adds network and bot protection in front of Apigee. Cloud Armor is part of Google Cloud's global load-balancing infrastructure and provides web application firewall (WAF) capabilities and distributed denial of service (DDoS) protection. WAAP brings together Cloud Armor, reCAPTCHA, and Apigee to protect against DDoS attacks and bots while also providing WAF and API protection. In this layered model, Cloud Armor evaluates traffic at the external Application Load Balancer, reCAPTCHA evaluates whether traffic is legitimate, and Apigee validates API keys or access tokens before forwarding a request to the backend.
The request flow for WAAP with Cloud Armor, reCAPTCHA, and Apigee follows a fixed order:
A sequence showing a client request passing External Load Balancer with Cloud Armor, reCAPTCHA, then Apigee, before reaching backends via internal IPs, Cloud Interconnect, or NAT.
If Apigee determines that API keys or access tokens are not valid, it can send a 403 response code. If the request is legitimate, Apigee forwards it to the backend.
Operational visibility with Apigee API Analytics (opens in a new tab) is deep monitoring of traffic that flows through API proxies. Apigee API Analytics provides detailed monitoring for specific gateway instances and granular data for investigating proxy-level issues within a single environment. It collects default data such as URL, IP, user ID for API call information, latency, and error data. Policies can add custom analytics data such as headers, query parameters, and portions of a request or response extracted from XML or JSON. This information is collected asynchronously from the actual request and response flow, so collection has no effect on API performance.
Apigee API Analytics helps answer questions about traffic trends, popular API methods, top developers, response times, geographic traffic, and revenue generated by transactions. The Apigee UI provides predefined dashboards, including:
Custom reports let a user select metrics, group data by dimensions, filter the data, and display it as a column or line chart. The Analytics API can download raw analytics data, and analytics data can be exported to Google Cloud Storage or BigQuery for further analysis with BigQuery and TensorFlow.
Sharing analytics and data residency control who sees analytics data and where that data is stored. Analytics visibility can be shared with app developers through the Drupal-based developer portal, which includes an optional App Performance page. That page gives developers information about errors their app is seeing, API performance, API availability, and how the app is doing against a quota. Custom reports can also be shared with app developers.
Where analytics data is stored and processed depends on the analytics region selected during provisioning. For analytics regions not in the United States or the European Union, analytics data is stored and processed in the analytics region. For analytics regions in the United States or the European Union, data is stored in the United States or European Union multi-region, respectively, for higher availability. If Apigee is installed with the one-click option, analytics data is stored in the us-west1 region, and that default location cannot be changed.
Business value of centralized API control comes from applying the same security, access, and insight rules across all APIs. Security policies, access limits, and API products apply consistently at the API proxy layer, so backend services can remain unchanged while access is controlled by API key, operation, HTTP method, and quota. Analytics then turns API traffic into operational insight for API teams, app developers, operations teams, and business owners. That insight helps teams improve APIs, plan capacity, and measure the return on API investment.
Legacy Modernization and Business Agility describes how Apigee lets a business expose old systems as modern APIs without rewriting them. Apigee (opens in a new tab) is Google Cloud's native API management platform for building, managing, and securing APIs for any use case, environment, or scale. By placing a proxy layer in front of backend services, Apigee creates an abstraction that decouples complex backends from mobile, web, and partner apps. That decoupling increases operational agility and speed to market.
How the Apigee proxy layer creates abstraction is through a public endpoint that stands in for the backend. The API proxy (opens in a new tab) is a publicly available HTTP endpoint on Apigee that maps to a backend service such as a database, app server, SOA system, or enterprise service bus. Traffic flows from the client app to the API proxy, then from the API proxy to the backend service, and the response flows back through the proxy to the client. All API traffic passes through the Apigee runtime, a set of containerized services that processes each request, while Apigee services (opens in a new tab) provide the tools to create, manage, and deploy the proxies.
A request moves through Apigee in a consistent order:
Because policies and actions run in Apigee and not on the backend server, the underlying backend services can remain unchanged. Apigee supports REST, gRPC, SOAP, and GraphQL, so teams can present one consistent style to developers even when backends use different technologies.
Decoupling backend complexity from frontend delivery means frontend developers depend only on a stable public API. An app developer using an Apigee proxy needs to know only the proxy URL, the required parameters and credentials, and the response format, not how the backend stores data or where it is hosted. The proxy isolates the app from the backend, so a team can change a database, move services to a new host, or shift workloads between a data center and cloud without breaking existing client apps.
A consistent API delivered through Apigee provides three related business benefits:
New capability can also be added at the proxy without touching legacy code, such as data transformation, filtering, authentication, conditional logic, and quotas. This separation lets business teams launch new digital experiences quickly while legacy systems keep running reliably underneath.
Exam tip: Apigee allows backend changes as long as the frontend proxy API stays consistent; client apps keep working because they call the proxy, not the backend directly.
Gaining agility with consistent APIs and hybrid choice comes from reliability, discoverability, and insight working together. Reliability comes from isolation: Apigee executes security and traffic policies at the proxy level, so backend updates do not interrupt client applications. Discoverability comes from a developer portal where internal and external developers find APIs, read documentation, get API keys, and stay informed about updates. Insight comes from security, monitoring, and analytics that track traffic, latency, errors, uptime, and who is using each API.
Apigee supports modernization across hybrid and multi-cloud environments through two deployment flavors:
| Option | Where runtime runs | Traffic and management boundary |
|---|---|---|
| Apigee | Cloud version hosted and maintained by Apigee | Teams focus on building services and defining APIs while Apigee maintains the environment |
| Apigee hybrid (opens in a new tab) | Runtime plane installed on-premises or in a chosen cloud provider, management plane runs in Apigee's cloud | API traffic and data stay confined within enterprise-approved boundaries |
Choose the cloud version when the goal is fastest delivery with Google maintaining the environment, and choose Apigee hybrid when data, compliance, or existing data-center systems require traffic to remain inside approved networks. In both cases, the same proxy abstraction lets an organization modernize step by step, connect legacy and cloud backends behind one interface, and deliver new apps faster.
Monetization and Ecosystem Growth describes how Apigee turns APIs into products that create revenue and attract developers. Apigee API Management (opens in a new tab) helps organizations serve API producers, who build and manage APIs that expose backend services, and API consumers, who use those APIs in client applications. Apigee packages backend services behind API proxies, groups those proxies into API products with service plans, and gives developers a portal to discover and use the APIs. Analytics then shows how APIs are used and how much revenue transactions generate, so producers can grow both the business and the developer community.
API products and service plans are the packaging that controls who can use which APIs. An API product (opens in a new tab) is a bundle of one or more API proxies combined with a service plan. The service plan can set access limits on the proxies, provide security, allow monitoring and analytics, and add other features. API products are the central mechanism Apigee uses for authorization and access control, so they determine which developers can reach which APIs. Multiple API products can share the same API proxy, which lets a producer create different offerings for different audiences. For example, one product might allow access to proxy 1 and proxy 3, while another product allows access only to proxy 3.
An API proxy is the public HTTP endpoint that maps to a backend service. Developers call the proxy instead of the backend, so the producer can change the backend implementation without breaking client apps. Policies attached to the proxy can add security, rate limiting, quotas, data transformation, and other controls. These controls support monetization because they let a producer define what is included in each API product and how much access each consumer receives.
Exam tip: An API proxy is the callable endpoint; an API product is the package of proxies plus a service plan that controls access.
Developer ecosystem and portals are how Apigee helps a producer attract and support app developers. Apigee developer services let an API producer manage the community of app developers that use its services. They also let the producer work with internal and external developers and formalize those relationships with financial models. The producer can onboard developers and create a developer portal where app developers access API documentation, learn about publicly available API products, and manage API keys. This makes APIs discoverable and lowers the effort for developers to start building, which helps expand market reach.
Every Apigee customer can create its own developer portal in the cloud. Apigee supports two portal types: an Integrated portal that can be instantly provisioned, and a Drupal-based portal that enables full customization. The portal is a key part of ecosystem growth because it is where developers discover APIs, register, and stay in sync with updates. When developers can find and use APIs easily, they are more likely to build apps that extend the producer's services and increase speed to market.
Analytics for revenue and ecosystem insight turns API traffic data into business decisions. Apigee API Analytics (opens in a new tab) collects and calculates information that flows through API proxies. Producers can view this data in graphs and charts or download raw data for offline analysis. Analytics helps answer questions such as how API traffic trends over time, which API methods are most popular, who the top developers are, when response time is fastest or slowest, where traffic comes from geographically, and how much revenue transactions generated. These answers help the API team improve APIs, the operations team plan backend resources, and the business owner see how API investment is paying off.
Analytics also strengthens the developer ecosystem by sharing useful data with app developers. The Drupal-based developer portal includes an optional App Performance page that shows developers errors, performance, availability, and quota status for their apps. Producers can also create custom reports and share them with app developers. When developers see how their apps are performing and contributing to the business, they can improve those apps and stay engaged with the API program.
How monetization and ecosystem growth connect is through a loop from product to developer to usage to insight. The producer creates API proxies, groups them into API products with service plans that set access limits, and makes those products available to developers through a developer portal. Developers discover the products, register, obtain API keys, and build apps that call the proxies. As traffic flows through Apigee, analytics measures usage and revenue-related outcomes, and those insights flow back to both the producer and the developers. The producer can adjust products and limits, while developers can improve their apps, which together can create new revenue streams and expand the reach of the API program.
Apigee API Management creates business value by placing an API proxy layer between backend services and client apps so old systems can be exposed as modern APIs without rewriting them. Clients call the public proxy instead of the backend, so a team can change a database, host, or implementation while keeping the public API consistent. This decoupling makes services easy to consume across phones, tablets, browsers, and partner systems and lets teams launch new digital experiences faster while legacy systems keep running.
API products in Apigee API Management are the central mechanism for authorization and access control. An API product is a bundle of one or more API proxies plus a service plan that can set access limits, provide security, and allow monitoring and analytics. Multiple API products can share the same API proxy with different operations, HTTP methods, and quotas, so different audiences receive different levels of access.
Use Apigee when the goal is fastest delivery with Apigee hosting and maintaining the runtime and management environment in the cloud. Use Apigee hybrid when data, compliance, or existing data-center systems require API traffic and data to stay within enterprise-approved boundaries. Apigee hybrid runs the runtime plane on-premises or in a chosen cloud provider while the management plane runs in Apigee's cloud.
A financial services organization uses Apigee API Management across a hybrid environment to expose digital services to partner applications. To strengthen API governance, security, and operational visibility, the organization wants to implement an integrated capability that meets the following requirements:
Which Google Cloud capability should the organization enable?
Last updated