[2023] Valid MCPA-Level-1 test answers & MuleSoft MCPA-Level-1 exam pdf

Verified MCPA-Level-1 dumps Q&As - Pass Guarantee or Full Refund

MuleSoft MCPA-Level-1 certification is an excellent certification for architects and developers who want to demonstrate their skills and expertise in the MuleSoft Anypoint Platform. MuleSoft Certified Platform Architect - Level 1 certification not only validates their skills but also provides access to MuleSoft's community and resources. If you are looking to advance your career in MuleSoft, the MCPA-Level-1 certification is a great place to start.

The MCPA-Level-1 certification exam is designed to test the skills and knowledge required to design, build, and deploy integration solutions using the MuleSoft Anypoint Platform. MCPA-Level-1 exam consists of scenario-based questions that assess the candidate's ability to use Anypoint Platform components such as connectors, transformers, routers, and more, to solve complex integration problems. MCPA-Level-1 exam also tests the candidate's knowledge of API design, security, and governance best practices.

MuleSoft MCPA-Level-1 certification exam is an excellent way for IT professionals, architects, and developers to demonstrate their expertise in designing, building, and managing integration solutions using MuleSoft Anypoint Platform. MuleSoft Certified Platform Architect - Level 1 certification exam measures the candidate's knowledge and skills in various areas, including integration design patterns, API design, and implementation, data transformation, security, and governance. A passing score on the exam validates the candidate's proficiency in MuleSoft Anypoint Platform and enhances their career prospects.

 

NEW QUESTION # 42
An organization wants MuleSoft-hosted runtime plane features (such as HTTP load balancing, zero downtime, and horizontal and vertical scaling) in its Azure environment. What runtime plane minimizes the organization's effort to achieve these features?

• A. Anypoint Platform for Pivotal Cloud Foundry
• B. CloudHub
• C. Anypoint Runtime Fabric
• D. A hybrid combination of customer-hosted and MuleSoft-hosted Mule runtimes

Answer: C

Explanation:
Correct answer: Anypoint Runtime Fabric
*****************************************
>> When a customer is already having an Azure environment, It is not at all an ideal approach to go with hybrid model having some Mule Runtimes hosted on Azure and some on MuleSoft. This is unnecessary and useless.
>> CloudHub is a Mulesoft-hosted Runtime plane and is on AWS. We cannot customize to point CloudHub to customer's Azure environment.
>> Anypoint Platform for Pivotal Cloud Foundry is specifically for infrastructure provided by Pivotal Cloud Foundry
>> Anypoint Runtime Fabric is right answer as it is a container service that automates the deployment and orchestration of Mule applications and API gateways. Runtime Fabric runs within a customer-managed infrastructure on AWS, Azure, virtual machines (VMs), and bare-metal servers.
-Some of the capabilities of Anypoint Runtime Fabric include:
-Isolation between applications by running a separate Mule runtime per application.
-Ability to run multiple versions of Mule runtime on the same set of resources.
-Scaling applications across multiple replicas.
-Automated application fail-over.
-Application management with Anypoint Runtime Manager.

NEW QUESTION # 43
Refer to the exhibit.

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

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

Answer: A

Explanation:
Correct answer: 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-Runtime-Manager-May-29th-2018

NEW QUESTION # 44
A code-centric API documentation environment should allow API consumers to investigate and execute API client source code that demonstrates invoking one or more APIs as part of representative scenarios.
What is the most effective way to provide this type of code-centric API documentation environment using Anypoint Platform?

• A. Enable mocking services for each of the relevant APIs and expose them via their Anypoint Exchange entry
• B. Ensure the APIs are well documented through their Anypoint Exchange entries and API Consoles and share these pages with all API consumers
• C. Create API Notebooks and include them in the relevant Anypoint Exchange entries
• D. Make relevant APIs discoverable via an Anypoint Exchange entry

Answer: C

NEW QUESTION # 45
What is true about API implementations when dealing with legal regulations that require all data processing to be performed within a certain jurisdiction (such as in the USA or the EU)?

• A. They must ensure ALL data is encrypted both in transit and at rest
• B. They must use a Jurisdiction-local external messaging system such as Active MQ rather than Anypoint MQ
• C. They must avoid using the Object Store as it depends on services deployed ONLY to the US East region
• D. They must te deployed to Anypoint Platform runtime planes that are managed by Anypoint Platform control planes, with both planes in the same Jurisdiction

Answer: C

NEW QUESTION # 46
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?

• A. GET, PUT, OPTIONS
• B. GET, OPTIONS, HEAD
• C. GET, HEAD, POST
• D. PUT, POST, DELETE

Answer: B

Explanation:
Correct answer: GET, OPTIONS, HEAD

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

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

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

Answer: D

NEW QUESTION # 48
What is a best practice when building System APIs?

• A. Model all API resources and methods to closely mimic the operations of the backend system
• B. Document the API using an easily consumable asset like a RAML definition
• C. Expose to API clients all technical details of the API implementation's interaction wifch the backend system
• D. Build an Enterprise Data Model (Canonical Data Model) for each backend system and apply it to System APIs

Answer: B

NEW QUESTION # 49
A company wants to move its Mule API implementations into production as quickly as possible. To protect access to all Mule application data and metadata, the company requires that all Mule applications be deployed to the company's customer-hosted infrastructure within the corporate firewall. What combination of runtime plane and control plane options meets these project lifecycle goals?

• A. MuleSoft-hosted runtime plane and customer-hosted control plane
• B. Manually provisioned customer-hosted runtime plane and customer-hosted control plane
• C. Manually provisioned customer-hosted runtime plane and MuleSoft-hosted control plane
• D. iPaaS provisioned customer-hosted runtime plane and MuleSoft-hosted control plane

Answer: B

Explanation:
Correct answer: Manually provisioned customer-hosted runtime plane and customer-hosted control plane
*****************************************
There are two key factors that are to be taken into consideration from the scenario given in the question.
>> Company requires both data and metadata to be resided within the corporate firewall
>> Company would like to go with customer-hosted infrastructure.
Any deployment model that is to deal with the cloud directly or indirectly (Mulesoft-hosted or Customer's own cloud like Azure, AWS) will have to share atleast the metadata.
Application data can be controlled inside firewall by having Mule Runtimes on customer hosted runtime plane. But if we go with Mulsoft-hosted/ Cloud-based control plane, the control plane required atleast some minimum level of metadata to be sent outside the corporate firewall.
As the customer requirement is pretty clear about the data and metadata both to be within the corporate firewall, even though customer wants to move to production as quickly as possible, unfortunately due to the nature of their security requirements, they have no other option but to go with manually provisioned customer-hosted runtime plane and customer-hosted control plane.

NEW QUESTION # 50
How are an API implementation, API client, and API consumer combined to invoke and process an API?

• A. The ApI consumer creates an API client, which sends API invocations to an API such that they are processed by an API implementation
• B. The ApI client creates an API consumer, which sends API invocations to an API such that they are processed by an API implementation
• C. The API client creates an API consumer, which receives API invocations from an API such that they are processed for an API implementation
• D. The API consumer creates an API implementation, which receives API invocations from an API such that they are processed for an API client

Answer: A

NEW QUESTION # 51
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 is migrated from an older to a newer version of the Mule runtime
• C. When the API implementation is optimized to improve its average response time
• D. When the API implementation changes from interacting with a legacy backend system deployed on-premises to a modern, cloud-based (SaaS) system

Answer: C

NEW QUESTION # 52
What condition requires using a CloudHub Dedicated Load Balancer?

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

Answer: B

Explanation:
Correct answer: 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
>> 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.

NEW QUESTION # 53
Which of the following sequence is correct?

• A. API Consumer requests access to API >> API Client implementes logic to call an API >> API routes the request to >> API Implementation
• B. API Client implementes logic to call an API >> API Consumer requests access to API >> API routes the request to >> API Implementation
• C. API Consumer implementes logic to call an API >> API Client requests access to API >> API Implementation routes the request to >> API
• D. API Client implementes logic to call an API >> API Consumer requests access to API >> API Implementation routes the request to >> API

Answer: A

Explanation:
Correct answer: API Consumer requests access to API >> API Client implementes logic to call an API >> API routes the request to >> API Implementation
*****************************************
>> API consumer does not implement any logic to invoke APIs. It is just a role. So, the option stating "API Consumer implementes logic to call an API" is INVALID.
>> API Implementation does not route any requests. It is a final piece of logic where functionality of target systems is exposed. So, the requests should be routed to the API implementation by some other entity. So, the options stating "API Implementation routes the request to >> API" is INVALID
>> The statements in one of the options are correct but sequence is wrong. The sequence is given as "API Client implementes logic to call an API >> API Consumer requests access to API >> API routes the request to >> API Implementation". Here, the statements in the options are VALID but sequence is WRONG.
>> Right option and sequence is the one where API consumer first requests access to API on Anypoint Exchange and obtains client credentials. API client then writes logic to call an API by using the access client credentials requested by API consumer and the requests will be routed to API implementation via the API which is managed by API Manager.

NEW QUESTION # 54
An API client calls one method from an existing API implementation. The API implementation is later updated. What change to the API implementation would require the API client's invocation logic to also be updated?

• A. When the data type of the response is changed for the method called by the API client
• B. When a new required field is added to the method called by the API client
• C. When a child method is added to the method called by the API client
• D. When a new method is added to the resource used by the API client

Answer: B

Explanation:
Correct answer: When a new required field is added to the method called by the API client
*****************************************
>> Generally, the logic on API clients need to be updated when the API contract breaks.
>> When a new method or a child method is added to an API , the API client does not break as it can still continue to use its existing method. So these two options are out.
>> We are left for two more where "datatype of the response if changed" and "a new required field is added".
>> Changing the datatype of the response does break the API contract. However, the question is insisting on the "invocation" logic and not about the response handling logic. The API client can still invoke the API successfully and receive the response but the response will have a different datatype for some field.
>> Adding a new required field will break the API's invocation contract. When adding a new required field, the API contract breaks the RAML or API spec agreement that the API client/API consumer and API provider has between them. So this requires the API client invocation logic to also be updated.

NEW QUESTION # 55
What is true about automating interactions with Anypoint Platform using tools such as Anypoint Platform REST APIs, Anypoint CU, or the Mule Maven plugin?

• A. Access to Anypoint Platform APIs and Anypoint CU can be controlled separately through the roles and permissions in Anypoint Platform, so that specific users can get access to Anypoint CLI white others get access to the platform APIs
• B. Anypoint Platform APIs can ONLY automate interactions with CloudHub, while the Mule Maven plugin is required for deployment to customer-hosted Mule runtimes
• C. API policies can be applied to the Anypoint Platform APIs so that ONLY certain LOBs have access to specific functions
• D. By default, the Anypoint CLI and Mule Maven plugin are NOT included in the Mule runtime, so are NOT available to be used by deployed Mule applications

Answer: D

NEW QUESTION # 56
When could the API data model of a System API reasonably mimic the data model exposed by the corresponding backend system, with minimal improvements over the backend system's data model?

• A. When there is an existing Enterprise Data Model widely used across the organization
• B. When the corresponding backend system is expected to be replaced in the near future
• C. When a pragmatic approach with only limited isolation from the backend system is deemed appropriate
• D. When the System API can be assigned to a bounded context with a corresponding data model

Answer: C

Explanation:
Correct answer: When a pragmatic approach with only limited isolation from the backend system is deemed appropriate.
*****************************************
General guidance w.r.t choosing Data Models:
>> If an Enterprise Data Model is in use then the API data model of System APIs should make use of data types from that Enterprise Data Model and the corresponding API implementation should translate between these data types from the Enterprise Data Model and the native data model of the backend system.
>> If no Enterprise Data Model is in use then each System API should be assigned to a Bounded Context, the API data model of System APIs should make use of data types from the corresponding Bounded Context Data Model and the corresponding API implementation should translate between these data types from the Bounded Context Data Model and the native data model of the backend system. In this scenario, the data types in the Bounded Context Data Model are defined purely in terms of their business characteristics and are typically not related to the native data model of the backend system. In other words, the translation effort may be significant.
>> If no Enterprise Data Model is in use, and the definition of a clean Bounded Context Data Model is considered too much effort, then the API data model of System APIs should make use of data types that approximately mirror those from the backend system, same semantics and naming as backend system, lightly sanitized, expose all fields needed for the given System API's functionality, but not significantly more and making good use of REST conventions.
The latter approach, i.e., exposing in System APIs an API data model that basically mirrors that of the backend system, does not provide satisfactory isolation from backend systems through the System API tier on its own. In particular, it will typically not be possible to "swap out" a backend system without significantly changing all System APIs in front of that backend system and therefore the API implementations of all Process APIs that depend on those System APIs! This is so because it is not desirable to prolong the life of a previous backend system's data model in the form of the API data model of System APIs that now front a new backend system. The API data models of System APIs following this approach must therefore change when the backend system is replaced.
On the other hand:
>> It is a very pragmatic approach that adds comparatively little overhead over accessing the backend system directly
>> Isolates API clients from intricacies of the backend system outside the data model (protocol, authentication, connection pooling, network address, ...)
>> Allows the usual API policies to be applied to System APIs
>> Makes the API data model for interacting with the backend system explicit and visible, by exposing it in the RAML definitions of the System APIs
>> Further isolation from the backend system data model does occur in the API implementations of the Process API tier

NEW QUESTION # 57
An organization is deploying their new implementation of the OrderStatus System API to multiple workers in CloudHub. This API fronts the organization's on-premises Order Management System, which is accessed by the API implementation over an IPsec tunnel.
What type of error typically does NOT result in a service outage of the OrderStatus System API?

• A. The AWS region goes offline with a major network failure to the relevant AWS data centers
• B. API Manager has an extended outage during the initial deployment of the API implementation
• C. The Order Management System is Inaccessible due to a network outage in the organization's on-premises data center
• D. A CloudHub worker fails with an out-of-memory exception

Answer: D

Explanation:
Correct answer: A CloudHub worker fails with an out-of-memory exception.
*****************************************
>> An AWS Region itself going down will definitely result in an outage as it does not matter how many workers are assigned to the Mule App as all of those in that region will go down. This is a complete downtime and outage.
>> Extended outage of API manager during initial deployment of API implementation will of course cause issues in proper application startup itself as the API Autodiscovery might fail or API policy templates and polices may not be downloaded to embed at the time of applicaiton startup etc... there are many reasons that could cause issues.
>> A network outage onpremises would of course cause the Order Management System not accessible and it does not matter how many workers are assigned to the app they all will fail and cause outage for sure.
The only option that does NOT result in a service outage is if a cloudhub worker fails with an out-of-memory exception. Even if a worker fails and goes down, there are still other workers to handle the requests and keep the API UP and Running. So, this is the right answer.

NEW QUESTION # 58
A new upstream API Is being designed to offer an SLA of 500 ms median and 800 ms maximum (99th percentile) response time. The corresponding API implementation needs to sequentially invoke 3 downstream APIs of very similar complexity.
The first of these downstream APIs offers the following SLA for its response time: median: 100 ms, 80th percentile: 500 ms, 95th percentile: 1000 ms.
If possible, how can a timeout be set in the upstream API for the invocation of the first downstream API to meet the new upstream API's desired SLA?

• A. Set a timeout of 50 ms; this times out more invocations of that API but gives additional room for retries
• B. Set a timeout of 100 ms; that leaves 400 ms for the other two downstream APIs to complete
• C. No timeout is possible to meet the upstream API's desired SLA; a different SLA must be negotiated with the first downstream API or invoke an alternative API
• D. Do not set a timeout; the Invocation of this API Is mandatory and so we must wait until it responds

Answer: B

NEW QUESTION # 59
What API policy would LEAST likely be applied to a Process API?

• A. Client ID enforcement
• B. Custom circuit breaker
• C. JSON threat protection
• D. Rate limiting

Answer: C

Explanation:
Correct answer: JSON threat protection
*****************************************
Fact: Technically, there are no restrictions on what policy can be applied in what layer. Any policy can be applied on any layer API. However, context should also be considered properly before blindly applying the policies on APIs.
That is why, this question asked for a policy that would LEAST likely be applied to a Process API.
From the given options:
>> All policies except "JSON threat protection" can be applied without hesitation to the APIs in Process tier.
>> JSON threat protection policy ideally fits for experience APIs to prevent suspicious JSON payload coming from external API clients. This covers more of a security aspect by trying to avoid possibly malicious and harmful JSON payloads from external clients calling experience APIs.
As external API clients are NEVER allowed to call Process APIs directly and also these kind of malicious and harmful JSON payloads are always stopped at experience API layer only using this policy, it is LEAST LIKELY that this same policy is again applied on Process Layer API.

NEW QUESTION # 60
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?

• A. Persistent Object Store
• B. File-based storage
• C. java.util.WeakHashMap
• D. Redis distributed cache

Answer: A

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

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

Answer: D

NEW QUESTION # 62
What is a best practice when building System APIs?

• A. Document the API using an easily consumable asset like a RAML definition
• B. Expose to API clients all technical details of the API implementation's interaction wifch the backend system
• C. Model all API resources and methods to closely mimic the operations of the backend system
• D. Build an Enterprise Data Model (Canonical Data Model) for each backend system and apply it to System APIs

Answer: C

Explanation:
Correct answer: Model all API resources and methods to closely mimic the operations of the backend system.
*****************************************
>> There are NO fixed and straight best practices while opting data models for APIs. They are completly contextual and depends on number of factors. Based upon those factors, an enterprise can choose if they have to go with Enterprise Canonical Data Model or Bounded Context Model etc.
>> One should NEVER expose the technical details of API implementation to their API clients. Only the API interface/ RAML is exposed to API clients.
>> It is true that the RAML definitions of APIs should be as detailed as possible and should reflect most of the documentation. However, just that is NOT enough to call your API as best documented API. There should be even more documentation on Anypoint Exchange with API Notebooks etc. to make and create a developer friendly API and repository..
>> The best practice always when creating System APIs is to create their API interfaces by modeling their resources and methods to closely reflect the operations and functionalities of that backend system.

NEW QUESTION # 63
Refer to the exhibit.

An organization uses one specific CloudHub (AWS) region for all CloudHub deployments.
How are CloudHub workers assigned to availability zones (AZs) when the organization's Mule applications are deployed to CloudHub in that region?

• A. Workers are randomly distributed across available AZs within that region
• B. An AZ is randomly selected for a Mule application, and all the Mule application's CloudHub workers are assigned to that one AZ
• C. AZs are selected as part of the Mule application's deployment configuration
• D. Workers belonging to a given environment are assigned to the same AZ within that region

Answer: B

NEW QUESTION # 64
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 a spike control policy that limits the number of requests for each client application type
• B. Use a cross-origin resource sharing (CORS) policy to limit resource sharing between client applications, configured by the client application type
• C. Use an SLA-based rate limiting policy and assign a client application to a matching SLA tier based on its type
• D. Use a rate limiting policy and a client ID enforcement policy, each configured by the client application type

Answer: C

Explanation:
Correct answer: 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

NEW QUESTION # 65
A retail company is using an Order API to accept new orders. The Order API uses a JMS queue to submit orders to a backend order management service. The normal load for orders is being handled using two (2) CloudHub workers, each configured with 0.2 vCore. The CPU load of each CloudHub worker normally runs well below 70%. However, several times during the year the Order API gets four times (4x) the average number of orders. This causes the CloudHub worker CPU load to exceed 90% and the order submission time to exceed 30 seconds. The cause, however, is NOT the backend order management service, which still responds fast enough to meet the response SLA for the Order API. What is the MOST resource-efficient way to configure the Mule application's CloudHub deployment to help the company cope with this performance challenge?

• A. Use a vertical CloudHub autoscaling policy that triggers on CPU utilization greater than 70%
• B. Permanently increase the number of CloudHub workers by four times (4x) to eight (8) CloudHub workers
• C. Permanently increase the size of each of the two (2) CloudHub workers by at least four times (4x) to one (1) vCore
• D. Use a horizontal CloudHub autoscaling policy that triggers on CPU utilization greater than 70%

Answer: D

Explanation:
Correct answer: Use a horizontal CloudHub autoscaling policy that triggers on CPU utilization greater than 70%
*****************************************
The scenario in the question is very clearly stating that the usual traffic in the year is pretty well handled by the existing worker configuration with CPU running well below 70%. The problem occurs only "sometimes" occasionally when there is spike in the number of orders coming in.
So, based on above, We neither need to permanently increase the size of each worker nor need to permanently increase the number of workers. This is unnecessary as other than those "occasional" times the resources are idle and wasted.
We have two options left now. Either to use horizontal Cloudhub autoscaling policy to automatically increase the number of workers or to use vertical Cloudhub autoscaling policy to automatically increase the vCore size of each worker.
Here, we need to take two things into consideration:
1. CPU
2. Order Submission Rate to JMS Queue
>> From CPU perspective, both the options (horizontal and vertical scaling) solves the issue. Both helps to bring down the usage below 90%.
>> However, If we go with Vertical Scaling, then from Order Submission Rate perspective, as the application is still being load balanced with two workers only, there may not be much improvement in the incoming request processing rate and order submission rate to JMS queue. The throughput would be same as before. Only CPU utilization comes down.
>> But, if we go with Horizontal Scaling, it will spawn new workers and adds extra hand to increase the throughput as more workers are being load balanced now. This way we can address both CPU and Order Submission rate.
Hence, Horizontal CloudHub Autoscaling policy is the right and best answer.

NEW QUESTION # 66
What is true about the technology architecture of Anypoint VPCs?

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

Answer: C

Explanation:
Explanation
https://docs.mulesoft.com/runtime-manager/vpc-connectivity-methods-concept

NEW QUESTION # 67
......

MCPA-Level-1 Exam Questions – Valid MCPA-Level-1 Dumps Pdf: https://www.dumptorrent.com/MCPA-Level-1-braindumps-torrent.html