Steps Necessary To Pass The MCPA-Level-1 Exam from Training Expert TestKingIT [Q39-Q54]

By adminOn April 27, 2022

Rate this post

Steps Necessary To Pass The MCPA-Level-1 Exam from Training Expert TestKingIT

Valid Way To Pass MuleSoft Certified Platform Architect’s MCPA-Level-1 Exam

How to book the MuleSoft MCPA – Level 1: MuleSoft Certified Platform Architect – Level 1 Exam

These are the following steps for registering the MuleSoft MCPA – Level 1: MuleSoft Certified Platform Architect – Level 1 exam.

Step 1: Visit MuleSoft Exam Registration.
Step 2: Sign up/log in to the MuleSoft account.
Step 3: Select a local center based on your country, date, time, and confirm with a payment method.

NO.39 An organization has created an API-led architecture that uses various API layers to integrate mobile clients with a backend system. The backend system consists of a number of specialized components and can be accessed via a REST API. The process and experience APIs share the same bounded-context model that is different from the backend data model. What additional canonical models, bounded-context models, or anti-corruption layers are best added to this architecture to help process data consumed from the backend system?

Create a bounded-context model for every layer and overlap them when the boundary contexts overlap, letting API developers know about the differences between upstream and downstream data models

Create a canonical model that combines the backend and API-led models to simplify and unify data models, and minimize data transformations.

Create a bounded-context model for the system layer to closely match the backend data model, and add an anti-corruption layer to let the different bounded contexts cooperate across the system and process layers

Create an anti-corruption layer for every API to perform transformation for every data model to match each other, and let data simply travel between APIs to avoid the complexity and overhead of building canonical models

NO.40 An organization makes a strategic decision to move towards an IT operating model that emphasizes consumption of reusable IT assets using modern APIs (as defined by MuleSoft).
What best describes each modern API in relation to this new IT operating model?

Each modern API has its own software development lifecycle, which reduces the need for documentation and automation

Each modem API must be treated like a product and designed for a particular target audience (for instance, mobile app developers)

Each modern API must be easy to consume, so should avoid complex authentication mechanisms such as SAML or JWT D

Each modern API must be REST and HTTP based

NO.41 What condition requires using a CloudHub Dedicated Load Balancer?

When cross-region load balancing is required between separate deployments of the same Mule application

When custom DNS names are required for API implementations deployed to customer-hosted Mule runtimes

When API invocations across multiple CloudHub workers must be load balanced

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

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

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

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

NO.45 When using CloudHub with the Shared Load Balancer, what is managed EXCLUSIVELY by the API implementation (the Mule application) and NOT by Anypoint Platform?

The assignment of each HTTP request to a particular CloudHub worker

The logging configuration that enables log entries to be visible in Runtime Manager

The SSL certificates used by the API implementation to expose HTTPS endpoints

The number of DNS entries allocated to the API implementation

NO.46 Refer to the exhibit.

Three business processes need to be implemented, and the implementations need to communicate with several different SaaS applications.
These processes are owned by separate (siloed) LOBs and are mainly independent of each other, but do share a few business entities. Each LOB has one development team and their own budget In this organizational context, what is the most effective approach to choose the API data models for the APIs that will implement these business processes with minimal redundancy of the data models?
A) Build several Bounded Context Data Models that align with coherent parts of the business processes and the definitions of associated business entities

B) Build distinct data models for each API to follow established micro-services and Agile API-centric practices

C) Build all API data models using XML schema to drive consistency and reuse across the organization

D) Build one centralized Canonical Data Model (Enterprise Data Model) that unifies all the data types from all three business processes, ensuring the data model is consistent and non-redundant

Option A

Option B

Option C

Option D

NO.47 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?

443

8081

8091

8082

NO.48 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)?

They must avoid using the Object Store as it depends on services deployed ONLY to the US East region

They must use a Jurisdiction-local external messaging system such as Active MQ rather than Anypoint MQ

They must te deployed to Anypoint Platform runtime planes that are managed by Anypoint Platform control planes, with both planes in the same Jurisdiction

They must ensure ALL data is encrypted both in transit and at rest

NO.49 A system API is deployed to a primary environment as well as to a disaster recovery (DR) environment, with different DNS names in each environment. A process API is a client to the system API and is being rate limited by the system API, with different limits in each of the environments. The system API’s DR environment provides only 20% of the rate limiting offered by the primary environment. What is the best API fault-tolerant invocation strategy to reduce overall errors in the process API, given these conditions and constraints?

Invoke the system API deployed to the primary environment; add timeout and retry logic to the process API to avoid intermittent failures; if it still fails, invoke the system API deployed to the DR environment

Invoke the system API deployed to the primary environment; add retry logic to the process API to handle intermittent failures by invoking the system API deployed to the DR environment

In parallel, invoke the system API deployed to the primary environment and the system API deployed to the DR environment; add timeout and retry logic to the process API to avoid intermittent failures; add logic to the process API to combine the results

Invoke the system API deployed to the primary environment; add timeout and retry logic to the process API to avoid intermittent failures; if it still fails, invoke a copy of the process API deployed to the DR environment

Correct answer: Invoke the system API deployed to the primary environment; add timeout and retry logic to the process API to avoid intermittent failures; if it still fails, invoke the system API deployed to the DR environment
*****************************************
There is one important consideration to be noted in the question which is – System API in DR environment provides only 20% of the rate limiting offered by the primary environment. So, comparitively, very less calls will be allowed into the DR environment API opposed to its primary environment. With this in mind, lets analyse what is the right and best fault-tolerant invocation strategy.
1. Invoking both the system APIs in parallel is definitely NOT a feasible approach because of the 20% limitation we have on DR environment. Calling in parallel every time would easily and quickly exhaust the rate limits on DR environment and may not give chance to genuine intermittent error scenarios to let in during the time of need.
2. Another option given is suggesting to add timeout and retry logic to process API while invoking primary environment’s system API. This is good so far. However, when all retries failed, the option is suggesting to invoke the copy of process API on DR environment which is not right or recommended. Only system API is the one to be considered for fallback and not the whole process API. Process APIs usually have lot of heavy orchestration calling many other APIs which we do not want to repeat again by calling DR’s process API. So this option is NOT right.
3. One more option given is suggesting to add the retry (no timeout) logic to process API to directly retry on DR environment’s system API instead of retrying the primary environment system API first. This is not at all a proper fallback. A proper fallback should occur only after all retries are performed and exhausted on Primary environment first. But here, the option is suggesting to directly retry fallback API on first failure itself without trying main API. So, this option is NOT right too.
This leaves us one option which is right and best fit.
– Invoke the system API deployed to the primary environment
– Add Timeout and Retry logic on it in process API
– If it fails even after all retries, then invoke the system API deployed to the DR environment.

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

NO.51 An API implementation is deployed to CloudHub.
What conditions can be alerted on using the default Anypoint Platform functionality, where the alert conditions depend on the end-to-end request processing of the API implementation?

When the API is invoked by an unrecognized API client

When a particular API client invokes the API too often within a given time period

When the response time of API invocations exceeds a threshold

When the API receives a very high number of API invocations

NO.52 An Anypoint Platform organization has been configured with an external identity provider (IdP) for identity management and client management. What credentials or token must be provided to Anypoint CLI to execute commands against the Anypoint Platform APIs?

The credentials provided by the IdP for identity management

The credentials provided by the IdP for client management

An OAuth 2.0 token generated using the credentials provided by the IdP for client management

An OAuth 2.0 token generated using the credentials provided by the IdP for identity management

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

NO.54 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?

Workers belonging to a given environment are assigned to the same AZ within that region

AZs are selected as part of the Mule application’s deployment configuration

Workers are randomly distributed across available AZs within that region

An AZ is randomly selected for a Mule application, and all the Mule application’s CloudHub workers are assigned to that one AZ

Topics of MuleSoft MCPA – Level 1: MuleSoft Certified Platform Architect – Level 1 Exam

Candidates must know the exam topics before they start preparation because it will help them in hitting the core. Our mcpa-level-1 practice exams will include the topics discussed in detail:

Given specific organizational requirements, preferences, and constraints, identify all suitable point Platform deployment options
Describe the metrics collected by Any point Platform for API invocations
When asynchronous execution of API invocations is needed, select when to appropriately use polling or callbacks
Describe and select between the options for performing API analytics within and outside of Any point Platform
Specify alerts to define for key metrics of API invocations for all layers of API-led connectivity
Describe the purpose and roles of a Center for Enablement (C4E)
Describe the creation and publication of reusable API-related assets using RAML and Anypoint Platform components
Correctly use the terms API, API implementation, API client, API consumer, and API invocation
Identify idempotent HTTP methods and HTTP-native support for optimistic concurrency.
Describe the role and characteristics of the “modern API.”
Identify changes to an API that would require or not require a major version increment.
Define and describe the benefits of API-led connectivity and application networks
Explain MuleSoft’s proposal for closing the IT delivery gap
Define outcome-based delivery (OBD)
Given specific preferences and constraints, select API policy enforcement with or without API proxies
Given a layer of API-led connectivity, identify API policies that are typically applied to that layer and the scenarios needing custom policies
Specify alerts to define for API implementations
Break down functional requirements into business-aligned APIs with effective granularity. Given a set of APIs and specific preferences and organizational characteristics, recommend the use of an Enterprise Data Model or Bounded Context Data Models
Select appropriate API policies to enforce non-functional constraints on API invocations
Identify KPIs to measure the success of a C4E

All MCPA-Level-1 Dumps and MuleSoft Certified Platform Architect – Level 1 Training Courses: https://www.testkingit.com/MuleSoft/latest-MCPA-Level-1-exam-dumps.html