2023 MCPA-Level-1 exam torrent MCPA-Level-1 Study Guide [Q49-Q73]

2023 MCPA-Level-1 exam torrent MCPA-Level-1 Study Guide [Q49-Q73]

June 18, 2023 latestexam 0 Comments

Rate this post

2023 MCPA-Level-1 exam torrent MCPA-Level-1 Study Guide

Easily pass MCPA-Level-1 Exam with our Dumps & PDF Test Engine

Introduction to MuleSoft MCPA – Level 1: MuleSoft Certified Platform Architect – Level 1 Exam

A MuleSoft Certified Developer – Level 1 should be able to successfully work on basic Mule 4 projects with guidance and supervision. The exam validates that a developer has the required knowledge and skills to design, build, test and debug, deploy, and manage basic APIs and integrations: moving from Anypoint Platform to Anypoint Studio and back.
Certified candidates should be able to:

Connect to a range of resources including databases, files, web services, SaaS applications, and JMS queues.
Process batch records.
Use MuleSoft-hosted Anypoint Platform to take a basic API through all the steps of its lifecycle: design, build, deploy, manage, and govern.
Perform basic data transformations using Data Weave 2.0.

Becoming a MuleSoft architect can either be achieved through the platform or the integration architect path. In the first case, candidates are tested for their ability to create company-level decisions by looking at the big picture in building an effective application network. This path is designed for higher-level solutions or enterprise architects.

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

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

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

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

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

Q50. What is a best practice when building System APIs?

Document the API using an easily consumable asset like a RAML definition

Model all API resources and methods to closely mimic the operations of the backend system

Build an Enterprise Data Model (Canonical Data Model) for each backend system and apply it to System APIs

Expose to API clients all technical details of the API implementation’s interaction wifch the backend system

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.

Q51. Which of the below, when used together, makes the IT Operational Model effective?

Create reusable assets, Do marketing on the created assets across organization, Arrange time to time LOB reviews to ensure assets are being consumed or not

Create reusable assets, Make them discoverable so that LOB teams can self-serve and browse the APIs, Get active feedback and usage metrics

Create resuable assets, make them discoverable so that LOB teams can self-serve and browse the APIs

Correct answer: Create reusable assets, Make them discoverable so that LOB teams can self-serve and browse the APIs, Get active feedback and usage metrics.
*****************************************

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

Approve the client application request for the chosen SLA tier

Request access to the appropriate API Instances deployed to multiple environments using the client application’s credentials

Modify the client application to call the API using the client application’s credentials

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

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

Q53. What best explains the use of auto-discovery in API implementations?

It makes API Manager aware of API implementations and hence enables it to enforce policies

It enables Anypoint Studio to discover API definitions configured in Anypoint Platform

It enables Anypoint Exchange to discover assets and makes them available for reuse

It enables Anypoint Analytics to gain insight into the usage of APIs

Q54. When designing an upstream API and its implementation, the development team has been advised to NOT set timeouts when invoking a downstream API, because that downstream API has no SLA that can be relied upon.
This is the only downstream API dependency of that upstream API.
Assume the downstream API runs uninterrupted without crashing. What is the impact of this advice?

An SLA for the upstream API CANNOT be provided

The invocation of the downstream API will run to completion without timing out

A default timeout of 500 ms will automatically be applied by the Mule runtime in which the upstream API implementation executes

A toad-dependent timeout of less than 1000 ms will be applied by the Mule runtime in which the downstream API implementation executes

Q55. What best describes the Fully Qualified Domain Names (FQDNs), also known as DNS entries, created when a Mule application is deployed to the CloudHub Shared Worker Cloud?

A fixed number of FQDNs are created, IRRESPECTIVE of the environment and VPC design

The FQDNs are determined by the application name chosen, IRRESPECTIVE of the region

The FQDNs are determined by the application name, but can be modified by an administrator after deployment

The FQDNs are determined by both the application name and the Anypoint Platform organization

Correct answer: The FQDNs are determined by the application name chosen, IRRESPECTIVE of the region
*****************************************
>> When deploying applications to Shared Worker Cloud, the FQDN are always determined by application name chosen.
>> It does NOT matter what region the app is being deployed to.
>> Although it is fact and true that the generated FQDN will have the region included in it (Ex: exp-salesorder-api.au-s1.cloudhub.io), it does NOT mean that the same name can be used when deploying to another CloudHub region.
>> Application name should be universally unique irrespective of Region and Organization and solely determines the FQDN for Shared Load Balancers.

Q56. 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 CloudHub worker fails with an out-of-memory exception

API Manager has an extended outage during the initial deployment of the API implementation

The AWS region goes offline with a major network failure to the relevant AWS data centers

The Order Management System is Inaccessible due to a network outage in the organization’s on-premises data center

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

OAuth 2.0 access token enforcement

Client ID enforcement

JSON threat protection

IP whitelist

Q58. An organization uses various cloud-based SaaS systems and multiple on-premises systems. The on-premises systems are an important part of the organization’s application network and can only be accessed from within the organization’s intranet.
What is the best way to configure and use Anypoint Platform to support integrations with both the cloud-based SaaS systems and on-premises systems?
A) Use CloudHub-deployed Mule runtimes in an Anypoint VPC managed by Anypoint Platform Private Cloud Edition control plane

B) Use CloudHub-deployed Mule runtimes in the shared worker cloud managed by the MuleSoft-hosted Anypoint Platform control plane

C) Use an on-premises installation of Mule runtimes that are completely isolated with NO external network access, managed by the Anypoint Platform Private Cloud Edition control plane

D) Use a combination of Cloud Hub-deployed and manually provisioned on-premises Mule runtimes managed by the MuleSoft-hosted Anypoint Platform control plane

Option A

Option B

Option C

Option D

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

Single sign-on is required to sign in to Anypoint Platform

The application network must include System APIs that interact with the Identity Provider

To invoke OAuth 2.0-protected APIs managed by Anypoint Platform, API clients must submit access tokens issued by that same Identity Provider

APIs managed by Anypoint Platform must be protected by SAML 2.0 policies

Explanation/Reference: https://www.folkstalk.com/2019/11/mulesoft-integration-and-platform.html

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

Implement (or generate) an API proxy Mule application for each of the APIs, then deploy the API proxies to the Mule runtimes

Redeploy the API implementations to the same servers running the Mule runtimes

Add an additional endpoint to each API for partner-enablement consumption

Duplicate the APIs as Mule applications, then deploy them to the Mule runtimes

Q61. What is a typical result of using a fine-grained rather than a coarse-grained API deployment model to implement a given business process?

A decrease in the number of connections within the application network supporting the business process

A higher number of discoverable API-related assets in the application network

A better response time for the end user as a result of the APIs being smaller in scope and complexity

An overall tower usage of resources because each fine-grained API consumes less resources

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

When the data type of the response is changed for the method called by the API client

When a new method is added to the resource used by the API client

When a new required field is added to the method called by the API client

When a child method is added to the method called by the API client

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.

Q63. In an organization, the InfoSec team is investigating Anypoint Platform related data traffic.

From where does most of the data available to Anypoint Platform for monitoring and alerting originate?

From the Mule runtime or the API implementation, depending on the deployment model

From various components of Anypoint Platform, such as the Shared Load Balancer, VPC, and Mule runtimes

From the Mule runtime or the API Manager, depending on the type of data

From the Mule runtime irrespective of the deployment model

Q64. An API implementation is being designed that must invoke an Order API, which is known to repeatedly experience downtime.
For this reason, a fallback API is to be called when the Order API is unavailable.
What approach to designing the invocation of the fallback API provides the best resilience?

Search Anypoint Exchange for a suitable existing fallback API, and then implement invocations to this fallback API in addition to the Order API

Create a separate entry for the Order API in API Manager, and then invoke this API as a fallback API if the primary Order API is unavailable

Redirect client requests through an HTTP 307 Temporary Redirect status code to the fallback API whenever the Order API is unavailable

Set an option in the HTTP Requester component that invokes the Order API to instead invoke a fallback API whenever an HTTP 4xx or 5xx response status code is returned from the Order API

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

When it Is required to make ALL applications highly available across multiple data centers

When it is required that ALL APIs are private and NOT exposed to the public cloud

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

When ALL backend systems in the application network are deployed in the organization’s intranet

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

Q66. What CANNOT be effectively enforced using an API policy in Anypoint Platform?

Guarding against Denial of Service attacks

Maintaining tamper-proof credentials between APIs

Logging HTTP requests and responses

Backend system overloading

Q67. An API implementation returns three X-RateLimit-* HTTP response headers to a requesting API client. What type of information do these response headers indicate to the API client?

The error codes that result from throttling

A correlation ID that should be sent in the next request

The HTTP response size

The remaining capacity allowed by the API implementation

Correct answer: The remaining capacity allowed by the API implementation.
*****************************************
>> Reference: https://docs.mulesoft.com/api-manager/2.x/rate-limiting-and-throttling-sla-based-policies#response-headers

Q68. What is true about the technology architecture of Anypoint VPCs?

The private IP address range of an Anypoint VPC is automatically chosen by CloudHub

Traffic between Mule applications deployed to an Anypoint VPC and on-premises systems can stay within a private network

Each CloudHub environment requires a separate Anypoint VPC

VPC peering can be used to link the underlying AWS VPC to an on-premises (non AWS) private network

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

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

Permanently increase the size of each of the two (2) CloudHub workers by at least four times (4x) to one (1) vCore

Use a vertical CloudHub autoscaling policy that triggers on CPU utilization greater than 70%

Permanently increase the number of CloudHub workers by four times (4x) to eight (8) CloudHub workers

Use a horizontal CloudHub autoscaling policy that triggers on CPU utilization greater than 70%

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.

Q70. How are an API implementation, API client, and API consumer combined to invoke and process an API?

The API consumer creates an API implementation, which receives API invocations from an API such that they are processed for an API client

The API client creates an API consumer, which receives API invocations from an API such that they are processed for an API implementation

The ApI consumer creates an API client, which sends API invocations to an API such that they are processed by an API implementation

The ApI client creates an API consumer, which sends API invocations to an API such that they are processed by an API implementation

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

The client ID and secret for the Anypoint Platform account owning the API in the STAGING environment

The client ID and secret for the Anypoint Platform account’s STAGING environment

The client ID and secret obtained from Anypoint Exchange for the API instance in the STAGING environment

A valid OAuth token obtained from Anypoint Platform and its associated client ID and secret

Explanation
https://docs.mulesoft.com/api-manager/2.x/policy-mule3-client-id-based-policies

Q72. Refer to the exhibit.

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

Anypoint Runtime Manager initiates a network connection to a Mule runtime in order to deploy Mule applications

The MuleSoft-hosted Shared Load Balancer can be used to load balance API invocations to the Mule runtimes

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

Anypoint Runtime Manager automatically ensures HA in the control plane by creating a new Mule runtime instance in case of a node failure

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

Q73. Which of the following sequence is correct?

API Client implementes logic to call an API >> API Consumer requests access to API >> API Implementation routes the request to >> API

API Consumer requests access to API >> API Client implementes logic to call an API >> API routes the request to >> API Implementation

API Consumer implementes logic to call an API >> API Client requests access to API >> API Implementation routes the request to >> API

API Client implementes logic to call an API >> API Consumer requests access to API >> API routes the request to >> API Implementation

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.

Loading …

MCPA-Level-1 PDF Pass Leader, MCPA-Level-1 Latest Real Test: https://www.latestcram.com/MCPA-Level-1-exam-cram-questions.html

Related Certifications

C_C4HCX_24 (1)
C-THR97-2405 (1)
C_THR83_2305 (1)
C_THR84_2405 (1)
C-C4H450-21 (1)
C-HCADM-01 (1)
C_FIORDEV_21 (1)
C_SECAUTH_20 (1)
C-HRHPC-2311 (1)
C_ARCON_2208 (1)

Free Cram & Latest Exams Dumps