Mule-Dev-301 Exam Dumps - Salesforce Certified MuleSoft Developer II

Java keytool -importkeystore converts a keystore by explicitly defining both the source keystore and its format and the destination keystore and its required format. To convert JKS → PKCS12, the source must therefore be the JKS file with -srcstoretype JKS, while the destination must be the .p12 file with -deststoretype PKCS12.

MuleSoft provides the same conversion pattern in its TLS-related documentation. Its example for converting a JKS client keystore to P12 uses -srckeystore ...jks, -srcstoretype JKS, followed by -destkeystore ...p12 and -deststoretype PKCS12.

Mule supports JKS, PKCS12, and other keystore types for TLS configurations, but the configured file type must correspond correctly to the actual keystore encoding.

Option A reverses the declared store types even though the filenames suggest JKS-to-P12 conversion. Option C performs the opposite conversion, PKCS12 to JKS. Option D incorrectly identifies a .p12 source as JKS and does not correctly express the required source/destination relationship.

Thus, option B contains the correct source and destination formats.

Reference topics: TLS configuration; Java Keytool; JKS; PKCS12; keystore conversion.

Official documentation: https://docs.mulesoft.com/runtime-manager/rtm-agent-REST-connections

Official documentation: https://docs.mulesoft.com/mule-runtime/4.9/tls-configuration

===============================================================

Anypoint Monitoring provides connector-level performance metrics without requiring additional application logging or custom instrumentation. For supported connectors, these statistics are accessible from the application's monitoring interface through the Connectors tab.

MuleSoft's documentation specifies that connector monitoring includes Requests, which reports the average number of connector requests over automatically selected intervals, and Response Time, which reports the average response time for connector requests. To access these metrics, the documented procedure is to open Anypoint Monitoring, select the relevant Mule application resource, and open the Connectors view.

Because these metrics are generated by the monitoring platform, examining raw logs is unnecessary. A custom dashboard may be useful when creating specialized operational visualizations, but it is not required simply to obtain standard connector request and response-time measurements. Modifying the Salesforce System API to manually log this information would also duplicate functionality already supplied by Anypoint Monitoring and increase application complexity.

The question additionally identifies Titanium support, which aligns with availability of connector monitoring capabilities described by MuleSoft.

Therefore, the correct procedure is to use the built-in Anypoint Monitoring dashboard and inspect the Connectors tab.

Reference topics: Anypoint Monitoring; connector performance metrics; built-in dashboards; request count; response time; Salesforce Connector.

Official documentation: https://docs.mulesoft.com/monitoring/monitor-connectors

===============================================================

For the Mule 4 custom-policy development model represented by this question, the policy's runtime behavior is implemented in an XML template, while the policy's configurable parameters and metadata are described in a YAML configuration file.

The XML template uses Mule's XML configuration language and policy-specific elements such as http-policy:proxy, http-policy:source, http-policy:operation, and http-policy:execute-next. In this scenario, the developer can place the header-token inspection and validation behavior in this implementation layer. The accompanying YAML file exposes configurable policy parameters to API Manager and provides the metadata needed for policy configuration.

MuleSoft's custom-policy development reference identifies an XML template and YAML file as core policy project artifacts; the complete project additionally contains its POM, Mule artifact descriptor, and any optional resources.

A ZIP file is not the source artifact pair used to define the policy. Similarly, a generic JSON properties file is not a replacement for the implementation template in this Mule 4 custom-policy model.

Thus, among the available combinations, the XML policy template together with the YAML configuration file is the required pair.

Reference topics: Mule Gateway custom policies; XML policy templates; YAML policy configuration; HTTP Policy Transform Extension.

Official documentation: https://docs.mulesoft.com/mule-gateway/policies-custom-mule-4-reference

===============================================================

When an API specification has already been published as an asset, Import a published API is the appropriate project-creation path because Anypoint Studio can resolve the published asset and its version and then use that specification to generate the Mule implementation skeleton.

APIkit scaffolding creates the implementation backbone from the selected specification, including the HTTP Listener entry flow, APIkit Router, console-related configuration, and operation-specific implementation flows. MuleSoft currently documents that Studio can scaffold APIs by importing a published API from Exchange/Maven, importing a local specification, or obtaining one from Design Center. However, the distinguishing requirement in this question is selecting the correct published API version. A published Exchange asset has explicit artifact/version coordinates, allowing the intended version to be selected rather than merely working from an unmanaged local RAML file.

Importing a local RAML can generate flows, but it does not inherently provide Exchange-based artifact/version selection. Likewise, "Generate a local RAML" is not the mechanism shown in the new-project API implementation interface.

Reference topics: APIkit for REST; API Scaffolding; Anypoint Exchange API assets; API version selection; Studio project creation.

Official documentation: https://docs.mulesoft.com/apikit/latest/apikit-4-scaffolding-reference

===============================================================

The distinction between entry TTL and expiration interval is the key to this question. entryTtl="1" specifies that an Object Store entry becomes eligible for expiration after one second. However, expirationInterval="30" determines how frequently Mule's expiration process checks the Object Store and removes expired entries.

MuleSoft describes the expiration interval as the frequency at which the expiration thread runs. Therefore, expiration is not equivalent to immediate physical removal at precisely the TTL boundary.

The flow first sets the payload to originalPayload, then stores "testPayload" under the key testKey. Ten seconds subsequently elapse before the Retrieve operation executes. Although this exceeds the configured one-second TTL, only 10 seconds have elapsed since storage, while the expiration process is configured to run at 30-second intervals. The entry has therefore not yet been evicted when retrieval occurs.

Because testKey remains available, os:retrieve returns the stored value, testPayload. The configured default value nullPayload would be used only if the key were unavailable according to the Retrieve operation's behavior.

Reference topics: Object Store Connector; entry TTL; expiration interval; expiration thread; Store and Retrieve operations.

Official documentation: https://docs.mulesoft.com/object-store-connector/latest/object-store-connector-reference

===============================================================