Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Cloud Digital Leader practice bank has an additional 3,070 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
A financial services company wants to create a new revenue stream and expand its market reach by allowing external developers to integrate its payment processing services into third-party applications. Using Apigee API Management, the company needs to:
Which approach should the company implement in Apigee to meet these requirements?
An API proxy acts as an abstraction layer or facade in front of backend services to manage traffic routing, security, and mediation policies. The VerifyAPIKey policy is an authentication policy attached to an API proxy that checks incoming requests for a valid API key and determines if a request is monetizable by checking for an active published rate plan. Manual registration is an administrative process where potential developers must contact the organization directly to have their accounts and keys created and sent to them.
VerifyAPIKey policy only authenticates keys and checks for an active rate plan; it does not define billing currencies, transaction fees, or revenue-sharing percentages. Financial terms must be defined within a rate plan associated with an API product.VerifyAPIKey or OAuth2) verify identity, MonetizationLimitsCheck verifies product subscriptions and wallet balances, and rate plans define pricing rules.This approach would only be partially applicable if the organization wanted to restrict API access to a small number of vetted partners through a manual registration workflow, and needed to attach the VerifyAPIKey policy to authenticate incoming proxy calls.
A common misconception is that business rules like pricing tiers and daily request quotas must be hardcoded into individual API proxies. By separating the technical facade (API proxy) from the commercial bundle (API product and rate plan), Apigee lets organizations adjust pricing and access limits without changing proxy configurations.
AppGroups in Apigee allow organizations to group multiple app developers together to manage shared API product subscriptions, shared billing wallets, and collaborative client app ownership. Postpaid billing is a monetization account type where app developers do not make upfront payments and are instead billed after consuming monetized API products.
PREPAID and POSTPAID billing types, prepaid wallet balance top-ups, manual balance adjustments, and revenue-sharing calculations.Configuring AppGroups would be appropriate if the company wanted to allow teams of developers within a partner organization to share a single API product subscription and a shared PREPAID or POSTPAID account balance while still authenticating every API call with an API key.
When API providers want automated upfront payment collection rather than handling postpaid invoicing externally, they typically use prepaid billing combined with a Drupal-based developer portal, where setup fees, recurring charges, and per-transaction costs are deducted directly from the developer's prepaid wallet.
In Apigee API Management, an API product is a collection of API proxies combined with access limits (quotas) and key approval methods that are offered to app developers as a package. A rate plan attaches to an API product to define the billing configuration, fees, and charges incurred when developers use the bundled APIs. An Apigee developer portal serves as a self-service website where internal and external developers can discover API documentation, register client applications, and manage their subscriptions.
VerifyAPIKey, MonetizationLimitsCheck, and Quota attached to the API proxies to validate active subscriptions, check prepaid wallet balances, and enforce traffic limits.Combining API products, rate plans, and a developer portal provides a unified framework for both API monetization and developer ecosystem cultivation. Rather than building custom billing pipelines or deploying redundant infrastructure for each customer tier, the company can centrally govern traffic, monetize transactions, and onboard third-party innovators.
SmartDocs is a documentation feature on the Apigee Developer Services portal that makes API documentation fully interactive, enabling portal users to read about an API, send live requests, and view live responses. The Apigee runtime plane is a set of containerized runtime services in a Kubernetes cluster that processes all incoming API traffic, enforces policies, and communicates with backend services.
Quota policy to the API proxies.Implementing SmartDocs would be the right choice if the specific requirement was solely to publish interactive reference documentation on an Apigee developer portal so developers could read API specifications and send live test requests.
Growing an external developer ecosystem requires balancing self-service convenience with strict centralized control. While features like SmartDocs and developer portals empower third-party developers to learn and onboard quickly, the API provider maintains full authority over quotas, security policies, and rate plans.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated