This page was exported from Free Exams Dumps Materials [ http://exams.dumpsmaterials.com ] Export date:Sat Nov 23 8:00:45 2024 / +0000 GMT ___________________________________________________ Title: Pass MuleSoft Certified Platform Architect MCPA-Level-1 exam [Feb 14, 2024] Updated 97 Questions [Q10-Q34] --------------------------------------------------- Pass MuleSoft Certified Platform Architect MCPA-Level-1 exam [Feb 14, 2024] Updated 97 Questions MuleSoft MCPA-Level-1 Actual Questions and 100% Cover Real Exam Questions QUESTION 10What 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:QUESTION 11What Anypoint Platform Capabilities listed below fall under APIs and API Invocations/Consumers category? Select TWO.  API Operations and Management  API Runtime Execution and Hosting  API Consumer Engagement  API Design and Development Correct Answers: API Design and Development and API Runtime Execution and Hosting*****************************************>> API Design and Development – Anypoint Studio, Anypoint Design Center, Anypoint Connectors>> API Runtime Execution and Hosting – Mule Runtimes, CloudHub, Runtime Services>> API Operations and Management – Anypoint API Manager, Anypoint ExchangeCorrect Answers: API Operations and Management and API Consumer Engagement*****************************************>> API Design and Development – Anypoint Studio, Anypoint Design Center, Anypoint Connectors>> API Runtime Execution and Hosting – Mule Runtimes, CloudHub, Runtime Services>> API Operations and Management – Anypoint API Manager, Anypoint Exchange>> API Consumer Management – API Contracts, Public Portals, Anypoint Exchange, API NotebooksQUESTION 12What is true about API implementations when dealing with legal regulations that require all data processing to be performed within a certain jurisdiction (such as in the USA or the EU)?  They must avoid using the Object Store as it depends on services deployed ONLY to the US East region  They must use a Jurisdiction-local external messaging system such as Active MQ rather than Anypoint MQ  They must te deployed to Anypoint Platform runtime planes that are managed by Anypoint Platform control planes, with both planes in the same Jurisdiction  They must ensure ALL data is encrypted both in transit and at rest QUESTION 13Refer to the exhibit.Three business processes need to be implemented, and the implementations need to communicate with several different SaaS applications.These processes are owned by separate (siloed) LOBs and are mainly independent of each other, but do share a few business entities. Each LOB has one development team and their own budget In this organizational context, what is the most effective approach to choose the API data models for the APIs that will implement these business processes with minimal redundancy of the data models?A) Build several Bounded Context Data Models that align with coherent parts of the business processes and the definitions of associated business entitiesB) Build distinct data models for each API to follow established micro-services and Agile API-centric practicesC) Build all API data models using XML schema to drive consistency and reuse across the organizationD) Build one centralized Canonical Data Model (Enterprise Data Model) that unifies all the data types from all three business processes, ensuring the data model is consistent and non-redundant  Option A  Option B  Option C  Option D Correct answer: Build several Bounded Context Data Models that align with coherent parts of 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.QUESTION 14When must an API implementation be deployed to an Anypoint VPC?  When the API Implementation must invoke publicly exposed services that are deployed outside of CloudHub in a customer- managed AWS instance  When the API implementation must be accessible within a subnet of a restricted customer-hosted network that does not allow public access  When the API implementation must be deployed to a production AWS VPC using the Mule Maven plugin  When the API Implementation must write to a persistent Object Store QUESTION 15An API implementation is deployed on a single worker on CloudHub and invoked by external API clients (outside of CloudHub). How can an alert be set up that is guaranteed to trigger AS SOON AS that API implementation stops responding to API invocations?  Implement a heartbeat/health check within the API and invoke it from outside the Anypoint Platform and alert when the heartbeat does not respond  Configure a “worker not responding” alert in Anypoint Runtime Manager  Handle API invocation exceptions within the calling API client and raise an alert from that API client when the API Is unavailable  Create an alert for when the API receives no requests within a specified time period QUESTION 16A company uses a hybrid Anypoint Platform deployment model that combines the EU control plane with customer-hosted Mule runtimes. After successfully testing a Mule API implementation in the Staging environment, the Mule API implementation is set with environment-specific properties and must be promoted to the Production environment. What is a way that MuleSoft recommends to configure the Mule API implementation and automate its promotion to the Production environment?  Bundle properties files for each environment into the Mule API implementation’s deployable archive, then promote the Mule API implementation to the Production environment using Anypoint CLI or the Anypoint Platform REST APIsB.  Modify the Mule API implementation’s properties in the API Manager Properties tab, then promote the Mule API implementation to the Production environment using API Manager  Modify the Mule API implementation’s properties in Anypoint Exchange, then promote the Mule API implementation to the Production environment using Runtime Manager  Use an API policy to change properties in the Mule API implementation deployed to the Staging environment and another API policy to deploy the Mule API implementation to the Production environment Correct answer: Bundle properties files for each environment into the Mule API implementation’s deployable archive, then promote the Mule API implementation to the Production environment using Anypoint CLI or the Anypoint Platform REST APIs*****************************************>> Anypoint Exchange is for asset discovery and documentation. It has got no provision to modify the properties of Mule API implementations at all.>> API Manager is for managing API instances, their contracts, policies and SLAs. It has also got no provision to modify the properties of API implementations.>> API policies are to address Non-functional requirements of APIs and has again got no provision to modify the properties of API implementations.So, the right way and recommended way to do this as part of development practice is to bundle properties files for each environment into the Mule API implementation and just point and refer to respective file per environment.QUESTION 17What best describes the Fully Qualified Domain Names (FQDNs), also known as DNS entries, created when a Mule application is deployed to the CloudHub Shared Worker Cloud?  A fixed number of FQDNs are created, IRRESPECTIVE of the environment and VPC design  The FQDNs are determined by the application name chosen, IRRESPECTIVE of the region  The FQDNs are determined by the application name, but can be modified by an administrator after deployment  The FQDNs are determined by both the application name and the Anypoint Platform organization QUESTION 18What API policy would be LEAST LIKELY used when designing an Experience API that is intended to work with a consumer mobile phone or tablet application?  OAuth 2.0 access token enforcement  Client ID enforcement  JSON threat protection  IPwhitellst Correct answer: IP whitelist*****************************************>> OAuth 2.0 access token and Client ID enforcement policies are VERY common to apply on Experience APIs as API consumers need to register and access the APIs using one of these mechanisms>> JSON threat protection is also VERY common policy to apply on Experience APIs to prevent bad or suspicious payloads hitting the API implementations.>> IP whitelisting policy is usually very common in Process and System APIs to only whitelist the IP range inside the local VPC. But also applied occassionally on some experience APIs where the End User/ API Consumers are FIXED.>> When we know the API consumers upfront who are going to access certain Experience APIs, then we can request for static IPs from such consumers and whitelist them to prevent anyone else hitting the API.However, the experience API given in the question/ scenario is intended to work with a consumer mobile phone or tablet application. Which means, there is no way we can know all possible IPs that are to be whitelisted as mobile phones and tablets can so many in number and any device in the city/state/country/globe.So, It is very LEAST LIKELY to apply IP Whitelisting on such Experience APIs whose consumers are typically Mobile Phones or Tablets.QUESTION 19A System API is designed to retrieve data from a backend system that has scalability challenges. What API policy can best safeguard the backend system?  IPwhitelist  SLA-based rate limiting  Auth 2 token enforcement  Client ID enforcement Explanationhttps://dzone.com/articles/how-to-secure-apisQUESTION 20What 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 https://www.folkstalk.com/2019/11/mulesoft-integration-and-platform.html Explanation:Correct answer: To invoke OAuth 2.0-protected APIs managed by Anypoint Platform, API clients must submit access tokens issued by that same Identity Provider*****************************************>> It is NOT necessary that single sign-on is required to sign in to Anypoint Platform because we are using an external Identity Provider for Client Management>> It is NOT necessary that all APIs managed by Anypoint Platform must be protected by SAML 2.0 policies because we are using an external Identity Provider for Client Management>> Not TRUE that the application network must include System APIs that interact with the Identity Provider because we are using an external Identity Provider for Client Management Only TRUE statement in the given options is – “To invoke OAuth 2.0-protected APIs managed by Anypoint Platform, API clients must submit access tokens issued by that same Identity Provider” References:https://docs.mulesoft.com/api-manager/2.x/external-oauth-2.0-token-validation-policyhttps://blogs.mulesoft.com/dev/api-dev/api-security-ways-to-authenticate-and-authorize/QUESTION 21An API experiences a high rate of client requests (TPS) vwth small message paytoads. How can usage limits be imposed on the API based on the type of client application?  Use an SLA-based rate limiting policy and assign a client application to a matching SLA tier based on its type  Use a spike control policy that limits the number of requests for each client application type  Use a cross-origin resource sharing (CORS) policy to limit resource sharing between client applications, configured by the client application type  Use a rate limiting policy and a client ID enforcement policy, each configured by the client application type Correct answer: Use an SLA-based rate limiting policy and assign a client application to a matching SLA tier based on its type.*****************************************>> SLA tiers will come into play whenever any limits to be imposed on APIs based on client typeQUESTION 22What Mule application deployment scenario requires using Anypoint Platform Private Cloud Edition or Anypoint Platform for Pivotal Cloud Foundry?  When it Is required to make ALL applications highly available across multiple data centers  When it is required that ALL APIs are private and NOT exposed to the public cloud  When regulatory requirements mandate on-premises processing of EVERY data item, including meta-data  When ALL backend systems in the application network are deployed in the organization’s intranet Correct answer: When regulatory requirements mandate on-premises processing of EVERY data item, including meta-data.*****************************************We need NOT require to use Anypoint Platform PCE or PCF for the below. So these options are OUT.>> We can make ALL applications highly available across multiple data centers using CloudHub too.>> We can use Anypoint VPN and tunneling from CloudHub to connect to ALL backend systems in the application network that are deployed in the organization’s intranet.>> We can use Anypoint VPC and Firewall Rules to make ALL APIs private and NOT exposed to the public cloud.Only valid reason in the given options that requires to use Anypoint Platform PCE/ PCF is – When regulatory requirements mandate on-premises processing of EVERY data item, including meta-data.QUESTION 23What is typically NOT a function of the APIs created within the framework called API-led connectivity?  They provide an additional layer of resilience on top of the underlying backend system, thereby insulating clients from extended failure of these systems.  They allow for innovation at the user Interface level by consuming the underlying assets without being aware of how data Is being extracted from backend systems.  They reduce the dependency on the underlying backend systems by helping unlock data from backend systems In a reusable and consumable way.  They can compose data from various sources and combine them with orchestration logic to create higher level value. Explanationhttps://dzone.com/articles/api-led-connectivity-with-muleQUESTION 24What is a typical result of using a fine-grained rather than a coarse-grained API deployment model to implement a given business process?  A decrease in the number of connections within the application network supporting the business process  A higher number of discoverable API-related assets in the application network  A better response time for the end user as a result of the APIs being smaller in scope and complexity  An overall tower usage of resources because each fine-grained API consumes less resources Correct answer: A higher number of discoverable API-related assets in the application network.*****************************************>> We do NOT get faster response times in fine-grained approach when compared to coarse-grained approach.>> In fact, we get faster response times from a network having coarse-grained APIs compared to a network having fine-grained APIs model. The reasons are below.Fine-grained approach:1. will have more APIs compared to coarse-grained2. So, more orchestration needs to be done to achieve a functionality in business process.3. Which means, lots of API calls to be made. So, more connections will needs to be established. So, obviously more hops, more network i/o, more number of integration points compared to coarse-grained approach where fewer APIs with bulk functionality embedded in them.4. That is why, because of all these extra hops and added latencies, fine-grained approach will have bit more response times compared to coarse-grained.5. Not only added latencies and connections, there will be more resources used up in fine-grained approach due to more number of APIs.That’s why, fine-grained APIs are good in a way to expose more number of resuable assets in your network and make them discoverable. However, needs more maintenance, taking care of integration points, connections, resources with a little compromise w.r.t network hops and response times.QUESTION 25Once an API Implementation is ready and the API is registered on API Manager, who should request the access to the API on Anypoint Exchange?  None  Both  API Client  API Consumer Correct answer: API Consumer*****************************************>> API clients are piece of code or programs that use the client credentials of API consumer but does not directly interact with Anypoint Exchange to get the access>> API consumer is the one who should get registered and request access to API and then API client needs to use those client credentials to hit the APIs So, API consumer is the one who needs to request access on the API from Anypoint ExchangeQUESTION 26What 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 QUESTION 27A code-centric API documentation environment should allow API consumers to investigate and execute API client source code that demonstrates invoking one or more APIs as part of representative scenarios.What is the most effective way to provide this type of code-centric API documentation environment using Anypoint Platform?  Enable mocking services for each of the relevant APIs and expose them via their Anypoint Exchange entry  Ensure the APIs are well documented through their Anypoint Exchange entries and API Consoles and share these pages with all API consumers  Create API Notebooks and include them in the relevant Anypoint Exchange entries  Make relevant APIs discoverable via an Anypoint Exchange entry QUESTION 28Refer to the exhibit.What is the best way to decompose one end-to-end business process into a collaboration of Experience, Process, and System APIs?A) Handle customizations for the end-user application at the Process API level rather than the Experience API levelB) Allow System APIs to return data that is NOT currently required by the identified Process or Experience APIsC) Always use a tiered approach by creating exactly one API for each of the 3 layers (Experience, Process and System APIs)D) Use a Process API to orchestrate calls to multiple System APIs, but NOT to other Process APIs  Option A  Option B  Option C  Option D QUESTION 29What is a key performance indicator (KPI) that measures the success of a typical C4E that is immediately apparent in responses from the Anypoint Platform APIs?  The number of production outage incidents reported in the last 24 hours  The number of API implementations that have a publicly accessible HTTP endpoint and are being managed by Anypoint Platform  The fraction of API implementations deployed manually relative to those deployed using a CI/CD tool  The number of API specifications in RAML or OAS format published to Anypoint Exchange QUESTION 30What condition requires using a CloudHub Dedicated Load Balancer?  When cross-region load balancing is required between separate deployments of the same Mule application  When custom DNS names are required for API implementations deployed to customer-hosted Mule runtimes  When API invocations across multiple CloudHub workers must be load balanced  When server-side load-balanced TLS mutual authentication is required between API implementations and API clients QUESTION 31What is a key performance indicator (KPI) that measures the success of a typical C4E that is immediately apparent in responses from the Anypoint Platform APIs?  The number of production outage incidents reported in the last 24 hours  The number of API implementations that have a publicly accessible HTTP endpoint and are being managed by Anypoint Platform  The fraction of API implementations deployed manually relative to those deployed using a CI/CD tool  The number of API specifications in RAML or OAS format published to Anypoint Exchange Correct answer: The number of API specifications in RAML or OAS format published to Anypoint Exchange*****************************************>> The success of C4E always depends on their contribution to the number of reusable assets that they have helped to build and publish to Anypoint Exchange.>> It is NOT due to any factors w.r.t # of outages, Manual vs CI/CD deployments or Publicly accessible HTTP endpoints>> Anypoint Platform APIs helps us to quickly run and get the number of published RAML/OAS assets to Anypoint Exchange. This clearly depicts how successful a C4E team is based on number of returned assets in the response.QUESTION 32What API policy would be LEAST LIKELY used when designing an Experience API that is intended to work with a consumer mobile phone or tablet application?  OAuth 2.0 access token enforcement  Client ID enforcement  JSON threat protection  IP whitelist QUESTION 33Refer to the exhibit. An organization is running a Mule standalone runtime and has configured Active Directory as the Anypoint Platform external Identity Provider. The organization does not have budget for other system components.What policy should be applied to all instances of APIs in the organization to most effecuvelyKestrict access to a specific group of internal users?  Apply a basic authentication – LDAP policy; the internal Active Directory will be configured as the LDAP source for authenticating users  Apply a client ID enforcement policy; the specific group of users will configure their client applications to use their specific client credentials  Apply an IP whitelist policy; only the specific users’ workstations will be in the whitelist  Apply an OAuth 2.0 access token enforcement policy; the internal Active Directory will be configured as the OAuth server QUESTION 34What 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  Loading … MuleSoft MCPA-Level-1 Real 2024 Braindumps Mock Exam Dumps: https://www.dumpsmaterials.com/MCPA-Level-1-real-torrent.html --------------------------------------------------- Images: https://exams.dumpsmaterials.com/wp-content/plugins/watu/loading.gif https://exams.dumpsmaterials.com/wp-content/plugins/watu/loading.gif --------------------------------------------------- --------------------------------------------------- Post date: 2024-02-14 11:30:28 Post date GMT: 2024-02-14 11:30:28 Post modified date: 2024-02-14 11:30:28 Post modified date GMT: 2024-02-14 11:30:28