Salesforce Salesforce Certifications SALESFORCE-MULESOFT-DEVELOPER-II Questions & Answers

• Question 51:

  A healthcare portal needs to validate the token that it sends to a Mule API. The developer plans to implement a custom policy using the HTTP Policy Transform Extension to match the token received in the header from the heathcare portal. Which files does the developer need to create in order to package the custom policy?

  A. Deployable ZIP file, YAML configuration file

  B. JSON properties file, YAML configuration file

  C. JSON properties file, XML template file

  D. XML template file, YAML configuration file

  Correct Answer: D

  To package a custom policy using the HTTP Policy Transform Extension, the developer needs to create an XML template file and a YAML configuration file. The XML template file defines the policy logic using Mule components and placeholders for user-defined properties. The YAML configuration file defines the metadata of the policy, such as its name, description, category, parameters, and dependencies. https://docs.mulesoft.com/ api-manager.x/http-policytransform#packaging-the-policy

• Question 52:

  Which type of cache invalidation does the Cache scope support without having to write any additional code?

  A. Write-through invalidation

  B. White-behind invalidation

  C. Time to live

  D. Notification-based invalidation

  Correct Answer: C

  The Cache scope supports time to live (TTL) as a cache invalidation strategy without having to write any additional code. TTL specifies how long the cached response is valid before it expires and needs to be refreshed. The Cache scope also supports custom invalidation strategies using MEL or DataWeave expressions. https://docs.mulesoft.com/mule-runtime.3/cachescope# cache_invalidation

• Question 53:

  What is the MuleSoft recommended method to encrypt sensitive property data?

  A. The encryption key and sensitive data should be different for each environment

  B. The encryption key should be identical for all environments

  C. The encryption key should be identical for all environments and the sensitive data should be different for each environment

  D. The encryption key should be different for each environment and the sensitive data should be the same for all environments

  Correct Answer: A

  The MuleSoft recommended method to encrypt sensitive property data is to use the Secure Properties Tool that comes with Anypoint Studio. This tool allows encrypting properties files with a secret key and then decrypting them at runtime using the same key. The encryption key and sensitive data should be different for each environment to ensure security and avoid accidental exposure of sensitive data. https:// docs.mulesoft.com/mule-runtime.3/secure-configurationproperties

• Question 54:

  Which statement is true when using XML SDK for creating custom message processors?

  A. Properties are fields defined by an end user of the XML SDK component and serve as a global configuration for the entire Mule project in which they are used

  B. An XML SDK provides both inbound and outbound operations

  C. Operations can be reused in recursive calls

  D. All operations are public

  Correct Answer: A

  When using XML SDK for creating custom message processors, all operations are public by default and can be used by any Mule application that imports them. There is no way to make an operation private or protected in XML SDK. https://docs.mulesoft.com/mule-sdk.1/xmlsdk# operations

• Question 55:

  Which statement is true about using mutual TLS to secure an application?

  A. Mutual TLS requires a hardware security module to be used

  B. Mutual TLS authenticates the identity of the server before the identity of the client

  C. Mutual TLS ensures only authorized end users are allowed to access an endpoint

  D. Mutual TLS increases the encryption strength versus server-side TLS alone

  Correct Answer: B

  Mutual TLS (mTLS) is an extension of TLS that requires both parties (client and server) to present their certificates to each other during the handshake process. This way, both parties can verify each other's identity and establish a secure connection. The authentication of the server happens before the authentication of the client, as the server sends its certificate first and then requests the client's certificate. https:// docs.mulesoft.com/mule-runtime.3/tls-configuration#mutualauthentication

• Question 56:

  When implementing a synchronous API where the event source is an HTTP Listener, a developer needs to return the same correlation ID back to the caller in the HTTP response header. How can this be achieved?

  A. Enable the auto-generate CorrelationID option when scaffolding the flow

  B. Enable the CorrelationID checkbox in the HTTP Listener configuration

  C. Configure a custom correlation policy

  D. NO action is needed as the correlation ID is returned to the caller in the response header by default

  Correct Answer: D

  When implementing a synchronous API where the event source is an HTTP Listener, Mule automatically propagates some message attributes between flows via outbound and inbound properties. One of these attributes is correlation ID,

  which is returned to the caller in the response header by default as MULE_CORRELATION_ID.

  https://docs.mulesoft.com/muleruntime/4.3/about-mule-message#message-attributes

• Question 57:

  A custom policy needs to be developed to intercept all cutbound HTTP requests made by Mule applications. Which XML element must be used to intercept outbound HTTP requests?

  A. It is not possible to intercept outgoing HTTP requests, only inbound requests

  B. http-policy:source

  C. htt-policy:operation

  D. http-policy:processor

  Correct Answer: B

  The http-policy:processor element is used to intercept outbound HTTP requests made by Mule applications. It allows customizing the request before it is sent to the target API and modifying the response after it is received from the target API. https://docs.mulesoft.com/apimanager/2.x/policy-mule4-custom-policy#policy-xml-file

• Question 58:

  An API has been built to enable scheduling email provider. The front-end system does very little data entry validation, and problems have started to appear in the email that go to patients. A validatecustomer'' flow is added validate the data.

  

  What is he expected behavior of the "validate-customer'' flow?

  A. If only the email address Is invalid a VALIDATION.INVALID_EMAIL error is raised

  B. If the email address is invalid, processing continues to see if the appointment data and customer name are also invalid

  C. If the appointment date and customer name are invalid, a SCHEDULE:INVALID_APPOINTMENT_DATE error is raised

  D. If all of the values are invalid the last validation error is raised:SCHEDULE:INVALID_CUSTOMER_NAME

  Correct Answer: A

  The validate-customer flow uses an until-successful scope to validate each field of the customer data. The until-successful scope executes its processors until they succeed or exhausts the maximum number of retries. If any processor fails, it

  raises an error and stops executing the remaining processors. Therefore, if only the email address is invalid, a VALIDATION.INVALID_EMAIL error is raised and the validation of appointment date and customer name is skipped.

  Reference:

  https://docs.mulesoft.com/mule-runtime.3/until-successful-scope

• Question 59:

  The flow is invoicing a target API. The API's protocol is HTTPS. The TLS configuration in the HTTP Request Configuration global element is set to None. A web client submits a request to http:localhost:8081/vehicles. If the certificate of the target API is signed by a certificate authority (CA), what is true about the HTTP Request operation when the flow executes?

  A. The HTTP Request operation will succeed if the CA'S certificate is present in the JRE's default keystore

  B. The HTTP Request operation will succeed if the CA's certificate is present in the JRE's default truststore.

  C. The HTTP Request operation will always succeed regardless of the CA

  D. The HTTP Request operation will always fail regardless of the CA

  Correct Answer: B

  The HTTP Request operation will use the default truststore of the JRE to validate the certificate of the target API. If the CA's certificate is present in the truststore, the operation will succeed. Otherwise, it will fail with a handshake exception. https://docs.mulesoft.com/mule-runtime.3/tlsconfiguration# tls-default

• Question 60:

  When a client and server are exchanging messages during the mTLS handshake, what is being agreed on during the cipher suite exchange?

  A. A protocol

  B. The TLS version

  C. An encryption algorithm

  D. The Public key format

  Correct Answer: C

  A cipher suite is a set of cryptographic algorithms that are used to secure the communication between a client and a server. A cipher suite consists of four components: a key exchange algorithm, an authentication algorithm, an encryption

  algorithm, and a message authentication code (MAC) algorithm. During the cipher suite exchange, the client and the server agree on which encryption algorithm to use for encrypting and decrypting the data.

  Reference:

  https://docs.mulesoft.com/mule-runtime.3/tls-configuration#cipher-suites