MuleSoft Certified Platform Architect-Level 1 Online Questions

dumps2022-01-27T03:41:57+08:00

MuleSoft Certified Platform Architect-Level 1 online questions are here for you. Passing the test is not difficult. There are 58 questions in real MuleSoft Certified Platform Architec-Level 1 exam, and you have 120 minutes to finish the test. The required passing score is 70%. The test language is English. MuleSoft Certified Platform Architect-Level 1 certification is valid in two years. Free MuleSoft Certified Platform Architect-Level 1 exam online questions are below.

Page 1 of 2

1. What API policy would LEAST likely be applied to a Process API?

Custom circuit breaker

Client ID enforcement

Rate limiting

JSON threat protection

2. What is a key performance indicator (KPI) that measures the success of a typical C4E that is immediately apparent in responses from the Anypoint Platform APIs?

The number of production outage incidents reported in the last 24 hours

The number of API implementations that have a publicly accessible HTTP endpoint and are being managed by Anypoint Platform

The fraction of API implementations deployed manually relative to those deployed using a CI/CD tool

The number of API specifications in RAML or OAS format published to Anypoint Exchange

3. An organization is implementing a Quote of the Day API that caches today's quote.

What scenario can use the CloudHub Object Store via the Object Store connector to persist the cache's state?

When there are three CloudHub deployments of the API implementation to three separate CloudHub regions that must share the cache state.

When there are two CloudHub deployments of the API implementation by two Anypoint Platform business groups to the same CloudHub region that must share the cache state.

When there is one deployment of the API implementation to CloudHub and another deployment to a customer-hosted Mule runtime that must share the cache state.

When there is one CloudHub deployment of the API implementation to three CloudHub workers that must share the cache state.

4. 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

5. What do the API invocation metrics provided by Anypoint Platform provide?

ROI metrics from APIs that can be directly shared with business users

Measurements of the effectiveness of the application network based on the level of reuse

Data on past API invocations to help identify anomalies and usage patterns across various APIs

Proactive identification of likely future policy violations that exceed a given threat threshold

6. What is true about the technology architecture of Anypoint VPCs?

The private IP address range of an Anypoint VPC is automatically chosen by CloudHub.

Traffic between Mule applications deployed to an Anypoint VPC and on-premises systems can stay within a private network.

Each CloudHub environment requires a separate Anypoint VP

VPC peering can be used to link the underlying AWS VPC to an on-premises (non AWS) private network.

7. An API implementation is deployed on a single worker on CloudHub and invoked by external API clients (outside of CloudHub).

How can an alert be set up that is guaranteed to trigger AS SOON AS that API implementation stops responding to API invocations?

Implement a heartbeat/health check within the API and invoke it from outside the Anypoint Platform and alert when the heartbeat does not respond.

Configure a “worker not responding” alert in Anypoint Runtime Manager.

Handle API invocation exceptions within the calling API client and raise an alert from that API client when the API is unavailable.

Create an alert for when the API receives no requests within a specified time period.

8. The implementation of a Process API must change.

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

Update the RAML definition of the current Process API and notify API client developers by sending them links to the updated RAML definition.

Postpone changes until API consumers acknowledge they are ready to migrate to a new Process API or API version.

Implement required changes to the Process API implementation so that, whenever possible, the Process API's RAML definition remains unchanged.

Implement the Process API changes in a new API implementation, and have the old API implementation return an HTTP status code 301 - Moved Permanentlyto inform API clients they should be calling the new API implementation.

9. 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 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.

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

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

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.

10. 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?

The client ID and secret for the Anypoint Platform account owning the API in the STAGING environment

The client ID and secret for the Anypoint Platform account's STAGING environment

The client ID and secret obtained from Anypoint Exchange for the API instance in the STAGING environment

A valid OAuth token obtained from Anypoint Platform and its associated client ID and secret

Page 2 of 2

11. 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

12. 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?

An SLA for the upstream API CANNOT be provided.

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

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

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

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

It makes API Manager aware of API implementations and hence enables it to enforce policies.

It enables Anypoint Studio to discover API definitions configured in Anypoint Platform.

It enables Anypoint Exchange to discover assets and makes them available for reuse.

It enables Anypoint Analytics to gain insight into the usage of APIs.

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

The visibility level of the API instances of that API that need to be publicly accessible should be set to public visibility.

The users needing access to the API should be added to the appropriate role in Anypoint Platform.

The API should be functional with at least an initial implementation deployed and accessible for users to interact with.

The API should be secured using one of the supported authentication/authorization mechanisms to ensure that data is not compromised.

15. 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?

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

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

Use Anypoint Studio to implement the API as a Mule application, then deploy that API implementation to CloudHub an Department to interact with it.

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

16. Refer to the exhibit.

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

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

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

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

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

17. 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?

IP whitelist

SLA-based rate limiting

OAuth 2 token enforcement

Client ID enforcement

18. Refer to the exhibit.