CompTIA
Checkpoint
ISC
HP
Dell
EC-Council
EXIN
Fortinet
ITIL®
Juniper
PMI
Microsoft
VMware
Avaya
Google
Salesforce
Amazon
Palo Alto Networks
Certiport
ISC2
All Vendors
  2. Home
  3. Exams
  4. MuleSoft
  5. MuleSoft Certified Platform Architect - Level 1

Free MuleSoft Certified Platform Architect - Level 1 Exam Braindumps (page: 12)

Page 11 of 24
PDF with 95 Questions

What is typically NOT a function of the APIs created within the framework called API-led connectivity?

  1. They provide an additional layer of resilience on top of the underlying backend system, thereby insulating clients from extended failure of these systems.
  2. They allow for innovation at the user Interface level by consuming the underlying assets without being aware of how data Is being extracted from backend systems.
  3. They reduce the dependency on the underlying backend systems by helping unlock data from backend systems In a reusable and consumable way.
  4. They can compose data from various sources and combine them with orchestration logic to create higher level value.

Answer(s): A

Explanation:

Correct Answer: They provide an additional layer of resilience on top of the underlying backend system, thereby insulating clients from extended failure of these systems.
***************************************** In API-led connectivity,
>> Experience APIs - allow for innovation at the user interface level by consuming the underlying assets without being aware of how data is being extracted from backend systems.
>> Process APIs - compose data from various sources and combine them with orchestration logic to create higher level value
>> System APIs - reduce the dependency on the underlying backend systems by helping unlock data from backend systems in a reusable and consumable way.
However, they NEVER promise that they provide an additional layer of resilience on top of the underlying backend system, thereby insulating clients from extended failure of these systems.


Reference:

https://dzone.com/articles/api-led-connectivity-with-mule



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?

  1. Approve the client application request for the chosen SLA tier
  2. Request access to the appropriate API Instances deployed to multiple environments using the client application's credentials
  3. Modify the client application to call the API using the client application's credentials
  4. Create a new application in Anypoint Exchange for requesting access to the API

Answer(s): A

Explanation:

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


Reference:

https://docs.mulesoft.com/api-manager/2.x/defining-sla-tiers#defining-a-tier



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

  1. A decrease in the number of connections within the application network supporting the business process
  2. A higher number of discoverable API-related assets in the application network
  3. A better response time for the end user as a result of the APIs being smaller in scope and complexity
  4. An overall tower usage of resources because each fine-grained API consumes less resources

Answer(s): B

Explanation:

Correct Answer: A higher number of discoverable API-related assets in the application network.
*****************************************
>> We do NOT get faster response times in fine-grained approach when compared to coarse-grained approach.
>> In fact, we get faster response times from a network having coarse-grained APIs compared to a network having fine-grained APIs model. The reasons are below.

Fine-grained approach:
1. will have more APIs compared to coarse-grained
2. So, more orchestration needs to be done to achieve a functionality in business process.
3. Which means, lots of API calls to be made. So, more connections will needs to be established. So, obviously more hops, more network i/o, more number of integration points compared to coarse- grained approach where fewer APIs with bulk functionality embedded in them.
4. That is why, because of all these extra hops and added latencies, fine-grained approach will have bit more response times compared to coarse-grained.
5. Not only added latencies and connections, there will be more resources used up in fine-grained approach due to more number of APIs.

That's why, fine-grained APIs are good in a way to expose more number of resuable assets in your network and make them discoverable. However, needs more maintenance, taking care of integration points, connections, resources with a little compromise w.r.t network hops and response times.



What correctly characterizes unit tests of Mule applications?

  1. They test the validity of input and output of source and target systems
  2. They must be run in a unit testing environment with dedicated Mule runtimes for the environment
  3. They must be triggered by an external client tool or event source
  4. They are typically written using MUnit to run in an embedded Mule runtime that does not require external connectivity

Answer(s): D

Explanation:

Correct Answer: They are typically written using MUnit to run in an embedded Mule runtime that does not require external connectivity.
*****************************************
Below TWO are characteristics of Integration Tests but NOT unit tests:
>> They test the validity of input and output of source and target systems.
>> They must be triggered by an external client tool or event source.
It is NOT TRUE that Unit Tests must be run in a unit testing environment with dedicated Mule runtimes for the environment.
MuleSoft offers MUnit for writing Unit Tests and they run in an embedded Mule Runtime without needing any separate/ dedicated Runtimes to execute them. They also do NOT need any external connectivity as MUnit supports mocking via stubs.


Reference:

https://dzone.com/articles/munit-framework






Post your Comments and Discuss MuleSoft MuleSoft Certified Platform Architect - Level 1 exam with other Community members:

MuleSoft Certified Platform Architect - Level 1 Exam Discussions & Posts