An established communications company is beginning its API-led connectivity journey, The company has been using a successful Enterprise Data Model for many years. The company has identified a self-service account management app as the first effort for API-led, and it has identified the following APIs.
Experience layer: Mobile Account Management EAPI, Browser Account Management EAPI Process layer: Customer Lookup PAPI, Service Lookup PAPI, Account Lookup PAPI System layer: Customer SAPI, Account SAPI, Product SAPI, Service SAPI According to MuleSoft's API-led connectivity approach, which API would not be served by the Enterprise Data Model?

• A.Customer SAPI
• B.Customer Lookup PAPI
• C.Mobile Account Management EAPI
• D.Service SAPI

Comment: *

Name: *

Email: *

Verification: *

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

Comment: *

Name: *

Email: *

Verification: *

Say, there is a legacy CRM system called CRM-Z which is offering below functions:
1. Customer creation
2. Amend details of an existing customer
3. Retrieve details of a customer
4. Suspend a customer

• A.Implement a system API named customerManagement which has all the functionalities wrapped in it as various operations/resources
• B.Implement different system APIs named createCustomer, amendCustomer, retrieveCustomer and suspendCustomer as they are modular and has seperation of concerns
• C.Implement different system APIs named createCustomerInCRMZ, amendCustomerInCRMZ, retrieveCustomerFromCRMZ and suspendCustomerInCRMZ as they are modular and has seperation of concerns

Comment: *

Name: *

Email: *

Verification: *

A System API is designed to retrieve data from a backend system that has scalability challenges. What API policy can best safeguard the backend system?

• A.IPwhitelist
• B.SLA-based rate limiting
• C.Auth 2 token enforcement
• D.Client ID enforcement

Comment: *

Name: *

Email: *

Verification: *

Refer to the exhibit. An organization needs to enable access to their customer data from both a mobile app and a web application, which each need access to common fields as well as certain unique fields.
The data is available partially in a database and partially in a 3rd-party CRM system.
What APIs should be created to best fit these design requirements?

A) A Process API that contains the data required by both the web and mobile apps, allowing these applications to invoke it directly and access the data they need thereby providing the flexibility to add more fields in the future without needing API changes

B) One set of APIs (Experience API, Process API, and System API) for the web app, and another set for the mobile app

C) Separate Experience APIs for the mobile and web app, but a common Process API that invokes separate System APIs created for the database and CRM system

D) A common Experience API used by both the web and mobile apps, but separate Process APIs for the web and mobile apps that interact with the database and the CRM System

• A.Option A
• B.Option B
• C.Option C
• D.Option D

Correct Answer: C

Correct answer: Separate Experience APIs for the mobile and web app, but a common Process API that invokes separate System APIs created for the database and CRM system
*****************************************
As per MuleSoft's API-led connectivity:
>> Experience APIs should be built as per each consumer needs and their experience.
>> Process APIs should contain all the orchestration logic to achieve the business functionality.
>> System APIs should be built for each backend system to unlock their data.
Reference:

Comment: *

Name: *

Email: *

Verification: *