Salesforce Certified MuleSoft Platform Architect (Mule-Arch-201) Exam Questions Instant Access

Question 1

What are 4 important Platform Capabilities offered by Anypoint Platform?

AAPI Versioning, API Runtime Execution and Hosting, API Invocation, API Consumer Engagement

BAPI Design and Development, API Runtime Execution and Hosting, API Versioning, API Deprecation

CAPI Design and Development, API Runtime Execution and Hosting, API Operations and Management, API Consumer Engagement

DAPI Design and Development, API Deprecation, API Versioning, API Consumer Engagement

Answer : C

Correct Answe r: API Design and Development, API Runtime Execution and Hosting, API Operations and Management, API Consumer Engagement

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

>> API Design and Development - Anypoint Studio, Anypoint Design Center, Anypoint Connectors

>> API Runtime Execution and Hosting - Mule Runtimes, CloudHub, Runtime Services

>> API Operations and Management - Anypoint API Manager, Anypoint Exchange

>> API Consumer Management - API Contracts, Public Portals, Anypoint Exchange, API Notebooks

Question 2

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)?

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

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

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

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

Answer : C

Correct Answe r: They must be deployed to Anypoint Platform runtime planes that are managed by Anypoint Platform control planes, with both planes in the same Jurisdiction.

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

>> As per legal regulations, all data processing to be performed within a certain jurisdiction. Meaning, the data in USA should reside within USA and should not go out. Same way, the data in EU should reside within EU and should not go out.

>> So, just encrypting the data in transit and at rest does not help to be compliant with the rules. We need to make sure that data does not go out too.

>> The data that we are talking here is not just about the messages that are published to Anypoint MQ. It includes the apps running, transaction states, application logs, events, metric info and any other metadata. So, just replacing Anypoint MQ with a locally hosted ActiveMQ does NOT help.

>> The data that we are talking here is not just about the key/value pairs that are stored in Object Store. It includes the messages published, apps running, transaction states, application logs, events, metric info and any other metadata. So, just avoiding using Object Store does NOT help.

>> The only option left and also the right option in the given choices is to deploy application on runtime and control planes that are both within the jurisdiction.

Question 3

Which layer in the API-led connectivity focuses on unlocking key systems, legacy systems, data sources etc and exposes the functionality?

AExperience Layer

BProcess Layer

CSystem Layer

Answer : C

Correct Answe r: System Layer

The APIs used in an API-led approach to connectivity fall into three categories:

System APIs -- these usually access the core systems of record and provide a means of insulating the user from the complexity or any changes to the underlying systems. Once built, many users, can access data without any need to learn the underlying systems and can reuse these APIs in multiple projects.

Process APIs -- These APIs interact with and shape data within a single system or across systems (breaking down data silos) and are created here without a dependence on the source systems from which that data originates, as well as the target channels through which that data is delivered.

Experience APIs -- Experience APIs are the means by which data can be reconfigured so that it is most easily consumed by its intended audience, all from a common data source, rather than setting up separate point-to-point integrations for each channel. An Experience API is usually created with API-first design principles where the API is designed for the specific user experience in mind.

Question 4

Refer to the exhibit.

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

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

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

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

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

Answer : C

Correct Answe r: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 usingRuntime 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.

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

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

Question 5

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

AGuarding against Denial of Service attacks

BMaintaining tamper-proof credentials between APIs

CLogging HTTP requests and responses

DBackend system overloading

Answer : A

Correct Answe r: Guarding against Denial of Service attacks

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

>> Backend system overloading can be handled by enforcing 'Spike Control Policy'

>> Logging HTTP requests and responses can be done by enforcing 'Message Logging Policy'

>> Credentials can be tamper-proofed using 'Security' and 'Compliance' Policies

However, unfortunately, there is no proper way currently on Anypoint Platform to guard against DOS attacks.

Question 6

Refer to the exhibit.

A RAML definition has been proposed for a new Promotions Process API, and has been published to Anypoint Exchange.

The Marketing Department, who will be an important consumer of the Promotions API, has important requirements and expectations that must be met.

What is the most effective way to use Anypoint Platform features to involve the Marketing Department in this early API design phase?

A) Ask the Marketing Department to interact with a mocking implementation of the API using the automatically generated API Console

B) Organize a design workshop with the DBAs of the Marketing Department in which the database schema of the Marketing IT systems is translated into RAML

C) Use Anypoint Studio to Implement the API as a Mule application, then deploy that API implementation to CloudHub and ask the Marketing Department to interact with it

D) Export an integration test suite from API designer and have the Marketing Department execute the tests In that suite to ensure they pass

AOption A

BOption B

COption C

DOption D

Answer : A

Correct Answe r:Ask the Marketing Department to interact with a mocking implementation of the API using the automatically generated API Console.

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

As per MuleSoft's IT Operating Model:

>>API consumers need NOT wait until the fullAPI implementation is ready.

>>NO technical test-suites needs to be shared with end users to interact with APIs.

>>Anypoint Platform offers a mocking capability on all the published API specifications to Anypoint Exchange which also will be rich in documentation covering all details of API functionalities and working nature.

>>No needs of arranging days of workshops with end users for feedback.

API consumers can use Anypoint Exchange features on the platform and interact with the API using its mocking feature. The feedback can be shared quickly on the same to incorporate any changes.

Question 7

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?

AAn SLA for the upstream API CANNOT be provided

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

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

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

Answer : A

Correct Answe r: An SLA for the upstream API CANNOT be provided.

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

>> First thing first, the default HTTP response timeout for HTTP connector is 10000 ms (10 seconds). NOT 500 ms.

>> Mule runtime does NOT apply any such 'load-dependent' timeouts. There is no such behavior currently in Mule.

>> As there is default 10000 ms time out for HTTP connector, we CANNOT always guarantee that the invocation of the downstream API will run to completion without timing out due to its unreliable SLA times. If the response time crosses 10 seconds then the request may time out.

The main impact due to this is that a proper SLA for the upstream API CANNOT be provided.