Discount Offer
Available in 1, 3, 6 and 12 Months Free Updates Plans
PDF: $15 $60

Test Engine: $20 $80

PDF + Engine: $25 $99



Pass exam with Dumps4free or we will provide you with three additional months of access for FREE.

MuleSoft-Platform-Architect-I Practice Test

Whether you're a beginner or brushing up on skills, our MuleSoft-Platform-Architect-I practice exam is your key to success. Our comprehensive question bank covers all key topics, ensuring you’re fully prepared.


Page 6 out of 31 Pages

What API policy would be LEAST LIKELY used when designing an Experience API that is intended to work with a consumer mobile phone or tablet application?


A. OAuth 2.0 access token enforcement


B. Client ID enforcement


C. JSON threat protection


D. IPwhitellst





D.
  IPwhitellst

Explanation

Correct Answer: IP whitelist

*****************************************

>> OAuth 2.0 access token and Client ID enforcement policies are VERY common to apply on Experience APIs as API consumers need to register and access the APIs using one of these mechanisms

>> JSON threat protection is also VERY common policy to apply on Experience APIs to prevent bad or suspicious payloads hitting the API implementations.

>> IP whitelisting policy is usually very common in Process and System APIs to only whitelist the IP range inside the local VPC. But also applied occassionally on some experience APIs where the End User/ API Consumers are FIXED.

>> When we know the API consumers upfront who are going to access certain Experience APIs, then we can request for static IPs from such consumers and whitelist them to prevent anyone else hitting the API.

However, the experience API given in the question/ scenario is intended to work with a consumer mobile phone or tablet application. Which means, there is no way we can know all possible IPs that are to be whitelisted as mobile phones and tablets can so many in number and any device in the city/state/country/globe.

So, It is very LEAST LIKELY to apply IP Whitelisting on such Experience APIs whose consumers are typically Mobile Phones or Tablets.

An organization has implemented a Customer Address API to retrieve customer address information. This API has been deployed to multiple environments and has been configured to enforce client IDs everywhere. A developer is writing a client application to allow a user to update their address. The developer has found the Customer Address API in Anypoint Exchange and wants to use it in their client application. What step of gaining access to the API can be performed automatically by Anypoint Platform?


A. Approve the client application request for the chosen SLA tier


B. Request access to the appropriate API Instances deployed to multiple environments using the client application's credentials


C. Modify the client application to call the API using the client application's credentials


D. Create a new application in Anypoint Exchange for requesting access to the API





A.
  Approve the client application request for the chosen SLA tier

Explanation

Correct Answer: Approve the client application request for the chosen SLA tier

*****************************************

>> Only approving the client application request for the chosen SLA tier can be automated >> Rest of the provided options are not valid

Reference:

https://docs.mulesoft.com/api-manager/2.x/defining-sla-tiers#defining-a-tier

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


A. ROI metrics from APIs that can be directly shared with business users


B. Measurements of the effectiveness of the application network based on the level of reuse


C. Data on past API invocations to help identify anomalies and usage patterns across various APIs


D. Proactive identification of likely future policy violations that exceed a given threat threshold





C.
   Data on past API invocations to help identify anomalies and usage patterns across various APIs

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

An organization wants to make sure only known partners can invoke the organization's APIs. To achieve this security goal, the organization wants to enforce a Client ID Enforcement policy in API Manager so that only registered partner applications can invoke the organization's APIs. In what type of API implementation does MuleSoft recommend adding an API proxy to enforce the Client ID Enforcement policy, rather than embedding the policy directly in the application's JVM?


A. A Mule 3 application using APIkit


B. A Mule 3 or Mule 4 application modified with custom Java code


C. A Mule 4 application with an API specification


D. A Non-Mule application





D.
  A Non-Mule application

Explanation

Correct Answer: A Non-Mule application

*****************************************

>> All type of Mule applications (Mule 3/ Mule 4/ with APIkit/ with Custom Java Code etc) running on Mule Runtimes support the Embedded Policy Enforcement on them.

>> The only option that cannot have or does not support embedded policy enforcement and must have API Proxy is for Non-Mule Applications.

So, Non-Mule application is the right answer.

What is a key performance indicator (KPI) that measures the success of a typical C4E that is immediately apparent in responses from the Anypoint Platform APIs?


A. The number of production outage incidents reported in the last 24 hours


B. The number of API implementations that have a publicly accessible HTTP endpoint and are being managed by Anypoint Platform


C. The fraction of API implementations deployed manually relative to those deployed using a CI/CD tool


D. The number of API specifications in RAML or OAS format published to Anypoint Exchange





D.
  The number of API specifications in RAML or OAS format published to Anypoint Exchange

Explanation

Correct Answer: The number of API specifications in RAML or OAS format published to Anypoint Exchange

*****************************************

>> The success of C4E always depends on their contribution to the number of reusable assets that they have helped to build and publish to Anypoint Exchange. >> It is NOT due to any factors w.r.t # of outages, Manual vs CI/CD deployments or Publicly accessible HTTP endpoints

>> Anypoint Platform APIs helps us to quickly run and get the number of published RAML/OAS assets to Anypoint Exchange. This clearly depicts how successful a C4E team is based on number of returned assets in the response.

Reference: https://help.mulesoft.com/s/question/0D52T00004mXSTUSA4/how-should-acompany-measure-c4e-success


Page 6 out of 31 Pages
Previous