01. What does the portal's interactive try-it facility let a consumer do?
a) Call the API from its documentation using their own application's credentials
b) Inspect the assembly to see how each policy processes the request
c) Exercise the API before registering an application, to decide whether to subscribe
d) Test a draft version of the API before the provider publishes it
02. A consumer organization wants to know whether it is close to outgrowing the tier it subscribes to.
What in its own analytics answers that?
a) How often its calls have been refused by the gateway
b) How its consumption compares with that of other organizations on the same Plan
c) How many of its applications are registered against the Product
d) Its own consumption measured against the allowance the Plan grants
03. Where does visibility actually live when a Product is made visible to a group of consumer organizations?
a) On the Product, which may point at a group instead of naming each organization
b) On the catalog, which grants the group access to everything published into it
c) On the group, which lists the Products its members may see
d) On each consumer organization, which records the Products it has been granted
04. A provider must know exactly which companies are consuming before any of them can register an application.
What arrangement gives that?
a) Making every Product visible only to named consumer organizations
b) Turning off self-service sign-up, so consumer organizations are created deliberately
c) Requiring approval on every Plan, so each subscription is decided individually
d) Removing the registration page from the portal theme
05. Which pair of transitions differs precisely in whether existing subscriptions are moved?
a) Deprecating and retiring
b) Publishing and deprecating
c) Superseding and replacing
d) Staging and publishing
06. A portal administrator must decide how much of the API's internal behavior to describe in its documentation.
What is the sound principle?
a) Describe the backend systems, the data stores and the queues involved, so consumers know what they depend on
b) Describe the assembly fully, so consumers can predict how their requests are handled
c) Describe nothing beyond the definition, since it is generated and always current
d) Describe what a consumer must send and can expect back, and no more
07. A partner is removed from a consumer organization group, and its existing subscriptions to a Product visible to that group keep working.
Is that consistent?
a) No, because visibility is what authorizes each call the application makes
b) Yes, because losing sight of a Product does not withdraw access already granted
c) Yes, because removal from a group takes effect only at the next lifecycle transition
d) No, because subscriptions are held by the group rather than by the organization
08. Twelve partner organizations are to receive the same Products, and the list changes as partners join and leave.
What keeps that manageable?
a) Naming all twelve organizations in each Product's visibility settings
b) A catalog for the partners, so everything published there reaches them
c) A consumer organization group, with each Product made visible to the group
d) A Plan the twelve subscribe to, since a Plan is shared across consumers
09. A Product is being replaced, and its consumers must end up on the new version without each of them acting.
What makes that possible?
a) Their subscriptions are migrated onto the new version's Plans
b) The old Product is deprecated, so its consumers move as their subscriptions lapse
c) The new Product is published with the same Plan names, so subscriptions resolve to them
d) The consumers are notified and asked to subscribe to the new version
10. An organization wants the portal to carry its own branding, and also to publish a page of guidance that no theme provides for.
What does each need?
a) Both require a custom module, since the theme cannot be altered once the site exists
b) The theme covers both, since a theme defines the pages as well as their appearance
c) The branding is set on the catalog and the guidance is added to the API documentation
d) The theme governs the branding; a custom page carries the guidance