Quality MuleSoft-Platform-Architect-I PDF Dumps - MuleSoft-Platform-Architect-I Exam Questions [Q92-Q111]

NO.92 What Mule application can have API policies applied by
Anypoint Platform to the endpoint exposed by that Mule application?
A) A Mule application that accepts requests over HTTP/1.x

B) A Mule application that accepts JSON requests over TCP but is NOT required to provide a response

C) A Mute application that accepts JSON requests over WebSocket

D) A Mule application that accepts gRPC requests over HTTP/2

Option A

Option B

Option C

Option D

NO.93 An API implementation is deployed to CloudHub.
What conditions can be alerted on using the default Anypoint Platform functionality, where the alert conditions depend on the end-to-end request processing of the API implementation?

When the API is invoked by an unrecognized API client

When a particular API client invokes the API too often within a given time period

When the response time of API invocations exceeds a threshold

When the API receives a very high number of API invocations

NO.94 Once an API Implementation is ready and the API is registered on API Manager, who should request the access to the API on Anypoint Exchange?

None

Both

API Client

API Consumer

NO.95 Which scenario is suited for MUnit tests instead of integration tests?

For read-only interactions to any dependencies (such as other web APIs)

When testing does not require knowledge of implementation details

When no mocking is permissible

For tests that are implemented using SoapUI

NO.96 A Mule 4 API has been deployed to CloudHub and a Basic Authentication – Simple policy has been applied to all API methods and resources. However, the API is still accessible by clients without using authentication.
How is this possible?

The APE Router component is pointing to the incorrect Exchange version of the APT

The Autodiscovery element is not present, in the deployed Mule application

No… for client applications have been created of this API

One of the application’s CloudHub workers restarted

NO.97 A company uses a hybrid Anypoint Platform deployment model that combines the EU control plane with customer-hosted Mule runtimes. After successfully testing a Mule API implementation in the Staging environment, the Mule API implementation is set with environment-specific properties and must be promoted to the Production environment. What is a way that MuleSoft recommends to configure the Mule API implementation and automate its promotion to the Production environment?

Bundle properties files for each environment into the Mule API implementation’s deployable archive, then promote the Mule API implementation to the Production environment using Anypoint CLI or the Anypoint Platform REST APIsB.

Modify the Mule API implementation’s properties in the API Manager Properties tab, then promote the Mule API implementation to the Production environment using API Manager

Modify the Mule API implementation’s properties in Anypoint Exchange, then promote the Mule API implementation to the Production environment using Runtime Manager

Use an API policy to change properties in the Mule API implementation deployed to the Staging environment and another API policy to deploy the Mule API implementation to the Production environment

NO.98 An Anypoint Platform organization has been configured with an external identity provider (IdP) for identity management and client management. What credentials or token must be provided to Anypoint CLI to execute commands against the Anypoint Platform APIs?

The credentials provided by the IdP for identity management

The credentials provided by the IdP for client management

An OAuth 2.0 token generated using the credentials provided by the IdP for client management

An OAuth 2.0 token generated using the credentials provided by the IdP for identity management

NO.99 What are 4 important Platform Capabilities offered by Anypoint Platform?

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

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

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

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

NO.100 The responses to some HTTP requests can be cached depending on the HTTP verb used in the request. According to the HTTP specification, for what HTTP verbs is this safe to do?

PUT, POST, DELETE

GET, HEAD, POST

GET, PUT, OPTIONS

GET, OPTIONS, HEAD

NO.101 Which two statements are true about the technology architecture of an Anypoint Virtual Private Cloud (VPC)?
Choose 2 answers

Ports 8081 and 8082 are used

CIDR blacks are used

Anypoint VPC is responsible for load balancing the applications

Round-robin load balancing is used to distribute client requests across different applications

By default, HTTP requests can be made from the public internet to workers at port 6091

NO.102 A Platform Architect inherits a legacy monolithic SOAP-based web service that performs a number of tasks, including showing all policies belonging to a client. The service connects to two back-end systems – a life-insurance administration system and a general-insurance administration system – and then queries for insurance policy information within each system, aggregates the results, and presents a SOAP-based response to a user interface (UI).
The architect wants to break up the monolithic web service to follow API-led conventions.
Which part of the service should be put into the process layer?

Combining the insurance policy information from the administration systems

Presenting the SOAP-based response to the UI

Authenticating and maintaining connections to each of the back-end administration systems

Querying the data from the administration systems

NO.103 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

NO.104 A company stores financial transaction data in two legacy systems. For each legacy system, a separate, dedicated System API (SAPI) exposes data for that legacy system. A Process API (PAPI) merges the data retrieved from ail of the System APIs into a common format. Several API clients call the PAPI through its public domain name.
The company now wants to expose a subset of financial data to a newly developed mobile application that uses a different Bounded Context Data Model. The company wants to follow MuleSoft’s best practices for building out an effective application network.
Following MuleSoft’s best practices, how can the company expose financial data needed by the mobile application in a way that minimizes the impact on the currently running API clients, API implementations, and support asset reuse?

Add two new Experience APIs (EAPI-i and EAPI-2}.
Add Mobile PAPI-2 to expose the Intended subset of financial data as requested.
Both PAPIs access the Legacy Systems via SAPI-1 and SAP]-2.

Create a new mobile Experince API (EAPI) chat exposes that subset of PAPI endpoints.
Add transformtion login to the mobile Experince API implementation to make mobile data compatible with the required PAPIs.

Develop and deploy is new PAPI implementation with data transformation and … login to support this required endpoints of both mobile and web clients.
Deploy an API Proxy with an endpoint from API Manager that redirect the existing PAPI endpoints to the new PAPI.

To achieve the goal of exposing financial data to a new mobile application while following MuleSoft’s best practices, the company should follow an API-led connectivity approach. This approach ensures minimal disruption to existing clients, maximizes reusability, and respects the separation of concerns across API layers.
of Solution:
Experience APIs for Client-Specific Requirements:
Create two new Experience APIs (EAPI-1 and EAPI-2) for the mobile application, tailored to meet the specific data and format requirements of the mobile application. These APIs encapsulate the client-specific needs and provide a custom interface without impacting other clients.
Process API Layer for Data Transformation:
By adding Mobile PAPI-2, we allow the mobile application to access the required subset of data, formatted according to the mobile application’s requirements. This approach ensures that data transformation and aggregation are handled in the Process layer, maintaining consistency and reusability across different applications.
Reuse of System APIs:
Both the new Mobile PAPI-2 and existing PAPI-1 access data from System APIs (SAPI-1 and SAPI-2), which continue to expose data from each legacy system in a consistent, reusable manner. This avoids duplicating logic and ensures that data access remains centralized and manageable.
Why Option A is Correct:
Option A aligns with MuleSoft’s best practices by isolating client-specific requirements in the Experience layer, utilizing Process APIs for data orchestration and transformation, and maintaining reusable System APIs for backend access.
This approach also ensures that the current API clients are not impacted, as new clients (e.g., the mobile app) interact with newly defined Experience APIs without modifying the existing API setup.
of Incorrect Options:
Option B: This option seems similar but lacks clarity on the separation of mobile-specific requirements and does not explicitly mention data transformation, which is essential in this scenario.
Option C: Creating a single mobile Experience API that exposes a subset of PAPI endpoints directly adds unnecessary complexity and may violate the separation of concerns, as transformation logic should not be in the Experience layer.
Option D: Deploying a new PAPI and using an API Proxy to redirect existing endpoints would add unnecessary complexity, disrupt the current API clients, and increase maintenance efforts.
Reference
For additional guidance, refer to MuleSoft documentation on API-led connectivity best practices and best practices for structuring Experience, Process, and System APIs.

NO.105 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

NO.106 An organization wants to make sure only known partners can invoke the organization’s APIs. To achieve this security goal, the organization wants to enforce a Client ID Enforcement policy in API Manager so that only registered partner applications can invoke the organization’s APIs. In what type of API implementation does MuleSoft recommend adding an API proxy to enforce the Client ID Enforcement policy, rather than embedding the policy directly in the application’s JVM?

A Mule 3 application using APIkit

A Mule 3 or Mule 4 application modified with custom Java code

A Mule 4 application with an API specification

A Non-Mule application

NO.107 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

Implement a system API named customerManagement which has all the functionalities wrapped in it as various operations/resources

Implement different system APIs named createCustomer, amendCustomer, retrieveCustomer and suspendCustomer as they are modular and has seperation of concerns

Implement different system APIs named createCustomerInCRMZ, amendCustomerInCRMZ, retrieveCustomerFromCRMZ and suspendCustomerInCRMZ as they are modular and has seperation of concerns

NO.108 An API has been updated in Anypoint Exchange by its API producer from version 3.1.1 to 3.2.0 following accepted semantic versioning practices and the changes have been communicated via the API’s public portal.
The API endpoint does NOT change in the new version.
How should the developer of an API client respond to this change?

The update should be identified as a project risk and full regression testing of the functionality that uses this API should be run

The API producer should be contacted to understand the change to existing functionality

The API producer should be requested to run the old version in parallel with the new one

The API client code ONLY needs to be changed if it needs to take advantage of new features

NO.109 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 VPC

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

NO.110 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

NO.111 An organization is deploying their new implementation of the OrderStatus System API to multiple workers in CloudHub. This API fronts the organization’s on-premises Order Management System, which is accessed by the API implementation over an IPsec tunnel.
What type of error typically does NOT result in a service outage of the OrderStatus System API?

A CloudHub worker fails with an out-of-memory exception

API Manager has an extended outage during the initial deployment of the API implementation

The AWS region goes offline with a major network failure to the relevant AWS data centers

The Order Management System is Inaccessible due to a network outage in the organization’s on-premises data center

Quality MuleSoft-Platform-Architect-I PDF Dumps – MuleSoft-Platform-Architect-I Exam Questions [Q92-Q111]

Quality MuleSoft-Platform-Architect-I PDF Dumps – MuleSoft-Platform-Architect-I Exam Questions [Q92-Q111]

TrainingDump

Leave a Reply
Cancel reply

Leave a Reply

Quality MuleSoft-Platform-Architect-I PDF Dumps – MuleSoft-Platform-Architect-I Exam Questions [Q92-Q111]

TrainingDump

Leave a Reply Cancel reply

Leave a Reply

Leave a Reply
Cancel reply