ExamGecko
Home Home / Salesforce / Certified MuleSoft Developer I

Salesforce Certified MuleSoft Developer I Practice Test - Questions Answers, Page 9

Question list
Search
Search

List of questions

Search

Related questions











Select the correct Owner-Layer combinations from below options

A.
1. App Developers owns and focuses on Experience Layer APIs 2. Central IT owns and focuses on Process Layer APIs 3. LOB IT owns and focuses on System Layer APIs
A.
1. App Developers owns and focuses on Experience Layer APIs 2. Central IT owns and focuses on Process Layer APIs 3. LOB IT owns and focuses on System Layer APIs
Answers
B.
1. Central IT owns and focuses on Experience Layer APIs 2. LOB IT owns and focuses on Process Layer APIs 3. App Developers owns and focuses on System Layer APIs
B.
1. Central IT owns and focuses on Experience Layer APIs 2. LOB IT owns and focuses on Process Layer APIs 3. App Developers owns and focuses on System Layer APIs
Answers
C.
1. App Developers owns and focuses on Experience Layer APIs 2. LOB IT owns and focuses on Process Layer APIs 3. Central IT owns and focuses on System Layer APIs
C.
1. App Developers owns and focuses on Experience Layer APIs 2. LOB IT owns and focuses on Process Layer APIs 3. Central IT owns and focuses on System Layer APIs
Answers
Suggested answer: C

Explanation:

1. App Developers owns and focuses on Experience Layer APIs2. LOB IT owns and focuses on Process Layer APIs3. Central IT owns and focuses on System Layer APIs

https://blogs.mulesoft.com/biz/api/experience-api-ownership/https://blogs.mulesoft.com/biz/api/process-api-ownership/https://blogs.mulesoft.com/biz/api/system-api-ownership/

What Anypoint Platform Capabilities listed below fall under APIs and API Invocations/Consumers category? Select TWO.

A.
API Operations and Management
A.
API Operations and Management
Answers
B.
API Runtime Execution and Hosting
B.
API Runtime Execution and Hosting
Answers
C.
API Consumer Engagement
C.
API Consumer Engagement
Answers
D.
API Design and Development
D.
API Design and Development
Answers
Suggested answer: D

Explanation:

Answer:s: API Design and Development and API Runtime Execution and Hosting. >> 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

Answer:s:API Operations and Management and 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

Bottom of FormTop of Form

What are 4 important Platform Capabilities offered by Anypoint Platform?

A.
API Versioning, API Runtime Execution and Hosting, API Invocation, API Consumer Engagement
A.
API Versioning, API Runtime Execution and Hosting, API Invocation, API Consumer Engagement
Answers
B.
API Design and Development, API Runtime Execution and Hosting, API Versioning, API Deprecation
B.
API Design and Development, API Runtime Execution and Hosting, API Versioning, API Deprecation
Answers
C.
API Design and Development, API Runtime Execution and Hosting, API Operations and Management, API Consumer Engagement
C.
API Design and Development, API Runtime Execution and Hosting, API Operations and Management, API Consumer Engagement
Answers
D.
API Design and Development, API Deprecation, API Versioning, API Consumer Engagement
D.
API Design and Development, API Deprecation, API Versioning, API Consumer Engagement
Answers
Suggested answer: C

Explanation:

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

The implementation of a Process API must change.

What is a valid approach that minimizes the impact of this change on API clients?

A.
Update the RAML definition of the current Process API and notify API client developers by sending them links to the updated RAML definition
A.
Update the RAML definition of the current Process API and notify API client developers by sending them links to the updated RAML definition
Answers
B.
Postpone changes until API consumers acknowledge they are ready to migrate to a new Process API or API version
B.
Postpone changes until API consumers acknowledge they are ready to migrate to a new Process API or API version
Answers
C.
Implement required changes to the Process API implementation so that whenever possible, the Process API's RAML definition remains unchanged
C.
Implement required changes to the Process API implementation so that whenever possible, the Process API's RAML definition remains unchanged
Answers
D.
Implement the Process API changes in a new API implementation, and have the old API implementation return an HTTP status code 301 - Moved Permanently to inform API clients they should be calling the new API implementation
D.
Implement the Process API changes in a new API implementation, and have the old API implementation return an HTTP status code 301 - Moved Permanently to inform API clients they should be calling the new API implementation
Answers
Suggested answer: C

Explanation:

Implement required changes to the Process API implementation sothat, whenever possible, the Process API's RAML definition remains unchanged.. Key requirement in the question is:>> Approach that minimizes the impact of this change on API clientsBased on above:>> Updating the RAML definition would possibly impact the API clients if the changes require any thing mandatory from client side. So, one should try to avoid doing that until really necessary.>> Implementing the changes as a completely different API and then redirectly the clients with 3xx status code is really upsetting design and heavily impacts the API clients.>> Organisations and IT cannot simply postpone the changes required until all API consumers acknowledge they are ready to migrate to a new Process API or API version. This is unrealistic and not possible.The best way to handle the changes always is to implement required changes to the API implementations so that, whenever possible, the API's RAML definition remains unchanged.

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
A.
Option A
Answers
B.
Option B
B.
Option B
Answers
C.
Option C
C.
Option C
Answers
D.
Option D
D.
Option D
Answers
Suggested answer: C

Explanation:

Separate Experience APIs for the mobile and web app, but acommon 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.

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?

A.
The client ID and secret for the Anypoint Platform account owning the API in the STAGING environment
A.
The client ID and secret for the Anypoint Platform account owning the API in the STAGING environment
Answers
B.
The client ID and secret for the Anypoint Platform account's STAGING environment
B.
The client ID and secret for the Anypoint Platform account's STAGING environment
Answers
C.
The client ID and secret obtained from Anypoint Exchange for the API instance in the STAGING environment
C.
The client ID and secret obtained from Anypoint Exchange for the API instance in the STAGING environment
Answers
D.
A valid OAuth token obtained from Anypoint Platform and its associated client ID and secret
D.
A valid OAuth token obtained from Anypoint Platform and its associated client ID and secret
Answers
Suggested answer: C

Explanation:

The client ID and secret obtained from Anypoint Exchange for theAPI instance in the STAGING environment. >> We CANNOT use the client ID and secret of Anypoint Platform account or any individual environments for accessing the APIs>> As the type of policy that is enforced on the API in question is 'Client ID Enforcment Policy', OAuth token based access won't work.Right way to access the API is to use the client ID and secret obtained from Anypoint Exchange for the API instance in a particular environment we want to work on.Managing API instance Contracts on API Managerhttps://docs.mulesoft.com/api-manager/1.x/request-access-to-api-taskhttps://docs.mulesoft.com/exchange/to-request-accesshttps://docs.mulesoft.com/api-manager/2.x/policy-mule3-client-id-based-policies

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?

A.
From the Mule runtime or the API implementation, depending on the deployment model
A.
From the Mule runtime or the API implementation, depending on the deployment model
Answers
B.
From various components of Anypoint Platform, such as the Shared Load Balancer, VPC, and Mule runtimes
B.
From various components of Anypoint Platform, such as the Shared Load Balancer, VPC, and Mule runtimes
Answers
C.
From the Mule runtime or the API Manager, depending on the type of data
C.
From the Mule runtime or the API Manager, depending on the type of data
Answers
D.
From the Mule runtime irrespective of the deployment model
D.
From the Mule runtime irrespective of the deployment model
Answers
Suggested answer: D

Explanation:

From the Mule runtime irrespective of the deployment model. >> Monitoring and Alerting metrics are always originated from Mule Runtimes irrespective of the deployment model.>> It may seems that some metrics (Runtime Manager) are originated from Mule Runtime and some are (API Invocations/ API Analytics) from API Manager. However, this is realistically NOT TRUE. The reason is, API manager is just a management tool for API instances but all policies upon applying on APIs eventually gets executed on Mule Runtimes only (Either Embedded or API Proxy).>> Similarly all API Implementations also run on Mule Runtimes.So, most of the day required for monitoring and alerts are originated fron Mule Runtimes only irrespective of whether the deployment model is MuleSoft-hosted or Customer-hosted or Hybrid.

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?

A.
An SLA for the upstream API CANNOT be provided
A.
An SLA for the upstream API CANNOT be provided
Answers
B.
The invocation of the downstream API will run to completion without timing out
B.
The invocation of the downstream API will run to completion without timing out
Answers
C.
A default timeout of 500 ms will automatically be applied by the Mule runtime in which the upstream API implementation executes
C.
A default timeout of 500 ms will automatically be applied by the Mule runtime in which the upstream API implementation executes
Answers
D.
A toad-dependent timeout of less than 1000 ms will be applied by the Mule runtime in which the downstream API implementation executes
D.
A toad-dependent timeout of less than 1000 ms will be applied by the Mule runtime in which the downstream API implementation executes
Answers
Suggested answer: A

Explanation:

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.

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

A.
It makes API Manager aware of API implementations and hence enables it to enforce policies
A.
It makes API Manager aware of API implementations and hence enables it to enforce policies
Answers
B.
It enables Anypoint Studio to discover API definitions configured in Anypoint Platform
B.
It enables Anypoint Studio to discover API definitions configured in Anypoint Platform
Answers
C.
It enables Anypoint Exchange to discover assets and makes them available for reuse
C.
It enables Anypoint Exchange to discover assets and makes them available for reuse
Answers
D.
It enables Anypoint Analytics to gain insight into the usage of APIs
D.
It enables Anypoint Analytics to gain insight into the usage of APIs
Answers
Suggested answer: A

Explanation:

It makes API Manager aware of API implementations and henceenables it to enforce policies.. >> API Autodiscovery is a mechanism that manages an API from API Manager by pairing the deployed application to an API created on the platform.>> API Management includes tracking, enforcing policies if you apply any, and reporting API analytics.>> Critical to the Autodiscovery process is identifying the API by providing the API name and version.https://docs.mulesoft.com/api-manager/2.x/api-auto-discovery-new-concepthttps://docs.mulesoft.com/api-manager/1.x/api-auto-discoveryhttps://docs.mulesoft.com/api-manager/2.x/api-auto-discovery-new-concept

What should be ensured before sharing an API through a public Anypoint Exchange portal?

A.
The visibility level of the API instances of that API that need to be publicly accessible should be set to public visibility
A.
The visibility level of the API instances of that API that need to be publicly accessible should be set to public visibility
Answers
B.
The users needing access to the API should be added to the appropriate role in Anypoint Platform
B.
The users needing access to the API should be added to the appropriate role in Anypoint Platform
Answers
C.
The API should be functional with at least an initial implementation deployed and accessible for users to interact with
C.
The API should be functional with at least an initial implementation deployed and accessible for users to interact with
Answers
D.
The API should be secured using one of the supported authentication/authorization mechanisms to ensure that data is not compromised
D.
The API should be secured using one of the supported authentication/authorization mechanisms to ensure that data is not compromised
Answers
Suggested answer: A

Explanation:

The visibility level of the API instances of that API that need to bepublicly accessible should be set to public visibility.. https://docs.mulesoft.com/exchange/to-share-api-asset-to-portal

Total 95 questions
Go to page: of 10