Salesforce Certified MuleSoft Platform Architect I Practice Test - Questions Answers, Page 2

An SLA for the upstream API CANNOT be provided. >> First thing first, the default HTTP response timeout for HTTP connector is 10000 ms (10 seconds). NOT 500 ms.>> Mule runtime does NOT apply any such 'load-dependent' timeouts. There is no such behavior currently in Mule.>> As there is default 10000 ms time out for HTTP connector, we CANNOT always guarantee that the invocation of the downstream API will run to completion without timing out due to its unreliable SLA times. If the response time crosses 10 seconds then the request may time out.The main impact due to this is that a proper SLA for the upstream API CANNOT be provided.

It makes API Manager aware of API implementations and henceenables it to enforce policies. >> API Autodiscovery is a mechanism that manages an API from API Manager by pairing the deployed application to an API created on the platform.>> API Management includes tracking, enforcing policies if you apply any, and reporting API analytics.>> Critical to the Autodiscovery process is identifying the API by providing the API name and version.https://docs.mulesoft.com/api-manager/2.x/api-auto-discovery-new-concepthttps://docs.mulesoft.com/api-manager/1.x/api-auto-discoveryhttps://docs.mulesoft.com/api-manager/2.x/api-auto-discovery-new-concept

The visibility level of the API instances of that API that need to bepublicly accessible should be set to public visibility. https://docs.mulesoft.com/exchange/to-share-api-asset-to-portal

Ask the Marketing Department to interact with a mocking implementationof the API using the automatically generated API Console. As per MuleSoft's IT Operating Model:>>API consumers need NOT wait until the fullAPI implementation is ready.>>NO technical test-suites needs to be shared with end users to interact with APIs.>>Anypoint Platform offers a mocking capability on all the published API specifications to Anypoint Exchange which also will be rich in documentation covering all details of API functionalities and working nature.>>No needs of arranging days of workshops with end users for feedback.API consumers can use Anypoint Exchange features on the platform and interact with the API using its mocking feature. The feedback can be shared quickly on the same to incorporate any changes.

API implementations can run successfully in customer-hosted Muleruntimes, even when they are unable to communicate with the control plane. >>We CANNOT use Shared Load balancer to load balance APIs on customer hosted runtimes

>>For Hybrid deployment models, the on-premises are first connected to Runtime Manager usingRuntime Manager agent.So, the connection is initiated first from On-premises to Runtime Manager. Then all control can be done from Runtime Manager.>>Anypoint Runtime Manager CANNOT ensure automatic HA. Clusters/Server Groups etc should be configured before hand.Only TRUE statement in the given choices is, API implementations can run successfully in customer-hosted Mule runtimes, even when they are unable to communicate with the control plane. There are several references below to justify this statement.https://docs.mulesoft.com/runtime-manager/deployment-strategies#hybrid-deploymentshttps://help.mulesoft.com/s/article/On-Premise-Runtimes-Disconnected-From-US-Control-Plane-June-18th-2018https://help.mulesoft.com/s/article/Runtime-Manager-cannot-manage-On-Prem-Applications-and-Servers-from-US-Control-Plane-June-25th-2019https://help.mulesoft.com/s/article/On-premise-Runtimes-Appear-Disconnected-in-Runtime-Manager-May-29th-2018========================================================

SLA-based rate limiting >> Client Id enforement policy is a 'Compliance' related NFR and does not help in maintaining the 'Quality of Service (QoS)'. It CANNOT and NOT meant for protecting the backend systems from scalability challenges.>> IP Whitelisting and OAuth 2.0 token enforcement are 'Security' related NFRs and again does not help in maintaining the 'Quality of Service (QoS)'. They CANNOT and are NOT meant for protecting the backend systems from scalability challenges.Rate Limiting, Rate Limiting-SLA, Throttling, Spike Control are the policies that are 'Quality of Service (QOS)' related NFRs and are meant to help in protecting the backend systems from getting overloaded.https://dzone.com/articles/how-to-secure-apis

XML over HTTP >>API-led connectivity and Application Networks urge to have the APIs on HTTP based protocols for building most effective APIs and networks on top of them.>>The HTTP based APIs allow the platform to apply various varities of policies to address many NFRs>>The HTTP based APIs also allow to implement many standard and effective implementation patterns that adhere to HTTP based w3c rules.

Bottom of FormTop of Form

Build several Bounded Context Data Models that align with coherent partsof the business processes and the definitions of associated business entities. >>The options w.r.t building API data models using XML schema/ Agile API-centric practices are irrelevant to the scenario given in the question. So these two are INVALID.>>Building EDM (Enterprise Data Model) is not feasible or right fit for this scenario as the teams and LOBs work in silo and they all have different initiatives, budget etc.. Building EDM needs intensive coordination among all the team which evidently seems not possible in this scenario.So, the right fit for this scenario is to build several Bounded Context Data Models that align with coherent parts of the business processes and the definitions of associated business entities.

The FQDNs are determined by the application name chosen,IRRESPECTIVE of the region >> When deploying applications to Shared Worker Cloud, the FQDN are always determined by application name chosen.>> It does NOT matter what region the app is being deployed to.>> Although it is fact and true that the generated FQDN will have the region included in it (Ex: exp-salesorder-api.au-s1.cloudhub.io), it does NOT mean that the same name can be used when deploying to another CloudHub region.>> Application name should be universally unique irrespective of Region and Organization and solely determines the FQDN for Shared Load Balancers.