What is the MuleSoft-recommended best practice to share the connector and configuration information among the APIs?

Build a Mule domain project, add the Database connector and configuration to it, and reference this one domain project from each System API

Build a separate Mule domain project for each API, and configure each of them to use a file on a shared file store to load the configuration information dynamically

Build another System API that connects to the database, and refactor all the other APIs to make requests through the new System API to access the database

Create an API proxy for each System API and share the Database connector configuration with all the API proxies via an automated policy

An external API frequently invokes an Employees System API to fetch employee data from a MySQL database. The architect must design a caching strategy to query the database only when there Is an update to the Employees table or else return a cached response in order to minimize the number of redundant transactions being handled by the database.

Use an On Table Row operation configured with the Employees table, call invalidate cache, and hardcode the new Employees data to cache. Use an object-store-caching-strategy and set the expiration interval to 1 hour.

Use an On Table Row operation configured with the Employees table and cail invalidate cache. Use an object-store-caching-strategy and the default expiration interval.

Use a Scheduler with a fixed frequency set to every hour to trigger an invalidate cache flow. Use an object-store-caching-strategy and the default expiration interval.

Use a Scheduler with a fixed frequency set to every hour, triggering an invalidate cache flow. Use an object-store-caching-strategy and set the expiration interval to 1 hour.

What approach configures an API gateway to hide sensitive data exchanged between API consumers and API implementations, but can convert tokenized fields back to their original value for other API requests or responses, without having to recode the API implementations?

Create both masking and tokenization formats and use both to apply a tokenization policy in an API gateway to mask sensitive values in message payloads withcharacters, and apply a corresponding detokenization policy to return the original values to other APIs

Create a masking format and use it to apply a tokenization policy in an API gateway to mask sensitive values in message payloads with characters, and apply a corresponding detokenization policy to return the original values to other APIs

Use a field-level encryption policy in an API gateway to replace sensitive fields in message payload with encrypted values, and apply a corresponding field-level decryption policy to return the original values to other APIs

Create a tokenization format and use it to apply a tokenization policy in an API gateway to replace sensitive fields in message payload with similarly formatted tokenized values, and apply a corresponding detokenization policy to return the original values to other APIs

A leading eCommerce giant will use MuleSoft APIs on Runtime Fabric (RTF) to process customer orders. Some customer-sensitive information, such as credit card information, is required in request payloads or is included in response payloads in some of the APIs. Other API requests and responses are not authorized to access some of this customer-sensitive information but have been implemented to validate and transform based on the structure and format of this customer-sensitive information (such as account IDs, phone numbers, and postal codes).What approach configures an API gateway to hide sensitive data exchanged between API consumers and API implementations, but can convert tokenized fields back to their original value for other API requests or responses, without having to recode the API implementations?Later, the project team requires all API specifications to be augmented with an additional non-functional requirement (NFR) to protect the backend services from a high rate of requests, according to defined service-level agreements (SLAs). The NFR's SLAs are based on a new tiered subscription level 'Gold', 'Silver', or 'Platinum' that must be tied to a new parameter that is being added to the Accounts object in their enterprise data model.Following MuleSoft's recommended best practices, how should the project team now convey the necessary non-functional requirement to stakeholders?

Create and deploy API proxies in API Manager for the NFR, change the baseurl in each API specification to the corresponding API proxy implementation endpoint, and publish each modified API specification to Exchange

Update each API specification with comments about the NFR's SLAs and publish each modified API specification to Exchange

Update each API specification with a shared RAML fragment required to implement the NFR and publish the RAML fragment and each modified API specification to Exchange

Create a shared RAML fragment required to implement the NFR, list each API implementation endpoint in the RAML fragment, and publish the RAML fragment to Exchange

When a Mule application using VM queues is deployed to a customer-hosted cluster or multiple CloudHub v1.0 workers/replicas, how are messages consumed across the nodes?

Sequentially, from a dedicated Anypoint MQ queue

Sequentially, only from the primary node

Round-robin, within an XA transaction

A retail company is implementing a MuleSoft API to get inventory details from two vendors by Invoking each vendor's online applications. Due to network issues, the invocations to the vendor applications are timing out intermittently, but the requests are successful after re-invoking eachWhat is the most performant way of implementing the API to invoke each vendor application and to retry invocations that generate timeout errors?

Use a For-Each scope to invoke the two vendor applications in series, one after the other. Place the For-Each scope inside an Until-Successful scope to retry requests that raise timeout errors.

Use a Choice scope to Invoke each vendor application on a separate route. Place the Choice scope inside an Until-Successful scope to retry requests that raise timeout errors.

Use a Scatter-Gather scope to invoke each vendor application on a separate route. Use an Until-Successful scope in each route to retry requests that raise timeout errors.

Use a Round-Robin scope to invoke each vendor application on a separate route. Use a Try-Catch scope in each route to retry requests that raise timeout errors.

An organization plans to use the Anypoint Platform audit logging service to log Anypoint MQ actions.What consideration must be kept in mind when leveraging Anypoint MQ Audit Logs?

Anypoint MQ Audit Logs include logs for sending, receiving, or browsing messages

Anypoint MQ Audit Logs include fogs for failed Anypoint MQ operations

Anypoint MQ Audit Logs include logs for queue create, delete, modify, and purge operations

What requirement prevents using Anypoint MQ as the messaging broker for a Mule application?

When the payload sent through the message broker must use XML format

When the payload sent through the message broker must be encrypted

When the messaging broker must support point-to-point messaging

When the messaging broker must be deployed on-premises

The company's FTPS server login username and password

TLS context trust store containing a public certificate for the company. The company's PGP public key that was used to sign the files

The partner's PGP public key used by the company to login to the FTPS server. A TLS context key store containing the private key for the company The partner's PGP private key that was used to sign the files

The company's FTPS server login username and password. A TLS context trust store containing a public certificate for ftps.partner.com The partner's PGP public key that was used to sign the files

The partner's PGP public key used by the company to login to the FTPS server. A TLS context key store containing the private key for ftps.partner.com The company's PGP private key that was used to sign the files

A new Mule application has been deployed through Runtime Manager to CloudHub 1.0 using a CI/CD pipeline with sensitive properties set as cleartext. The Runtime Manager Administrator opened a high priority incident ticket about this violation of their security requirements indicating these sensitive properties values must not be stored or visible in Runtime Manager but should be changeable in Runtime Manager by Administrators with proper permissions.How can the Mule application be deployed while safely hiding the sensitive properties?

Add an ArrayList of all the sensitive properties' names in the mule-artifact.json file of the application

Add encrypted versions of the sensitive properties as global configuration properties in the Mule application

Add a new wrapper.java.additional.xx parameter for each sensitive property in the wrapper.conf file used by the CI/CD pipeline scripts

Create a variable for each sensitive property and declare them as hidden in the CI/CD pipeline scripts

As a part of design , Mule application is required call the Google Maps API to perform a distance computation. The application is deployed to cloudhub.At the minimum what should be configured in the TLS context of the HTTP request configuration to meet these requirements?

The configuration is built-in and nothing extra is required for the TLS context

Request a private key from Google and create a PKCS12 file with it and add it in keyStore as a part of TLS context

Download the Google public certificate from a browser, generate JKS file from it and add it in key store as a part of TLS context

Download the Google public certificate from a browser, generate a JKS file from it and add it in Truststore as part of the TLS context

A project team is working on an API implementation using the RAML definition as a starting point. The team has updated the definition to include new operations and has published a new version to exchange. Meanwhile another team is working on a mule application consuming the same API implementation.During the development what has to be performed by the mule application team to take advantage of the newly added operations?

Update the REST connector from exchange in the client application

Scaffold the client application with the new definition

Scaffold API implementation application with the new definition

Update the REST connector from exchange in the client application

Update the API connector in the API implementation and publish to exchange

A company is implementing a new Mule application that supports a set of critical functions driven by a rest API enabled, claims payment rules engine hosted on oracle ERP. As designed the mule application requires many data transformation operations as it performs its batch processing logic.The company wants to leverage and reuse as many of its existing java-based capabilities (classes, objects, data model etc.) as possibleWhat approach should be considered when implementing required data mappings and transformations between Mule application and Oracle ERP in the new Mule application?

Transform by calling any suitable Java class from Dataweave

Create a new metadata RAML classes in Mule from the appropriate Java objects and then perform transformations via Dataweave

From the mule application, transform via theXSLT model

Transform by calling any suitable Java class from Dataweave

Invoke any of the appropriate Java methods directly, create metadata RAML classes and then perform required transformations via Dataweave

An insurance company has an existing API which is currently used by customers. API is deployed to customer hosted Mule runtime cluster. The load balancer that is used to access any APIs on the mule cluster is only configured to point to applications hosted on the server at port 443.Mule application team of a company attempted to deploy a second API using port 443 but the application will not start and checking logs shows an error indicating the address is already in use.Which steps must the organization take to resolve this error and allow customers to access both the API's?

Move the HTTP listener configurations from the API's and package them in a mule domain project using port 443

Change the base path of the HTTP listener configuration in the second API to a different one from the first API

Set HTTP listener configuration in both API's to allow for connections from multiple ports

Move the HTTP listener configurations from the API's and package them in a mule domain project using port 443

Set the HTTP listener of the second API to use different port than the one used in the first API

Which of the below requirements prevent the usage of Anypoint MQ in a company's network? (Choose two answers)

the message broker must be hosted on premises

support for point-to-point messaging

single message payload can be up to 15 MB

the message broker must be hosted on premises

support for point-to-point messaging

ability for a third party outside the company's network to consume events from the queue

An organization plans to migrate its deployment environment from an onpremises cluster to a Runtime Fabric (RTF) cluster. The on-premises Mule applications are currently configured with persistent object stores.There is a requirement to enable Mule applications deployed to the RTF cluster to store and share data across application replicas and through restarts of the entire RTF cluster,How can these reliability requirements be met?

Replace persistent object stores with persistent VM queues in each Mule application deployment

Install the Object Store pod on one of the cluster nodes

Configure Anypoint Object Store v2 to share data between replicas in the RTF cluster

Configure the Persistence Gateway in the RTF installation

A payment processing company has implemented a Payment Processing API Mule application to process credit card and debit card transactions, Because the Payment Processing API handles highly sensitive information, the payment processing company requires that data must be encrypted both In-transit and at-rest.To meet these security requirements, consumers of the Payment Processing API must create request message payloads in a JSON format specified by the API, and the message payload values must be encrypted.How can the Payment Processing API validate requests received from API consumers?

A Transport Layer Security (TLS) - Inbound policy can be applied in API Manager to decrypt the message payload and the Mule application implementation can then use the JSON Validation module to validate the JSON data

The Mule application implementation can use the APIkit module to decrypt and then validate the JSON data

The Mule application implementation can use the Validation module to decrypt and then validate the JSON data

The Mule application implementation can use DataWeave to decrypt the message payload and then use the JSON Scheme Validation module to validate the JSON data

Why would an Enterprise Architect use a single enterprise-wide canonical data model (CDM) when designing an integration solution using Anypoint Platform?

To reduce dependencies when integrating multiple systems that use different data formats

To automate Al-enabled API implementation generation based on normalized backend databases from separate vendors

To leverage a data abstraction layer that shields existing Mule applications from nonbackward compatible changes to the model's data structure

To remove the need to perform data transformation when processing message payloads in Mule applications

A stock trading company handles millions of trades a day and requires excellent performance and reliability within its stock trading system. The company operates a number of event-driven APIs Implemented as Mule applications that are hosted on various customer-hosted Mule clusters and needs to enable message exchanges between the APIs within their internal network using shared message queues.What is an effective way to meet the cross-cluster messaging requirements of its event-driven APIs?

Non-transactional JMS operations with a reliability pattern and manual acknowledgements

Persistent VM queues with automatic acknowledgements

JMS transactions with automatic acknowledgements

extended Architecture (XA) transactions and XA connected components with manual acknowledgements

Refer to the exhibit. A customer is running Mule applications on Runtime Fabric for Self-Managed Kubernetes(RTF-BYOKS) in a multi-cloud environment.Based on this configuration, how do Agents and Runtime Manager communicate, and what Is exchanged between them?

UBER, Dedicated NIO Selector Pool

Shared NIO Selector Pool, CPU_LITE

Following MuleSoft best practices, what MuleSoft runtime deployment option best meets the company's goals to begin its digital transformation journey?

Runtime Fabric on VMs/bare metal

Customer-hosted runtimes provisioned by a MuleSoft services partner

Customer-hosted self-provisioned runtimes

An architect is designing a Mule application to meet the following two requirements:1. The application must process files asynchronously and reliably from an FTPS server to a back-end database using VM intermediary queues for load-balancing Mule events.2. The application must process a medium rate of records from a source to a target system using a Batch Job scope.To make the Mule application more reliable, the Mule application will be deployed to two CloudHub 1.0 workers.Following MuleSoft-recommended best practices, how should the Mule application deployment typically be configured in Runtime Manger to best support the performance and reliability goals of both the Batch Job scope and the file processing VM queues?

Check the Persistent VM queues checkbox in the application deployment configuration

Check the Non-persistent VM queues checkbox in the application deployment configuration

In the Runtime Manager Properties tab, disable persistent VM queues for Batch Job scopes

In the Runtime Manager Properties tab, enable persistent VM queues for the FTPS connector

An organization is building out a test suite for their application using MUnit.The Integration Architect has recommended using Test Recorder in Anypoint Studio to record the processing flows and then configure unit tests based on the captured events.What Is a core consideration that must be kept In mind while using Test Recorder?

Mocking values resulting from parallel processes are possible and will not affect theexecution of the processors that follow in the test

The Recorder supports loops where the structure of the data being tested changes inside the Iteration

Mocking values resulting from parallel processes are possible and will not affect theexecution of the processors that follow in the test

The Recorder supports mocking a message before or inside a Foreach processor

Tests for flows cannot be created if Mule errors are raised Inside the flows, even if the errors are handled by On-Error Continue error handlers

A large life sciences customer plans to use the Mule Tracing module with the Mapped Diagnostic Context (MDC) logging operations to enrich logging in its Mule application and to improve tracking by providing more context in the Mule application logs. The customer also wants to improve throughput and lower the message processing latency in its Mule application flows.After installing the Mule Tracing module in the Mule application, how should logging be performed in flows in Mule applications, and what should be changed In the log4j2.xml files?

In the flows, add Mule Tracing module Set logging variable operations before any Core Logger components. In log4j2.xml files, change the appender's pattern layout to use %MDC and then assign the appender to a Logger or Root element.

In the flows, add Mule Tracing module Set logging variable operations before any Core Logger components. In log4j2.xmI files, change the appender's pattern layout to use the %MDC placeholder and then assign the appender to an AsyncLogger element.

In the flows, add Mule Tracing module Set logging variable operations before any Core Logger components. In log4j2.xmI files, change the appender''s pattern layout to use %asyncLogger placeholder and then assign the appender to an AsyncLogger element.

In the flows, wrap Logger components in Async scopes. In log4j2.xmI files, change the appender's pattern layout to use the %asyncLogger placeholder and then assign the appender to a Logger or Root element.

The retrieveBalances flow in the Mule application is designed to use an operation in a connector to the Finance system (the Finance operation) that can only look up one account record at a time, and a operation from a different connector to the Audit system (the Audit operation) that can only insert one account record at a time.To best meet the performance-related requirements, what scope or scopes should be used and how should they be used to incorporate the Finance operation and Audit operation into the retrieveBalances flow?

Wrap the Finance operation in a Parallel For-Each scope. Wrap the Audit operation in a Async scope.

Wrap the Finance operation in a Until-Successful scope. Wrap the Audit operation in a Try-Catch scope.

Wrap both connector operations in a Async scope.

Wrap both connector operations in a For-Each scope.

What are two reasons why a typical MuleSoft customer favors a MuleSoft-hosted Anypoint Platform runtime plane over a customer-hosted runtime for its Mule application deployments? (Choose two.)

Reduced time-to-market for the first application

Increased application isolation

Reduced time-to-market for the first application

Increased application throughput

Which key DevOps practice and associated Anypoint Platform component should a MuteSoft integration team adopt to improve delivery quality?

A Continuous design with API Designer

Passive monitoring with Anypoint Monitoring

Manual testing with Anypoint Studio

Salesforce Certified MuleSoft Integration Architect I Practice Test 7

An organization is in the process of building automated deployments using a CI/CD process. As a part of automated deployments, it wants to apply policies to API Instances.

What tool can the organization use to promote and deploy API Manager policies?

Become a Premium Member for full access

Unlock Premium Member

Salesforce Certified MuleSoft Integration Architect I Practice Test 7

Question

Salesforce Certified MuleSoft Integration Architect I Practice Tests

Practice Tests