This page was exported from Exams Labs Braindumps [ http://blog.examslabs.com ] Export date:Thu Nov 7 7:31:26 2024 / +0000 GMT ___________________________________________________ Title: 2023 Valid MCPA-Level-1 test answers & MuleSoft Exam PDF [Q28-Q46] --------------------------------------------------- 2023 Valid MCPA-Level-1 test answers & MuleSoft Exam PDF Free MuleSoft MCPA-Level-1 Exam Questions and Answer from Training Expert ExamsLabs Q28. Refer to the exhibit. An organization needs to enable access to their customer data from both a mobile app and a web application, which each need access to common fields as well as certain unique fields.The data is available partially in a database and partially in a 3rd-party CRM system.What APIs should be created to best fit these design requirements?A) A Process API that contains the data required by both the web and mobile apps, allowing these applications to invoke it directly and access the data they need thereby providing the flexibility to add more fields in the future without needing API changesB) One set of APIs (Experience API, Process API, and System API) for the web app, and another set for the mobile appC) Separate Experience APIs for the mobile and web app, but a common Process API that invokes separate System APIs created for the database and CRM systemD) A common Experience API used by both the web and mobile apps, but separate Process APIs for the web and mobile apps that interact with the database and the CRM System  Option A  Option B  Option C  Option D Correct answer: Separate Experience APIs for the mobile and web app, but a common Process API that invokes separate System APIs created for the database and CRM system*****************************************As per MuleSoft’s API-led connectivity:>> Experience APIs should be built as per each consumer needs and their experience.>> Process APIs should contain all the orchestration logic to achieve the business functionality.>> System APIs should be built for each backend system to unlock their data.Reference:Q29. An API has been updated in Anypoint Exchange by its API producer from version 3.1.1 to 3.2.0 following accepted semantic versioning practices and the changes have been communicated via the API’s public portal.The API endpoint does NOT change in the new version.How should the developer of an API client respond to this change?  The update should be identified as a project risk and full regression testing of the functionality that uses this API should be run  The API producer should be contacted to understand the change to existing functionality  The API producer should be requested to run the old version in parallel with the new one  The API client code ONLY needs to be changed if it needs to take advantage of new features Q30. An API implementation is being designed that must invoke an Order API, which is known to repeatedly experience downtime.For this reason, a fallback API is to be called when the Order API is unavailable.What approach to designing the invocation of the fallback API provides the best resilience?  Search Anypoint Exchange for a suitable existing fallback API, and then implement invocations to this fallback API in addition to the Order API  Create a separate entry for the Order API in API Manager, and then invoke this API as a fallback API if the primary Order API is unavailable  Redirect client requests through an HTTP 307 Temporary Redirect status code to the fallback API whenever the Order API is unavailable  Set an option in the HTTP Requester component that invokes the Order API to instead invoke a fallback API whenever an HTTP 4xx or 5xx response status code is returned from the Order API Correct answer: Search Anypoint exchange for a suitable existing fallback API, and then implement invocations to this fallback API in addition to the order API*****************************************>> It is not ideal and good approach, until unless there is a pre-approved agreement with the API clients that they will receive a HTTP 3xx temporary redirect status code and they have to implement fallback logic their side to call another API.>> Creating separate entry of same Order API in API manager would just create an another instance of it on top of same API implementation. So, it does NO GOOD by using clone od same API as a fallback API. Fallback API should be ideally a different API implementation that is not same as primary one.>> There is NO option currently provided by Anypoint HTTP Connector that allows us to invoke a fallback API when we receive certain HTTP status codes in response.The only statement TRUE in the given options is to Search Anypoint exchange for a suitable existing fallback API, and then implement invocations to this fallback API in addition to the order API.Q31. The responses to some HTTP requests can be cached depending on the HTTP verb used in the request. According to the HTTP specification, for what HTTP verbs is this safe to do?  PUT, POST, DELETE  GET, HEAD, POST  GET, PUT, OPTIONS  GET, OPTIONS, HEAD Correct answer: GET, OPTIONS, HEADhttp://restcookbook.com/HTTP%20Methods/idempotency/Q32. What do the API invocation metrics provided by Anypoint Platform provide?  ROI metrics from APIs that can be directly shared with business users  Measurements of the effectiveness of the application network based on the level of reuse  Data on past API invocations to help identify anomalies and usage patterns across various APIs  Proactive identification of likely future policy violations that exceed a given threat threshold Q33. When using CloudHub with the Shared Load Balancer, what is managed EXCLUSIVELY by the API implementation (the Mule application) and NOT by Anypoint Platform?  The assignment of each HTTP request to a particular CloudHub worker  The logging configuration that enables log entries to be visible in Runtime Manager  The SSL certificates used by the API implementation to expose HTTPS endpoints  The number of DNS entries allocated to the API implementation Correct answer: The SSL certificates used by the API implementation to expose HTTPS endpoints*****************************************>> The assignment of each HTTP request to a particular CloudHub worker is taken care by Anypoint Platform itself. We need not manage it explicitly in the API implementation and in fact we CANNOT manage it in the API implementation.>> The logging configuration that enables log entries to be visible in Runtime Manager is ALWAYS managed in the API implementation and NOT just for SLB. So this is not something we do EXCLUSIVELY when using SLB.>> We DO NOT manage the number of DNS entries allocated to the API implementation inside the code. Anypoint Platform takes care of this.It is the SSL certificates used by the API implementation to expose HTTPS endpoints that is to be managed EXCLUSIVELY by the API implementation. Anypoint Platform does NOT do this when using SLBs.Q34. Refer to the exhibit. An organization needs to enable access to their customer data from both a mobile app and a web application, which each need access to common fields as well as certain unique fields.The data is available partially in a database and partially in a 3rd-party CRM system.What APIs should be created to best fit these design requirements?A) A Process API that contains the data required by both the web and mobile apps, allowing these applications to invoke it directly and access the data they need thereby providing the flexibility to add more fields in the future without needing API changesB) One set of APIs (Experience API, Process API, and System API) for the web app, and another set for the mobile appC) Separate Experience APIs for the mobile and web app, but a common Process API that invokes separate System APIs created for the database and CRM systemD) A common Experience API used by both the web and mobile apps, but separate Process APIs for the web and mobile apps that interact with the database and the CRM System  Option A  Option B  Option C  Option D Q35. Refer to the exhibit.What is the best way to decompose one end-to-end business process into a collaboration of Experience, Process, and of System APIs?  Handle customizations for the end-user application at the Process API level rather than the Experience API level.  Allow System APIs to return data that is NOT currently required by the identified Process or Experience APIs.  Always use a tiered approach by creating exactly one API for each of the 3 layers (Experience, Process and System APIs).  Use a Process API to orchestrate calls to multiple System APIs, but NOT to other Process APIs. Q36. An API implementation is being designed that must invoke an Order API, which is known to repeatedly experience downtime.For this reason, a fallback API is to be called when the Order API is unavailable.What approach to designing the invocation of the fallback API provides the best resilience?  Search Anypoint Exchange for a suitable existing fallback API, and then implement invocations to this fallback API in addition to the Order API  Create a separate entry for the Order API in API Manager, and then invoke this API as a fallback API if the primary Order API is unavailable  Redirect client requests through an HTTP 307 Temporary Redirect status code to the fallback API whenever the Order API is unavailable  Set an option in the HTTP Requester component that invokes the Order API to instead invoke a fallback API whenever an HTTP 4xx or 5xx response status code is returned from the Order API Q37. An organization is deploying their new implementation of the OrderStatus System API to multiple workers in CloudHub. This API fronts the organization’s on-premises Order Management System, which is accessed by the API implementation over an IPsec tunnel.What type of error typically does NOT result in a service outage of the OrderStatus System API?  A CloudHub worker fails with an out-of-memory exception  API Manager has an extended outage during the initial deployment of the API implementation  The AWS region goes offline with a major network failure to the relevant AWS data centers  The Order Management System is Inaccessible due to a network outage in the organization’s on-premises data center Q38. What is a key requirement when using an external Identity Provider for Client Management in Anypoint Platform?  Single sign-on is required to sign in to Anypoint Platform  The application network must include System APIs that interact with the Identity Provider  To invoke OAuth 2.0-protected APIs managed by Anypoint Platform, API clients must submit access tokens issued by that same Identity Provider  APIs managed by Anypoint Platform must be protected by SAML 2.0 policies Explanationhttps://www.folkstalk.com/2019/11/mulesoft-integration-and-platform.htmlQ39. An organization is implementing a Quote of the Day API that caches today’s quote.What scenario can use the GoudHub Object Store via the Object Store connector to persist the cache’s state?  When there are three CloudHub deployments of the API implementation to three separate CloudHub regions that must share the cache state  When there are two CloudHub deployments of the API implementation by two Anypoint Platform business groups to the same CloudHub region that must share the cache state  When there is one deployment of the API implementation to CloudHub and anottV deployment to a customer-hosted Mule runtime that must share the cache state  When there is one CloudHub deployment of the API implementation to three CloudHub workers that must share the cache state Q40. Refer to the exhibit.A RAML definition has been proposed for a new Promotions Process API, and has been published to Anypoint Exchange.The Marketing Department, who will be an important consumer of the Promotions API, has important requirements and expectations that must be met.What is the most effective way to use Anypoint Platform features to involve the Marketing Department in this early API design phase?A) Ask the Marketing Department to interact with a mocking implementation of the API using the automatically generated API ConsoleB) Organize a design workshop with the DBAs of the Marketing Department in which the database schema of the Marketing IT systems is translated into RAMLC) Use Anypoint Studio to Implement the API as a Mule application, then deploy that API implementation to CloudHub and ask the Marketing Department to interact with itD) Export an integration test suite from API designer and have the Marketing Department execute the tests In that suite to ensure they pass  Option A  Option B  Option C  Option D Q41. What is the most performant out-of-the-box solution in Anypoint Platform to track transaction state in an asynchronously executing long-running process implemented as a Mule application deployed to multiple CloudHub workers?  Redis distributed cache  java.util.WeakHashMap  Persistent Object Store  File-based storage Q42. What is true about where an API policy is defined in Anypoint Platform and how it is then applied to API instances?  The API policy Is defined In Runtime Manager as part of the API deployment to a Mule runtime, and then ONLY applied to the specific API Instance  The API policy Is defined In API Manager for a specific API Instance, and then ONLY applied to the specific API instance  The API policy Is defined in API Manager and then automatically applied to ALL API instances  The API policy is defined in API Manager, and then applied to ALL API instances in the specified environment Q43. An organization has created an API-led architecture that uses various API layers to integrate mobile clients with a backend system. The backend system consists of a number of specialized components and can be accessed via a REST API. The process and experience APIs share the same bounded-context model that is different from the backend data model. What additional canonical models, bounded-context models, or anti-corruption layers are best added to this architecture to help process data consumed from the backend system?  Create a bounded-context model for every layer and overlap them when the boundary contexts overlap, letting API developers know about the differences between upstream and downstream data models  Create a canonical model that combines the backend and API-led models to simplify and unify data models, and minimize data transformations.  Create a bounded-context model for the system layer to closely match the backend data model, and add an anti-corruption layer to let the different bounded contexts cooperate across the system and process layers  Create an anti-corruption layer for every API to perform transformation for every data model to match each other, and let data simply travel between APIs to avoid the complexity and overhead of building canonical models Correct answer: Create a bounded-context model for the system layer to closely match the backend data model, and add an anti-corruption layer to let the different bounded contexts cooperate across the system and process layers*****************************************>> Canonical models are not an option here as the organization has already put in efforts and created bounded-context models for Experience and Process APIs.>> Anti-corruption layers for ALL APIs is unnecessary and invalid because it is mentioned that experience and process APIs share same bounded-context model. It is just the System layer APIs that need to choose their approach now.>> So, having an anti-corruption layer just between the process and system layers will work well. Also to speed up the approach, system APIs can mimic the backend system data model.Q44. How are an API implementation, API client, and API consumer combined to invoke and process an API?  The API consumer creates an API implementation, which receives API invocations from an API such that they are processed for an API client  The API client creates an API consumer, which receives API invocations from an API such that they are processed for an API implementation  The ApI consumer creates an API client, which sends API invocations to an API such that they are processed by an API implementation  The ApI client creates an API consumer, which sends API invocations to an API such that they are processed by an API implementation Q45. Refer to the exhibit.An organization uses one specific CloudHub (AWS) region for all CloudHub deployments.How are CloudHub workers assigned to availability zones (AZs) when the organization’s Mule applications are deployed to CloudHub in that region?  Workers belonging to a given environment are assigned to the same AZ within that region  AZs are selected as part of the Mule application’s deployment configuration  Workers are randomly distributed across available AZs within that region  An AZ is randomly selected for a Mule application, and all the Mule application’s CloudHub workers are assigned to that one AZ Correct answer: Workers are randomly distributed across available AZs within that region.*****************************************>> Currently, we only have control to choose which AWS Region to choose but there is no control at all using any configurations or deployment options to decide what Availability Zone (AZ) to assign to what worker.>> There are NO fixed or implicit rules on platform too w.r.t assignment of AZ to workers based on environment or application.>> They are completely assigned in random. However, cloudhub definitely ensures that HA is achieved by assigning the workers to more than on AZ so that all workers are not assigned to same AZ for same application.Reference:Q46. What Mule application can have API policies applied by Anypoint Platform to the endpoint exposed by that Mule application?  A Mule application that accepts requests over HTTP/1x.  A Mule application that accepts JSON requests over TCP but is NOT required to provide a response.  A Mule application that accepts JSON requests over WebSocket.  A Mule application that accepts gRPC requests over HTTP/2 Explanation/Reference: Loading … Top MuleSoft MCPA-Level-1 Courses Online: https://www.examslabs.com/MuleSoft/MuleSoft-Certified-Platform-Architect/best-MCPA-Level-1-exam-dumps.html --------------------------------------------------- Images: https://blog.examslabs.com/wp-content/plugins/watu/loading.gif https://blog.examslabs.com/wp-content/plugins/watu/loading.gif --------------------------------------------------- --------------------------------------------------- Post date: 2023-02-28 12:49:39 Post date GMT: 2023-02-28 12:49:39 Post modified date: 2023-02-28 12:49:39 Post modified date GMT: 2023-02-28 12:49:39