Pass Exam With Full Sureness - MCPA-Level-1 Dumps with 154 Questions
Verified MCPA-Level-1 dumps Q&As - 100% Pass from PremiumVCEDump
MuleSoft MCPA-Level-1 certification is designed to validate the skills and knowledge of a MuleSoft Certified Platform Architect - Level 1. MuleSoft Certified Platform Architect - Level 1 certification is intended for individuals who have experience in designing, building, and deploying integration solutions using MuleSoft's Anypoint Platform. The MCPA-Level-1 certification exam tests the candidate's understanding of various aspects of MuleSoft, including the architecture of the Anypoint Platform, MuleSoft's API-led connectivity approach, and building and designing APIs using Anypoint Studio.
The MuleSoft Certified Platform Architect - Level 1 certification is an essential requirement for professionals who want to advance their careers in the field of MuleSoft integration. It is ideal for architects, developers, and integration specialists who want to demonstrate their expertise in MuleSoft integration. MuleSoft Certified Platform Architect - Level 1 certification provides a competitive edge to the candidates and helps them stand out in the job market.
NEW QUESTION # 77
What condition requires using a CloudHub Dedicated Load Balancer?
- A. When API invocations across multiple CloudHub workers must be load balanced
- B. When custom DNS names are required for API implementations deployed to customer-hosted Mule runtimes
- C. When server-side load-balanced TLS mutual authentication is required between API implementations and API clients
- D. When cross-region load balancing is required between separate deployments of the same Mule application
Answer: B
NEW QUESTION # 78
A customer has an ELA contract with MuleSoft. An API deployed to CloudHub is consistently experiencing performance issues. Based on the root cause analysis, it is determined that autoscaling needs to be applied.
How can this be achieved?
- A. Configure a policy based on CPU usage so that CloudHub auto-adjusts the number of workers/replicas (horizontal scaling)
- B. Configure a policy so that when the response time reaches a certain threshold the worker/replica type increases (vertical scaling)
- C. Configure a policy so that when the number of HTTP requests reaches a certain threshold the number of workers/replicas increases (horizontal scaling)
- D. Configure two separate policies: When CPU and memory reach certain threshold, increase the worker
/replica type (vertical sealing) and the number of workers/replicas (horizontal sealing)
Answer: A
Explanation:
In MuleSoft CloudHub, autoscaling is essential to managing application load efficiently. CloudHub supports horizontal scaling based on CPU usage, which is well-suited to applications experiencing variable demand and needing responsive resource allocation.
* Autoscaling on CloudHub:
* Horizontal scaling increases the number of workers in response to CPU usage thresholds, allowing the application to handle higher loads dynamically. This approach improves performance without downtime or manual intervention.
* Why Option C is Correct:
* Setting up autoscaling based on CPU usage aligns with MuleSoft's best practices for scalable and responsive applications on CloudHub, particularly in an environment with fluctuating load patterns.
* Option C correctly leverages CloudHub's autoscaling features based on resource metrics, which are part of CloudHub's managed scaling solutions.
* Explanation of Incorrect Options:
* Option A (based on HTTP request thresholds) and Option B (separate policies for CPU and memory) do not represent CloudHub's recommended scaling practices.
* Option D suggests vertical scaling based on response time, which is not how CloudHub handles autoscaling.
ReferencesFor more on CloudHub's autoscaling configuration, refer to MuleSoft documentation on CloudHub autoscaling policies.
NEW QUESTION # 79
What API policy would LEAST likely be applied to a Process API?
- A. Custom circuit breaker
- B. Rate limiting
- C. JSON threat protection
- D. Client ID enforcement
Answer: C
Explanation:
JSON threat protection
*****************************************
Fact: Technically, there are no restrictions on what policy can be applied in what layer. Any policy can be applied on any layer API. However, context should also be considered properly before blindly applying the policies on APIs.
That is why, this question asked for a policy that would LEAST likely be applied to a Process API.
From the given options:
>> All policies except "JSON threat protection" can be applied without hesitation to the APIs in Process tier.
>> JSON threat protection policy ideally fits for experience APIs to prevent suspicious JSON payload coming from external API clients. This covers more of a security aspect by trying toavoid possibly malicious and harmful JSON payloads from external clients calling experience APIs.
As external API clients are NEVER allowed to call Process APIs directly and also these kind of malicious and harmful JSON payloads are always stopped at experience API layer only using this policy, it is LEAST LIKELY that this same policy is again applied on Process Layer API.
NEW QUESTION # 80
An online store's marketing team has noticed an increase in customers leaving online baskets without checking out. They suspect a technology issue is at the root cause of the baskets being left behind. They approach the Center for Enablement to ask for help identifying the issue. Multiple APIs from across all the layers of their application network are involved in the shopping application.
Which feature of the Anypoint Platform can be used to view metrics from all involved APIs at the same time?
- A. Functional monitoring
- B. API Manager
- C. Custom dashboards
- D. Built-in dashboards
Answer: D
Explanation:
* Understanding the Need for Cross-API Monitoring:
* The Center for Enablement (C4E) needs to investigate potential technical issues across multiple APIs in the application network that may be causing customers to abandon their carts.
* This requires a solution that allows viewing metrics across several APIs in real-time to identify any performance issues or bottlenecks.
* Evaluating Anypoint Platform Features:
* Built-in Dashboards: Anypoint Platform provides built-in dashboards in Anypoint Monitoring, allowing teams to view metrics from multiple APIs in a single interface. This feature is designed to monitor API performance, latency, errors, and throughput, and is ideal for tracking performance across all layers of the application network.
* Custom Dashboards: While custom dashboards allow for more tailored views, the built-in dashboards already aggregate metrics for multiple APIs, making it unnecessary to build a custom solution for this scenario.
* Functional Monitoring: This feature is used to set up tests to monitor specific API functionality and uptime but is not suited for tracking metrics across multiple APIs in real-time.
* API Manager: API Manager primarily focuses on managing API policies, contracts, and access control rather than providing detailed, real-time metrics across the entire application network.
* Conclusion:
* Option B (Built-in dashboards) is the best choice because it provides a comprehensive view of metrics from all APIs involved, enabling the C4E team to quickly identify any issues that may be contributing to abandoned shopping carts.
Refer to MuleSoft's documentation on Anypoint Monitoring and built-in dashboards for more details on configuring and using these dashboards effectively.
NEW QUESTION # 81
Refer to the exhibit.
What is a valid API in the sense of API-led connectivity and application networks?
A) Java RMI over TCP
B) Java RMI over TCP
C) CORBA over HOP
D) XML over UDP
- A. Option A
- B. Option D
- C. Option C
- D. Option B
Answer: B
Explanation:
Correct answer: 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.
NEW QUESTION # 82
An auto manufacturer has a mature CI/CD practice and wants to automate packaging and deployment of any Mule applications to various deployment targets, including CloudHub workers/replicas, customer-hosted Mule runtimes, and Anypoint Runtime Fabric.
Which MuleSoft-provided tool or component facilitates automating the packaging and deployment of Mule applications to various deployment targets as part of the company's CI/CD practice?
- A. Anypoint Platform REST APIs
- B. Anypoint Runtime Manager
- C. Mule Maven plugin
- D. Anypoint Platform CLI
Answer: C
Explanation:
For organizations with established CI/CD practices, the Mule Maven plugin is the recommended tool for automating packaging and deployment across multiple environments, including CloudHub, on-premise Mule runtimes, and Anypoint Runtime Fabric. Here's why:
* Automation with Maven:
* The Mule Maven plugin allows for CI/CD integration by supporting automated build and deployment processes. It is commonly used in CI/CD pipelines to handle application packaging and deployment directly through Maven commands, making it ideal for teams that want consistent deployment automation across different MuleSoft environments.
* Supported Deployment Targets:
* The Mule Maven plugin supports deployment to various targets, including CloudHub, Runtime Fabric, and on-premises servers, thus meeting the needs of environments with diverse deployment destinations.
* Why Option B is Correct:
* The Mule Maven plugin is specifically designed for CI/CD pipelines and integrates with Jenkins, GitLab, and other CI/CD tools to facilitate continuous deployment. It is the most efficient MuleSoft-provided tool for this purpose.
* Explanation of Incorrect Options:
* Option A (Anypoint Runtime Manager) provides deployment management but does not automate CI/CD processes.
* Option C (Anypoint Platform CLI) can script deployments but lacks direct integration with CI
/CD tools.
* Option D (Anypoint Platform REST APIs) requires custom scripting for deployment, which can be more complex than using the Mule Maven plugin.
ReferencesFor more details, refer to MuleSoft documentation on using the Mule Maven plugin for CI/CD.
NEW QUESTION # 83
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
Answer: A
Explanation:
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.
NEW QUESTION # 84
What correctly characterizes unit tests of Mule applications?
- A. They test the validity of input and output of source and target systems
- B. They must be triggered by an external client tool or event source
- C. They must be run in a unit testing environment with dedicated Mule runtimes for the environment
- D. They are typically written using MUnit to run in an embedded Mule runtime that does not require external connectivity
Answer: C
NEW QUESTION # 85
Refer to the exhibits.
Which architectural constraint is compatible with the API-led connectivity architectural style?
- A. Use a Process API to-orchestrate calls to multiple System APIs but not to other Process APIs:
- B. Handle customizations for the end-user application at the Process layer rather than at the Experience layer
- C. Always use a tiered approach by creating exactly one API for each of the three layers (Experience, Process, and System)
- D. Allow System APIs to return data that is not currently required by the identified Process or Experience APIs
Answer: A
Explanation:
* Understanding API-led Connectivity Layers:
* In MuleSoft's API-led connectivity approach, APIs are categorized into three layers:
* Experience Layer: This layer is responsible for providing data to the end-user applications and is often customized to meet the needs of different user interfaces.
* Process Layer: This layer is used to orchestrate and combine data from multiple System APIs. It acts as a mediator and business logic layer without directly interacting with the backend systems.
* System Layer: This layer provides direct access to the backend systems (e.g., databases, ERPs) and is usually focused on exposing atomic data operations.
* Evaluating the Architectural Constraints:
* Option A: Always using a strict tiered approach by creating exactly one API per layer is not necessarily an architectural constraint of API-led connectivity. While a layered approach is recommended, it is common to have multiple APIs in each layer as needed for different functionalities.
* Option B (Correct Answer): In API-led connectivity, Process APIs are generally responsible for orchestrating calls to System APIs and should not call other Process APIs. This maintains a clear separation of concerns, ensuring that Process APIs aggregate data from System APIs only and provide it to Experience APIs.
* Option C: System APIs are generally designed to provide only the necessary data to meet current business requirements. Allowing them to return extra data that is not needed by Process or Experience APIs is not a best practice, as it can lead to inefficiencies.
* Option D: Customizations specific to end-user applications are typically handled at the Experience Layer rather than the Process Layer, as the Experience Layer is intended to tailor the data to fit the needs of each specific client or front-end application.
* Conclusion:
* Option B is the correct answer as it aligns with the API-led connectivity principles. In this architectural style, Process APIs should orchestrate System APIs but should avoid interacting with other Process APIs to keep a clear separation of responsibilities across the layers.
For additional details, refer to MuleSoft documentation on API-led connectivity best practices, particularly around the roles of each layer in API orchestration and data handling.
NEW QUESTION # 86
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?
- A. GET, PUT, OPTIONS
- B. GET, HEAD, POST
- C. GET, OPTIONS, HEAD
- D. PUT, POST, DELETE
Answer: D
NEW QUESTION # 87
What 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)?
- A. They must avoid using the Object Store as it depends on services deployed ONLY to the US East region
- B. They must use a Jurisdiction-local external messaging system such as Active MQ rather than Anypoint MQ
- C. They must ensure ALL data is encrypted both in transit and at rest
- D. They must te deployed to Anypoint Platform runtime planes that are managed by Anypoint Platform control planes, with both planes in the same Jurisdiction
Answer: D
NEW QUESTION # 88
True or False. We should always make sure that the APIs being designed and developed are self-servable even if it needs more man-day effort and resources.
- A. FALSE
- B. TRUE
Answer: B
Explanation:
Correct answer: TRUE
*****************************************
>> As per MuleSoft proposed IT Operating Model, designing APIs and making sure that they are discoverable and self-servable is VERY VERY IMPORTANT and decides the success of an API and its application network.
NEW QUESTION # 89
A new upstream API Is being designed to offer an SLA of 500 ms median and 800 ms maximum (99th percentile) response time. The corresponding API implementation needs to sequentially invoke 3 downstream APIs of very similar complexity.
The first of these downstream APIs offers the following SLA for its response time: median: 100 ms, 80th percentile: 500 ms, 95th percentile: 1000 ms.
If possible, how can a timeout be set in the upstream API for the invocation of the first downstream API to meet the new upstream API's desired SLA?
- A. Do not set a timeout; the Invocation of this API Is mandatory and so we must wait until it responds
- B. No timeout is possible to meet the upstream API's desired SLA; a different SLA must be negotiated with the first downstream API or invoke an alternative API
- C. Set a timeout of 100 ms; that leaves 400 ms for the other two downstream APIs to complete
- D. Set a timeout of 50 ms; this times out more invocations of that API but gives additional room for retries
Answer: C
Explanation:
Set a timeout of 100ms; that leaves 400ms for other two downstream APIs to complete
*****************************************
Key details to take from the given scenario:
>> Upstream API's designed SLA is 500ms (median). Lets ignore maximum SLA response times.
>> This API calls 3 downstream APIs sequentially and all these are of similar complexity.
>> The first downstream API is offering median SLA of 100ms, 80th percentile: 500ms; 95th percentile:
1000ms.
Based on the above details:
>> We can rule out the option which is suggesting to set 50ms timeout. Because, if the median SLA itself being offered is 100ms then most of the calls are going to timeout and time gets wasted in retried them and eventually gets exhausted with all retries. Even if some retries gets successful, the remaining time wont leave enough room for 2nd and 3rd downstream APIs to respond within time.
>> The option suggesting to NOT set a timeout as the invocation of this API is mandatory and so we must wait until it responds is silly. As not setting time out would go against the good implementation pattern and moreover if the first API is not responding within its offered median SLA 100ms then most probably it would either respond in 500ms (80th percentile) or 1000ms (95th percentile). In BOTH cases, getting a successful response from 1st downstream API does NO GOOD because already by this time the Upstream API SLA of
500 ms is breached. There is no time left to call 2nd and 3rd downstream APIs.
>> It is NOT true that no timeout is possible to meet the upstream APIs desired SLA.
As 1st downstream API is offering its median SLA of 100ms, it means MOST of the time we would get the responses within that time. So, setting a timeout of 100ms would be ideal for MOST calls as it leaves enough room of 400ms for remaining 2 downstream API calls.
NEW QUESTION # 90
A Rate Limiting policy is applied to an API implementation to protect the back-end system. Recently, there have been surges in demand that cause some API client POST requests to the API implementation to be rejected with policy-related errors, causing delays and complications to the API clients.
How should the API policies that are applied to the API implementation be changed to reduce the frequency of errors returned to API clients, while still protecting the back-end system?
- A. Keep the Rate Limiting policy and add 9 Client ID Enforcement policy
- B. Remove the Rate Limiting policy and add an HTTP Caching policy
- C. Remove the Rate Limiting policy and add a Spike Control policy
- D. Keep the Rate Limiting policy and add an SLA-based Spike Control policy
Answer: D
Explanation:
When managing high traffic to an API, especially with POST requests, it is crucial to ensure the API's policies both protect the back-end systems and provide a smooth client experience. Here's the approach to reducing errors:
* Rate Limiting Policy: This policy enforces a limit on the number of requests within a defined time period. However, rate limiting alone may cause clients to hit limits during demand surges, leading to errors.
* Adding an SLA-based Spike Control Policy:
* Spike Control is designed to handle sudden increases in traffic by smoothing out bursts of requests, which is particularly useful during high-demand periods.
* By configuring SLA-based Spike Control, you can define thresholds for specific client tiers. For instance, premium clients might have higher limits or more flexibility in traffic bursts than standard clients.
* Why Option D is Correct:
* Keeping the Rate Limiting policy continues to provide baseline protection for the back-end.
* Adding the SLA-based Spike Control policy allows for differentiated control, where requests are queued or delayed during bursts rather than outright rejected. This approach significantly reduces error responses to clients while still controlling overall traffic.
* Explanation of Incorrect Options:
* Option A (adding Client ID Enforcement) would not reduce errors related to traffic surges.
* Option B (HTTP Caching) is not applicable as caching is generally ineffective for non- idempotent requests like POST.
* Option C (only Spike Control without Rate Limiting) may leave the back-end system vulnerable to sustained high traffic levels, reducing protection.
ReferencesFor more information on configuring Rate Limiting and SLA-based Spike Control policies, refer to MuleSoft documentation on API Policies and Rate Limiting.
NEW QUESTION # 91
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?
- A. If there are misspellings of the data fields in the back-end system, Systerm APIs should not correct it, and expose it as-is to mirror the back-end systems
- B. The data model should define its own naming convention, and not follow the same naming as the back- end systems
- C. The System APIs should expose all back-end system fields
- D. The data model of the System APIs should make use of data types that approximately mirror those from the back-end systems
Answer: D
Explanation:
When defining data models for System APIs without an established Enterprise Data Model, MuleSoft recommends mirroring the back-end systems' data types to achieve quick and effective integration without adding complexity. This approach has several benefits:
* Alignment with Backend Systems:
* Mirroring data types ensures consistency with backend data sources, which simplifies integration, reduces mapping requirements, and minimizes potential data transformation issues.
* Flexibility for Future Enhancements:
* By retaining close alignment with backend data structures, System APIs can evolve to support an Enterprise Data Model in the future without immediate restructuring.
* Explanation of Incorrect Options:
* Option A (exposing misspellings) is not recommended as System APIs should still ensure a professional and coherent interface.
* Option C (custom naming) complicates the API structure without adding immediate value in the absence of a clear data model.
* Option D (exposing all fields) is unnecessary and can reduce performance and add complexity.
ReferencesRefer to MuleSoft best practices for data modeling in System APIs for additional information on mirroring backend systems.
NEW QUESTION # 92
What 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?
- A. The fraction of API implementations deployed manually relative to those deployed using a CI/CD tool
- B. The number of API implementations that have a publicly accessible HTTP endpoint and are being managed by Anypoint Platform
- C. The number of API specifications in RAML or OAS format published to Anypoint Exchange
- D. The number of production outage incidents reported in the last 24 hours
Answer: B
NEW QUESTION # 93
Refer 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 level
B) Allow System APIs to return data that is NOT currently required by the identified Process or Experience APIs
C) 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
- A. Option D
- B. Option A
- C. Option B
- D. Option C
Answer: D
NEW QUESTION # 94
What 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. The FQDNs are determined by both the application name and the Anypoint Platform organization
- B. A fixed number of FQDNs are created, IRRESPECTIVE of the environment and VPC design
- C. The FQDNs are determined by the application name, but can be modified by an administrator after deployment
- D. The FQDNs are determined by the application name chosen, IRRESPECTIVE of the region
Answer: D
Explanation:
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.
NEW QUESTION # 95
An organization wants MuleSoft-hosted runtime plane features (such as HTTP load balancing, zero downtime, and horizontal and vertical scaling) in its Azure environment. What runtime plane minimizes the organization's effort to achieve these features?
- A. A hybrid combination of customer-hosted and MuleSoft-hosted Mule runtimes
- B. Anypoint Runtime Fabric
- C. CloudHub
- D. Anypoint Platform for Pivotal Cloud Foundry
Answer: B
Explanation:
Anypoint Runtime Fabric
*****************************************
>> When a customer is already having an Azure environment, It is not at all an ideal approach to go with hybrid model having some Mule Runtimes hosted on Azure and some on MuleSoft. This is unnecessary and useless.
>> CloudHub is a Mulesoft-hosted Runtime plane and is on AWS. We cannot customize to point CloudHub to customer's Azure environment.
>> Anypoint Platform for Pivotal Cloud Foundry is specifically for infrastructure provided by Pivotal Cloud Foundry
>> Anypoint Runtime Fabric is right answer as it is a container service that automates the deployment and orchestration of Mule applications and API gateways. Runtime Fabric runs within a customer-managed infrastructure on AWS, Azure, virtual machines (VMs), and bare-metal servers.
-Some of the capabilities of Anypoint Runtime Fabric include:
-Isolation between applications by running a separate Mule runtime per application.
-Ability to run multiple versions of Mule runtime on the same set of resources.
-Scaling applications across multiple replicas.
-Automated application fail-over.
-Application management with Anypoint Runtime Manager.
NEW QUESTION # 96
What do the API invocation metrics provided by Anypoint Platform provide?
- A. Proactive identification of likely future policy violations that exceed a given threat threshold
- B. Data on past API invocations to help identify anomalies and usage patterns across various APIs
- C. ROI metrics from APIs that can be directly shared with business users
- D. Measurements of the effectiveness of the application network based on the level of reuse
Answer: D
Explanation:
Explanation/Reference: https://usermanual.wiki/Document/APAAppNetstudentManual02may2018.991784750.pdf
NEW QUESTION # 97
A company wants to move its Mule API implementations into production as quickly as possible. To protect access to all Mule application data and metadata, the company requires that all Mule applications be deployed to the company's customer-hosted infrastructure within the corporate firewall. What combination of runtime plane and control plane options meets these project lifecycle goals?
- A. Manually provisioned customer-hosted runtime plane and MuleSoft-hosted control plane
- B. MuleSoft-hosted runtime plane and customer-hosted control plane
- C. iPaaS provisioned customer-hosted runtime plane and MuleSoft-hosted control plane
- D. Manually provisioned customer-hosted runtime plane and customer-hosted control plane
Answer: D
Explanation:
Manually provisioned customer-hosted runtime plane and customer-hosted control plane
*****************************************
There are two key factors that are to be taken into consideration from the scenario given in the question.
>> Company requires both data and metadata to be resided within the corporate firewall
>> Company would like to go with customer-hosted infrastructure.
Any deployment model that is to deal with the cloud directly or indirectly (Mulesoft-hosted or Customer's own cloud like Azure, AWS) will have to share atleast the metadata.
Application data can be controlled inside firewall by having Mule Runtimes on customer hosted runtime plane. But if we go with Mulsoft-hosted/ Cloud-based control plane, the control plane required atleast some minimum level of metadata to be sent outside the corporate firewall.
As the customer requirement is pretty clear about the data and metadata both to be within the corporate firewall, even though customer wants to move to production as quickly as possible, unfortunately due to the nature of their security requirements, they have no other option but to go with manually provisioned customer-hosted runtime plane and customer-hosted control plane.
NEW QUESTION # 98
An Order API must be designed that contains significant amounts of integration logic and involves the invocation of the Product API.
The power relationship between Order API and Product API is one of "Customer/Supplier", because the Product API is used heavily throughout the organization and is developed by a dedicated development team located in the office of the CTO.
What strategy should be used to deal with the API data model of the Product API within the Order API?
- A. Start an organization-wide data modeling initiative that will result in an Enterprise Data Model that will then be used in both the Product API and the Order API
- B. Implement an anti-corruption layer in the Order API that transforms the Product API data model into internal data types of the Order API
- C. Work with the API data types of the Product API directly when implementing the integration logic of the Order API such that the Order API uses the same (unchanged) data types as the Product API
- D. Convince the development team of the Product API to adopt the API data model of the Order API such that the integration logic of the Order API can work with one consistent internal data model
Answer: B
NEW QUESTION # 99
What should be ensured before sharing an API through a public Anypoint Exchange portal?
- A. The users needing access to the API should be added to the appropriate role in Anypoint Platform
- B. The API should be secured using one of the supported authentication/authorization mechanisms to ensure that data is not compromised
- C. The API should be functional with at least an initial implementation deployed and accessible for users to interact with
- D. The visibility level of the API instances of that API that need to be publicly accessible should be set to public visibility
Answer: D
Explanation:
The visibility level of the API instances of that API that need to be publicly accessible should be set to public visibility.
*****************************************
NEW QUESTION # 100
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?
- A. AZs are selected as part of the Mule application's deployment configuration
- B. An AZ is randomly selected for a Mule application, and all the Mule application's CloudHub workers are assigned to that one AZ
- C. Workers are randomly distributed across available AZs within that region
- D. Workers belonging to a given environment are assigned to the same AZ within that region
Answer: B
NEW QUESTION # 101
......
MuleSoft is a leading provider of integration software that connects applications, data, and devices. The MuleSoft platform enables organizations to integrate their systems and applications with ease, making it a popular choice for businesses of all sizes. The MCPA-Level-1 certification is an essential credential for professionals who work with MuleSoft technologies.
MCPA-Level-1 Dumps Full Questions - Exam Study Guide: https://examsites.premiumvcedump.com/MuleSoft/valid-MCPA-Level-1-premium-vce-exam-dumps.html