MCPA-Level-1試験無料問題集「MuleSoft Certified Platform Architect - Level 1 認定」
A large organization with an experienced central IT department is getting started using MuleSoft. There is a project to connect a siloed back-end system to a new Customer Relationship Management (CRM) system. The Center for Enablement is coaching them to use API- led connectivity.
What action would support the creation of an application network using API-led connectivity?
What action would support the creation of an application network using API-led connectivity?
正解:B
解答を投票する
解説: (GoShiken メンバーにのみ表示されます)
An enterprise is embarking on the API-led digital transformation journey, and the central IT team has started to define System APIs. Currently there is no Enterprise Data Model being defined within the enterprise, and the definition of a clean Bounded Context Data Model requires too much effort.
According to MuleSoft's recommended guidelines, how should the System API data model be defined?
According to MuleSoft's recommended guidelines, how should the System API data model be defined?
正解:D
解答を投票する
解説: (GoShiken メンバーにのみ表示されます)
A retail company is using an Order API to accept new orders. The Order API uses a JMS queue to submit orders to a backend order management service. The normal load for orders is being handled using two (2) CloudHub workers, each configured with 0.2 vCore. The CPU load of each CloudHub worker normally runs well below 70%. However, several times during the year the Order API gets four times (4x) the average number of orders. This causes the CloudHub worker CPU load to exceed 90% and the order submission time to exceed 30 seconds. The cause, however, is NOT the backend order management service, which still responds fast enough to meet the response SLA for the Order API. What is the MOST resource-efficient way to configure the Mule application's CloudHub deployment to help the company cope with this performance challenge?
正解:B
解答を投票する
解説: (GoShiken メンバーにのみ表示されます)
A system API is deployed to a primary environment as well as to a disaster recovery (DR) environment, with different DNS names in each environment. A process API is a client to the system API and is being rate limited by the system API, with different limits in each of the environments. The system API's DR environment provides only 20% of the rate limiting offered by the primary environment. What is the best API fault-tolerant invocation strategy to reduce overall errors in the process API, given these conditions and constraints?
正解:D
解答を投票する
解説: (GoShiken メンバーにのみ表示されます)