Salesforce Mule-Dev-301 Exam With Confidence Using Practice Dumps

Mule's Cache scope is backed by a caching strategy, commonly using an Object Store. The caching strategy can directly configure expiration characteristics, including entry time to live (TTL). Once the TTL expires and the corresponding expiration processing occurs, cached entries are removed according to the configured Object Store policy without requiring application-specific invalidation logic.

MuleSoft's cache strategy documentation shows that the Object Store used by a caching strategy can define values such as entryTtl, expirationInterval, and maximum entries. A Cache component can then reference that strategy and automatically use those expiration settings.

Write-through and write-behind describe cache/database synchronization strategies in which cache updates are coordinated with writes to an underlying persistent data source. Mule's standard Cache scope does not automatically implement those patterns as an invalidation mode. Notification-based invalidation would similarly require external notification logic or explicit Mule processing to identify and invalidate affected keys.

TTL requires no such custom invalidation workflow. The developer establishes the lifetime when configuring the caching Object Store, after which Mule manages expiration automatically.

Therefore, Time to live is the cache invalidation mechanism directly available through standard Cache scope configuration.

Reference topics: Cache Scope; Object Store Caching Strategy; entryTtl; expirationInterval; automatic cache expiration.

Official documentation:

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

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:

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

The Insecure setting belongs to Mule's TLS truststore configuration. MuleSoft defines the insecure property as a Boolean that determines whether truststore validation is performed. When insecure="true", Mule stops performing certificate validation.

For an HTTP Listener operating as the TLS server, the truststore is used when validating certificates supplied by connecting clients. Therefore, disabling truststore validation means the listener does not enforce normal trust verification against the configured certificate authorities; effectively, certificates presented by HTTP clients are trusted without the standard certificate-chain validation represented by the truststore. This corresponds to option A.

Selecting Insecure does not convert HTTPS into plain HTTP, so option B is incorrect. It also does not itself enable mutual TLS. Full mutual TLS requires appropriate server key material and client-certificate authentication/trust configuration. Likewise, "Insecure" specifically concerns certificate validation; it should not be interpreted as a generic instruction to bypass every possible authentication mechanism applied to the API.

MuleSoft explicitly warns that this option creates a security vulnerability and is appropriate only for development or prototyping, not production.

Reference topics: TLS Context; Truststore; insecure; client-certificate validation; mutual TLS.

Official documentation:

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