QUESTION: 5

What do the API invocation metrics provided by Anypoint Platform provide?

ROI metrics from APIs that can be directly shared with business users
Measurements of the effectiveness of the application network based on the level of reuse
Data on past API invocations to help identify anomalies and usage patterns across various APIs
Proactive identification of likely future policy violations that exceed a given threat threshold

Answer(s): C

Explanation:

Correct Answer: Data on past API invocations to help identify anomalies and usage patterns across various APIs ***************************************** API Invocation metrics provided by Anypoint Platform:
>> Does NOT provide any Return Of Investment (ROI) related information. So the option suggesting it is OUT.
>> Does NOT provide any information w.r.t how APIs are reused, whether there is effective usage of APIs or not etc...
>> Does NOT prodive any prediction information as such to help us proactively identify any future policy violations.
So, the kind of data/information we can get from such metrics is on past API invocations to help identify anomalies and usage patterns across various APIs.

Reference:

https://usermanual.wiki/Document/APAAppNetstudentManual02may2018.991784750.pdf

Reveal Solution Next Question

QUESTION: 6

What is true about the technology architecture of Anypoint VPCs?

The private IP address range of an Anypoint VPC is automatically chosen by CloudHub
Traffic between Mule applications deployed to an Anypoint VPC and on-premises systems can stay within a private network
Each CloudHub environment requires a separate Anypoint VPC
VPC peering can be used to link the underlying AWS VPC to an on-premises (non AWS) private network

Answer(s): B

Explanation:

Correct Answer: Traffic between Mule applications deployed to an Anypoint VPC and on-premises systems can stay within a private network
*****************************************
>> The private IP address range of an Anypoint VPC is NOT automatically chosen by CloudHub. It is chosen by us at the time of creating VPC using thr CIDR blocks.
CIDR Block: The size of the Anypoint VPC in Classless Inter-Domain Routing (CIDR) notation.
For example, if you set it to 10.111.0.0/24, the Anypoint VPC is granted 256 IP addresses from 10.111.0.0 to 10.111.0.255.
Ideally, the CIDR Blocks you choose for the Anypoint VPC come from a private IP space, and should not overlap with any other Anypoint VPC’s CIDR Blocks, or any CIDR Blocks in use in your corporate network.

that each CloudHub environment requires a separate Anypoint VPC. Once an Anypoint VPC is created, we can choose a same VPC by multiple environments. However, it is generally a best and recommended practice to always have seperate Anypoint VPCs for Non-Prod and Prod environments.
>> We use Anypoint VPN to link the underlying AWS VPC to an on-premises (non AWS) private network. NOT VPC Peering.

Reference:

https://docs.mulesoft.com/runtime-manager/vpn-about
Only true statement in the given choices is that the traffic between Mule applications deployed to an Anypoint VPC and on-premises systems can stay within a private network. https://docs.mulesoft.com/runtime-manager/vpc-connectivity-methods-concept

Reveal Solution Next Question

QUESTION: 7

An API implementation is deployed on a single worker on CloudHub and invoked by external API clients (outside of CloudHub). How can an alert be set up that is guaranteed to trigger AS SOON AS that API implementation stops responding to API invocations?

Implement a heartbeat/health check within the API and invoke it from outside the Anypoint Platform and alert when the heartbeat does not respond
Configure a "worker not responding" alert in Anypoint Runtime Manager
Handle API invocation exceptions within the calling API client and raise an alert from that API client when the API Is unavailable
Create an alert for when the API receives no requests within a specified time period

Answer(s): B

Explanation:

Correct Answer: Configure a “Worker not responding” alert in Anypoint Runtime Manager.
*****************************************
>> All the options eventually helps to generate the alert required when the application stops responding.
>> However, handling exceptions within calling API and then raising alert from API client is inappropriate and silly. There could be many API clients invoking the API implementation and it is not ideal to have this setup consistently in all of them. Not a realistic way to do.
>> Implementing a health check/ heartbeat with in the API and calling from outside to detmine the health sounds OK but needs extra setup for it and same time there are very good chances of generating false alarms when there are any intermittent network issues between external tool calling the health check API on API implementation. The API implementation itself may not have any issues but due to some other factors some false alarms may go out.
>> Creating an alert in API Manager when the API receives no requests within a specified time period would actually generate realistic alerts but even here some false alarms may go out when there are genuinely no requests from API clients.
The best and right way to achieve this requirement is to setup an alert on Runtime Manager with a condition "Worker not responding". This would generate an alert AS SOON AS the workers become unresponsive.

Reveal Solution Next Question

QUESTION: 8

The implementation of a Process API must change.
What is a valid approach that minimizes the impact of this change on API clients?

Update the RAML definition of the current Process API and notify API client developers by sending them links to the updated RAML definition
Postpone changes until API consumers acknowledge they are ready to migrate to a new Process API or API version
Implement required changes to the Process API implementation so that whenever possible, the Process API's RAML definition remains unchanged
Implement the Process API changes in a new API implementation, and have the old API implementation return an HTTP status code 301 - Moved Permanently to inform API clients they should be calling the new API implementation

Answer(s): C

Explanation:

Correct Answer: Implement required changes to the Process API implementation so that, whenever possible, the Process API’s RAML definition remains unchanged.
***************************************** Key requirement in the question is:
>> Approach that minimizes the impact of this change on API clients Based on above:
>> Updating the RAML definition would possibly impact the API clients if the changes require any thing mandatory from client side. So, one should try to avoid doing that until really necessary.
>> Implementing the changes as a completely different API and then redirectly the clients with 3xx status code is really upsetting design and heavily impacts the API clients.
>> Organisations and IT cannot simply postpone the changes required until all API consumers acknowledge they are ready to migrate to a new Process API or API version. This is unrealistic and not possible.
The best way to handle the changes always is to implement required changes to the API implementations so that, whenever possible, the API’s RAML definition remains unchanged.

Reveal Solution Next Question

Free MuleSoft Certified Platform Architect - Level 1 Exam Braindumps (page: 3)

QUESTION: 5

Explanation:

Reference:

QUESTION: 6

Explanation:

Reference:

QUESTION: 7

Explanation:

QUESTION: 8

Explanation:

MuleSoft Certified Platform Architect - Level 1 Discussions & Posts