New Year Special - 75% Discount Offer - Ends in 0d 00h 00m 00s - Coupon code: ac75sure

When designing an upstream API and its implementation, the development team has been advised to...

Salesforce MuleSoft-Platform-Architect-I Full Course Access
Salesforce MuleSoft-Platform-Architect-I View All Questions

When designing an upstream API and its implementation, the development team has been advised to NOT set timeouts when invoking a downstream API, because that downstream API has no SLA that can be relied upon. This is the only downstream API dependency of that upstream API.

Assume the downstream API runs uninterrupted without crashing. What is the impact of this advice?

A.

An SLA for the upstream API CANNOT be provided

B.

The invocation of the downstream API will run to completion without timing out

C.

A default timeout of 500 ms will automatically be applied by the Mule runtime in which the upstream API implementation executes

D.

A toad-dependent timeout of less than 1000 ms will be applied by the Mule runtime in which the downstream API implementation executes

MuleSoft-Platform-Architect-I PDF/Engine
  • Printable Format
  • Value of Money
  • 100% Pass Assurance
  • Verified Answers
  • Researched by Industry Experts
  • Based on Real Exams Scenarios
  • 100% Real Questions
buy now MuleSoft-Platform-Architect-I pdf
Get 75% Discount on All Products, Use Coupon: "ac75sure"
Next
What best describes the Fully Qualified Domain Names (FQDNs), also known as DNS entries, created...
Question 10: SkippedAn API implementation returns three X-RateLimit-* HTTP response headers to a requesting API...
Previous