An organization makes a strategic decision to move towards an IT operating model that emphasizes consumption of reusable IT assets using modern APIs (as defined by MuleSoft).
What best describes each modern API in relation to this new IT operating model?

1. A. Each modern API has its own software development lifecycle, which reduces the need for documentation and automation
2. B. Each modem API must be treated like a product and designed for a particular target audience (for instance, mobile app developers)
3. C. Each modern API must be easy to consume, so should avoid complex authentication mechanisms such as SAML or JWT D
4. D. Each modern API must be REST and HTTP based

Correct Answer: B

Correct Answers:
* 1. Each modern API must be treated like a product and designed for a particular target audience (for instance mobile app developers)
*****************************************

Bottom of Form Top of Form

Once an API Implementation is ready and the API is registered on API Manager, who should request the access to the API on Anypoint Exchange?

1. A. None
2. B. Both
3. C. API Client
4. D. API Consumer

Correct Answer: D

Correct Answer:: API Consumer
*****************************************
>> API clients are piece of code or programs that use the client credentials of API consumer but does not directly interact with Anypoint Exchange to get the access
>> API consumer is the one who should get registered and request access to API and then API client needs to use those client credentials to hit the APIs
So, API consumer is the one who needs to request access on the API from Anypoint Exchange

What is true about where an API policy is defined in Anypoint Platform and how it is then applied to API instances?

1. A. The API policy Is defined In Runtime Manager as part of the API deployment to a Mule runtime, and then ONLY applied to the specific API Instance
2. B. The API policy Is defined In API Manager for a specific API Instance, and then ONLY applied to the specific API instance
3. C. The API policy Is defined in API Manager and then automatically applied to ALL API instances
4. D. The API policy is defined in API Manager, and then applied to ALL API instances in the specified environment

Correct Answer: B

Correct Answer:: The API policy is defined in API Manager for a specific API instance, and then ONLY applied to the specific API instance.
*****************************************
>> Once our API specifications are ready and published to Exchange, we need to visit API Manager and register an API instance for each API.
>> API Manager is the place where management of API aspects takes place like addressing NFRs by enforcing policies on them.
>> We can create multiple instances for a same API and manage them differently for different purposes.
>> One instance can have a set of API policies applied and another instance of same API can have different set of policies applied for some other purpose.
>> These APIs and their instances are defined PER environment basis. So, one need to manage them seperately in each environment.
>> We can ensure that same configuration of API instances (SLAs, Policies etc..) gets promoted when promoting to higher environments using platform feature. But this is optional only. Still one can change them per environment basis if they have to.
>> Runtime Manager is the place to manage API Implementations and their Mule Runtimes but NOT APIs itself. Though API policies gets executed in Mule Runtimes, We CANNOT enforce API policies in Runtime Manager. We would need to do that via API Manager only for a cherry picked instance in an environment.
So, based on these facts, right statement in the given choices is - "The API policy is defined in API Manager for a specific API instance, and then ONLY applied to the specific API instance".

An API has been updated in Anypoint exchange by its API producer from version 3.1.1 to 3.2.0 following accepted semantic versioning practices and the changes have been communicated via the APIs public portal. The API endpoint does NOT change in the new version. How should the developer of an API client respond to this change?

1. A. The API producer should be requested to run the old version in parallel with the new one
2. B. The API producer should be contacted to understand the change to existing functionality
3. C. The API client code only needs to be changed if it needs to take advantage of the new features
4. D. The API clients need to update the code on their side and need to do full regression

Correct Answer: C

A company wants to move its Mule API implementations into production as quickly as possible. To protect access to all Mule application data and metadata, the company requires that all Mule applications be deployed to the company's customer-hosted infrastructure within the corporate firewall. What combination of runtime plane and control plane options meets these project lifecycle goals?

1. A. Manually provisioned customer-hosted runtime plane and customer-hosted control plane
2. B. MuleSoft-hosted runtime plane and customer-hosted control plane
3. C. Manually provisioned customer-hosted runtime plane and MuleSoft-hosted control plane
4. D. iPaaS provisioned customer-hosted runtime plane and MuleSoft-hosted control plane

Correct Answer: A
Correct Answer::
Manually provisioned customer-hosted runtime plane and customer-hosted control plane
*****************************************
There are two key factors that are to be taken into consideration from the scenario given in the question.
>> Company requires both data and metadata to be resided within the corporate firewall
>> Company would like to go with customer-hosted infrastructure.
Any deployment model that is to deal with the cloud directly or indirectly (Mulesoft-hosted or Customer's own cloud like Azure, AWS) will have to share atleast the metadata.
Application data can be controlled inside firewall by having Mule Runtimes on customer hosted runtime plane. But if we go with Mulsoft-hosted/ Cloud-based control plane, the control plane required atleast some minimum level of metadata to be sent outside the corporate firewall.
As the customer requirement is pretty clear about the data and metadata both to be within the corporate firewall, even though customer wants to move to production as quickly as possible, unfortunately due to the nature of their security requirements, they have no other option but to go with manually provisioned customer-hosted runtime plane and customer-hosted control plane.