Certified Platform Architect - Level 1 MAINTENANCE Dumps in PDF and Online

QUESTION: 6

When using CloudHub with the Shared Load Balancer, what is managed EXCLUSIVELY by the API implementation (the Mule application) and NOT by Anypoint Platform?

The assignment of each HTTP request to a particular CloudHub worker
The logging configuration that enables log entries to be visible in Runtime Manager
The SSL certificates used by the API implementation to expose HTTPS endpoints
The number of DNS entries allocated to the API implementation

Answer(s): C

Explanation:

Correct Answer: The SSL certificates used by the API implementation to expose HTTPS endpoints
*****************************************
>> The assignment of each HTTP request to a particular CloudHub worker is taken care by Anypoint Platform itself. We need not manage it explicitly in the API implementation and in fact we CANNOT manage it in the API implementation.
>> The logging configuration that enables log entries to be visible in Runtime Manager is ALWAYS managed in the API implementation and NOT just for SLB. So this is not something we do EXCLUSIVELY when using SLB.
>> We DO NOT manage the number of DNS entries allocated to the API implementation inside the code. Anypoint Platform takes care of this.

It is the SSL certificates used by the API implementation to expose HTTPS endpoints that is to be managed EXCLUSIVELY by the API implementation. Anypoint Platform does NOT do this when using SLBs.

Reveal Solution Next Question

QUESTION: 7

Refer to the exhibit.

What is the best way to decompose one end-to-end business process into a collaboration of Experience, Process, and System APIs?

Handle customizations for the end-user application at the Process API level rather than the Experience API level
Allow System APIs to return data that is NOT currently required by the identified Process or Experience APIs
Always use a tiered approach by creating exactly one API for each of the 3 layers (Experience, Process and System APIs)
Use a Process API to orchestrate calls to multiple System APIs, but NOT to other Process APIs

Answer(s): B

Explanation:

Correct Answer: Allow System APIs to return data that is NOT currently required by the identified Process or Experience APIs.
*****************************************
>> All customizations for the end-user application should be handled in "Experience API" only. Not in Process API
>> We should use tiered approach but NOT always by creating exactly one API for each of the 3 layers. Experience APIs might be one but Process APIs and System APIs are often more than one. System APIs for sure will be more than one all the time as they are the smallest modular APIs built in front of end systems.
>> Process APIs can call System APIs as well as other Process APIs. There is no such anti-design pattern in API-Led connectivity saying Process APIs should not call other Process APIs. So, the right answer in the given set of options that makes sense as per API-Led connectivity principles is to allow System APIs to return data that is NOT currently required by the identified Process or Experience APIs. This way, some future Process APIs can make use of that data from System APIs and we need NOT touch the System layer APIs again and again.

Reveal Solution Next Question

QUESTION: 8

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

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
The API policy Is defined In API Manager for a specific API Instance, and then ONLY applied to the specific API instance
The API policy Is defined in API Manager and then automatically applied to ALL API instances
The API policy is defined in API Manager, and then applied to ALL API instances in the specified environment

Answer(s): B

Explanation:

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".

Reference:

https://docs.mulesoft.com/api-manager/2.x/latest-overview-concept

Reveal Solution Next Question

QUESTION: 9

An API implementation is deployed to CloudHub.
What conditions can be alerted on using the default Anypoint Platform functionality, where the alert conditions depend on the end-to-end request processing of the API implementation?

When the API is invoked by an unrecognized API client
When a particular API client invokes the API too often within a given time period
When the response time of API invocations exceeds a threshold
When the API receives a very high number of API invocations

Answer(s): C

Explanation:

Correct Answer: When the response time of API invocations exceeds a threshold
*****************************************
>> Alerts can be setup for all the given options using the default Anypoint Platform functionality >> However, the question insists on an alert whose conditions depend on the end-to-end request processing of the API implementation.
>> Alert w.r.t "Response Times" is the only one which requires end-to-end request processing of API implementation in order to determine if the threshold is exceeded or not.

Reference:

https://docs.mulesoft.com/api-manager/2.x/using-api-alerts

Reveal Solution Next Question

QUESTION: 10

A Mule application exposes an HTTPS endpoint and is deployed to the CloudHub Shared Worker Cloud. All traffic to that Mule application must stay inside the AWS VPC. To what TCP port do API invocations to that Mule application need to be sent?

443
8081
8091
8082

Answer(s): D

Explanation:

Correct Answer: 8082
*****************************************
>> 8091 and 8092 ports are to be used when keeping your HTTP and HTTPS app private to the LOCAL VPC respectively.
>> Above TWO ports are not for Shared AWS VPC/ Shared Worker Cloud. >> 8081 is to be used when exposing your HTTP endpoint app to the internet through Shared LB >> 8082 is to be used when exposing your HTTPS endpoint app to the internet through Shared LB

So, API invocations should be sent to port 8082 when calling this HTTPS based app.

Reference:

https://docs.mulesoft.com/runtime-manager/cloudhub-networking-guide https://help.mulesoft.com/s/article/Configure-Cloudhub-Application-to-Send-a-HTTPS-Request- Directly-to-Another-Cloudhub-Application
https://help.mulesoft.com/s/question/0D52T00004mXXULSA4/multiple-http-listerners-on- cloudhub-one-with-port-9090

Reveal Solution Next Question

MuleSoft Certified Platform Architect - Level 1 MAINTENANCE MuleSoft Certified Platform Architect - Level 1 MAINTENANCE Dumps in PDF

Free MuleSoft MuleSoft Certified Platform Architect - Level 1 MAINTENANCE Real Questions (page: 2)

QUESTION: 6

Explanation:

QUESTION: 7

Explanation:

QUESTION: 8

Explanation:

Reference:

QUESTION: 9

Explanation:

Reference:

QUESTION: 10

Explanation:

Reference: