Certified MuleSoft Integration Architect I

Certified MuleSoft Integration Architect I practice questions, page 3 of 3, with answer review and explanations.

Question 11

A company is designing a Mule application to consume batch data from a partner’s FTPS server, ftps.partner.com. The data files have been compressed (but not encrypted) and then digitally signed by the partner using Pretty Good Privacy (PGP). What inputs are required for the application to securely login to the FTPS server and to consume these files?

  1. 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
  2. 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
  3. The company’s FTPS server login username and password A TLS context trust store containing a public certificate for the company The company’s PGP public key that was used to sign the files
  4. The partner’s PGP public key used by the company to login 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

Question 12

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?

  1. 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.
  2. 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.
  3. 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 the % asyncLogger placeholder and then assign the appender to an AsyncLogger element.
  4. 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.