Free Salesforce-MuleSoft-Developer-II: Salesforce Certified MuleSoft Developer 2 (SP24) Exam Questions and Answers

Several Mule applications run on standalone Mule runtimes in a company data center. The operations team needs the application logs from all runtimes searchable in a central Elasticsearch cluster. Developers must not have to collect log files from each server by hand. What should the developer do?

• AA. Change the root logger level in the Mule runtime wrapper.conf file to ALL on every server
• BB. Add a Logger component to every flow that posts the log message to the Elasticsearch REST API
• CC. Add a Log4j2 appender that ships events to the central log system in the log4j2.xml file of each application
• DD. Create a scheduled flow in each application that zips the log folder and uploads it to a shared file server

A CI pipeline runs mvn clean package for a Mule application. The build succeeds and creates the application archive, but nothing is deployed to CloudHub. The pom.xml contains this plugin configuration, and the cloudHubDeployment settings are valid: <plugin> <groupId>org.mule.tools.maven</groupId> <artifactId>mule-maven-plugin</artifactId> <version>4.1.1</version> <extensions>true</extensions> <configuration> <cloudHubDeployment>...</cloudHubDeployment> </configuration> <executions> <execution> <id>deploy</id> <phase>deploy</phase> <goals> <goal>deploy</goal> </goals> </execution> </executions> </plugin> What should the developer change?

• AA. Run mvn clean install in the pipeline
• BB. Run mvn clean deploy in the pipeline
• CC. Run mvn clean package -Pdeploy in the pipeline
• DD. Run mvn clean verify in the pipeline

A developer deploys a Mule application to CloudHub 2.0 with the Mule Maven plugin, and the deployment fails because the credentials cannot be resolved. The relevant files contain: pom.xml <cloudhub2Deployment> <uri>https://anypoint.mulesoft.com</uri> <provider>MC</provider> <environment>QA</environment> <server>anypoint-qa</server> </cloudhub2Deployment> settings.xml <servers> <server> <id>anypoint-qa-env</id> <username>${anypoint.user}</username> <password>${anypoint.password}</password> </server> </servers> What should the developer change?

• AA. Add the username and password as properties in the mule-artifact.json file
• BB. Change the provider element in the pom.xml to CH2
• CC. Move the server definition from settings.xml into the pluginManagement section of the pom.xml
• DD. Change the server element in the pom.xml to anypoint-qa-env

A Mule application deployed to a standalone Mule runtime contains several flows that process card payments. The operations team wants every message written by the Logger components in the payment flows to go to a dedicated RollingFile appender, while all other application logs continue to use the existing appender. What should the developer do?

• AA. Set the same category value on the Logger components in the payment flows and add a logger with that name in log4j2.xml that references the new appender
• BB. Move the payment flows to a separate Mule configuration file and register a different log4j2.xml file for that configuration file
• CC. Prefix each payment log message with a fixed tag and define a RegexFilter on the root logger that sends tagged messages to the new appender
• DD. Set the level attribute to WARN on the Logger components in the payment flows and route WARN events to the new appender with a level filter

A developer creates a custom API policy project for Mule 4 so that it can be published to Anypoint Exchange and applied from API Manager. Which two artifacts must the policy project contain? (Choose 2 answers.)

Select 2 answers.

• AA. A policy definition file that describes the policy and its configuration parameters
• BB. A RAML fragment that lists the API resources to which the policy is applied
• CC. A Mule flow starting with an HTTP Listener that receives requests before the API implementation
• DD. A policy implementation XML file that wraps the logic around the execute-next element

An API managed in API Manager is consumed by a Gold partner group and a Basic partner group. Gold applications must be allowed 1,000 requests per minute and Basic applications 100 requests per minute. Each client application registers for access to the API instance. Which policy configuration meets the requirement?

• AA. Apply the Spike control policy with a different queue size for each partner group
• BB. Apply the Client ID enforcement policy and enter a separate maximum request count for each partner group
• CC. Apply the Rate limiting - SLA based policy and define one SLA tier for each partner group in API Manager
• DD. Apply two Rate limiting policies, one with 1,000 and one with 100 requests per minute, and set different policy orders

A CI pipeline runs mvn clean verify on a Mule project. The build must fail when overall application coverage reported by MUnit is below 80 percent. Which configuration of the coverage element of the munit-maven-plugin meets this requirement?

• AA. runCoverage set to true and requiredApplicationCoverage set to 80, with failBuild left at its default value
• BB. runCoverage set to true, failBuild set to true, and requiredFlowCoverage set to 80
• CC. runCoverage set to true, failBuild set to true, and requiredApplicationCoverage set to 80
• DD. runCoverage set to false, failBuild set to true, and requiredApplicationCoverage set to 80

A Mule application consumes order messages from an Anypoint MQ queue and posts each one to a billing system that is sometimes unavailable. No message may be lost, and a message that still fails after three delivery attempts must be kept for later investigation. How should the developer configure the solution?

• AA. Use the IMMEDIATE acknowledgement mode on the subscriber and add an Until Successful scope with three retries around the billing call
• BB. Use the MANUAL acknowledgement mode, acknowledge at the end of the flow, and attach a dead letter queue with a maximum of three deliveries to the source queue
• CC. Use the AUTO acknowledgement mode on the subscriber and handle billing errors with an On Error Continue that logs the message
• DD. Use the MANUAL acknowledgement mode, acknowledge at the start of the flow, and publish failed messages to a second queue from an On Error Propagate

A Mule project's pom.xml declares the munit-maven-plugin in the build plugins section with only its version and a coverage configuration. Developers see that mvn clean package finishes successfully without running any MUnit suites, although suites exist in src/test/munit. What should be added so the suites run in the standard Maven lifecycle?

• AA. A packaging element set to mule-munit-test so Maven selects the MUnit lifecycle
• BB. An execution of the munit-maven-plugin that binds its test and coverage-report goals to the test phase
• CC. A munit-tools dependency with test scope so the suites can be discovered
• DD. An entry in pluginManagement that repeats the plugin coordinates and its configuration

An API in API Manager exposes GET, POST and DELETE methods on the /orders resource and GET on /products. A JWT validation policy must be enforced only for POST and DELETE requests to /orders. All other requests must reach the implementation without the policy. What should the developer do?

• AA. Apply the policy with method and resource conditions that select POST and DELETE on /orders
• BB. Create a separate API instance for /orders and apply the policy to the whole instance
• CC. Add the policy to an API group that contains only the consumers of /orders
• DD. Apply the policy to the whole API and add a Choice router in the implementation to skip validation for other requests