MCPA-Level-1-Maintenance Dumps - Kickstart your Career with Real Updated Questions [Q14-Q35]

Share

MCPA-Level-1-Maintenance Dumps - Kickstart your Career with Real  Updated Questions

Earn Quick And Easy Success With MCPA-Level-1-Maintenance Dumps


MuleSoft MCPA-Level-1-Maintenance Exam Syllabus Topics:

TopicDetails
Topic 1
  • Describe the purpose and roles of a Center for Enablement (C4E)
  • Describe the capabilities and high-level components of Anypoint Platform
Topic 2
  • Identify changes to an API that would require or not require a major version increment
  • Explain how to register an API client for access to an API version
Topic 3
  • Break down functional requirements into business-aligned APIs with effective granularity
  • Identify idempotent HTTP methods and HTTP-native support for optimistic concurrency
Topic 4
  • Governing APIs on Anypoint Platform
  • Select appropriate API policies to enforce non-functional constraints on API invocations
Topic 5
  • Define and describe the benefits of API-led connectivity and application networks
  • Explain MuleSoft’s proposal for closing the IT delivery gap
Topic 6
  • Identify single points of failure in typical CloudHub usage
  • Identify the components of Anypoint Platform that generate data for monitoring and alerting
Topic 7
  • Correctly use the terms API, API implementation, API client, API consumer, and API invocation
  • Describe the fundamentals of deployments, networking, and routing on CloudHub

 

NEW QUESTION 14
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. 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
  • B. 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
  • 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. Implement an anti-corruption layer in the Order API that transforms the Product API data model into internal data types of the Order API

Answer: D

Explanation:
Convince the development team of the product API to adopt the API data model of the Order API such that integration logic of the Order API can work with one consistent internal data model
*****************************************
Key details to note from the given scenario:
>> Power relationship between Order API and Product API is customer/supplier So, as per below rules of "Power Relationships", the caller (in this case Order API) would request for features to the called (Product API team) and the Product API team would need to accomodate those requests.

 

NEW QUESTION 15
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:
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 16
What is true about automating interactions with Anypoint Platform using tools such as Anypoint Platform REST APIs, Anypoint CU, or the Mule Maven plugin?

  • A. Access to Anypoint Platform APIs and Anypoint CU can be controlled separately through the roles and permissions in Anypoint Platform, so that specific users can get access to Anypoint CLI white others get access to the platform APIs
  • B. Anypoint Platform APIs can ONLY automate interactions with CloudHub, while the Mule Maven plugin is required for deployment to customer-hosted Mule runtimes
  • C. API policies can be applied to the Anypoint Platform APIs so that ONLY certain LOBs have access to specific functions
  • D. By default, the Anypoint CLI and Mule Maven plugin are NOT included in the Mule runtime, so are NOT available to be used by deployed Mule applications

Answer: D

Explanation:
By default, the Anypoint CLI and Mule Maven plugin are NOT included in the Mule runtime, so are NOT available to be used by deployed Mule applications
*****************************************
>> We CANNOT apply API policies to the Anypoint Platform APIs like we can do on our custom written API instances. So, option suggesting this is FALSE.
>> Anypoint Platform APIs can be used for automating interactions with both CloudHub and customer-hosted Mule runtimes. Not JUST the CloudHub. So, option opposing this is FALSE.
>> Mule Maven plugin is NOT mandatory for deployment to customer-hosted Mule runtimes. It just helps your CI/CD to have smoother automation. But not a compulsory requirement to deploy. So, option opposing this is FALSE.
>> We DO NOT have any such special roles and permissions on the platform to separately control access for some users to have Anypoint CLI and others to have Anypoint Platform APIs. With proper general roles/permissions (API Owner, Cloudhub Admin etc..), one can use any of the options (Anypoint CLI or Platform APIs). So, option suggesting this is FALSE.
Only TRUE statement given in the choices is that - Anypoint CLI and Mule Maven plugin are NOT included in the Mule runtime, so are NOT available to be used by deployed Mule applications.
Maven is part of Studio or you can use other Maven installation for development.
CLI is convenience only. It is one of many ways how to install app to the runtime.
These are definitely NOT part of anything except your process of deployment or automation.

 

NEW QUESTION 17
A set of tests must be performed prior to deploying API implementations to a staging environment. Due to data security and access restrictions, untested APIs cannot be granted access to the backend systems, so instead mocked data must be used for these tests. The amount of available mocked data and its contents is sufficient to entirely test the API implementations with no active connections to the backend systems. What type of tests should be used to incorporate this mocked data?

  • A. Functional tests (Blackbox)
  • B. Integration tests
  • C. Performance tests
  • D. Unit tests (Whitebox)

Answer: D

Explanation:
Unit tests (Whitebox)
*****************************************

 

NEW QUESTION 18
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 customer-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 MuleSoft-hosted control plane

Answer: A

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 19
What is a key requirement when using an external Identity Provider for Client Management in Anypoint Platform?

  • A. APIs managed by Anypoint Platform must be protected by SAML 2.0 policies
  • B. To invoke OAuth 2.0-protected APIs managed by Anypoint Platform, API clients must submit access tokens issued by that same Identity Provider
  • C. The application network must include System APIs that interact with the Identity Provider
  • D. Single sign-on is required to sign in to Anypoint Platform

Answer: B

Explanation:
Explanation
https://www.folkstalk.com/2019/11/mulesoft-integration-and-platform.html Explanation
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-policy
https://blogs.mulesoft.com/dev/api-dev/api-security-ways-to-authenticate-and-authorize/

 

NEW QUESTION 20
The application network is recomposable: it is built for change because it "bends but does not break"

  • A. FALSE
  • B. TRUE

Answer: B

Explanation:
Explanation
*****************************************
>> Application Network is a disposable architecture.
>> Which means, it can be altered without disturbing entire architecture and its components.
>> It bends as per requirements or design changes but does not break

 

NEW QUESTION 21
A company requires Mule applications deployed to CloudHub to be isolated between non-production and production environments. This is so Mule applications deployed to non-production environments can only access backend systems running in their customer-hosted non-production environment, and so Mule applications deployed to production environments can only access backend systems running in their customer-hosted production environment. How does MuleSoft recommend modifying Mule applications, configuring environments, or changing infrastructure to support this type of per-environment isolation between Mule applications and backend systems?

  • A. Create separate Anypoint VPCs for non-production and production environments, then configure connections to the backend systems in the corresponding customer-hosted environments
  • B. Modify properties of Mule applications deployed to the production Anypoint Platform environments to prevent access from non-production Mule applications
  • C. Configure firewall rules in the infrastructure inside each customer-hosted environment so that only IP addresses from the corresponding Anypoint Platform environments are allowed to communicate with corresponding backend systems
  • D. Create non-production and production environments in different Anypoint Platform business groups

Answer: A

Explanation:
Create separate Anypoint VPCs for non-production and production environments, then configure connections to the backend systems in the corresponding customer-hosted environments.
*****************************************
>> Creating different Business Groups does NOT make any difference w.r.t accessing the non-prod and prod customer-hosted environments. Still they will be accessing from both Business Groups unless process network restrictions are put in place.
>> We need to modify or couple the Mule Application Implementations with the environment. In fact, we should never implements application coupled with environments by binding them in the properties. Only basic things like endpoint URL etc should be bundled in properties but not environment level access restrictions.
>> IP addresses on CloudHub are dynamic until unless a special static addresses are assigned. So it is not possible to setup firewall rules in customer-hosted infrastrcture. More over, even if static IP addresses are assigned, there could be 100s of applications running on cloudhub and setting up rules for all of them would be a hectic task, non-maintainable and definitely got a good practice.
>> The best practice recommended ), is to have your Anypoint VPCs
seperated for Prod and Non-Prod and perform the VPC peering or VPN tunneling for these Anypoint VPCs to respective Prod and Non-Prod customer-hosted environment networks.

 

NEW QUESTION 22
Version 3.0.1 of a REST API implementation represents time values in PST time using ISO 8601 hh:mm:ss format. The API implementation needs to be changed to instead represent time values in CEST time using ISO
8601 hh:mm:ss format. When following the semver.org semantic versioning specification, what version should be assigned to the updated API implementation?

  • A. 4.0.0
  • B. 3.0.1
  • C. 3.1.0
  • D. 3.0.2

Answer: A

Explanation:
4.0.0
*****************************************
As per semver.org semantic versioning specification:
Given a version number MAJOR.MINOR.PATCH, increment the:
- MAJOR version when you make incompatible API changes.
- MINOR version when you add functionality in a backwards compatible manner.
- PATCH version when you make backwards compatible bug fixes.
As per the scenario given in the question, the API implementation is completely changing its behavior.
Although the format of the time is still being maintained as hh:mm:ss and there is no change in schema w.r.t format, the API will start functioning different after this change as the times are going to come completely different.
Example: Before the change, say, time is going as 09:00:00 representing the PST. Now on, after the change, the same time will go as 18:00:00 as Central European Summer Time is 9 hours ahead of Pacific Time.
>> This may lead to some uncertain behavior on API clients depending on how they are handling the times in the API response. All the API clients need to be informed that the API functionality is going to change and will return in CEST format. So, this considered as a MAJOR change and the version of API for this new change would be 4.0.0

 

NEW QUESTION 23
An API implementation is deployed to CloudHub.
What conditions can be alerted on using the default Anypoint Platform functionality, where the alert conditions depend on the end-to-end request processing of the API implementation?

  • A. When a particular API client invokes the API too often within a given time period
  • B. When the API is invoked by an unrecognized API client
  • C. When the response time of API invocations exceeds a threshold
  • D. When the API receives a very high number of API invocations

Answer: C

Explanation:
When the response time of API invocations exceeds a threshold
*****************************************
>> Alerts can be setup for all the given options using the default Anypoint Platform functionality
>> However, the question insists on an alert whose conditions depend on the end-to-end request processing of the API implementation.
>> Alert w.r.t "Response Times" is the only one which requires end-to-end request processing of API implementation in order to determine if the threshold is exceeded or not.

 

NEW QUESTION 24
What Mule application deployment scenario requires using Anypoint Platform Private Cloud Edition or Anypoint Platform for Pivotal Cloud Foundry?

  • A. When regulatory requirements mandate on-premises processing of EVERY data item, including meta-data
  • B. When it Is required to make ALL applications highly available across multiple data centers
  • C. When it is required that ALL APIs are private and NOT exposed to the public cloud
  • D. When ALL backend systems in the application network are deployed in the organization's intranet

Answer: A

Explanation:
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.

 

NEW QUESTION 25
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 ensure ALL data is encrypted both in transit and at rest
  • B. They must avoid using the Object Store as it depends on services deployed ONLY to the US East region
  • C. They must te deployed to Anypoint Platform runtime planes that are managed by Anypoint Platform control planes, with both planes in the same Jurisdiction
  • D. They must use a Jurisdiction-local external messaging system such as Active MQ rather than Anypoint MQ

Answer: C

Explanation:
They must be deployed to Anypoint Platform runtime planes that are managed by Anypoint Platform control planes, with both planes in the same Jurisdiction.
*****************************************
>> As per legal regulations, all data processing to be performed within a certain jurisdiction. Meaning, the data in USA should reside within USA and should not go out. Same way, the data in EU should reside within EU and should not go out.
>> So, just encrypting the data in transit and at rest does not help to be compliant with the rules. We need to make sure that data does not go out too.
>> The data that we are talking here is not just about the messages that are published to Anypoint MQ. It includes the apps running, transaction states, application logs, events, metric info and any other metadata. So, just replacing Anypoint MQ with a locally hosted ActiveMQ does NOT help.
>> The data that we are talking here is not just about the key/value pairs that are stored in Object Store. It includes the messages published, apps running, transaction states, application logs, events, metric info and any other metadata. So, just avoiding using Object Store does NOT help.
>> The only option left and also the right option in the given choices is to deploy application on runtime and control planes that are both within the jurisdiction.

 

NEW QUESTION 26
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?

  • A. Permanently increase the size of each of the two (2) CloudHub workers by at least four times (4x) to one (1) vCore
  • B. Permanently increase the number of CloudHub workers by four times (4x) to eight (8) CloudHub workers
  • C. Use a horizontal CloudHub autoscaling policy that triggers on CPU utilization greater than 70%
  • D. Use a vertical CloudHub autoscaling policy that triggers on CPU utilization greater than 70%

Answer: C

Explanation:
Use a horizontal CloudHub autoscaling policy that triggers on CPU utilization greater than
70%
*****************************************
The scenario in the question is very clearly stating that the usual traffic in the year is pretty well handled by the existing worker configuration with CPU running well below 70%. The problem occurs only "sometimes" occasionally when there is spike in the number of orders coming in.
So, based on above, We neither need to permanently increase the size of each worker nor need to permanently increase the number of workers. This is unnecessary as other than those "occasional" times the resources are idle and wasted.
We have two options left now. Either to use horizontal Cloudhub autoscaling policy to automatically increase the number of workers or to use vertical Cloudhub autoscaling policy to automatically increase the vCore size of each worker.
Here, we need to take two things into consideration:
1. CPU
2. Order Submission Rate to JMS Queue
>> From CPU perspective, both the options (horizontal and vertical scaling) solves the issue. Both helps to bring down the usage below 90%.
>> However, If we go with Vertical Scaling, then from Order Submission Rate perspective, as the application is still being load balanced with two workers only, there may not be much improvement in the incoming request processing rate and order submission rate to JMS queue. The throughput would be same as before.
Only CPU utilization comes down.
>> But, if we go with Horizontal Scaling, it will spawn new workers and adds extra hand to increase the throughput as more workers are being load balanced now. This way we can address both CPU and Order Submission rate.
Hence, Horizontal CloudHub Autoscaling policy is the right and best answer.

 

NEW QUESTION 27
A Mule application exposes an HTTPS endpoint and is deployed to the CloudHub Shared Worker Cloud. All traffic to that Mule application must stay inside the AWS VPC.
To what TCP port do API invocations to that Mule application need to be sent?

  • A. 0
  • B. 1
  • C. 2
  • D. 3

Answer: B

Explanation:
8082
*****************************************
>> 8091 and 8092 ports are to be used when keeping your HTTP and HTTPS app private to the LOCAL VPC respectively.
>> Above TWO ports are not for Shared AWS VPC/ Shared Worker Cloud.
>> 8081 is to be used when exposing your HTTP endpoint app to the internet through Shared LB
>> 8082 is to be used when exposing your HTTPS endpoint app to the internet through Shared LB So, API invocations should be sent to port 8082 when calling this HTTPS based app.
References:
https://docs.mulesoft.com/runtime-manager/cloudhub-networking-guide
https://help.mulesoft.com/s/article/Configure-Cloudhub-Application-to-Send-a-HTTPS-Request-Directly-to-Ano
https://help.mulesoft.com/s/question/0D52T00004mXXULSA4/multiple-http-listerners-on-cloudhub-one-with-p

 

NEW QUESTION 28
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 A
  • B. Option D
  • C. Option C
  • D. Option B

Answer: D

Explanation:
Allow System APIs to return data that is NOT currently required by the identified Process or Experience APIs.
*****************************************
>> All customizations for the end-user application should be handled in "Experience API" only. Not in Process API
>> We should use tiered approach but NOT always by creating exactly one API for each of the 3 layers.
Experience APIs might be one but Process APIs and System APIs are often more than one. System APIs for sure will be more than one all the time as they are the smallest modular APIs built in front of end systems.
>> Process APIs can call System APIs as well as other Process APIs. There is no such anti-design pattern in API-Led connectivity saying Process APIs should not call other Process APIs.
So, the right answer in the given set of options that makes sense as per API-Led connectivity principles is to allow System APIs to return data that is NOT currently required by the identified Process or Experience APIs.
This way, some future Process APIs can make use of that data from System APIs and we need NOT touch the System layer APIs again and again.

 

NEW QUESTION 29
A company has started to create an application network and is now planning to implement a Center for Enablement (C4E) organizational model. What key factor would lead the company to decide upon a federated rather than a centralized C4E?

  • A. When there are a large number of existing common assets shared by development teams
  • B. When various teams responsible for creating APIs are new to integration and hence need extensive training
  • C. When development is already organized into several independent initiatives or groups
  • D. When the majority of the applications in the application network are cloud based

Answer: C

Explanation:
When development is already organized into several independent initiatives or groups
*****************************************
>> It would require lot of process effort in an organization to have a single C4E team coordinating with multiple already organized development teams which are into several independent initiatives. A single C4E works well with different teams having at least a common initiative. So, in this scenario, federated C4E works well instead of centralized C4E.

 

NEW QUESTION 30
Due to a limitation in the backend system, a system API can only handle up to 500 requests per second. What is the best type of API policy to apply to the system API to avoid overloading the backend system?

  • A. Rate limiting - SLA based
  • B. Rate limiting
  • C. HTTP caching
  • D. Spike control

Answer: D

Explanation:
Spike control
*****************************************
>> First things first, HTTP Caching policy is for purposes different than avoiding the backend system from overloading. So this is OUT.
>> Rate Limiting and Throttling/ Spike Control policies are designed to limit API access, but have different intentions.
>> Rate limiting protects an API by applying a hard limit on its access.
>> Throttling/ Spike Control shapes API access by smoothing spikes in traffic.
That is why, Spike Control is the right option.

 

NEW QUESTION 31
An organization makes a strategic decision to move towards an IT operating model that emphasizes consumption of reusable IT assets using modern APIs (as defined by MuleSoft).
What best describes each modern API in relation to this new IT operating model?

  • A. Each modern API must be REST and HTTP based
  • B. Each modern API must be easy to consume, so should avoid complex authentication mechanisms such as SAML or JWT D
  • C. Each modern API has its own software development lifecycle, which reduces the need for documentation and automation
  • D. Each modem API must be treated like a product and designed for a particular target audience (for instance, mobile app developers)

Answer: D

Explanation:
Explanation
Correct Answers:
1. Each modern API must be treated like a product and designed for a particular target audience (for instance mobile app developers)
*****************************************

Bottom of Form
Top of Form

 

NEW QUESTION 32
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 APIs public portal.
The API endpoint does NOT change in the new version. How should the developer of an API client respond to this change?

  • A. The API producer should be requested to run the old version in parallel with the new one
  • B. The API clients need to update the code on their side and need to do full regression
  • C. The API client code only needs to be changed if it needs to take advantage of the new features
  • D. The API producer should be contacted to understand the change to existing functionality

Answer: C

 

NEW QUESTION 33
Select the correct Owner-Layer combinations from below options

  • A. 1. App Developers owns and focuses on Experience Layer APIs
    2. LOB IT owns and focuses on Process Layer APIs
    3. Central IT owns and focuses on System Layer APIs
  • B. 1. App Developers owns and focuses on Experience Layer APIs
    2. Central IT owns and focuses on Process Layer APIs
    3. LOB IT owns and focuses on System Layer APIs
  • C. 1. Central IT owns and focuses on Experience Layer APIs
    2. LOB IT owns and focuses on Process Layer APIs
    3. App Developers owns and focuses on System Layer APIs

Answer: A

Explanation:
1. App Developers owns and focuses on Experience Layer APIs
2. LOB IT owns and focuses on Process Layer APIs
3. Central IT owns and focuses on System Layer APIs

References:
https://blogs.mulesoft.com/biz/api/experience-api-ownership/
https://blogs.mulesoft.com/biz/api/process-api-ownership/
https://blogs.mulesoft.com/biz/api/system-api-ownership/

 

NEW QUESTION 34
What is true about where an API policy is defined in Anypoint Platform and how it is then applied to API instances?

  • A. The API policy Is defined in API Manager and then automatically applied to ALL API instances
  • B. The API policy Is defined In API Manager for a specific API Instance, and then ONLY applied to the specific API instance
  • C. 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
  • D. The API policy is defined in API Manager, and then applied to ALL API instances in the specified environment

Answer: B

Explanation:
The API policy is defined in API Manager for a specific API instance, and then ONLY applied to the specific API instance.
*****************************************
>> Once our API specifications are ready and published to Exchange, we need to visit API Manager and register an API instance for each API.
>> API Manager is the place where management of API aspects takes place like addressing NFRs by enforcing policies on them.
>> We can create multiple instances for a same API and manage them differently for different purposes.
>> One instance can have a set of API policies applied and another instance of same API can have different set of policies applied for some other purpose.
>> These APIs and their instances are defined PER environment basis. So, one need to manage them seperately in each environment.
>> We can ensure that same configuration of API instances (SLAs, Policies etc..) gets promoted when promoting to higher environments using platform feature. But this is optional only. Still one can change them per environment basis if they have to.
>> Runtime Manager is the place to manage API Implementations and their Mule Runtimes but NOT APIs itself. Though API policies gets executed in Mule Runtimes, We CANNOT enforce API policies in Runtime Manager. We would need to do that via API Manager only for a cherry picked instance in an environment.
So, based on these facts, right statement in the given choices is - "The API policy is defined in API Manager for a specific API instance, and then ONLY applied to the specific API instance".

 

NEW QUESTION 35
......

Free MCPA-Level-1-Maintenance pdf Files With Updated and Accurate Dumps Training: https://certmagic.surepassexams.com/MCPA-Level-1-Maintenance-exam-bootcamp.html