Mulesoft MCPA-LEVEL1 Online Practice Questions and Exam Preparation

Mulesoft MCPA-LEVEL1 Online Questions & Answers

• Question 1:

  Version 3.0.1 of a REST API implementation represents time values in PST time using ISO 8601 hh:mm:ss format. The API implementation needs to be changed to instead represent time values in CEST time using ISO 8601 hh:mm:ss format. When following the semver.org semantic versioning specification, what version should be assigned to the updated API implementation?

  A. 3.0.2
  B. 4.0.0
  C. 3.1.0
  D. 3.0.1
  B. 4.0.0

  ---

  Explanation/Reference:

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

  As per semver.org semantic versioning specification:

  Given a version number MAJOR.MINOR.PATCH, increment the:

  -MAJOR version when you make incompatible API changes.

  -

  MINOR version when you add functionality in a backwards compatible manner.

  -

  PATCH version when you make backwards compatible bug fixes. As per the scenario given in the question, the API implementation is completely changing its behavior. Although the format of the time is still being maintained as hh:mm:ss and there is no change in schema w.r.t format, the API will start functioning different after this change as the times are going to come completely different. Example: Before the change, say, time is going as 09:00:00 representing the PST. Now on, after the change, the same time will go as 18:00:00 as Central European Summer Time is 9 hours ahead of Pacific Time. >> This may lead to some uncertain behavior on API clients depending on how they are handling the times in the API response. All the API clients need to be informed that the API functionality is going to change and will return in CEST format. So, this considered as a MAJOR change and the version of API for this new change would be 4.0.0

• Question 2:

  An API implementation is updated. When must the RAML definition of the API also be updated?

  A. When the API implementation changes the structure of the request or response messages
  B. When the API implementation changes from interacting with a legacy backend system deployed on-premises to a modern, cloud-based (SaaS) system
  C. When the API implementation is migrated from an older to a newer version of the Mule runtime
  D. When the API implementation is optimized to improve its average response time
  A. When the API implementation changes the structure of the request or response messages

  ---

  Explanation/Reference:

  When the API implementation changes the structure of the request or response messages

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

  >> RAML definition usually needs to be touched only when there are changes in the request/response schemas or in any traits on API. >> It need not be modified for any internal changes in API implementation like performance tuning,

  backend system migrations etc..

• Question 3:

  Refer to the exhibit.

  

  What is true when using customer-hosted Mule runtimes with the MuleSoft-hosted Anypoint Platform control plane (hybrid deployment)?

  A. Anypoint Runtime Manager initiates a network connection to a Mule runtime in order to deploy Mule applications
  B. The MuleSoft-hosted Shared Load Balancer can be used to load balance API invocations to the Mule runtimes
  C. API implementations can run successfully in customer-hosted Mule runtimes, even when they are unable to communicate with the control plane
  D. Anypoint Runtime Manager automatically ensures HA in the control plane by creating a new Mule runtime instance in case of a node failure
  C. API implementations can run successfully in customer-hosted Mule runtimes, even when they are unable to communicate with the control plane

  ---

  Explanation/Reference:

  API implementations can run successfully in customer-hosted Mule runtimes, even when they are unable to communicate with the control plane.

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

  >> We CANNOT use Shared Load balancer to load balance APIs on customer hosted runtimes

  

  >> For Hybrid deployment models, the on-premises are first connected to Runtime Manager using Runtime Manager agent. So, the connection is initiated first from On- premises to Runtime Manager. Then all control can be done from Runtime Manager. >> Anypoint Runtime Manager CANNOT ensure automatic HA. Clusters/Server Groups etc should be configured before hand.

  Only TRUE statement in the given choices is, API implementations can run successfully in customer-hosted Mule runtimes, even when they are unable to communicate with the control plane. There are several references below to justify this statement.

  References: https://docs.mulesoft.com/runtime-manager/deployment-strategies#hybrid-deployments https://help.mulesoft.com/s/article/On-Premise-Runtimes-Disconnected-From-US-Control- Plane-June-18th-2018 https://help.mulesoft.com/s/article/Runtime-Manager-cannot-manage-On-Prem-Applications-and-Servers-from-US-Control-Plane-June-25th-2019 https://help.mulesoft.com/s/article/On-premise-Runtimes-Appear-Disconnected-in-RuntimeManager-May-29th-2018

  

  ============================

  

  ============================

  

• Question 4:

  An API experiences a high rate of client requests (TPS) vwth small message paytoads. How can usage limits be imposed on the API based on the type of client application?

  A. Use an SLA-based rate limiting policy and assign a client application to a matching SLA tier based on its type
  B. Use a spike control policy that limits the number of requests for each client application type
  C. Use a cross-origin resource sharing (CORS) policy to limit resource sharing between client applications, configured by the client application type
  D. Use a rate limiting policy and a client ID enforcement policy, each configured by the client application type
  A. Use an SLA-based rate limiting policy and assign a client application to a matching SLA tier based on its type

  ---

  Explanation/Reference:

  Use an SLA-based rate limiting policy and assign a client application to a matching SLA tier based on its type.

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

  >> SLA tiers will come into play whenever any limits to be imposed on APIs based on client type

  Reference: https://docs.mulesoft.com/api-manager/2.x/rate-limiting-and-throttling-sla- based-policies

• Question 5:

  What condition requires using a CloudHub Dedicated Load Balancer?

  A. When cross-region load balancing is required between separate deployments of the same Mule application
  B. When custom DNS names are required for API implementations deployed to customer- hosted Mule runtimes
  C. When API invocations across multiple CloudHub workers must be load balanced
  D. When server-side load-balanced TLS mutual authentication is required between API implementations and API clients
  D. When server-side load-balanced TLS mutual authentication is required between API implementations and API clients

  ---

  Explanation/Reference:

  When server-side load-balanced TLS mutual authentication is required between API implementations and API clients

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

  Fact/ Memory Tip: Although there are many benefits of CloudHub Dedicated Load balancer, TWO important things that should come to ones mind for considering it are:

  >> Having URL endpoints with Custom DNS names on CloudHub deployed apps >> Configuring custom certificates for both HTTPS and Two-way (Mutual) authentication.

  Coming to the options provided for this question:

  >> We CANNOT use DLB to perform cross-region load balancing between separate deployments of the same Mule application.

  >> We can have mapping rules to have more than one DLB URL pointing to same Mule app. But vicevera (More than one Mule app having same DLB URL) is NOT POSSIBLE >> It is true that DLB helps to setup custom DNS names for

  Cloudhub deployed Mule apps but NOT true for apps deployed to Customer-hosted Mule Runtimes. >> It is true to that we can load balance API invocations across multiple CloudHub workers using DLB but it is NOT A MUST. We can

  achieve the same (load balancing) using SLB (Shared Load Balancer) too. We DO NOT necessarily require DLB for achieve it. So the only right option that fits the scenario and requires us to use DLB is when TLS mutual authentication is

  required between API implementations and API clients. Reference: https://docs.mulesoft.com/runtime-manager/cloudhub-dedicated-load-balancer

• Question 6:

  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?

  A. 443
  B. 8081
  C. 8091
  D. 8082
  D. 8082

  ---

  Explanation/Reference:

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

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

  References:

  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- cloudhubone-with-port-9090

• Question 7:

  Mule applications that implement a number of REST APIs are deployed to their own subnet that is inaccessible from outside the organization.

  External business-partners need to access these APIs, which are only allowed to be invoked from a separate subnet dedicated to partners - called Partner-subnet. This subnet is accessible from the public internet, which allows these external partners to reach it.

  Anypoint Platform and Mule runtimes are already deployed in Partner-subnet. These Mule runtimes can already access the APIs.

  What is the most resource-efficient solution to comply with these requirements, while having the least impact on other applications that are currently using the APIs?

  A. Implement (or generate) an API proxy Mule application for each of the APIs, then deploy the API proxies to the Mule runtimes
  B. Redeploy the API implementations to the same servers running the Mule runtimes
  C. Add an additional endpoint to each API for partner-enablement consumption
  D. Duplicate the APIs as Mule applications, then deploy them to the Mule runtimes
  A. Implement (or generate) an API proxy Mule application for each of the APIs, then deploy the API proxies to the Mule runtimes

• Question 8:

  Refer to the exhibit.

  

  A developer is building a client application to invoke an API deployed to the STAGING environment that is governed by a client ID enforcement policy.

  What is required to successfully invoke the API?

  A. The client ID and secret for the Anypoint Platform account owning the API in the STAGING environment
  B. The client ID and secret for the Anypoint Platform account's STAGING environment
  C. The client ID and secret obtained from Anypoint Exchange for the API instance in the STAGING environment
  D. A valid OAuth token obtained from Anypoint Platform and its associated client ID and secret
  C. The client ID and secret obtained from Anypoint Exchange for the API instance in the STAGING environment

  ---

  Explanation/Reference:

  The client ID and secret obtained from Anypoint Exchange for the API instance in the STAGING environment ***************************************** >> We CANNOT use the client ID and secret of Anypoint Platform account or any individual environments for accessing the APIs >> As the type of policy that is enforced on the API in question is "Client ID Enforcment Policy", OAuth token based access won't work. Right way to access the API is to use the client ID and secret obtained from Anypoint Exchange for the API instance in a particular environment we want to work on. References: Managing API instance Contracts on API Manager https://docs.mulesoft.com/api-manager/1.x/request-access-to-api-task https://docs.mulesoft.com/exchange/to-request-access https://docs.mulesoft.com/api-manager/2.x/policy-mule3-client-id-based-policies

• Question 9:

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

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

  ---

  Explanation/Reference:

  https://www.folkstalk.com/2019/11/mulesoft-integration-and-platform.html 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" References: 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/

• Question 10:

  What Mule application deployment scenario requires using Anypoint Platform Private Cloud Edition or Anypoint Platform for Pivotal Cloud Foundry?

  A. When it Is required to make ALL applications highly available across multiple data centers
  B. When it is required that ALL APIs are private and NOT exposed to the public cloud
  C. When regulatory requirements mandate on-premises processing of EVERY data item, including meta-data
  D. When ALL backend systems in the application network are deployed in the organization's intranet
  C. When regulatory requirements mandate on-premises processing of EVERY data item, including meta-data

  ---

  Explanation/Reference:

  When regulatory requirements mandate on-premises processing of EVERY data item, including meta-data.

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

  We need NOT require to use Anypoint Platform PCE or PCF for the below. So these options are OUT.

  >> We can make ALL applications highly available across multiple data centers using CloudHub too.

  >> We can use Anypoint VPN and tunneling from CloudHub to connect to ALL backend systems in the application network that are deployed in the organization's intranet. >> We can use Anypoint VPC and Firewall Rules to make ALL APIs

  private and NOT exposed to the public cloud.

  Only valid reason in the given options that requires to use Anypoint Platform PCE/ PCF is - When regulatory requirements mandate on-premises processing of EVERY data item, including meta-data.