Free Salesforce ARC730 Exam Questions

Question 1

An organization has an HTTPS-enabled Mule application named Orders API that receives requests from another Mule application named Process Orders. The communication between these two Mule applications must be secured by TLS mutual authentication (two-way TLS). At a minimum, what must be stored in each truststore and keystore of these two Mule applications to properly support two-way TLS between the two Mule applications while properly protecting each Mule application's keys?

A : Orders API truststore: The Orders API public key Process Orders keystore: The Process Orders private key and public key

B : Orders API truststore: The Orders API private key and public key Process Orders keystore: The Process Orders private key public key

C : Orders API truststore: The Process Orders public key Orders API keystore: The Orders API private key and public key Process Orders truststore: The Orders API public key Process Orders keystore: The Process Orders private key and public key

D : Orders API truststore: The Process Orders public key Orders API keystore: The Orders API private key Process Orders truststore: The Orders API public key Process Orders keystore: The Process Orders private key

Answer: C

Question 2

A leading e-commerce giant will use Mulesoft API's on runtime fabric (RTF) to process customer orders. Some customer's sensitive information such as credit card information is also there as a part of a API payload. What approach minimizes the risk of matching sensitive data to the original and can convert back to the original value whenever and wherever required?

A : Apply masking to hide the sensitive information and then use API

B : manager to detokenize the masking format to return the original value

C : create a tokenization format and apply a tokenization policy to the API Gateway

D : Used both masking and tokenization

E : Apply a field level encryption policy in the API Gateway

Answer: C

Question 3

An external web UI application currently accepts occasional HTTP requests from client web browsers to change (insert, update, or delete) inventory pricing information in an inventory system's database. Each inventory pricing change must be transformed and then synchronized with multiple customer experience systems in near real-time (in under 10 seconds). New customer experience systems are expected to be added in the future. The database is used heavily and limits the number of SELECT queries that can be made to the database to 10 requests per hour per user. What is the most scalable, idiomatic (used for its intended purpose), decoupled. reusable, and maintainable integration mechanism available to synchronize each inventory pricing change with the various customer experience systems in near real-time?

A : Write a Mule application with a Database On Table Row event source configured for the inventory pricing database, with the watermark attribute set to an appropriate database column In the same now, use a Scatter-Gather to call each customer experience system-s REST API with transformed inventory-pricing records

B : Add a trigger to the inventory-pricing database table so that for each change to the inventory pricing database, a stored procedure is called that makes a REST call to a Mule application Write the Mule application to publish each Mule event as a message to an Anypoint MQ exchange Write other Mule applications to subscribe to the Anypoint MQ exchange, transform each received message, and then update the Mule application-s corresponding customer experience system(s)

C : Replace the external web UI application with a Mule application to accept HTTP requests from client web browsers In the same Mule application, use a Batch Job scope to test if the database request will succeed, aggregate pricing changes within a short time window, and then update both the inventory pricing database and each customer experience system using a Parallel For Each scope

D : Write a Mule application with a Database On Table Row event source configured for the inventory pricing database, with the ID attribute set to an appropriate database column In the same flow, use a Batch Job scope to publish transformed Inventory-pricing records to an Anypoint MQ queue Write other Mule applications to subscribe to the Anypoint MQ queue, transform each received message, and then update the Mule application-s corresponding customer experience system(s)

Answer: B

Question 4

How should the developer update the logging configuration in order to enable this package specific debugging?

A : In Anypoint Monitoring, define a logging search query with class property set to org.apache.cxf and level set to DEBUG

B : In the Mule application-s log4j2.xml file, add an AsyncLogger element with name property set to org.apache.cxf and level set to DEBUG, then redeploy the Mule application in the CloudHub production environment

C : In the Mule application-s log4j2.xmI file, change the root logger-s level property to DEBUG, then redeploy the Mule application to the CloudHub production environment

D : In Anypoint Runtime Manager, in the Deployed Application Properties tab for the Mule application, add a line item with DEBUG level for package org.apache.cxf and apply the changes

Answer: A

Question 5

An organization plans to extend its Mule APIs to the EU (Frankfurt) region. Currently, all Mule applications are deployed to CloudHub 1.0 in the default North American region, from the North America control plane, following this naming convention: {API-name}—{environment} (for example, Orderssapi—dev, Orders-sapi-—qa, Orders-sapi-—prod, etc.). There is no network restriction to block communications between APIs. What strategy should be implemented in order to deploy the same Mule APIs to the CloudHub 1.0 EU region from the North America control plane, as well as to minimize latency between APIs and target users and systems in Europe?

A : In Runtime Manager, for each Mule application deployment, set the Region property to EU (Frankfurt) and reuse the same Mule application mame as in the North American region. Communicate the new urls {API-name}—{environment}.de-ci.cloudhub.io to the consuming API clients In Europe.

B : In API Manager, set the Region property to EU (Frankfurt) to create an API proxy named {API-name}—proxy—{environment} for each Mule application. Communicate the new url {API-name}—proxy—{environment}.de-c1.cloudhub.io to the consuming API clients In Europe.

C : In Runtime Manager, for each Mule application deployment, leave the Region property blank (default) and change the Mule application name to {API-name}— {environment).de-cl. Communicate the new urls {API-name}—{environment}.de-ci1.cloudhub.io to the consuming API clients in Europe

D : In API Manager, leave the Region property blank (default) to deploy an API proxy named {API-name}~proxy~- (environment}.de-cl for each Mule application. Communicate the new url {API-name}—proxy—{environment}.de-cl.cloudhub.io to the consuming API clients in Europe.

Answer: A