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

Page 7 of 24

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?

  1. 443
  2. 8081
  3. 8091
  4. 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



What is a key requirement when using an external Identity Provider for Client Management in Anypoint Platform?

  1. Single sign-on is required to sign in to Anypoint Platform
  2. The application network must include System APIs that interact with the Identity Provider
  3. To invoke OAuth 2.0-protected APIs managed by Anypoint Platform, API clients must submit access tokens issued by that same Identity Provider
  4. APIs managed by Anypoint Platform must be protected by SAML 2.0 policies

Answer(s): C

Explanation:

Correct Answer: To invoke OAuth 2.0-protected APIs managed by Anypoint Platform, API clients must submit access tokens issued by that same Identity Provider
*****************************************
>> It is NOT necessary that single sign-on is required to sign in to Anypoint Platform because we are using an external Identity Provider for Client Management
>> It is NOT necessary that all APIs managed by Anypoint Platform must be protected by SAML 2.0 policies because we are using an external Identity Provider for Client Management
>> Not TRUE that the application network must include System APIs that interact with the Identity Provider because we are using an external Identity Provider for Client Management
Only TRUE statement in the given options is - "To invoke OAuth 2.0-protected APIs managed by Anypoint Platform, API clients must submit access tokens issued by that same Identity Provider"


Reference:

https://docs.mulesoft.com/api-manager/2.x/external-oauth-2.0-token-validation-policy https://blogs.mulesoft.com/dev/api-dev/api-security-ways-to-authenticate-and-authorize/
https://www.folkstalk.com/2019/11/mulesoft-integration-and-platform.html



The responses to some HTTP requests can be cached depending on the HTTP verb used in the request. According to the HTTP specification, for what HTTP verbs is this safe to do?

  1. PUT, POST, DELETE
  2. GET, HEAD, POST
  3. GET, PUT, OPTIONS
  4. GET, OPTIONS, HEAD

Answer(s): D

Explanation:

Correct Answer: GET, OPTIONS, HEAD


Reference:

http://restcookbook.com/HTTP%20Methods/idempotency/



What is the most performant out-of-the-box solution in Anypoint Platform to track transaction state in an asynchronously executing long-running process implemented as a Mule application deployed to multiple CloudHub workers?

  1. Redis distributed cache
  2. java.util.WeakHashMap
  3. Persistent Object Store
  4. File-based storage

Answer(s): C

Explanation:

Correct Answer: Persistent Object Store
*****************************************
>> Redis distributed cache is performant but NOT out-of-the-box solution in Anypoint Platform
>> File-storage is neither performant nor out-of-the-box solution in Anypoint Platform
>> java.util.WeakHashMap needs a completely custom implementation of cache from scratch using Java code and is limited to the JVM where it is running. Which means the state in the cache is not worker aware when running on multiple workers. This type of cache is local to the worker. So, this is neither out-of-the-box nor worker-aware among multiple workers on cloudhub.


https://www.baeldung.com/java-weakhashmap
>> Persistent Object Store is an out-of-the-box solution provided by Anypoint Platform which is performant as well as worker aware among multiple workers running on CloudHub. https://docs.mulesoft.com/object-store/
So, Persistent Object Store is the right answer.



Page 7 of 24



Post your Comments and Discuss MuleSoft MuleSoft Certified Platform Architect - Level 1 exam with other Community members:

Olympia commented on October 25, 2024
The free version is good but does not have all questions. However the PDF has double the amount of questions and very helpful to pass the exam.
Canada
upvote