[Sep-2022] MuleSoft MCIA-Level-1 Exam Practice Test Questions - ITPassLeader
Updated Certification Exam MCIA-Level-1 Dumps - Practice Test Questions
For more info read reference:
Topics of MuleSoft mcia - Level 1: MuleSoft Certified Integration Architect - Level 1 Exam
Candidates must know the exam topics before they start preparation because it will help them in hitting the core. Our mcia-level-1 practice exams will include the topics discussed in detail:
Configuring Anypoint Platform
- Configure business groups, roles, and permissions within an Anypoint Platform organization.
- Select monitoring options for all available Anypoint Platform deployment options.
- Suggest the number of Mule runtimes needed for a Mule application given performance targets and HA requirements.
- Define a performant and HA deployment architecture for Mule applications in on-prem deployments.
- Identify common and distinguishing features and usage scenarios for CloudHub VPCs and public worker cloud.
Selection Integration Styles
- When designing an integration solution, select the most appropriate interface/data technology and interface definition language for all integration interfaces.
- Given a description of an integration problem, identify the most appropriate integration style.
- Recognize scenarios where message correlation is necessary.
- Design parts of an integration solution using general message-based integration or event-driven architecture (EDA) using message brokers or streaming technologies.
Operating and Monitoring Integration Solutions
- Identify ways of transmitting IDs between components in remote interactions and capture this in the interface design of the remote interaction.
- Specify the type of metrics for API invocations and API implementations that can be monitored with Anypoint Platform.
- Identify metrics and operations exposed by default via JMX.
- Identify differences in monitoring and alerting between customer-hosted and MuleSoft-hosted Anypoint Platform.
DevOps
- Specify testing strategies that use both mocking and invoking of external dependencies.
- Specify the purpose of various MuleSoft products in DevOps and CI/CD.
- Identify differences, advantages, and disadvantages of DevOps based on deployable Mule applications versus container images.
- Formulate an effective source code management strategy including branching and merging.
Handling Events
- Use Mule 4 constructs to make effective use of Enterprise Integration Patterns.
- Use the streaming to handle large payloads within Mule applications.
- Predict the runtime behavior of messages queued internally for processing for load balancing or to achieve reliability.
Designing Applications
- Specify when a Mule application would require persistence and select an appropriate persistence solution.
- Specify the requirements that would require the use of domain-level connectors.
- For a given Mule 4 connector (Premium, Select, and MuleSoft Certified), identify its purpose, the network protocol it uses, and whether it supports incoming or outgoing types of connections.
- Identify possible failures when a component (such as an API client) invokes a remote component (such as an API implementation).
Designing Networks
- When incoming and outgoing HTTPS connections with mutual authentication are used, identify what certificates are needed in what stores in a different environment.
- For a given connector, recognize whether it will typically connect to/from an external -system across organizational boundaries.
- Use transport protocols and connectors correctly and coherently when and where applicable.
- Match protocols with networking constraints and API layers.
MuleSoft mcia - Level 1: MuleSoft Certified Integration Architect - Level 1 Certification Path
MuleSoft mcia - Level 1: MuleSoft Certified Integration Architect - Level 1 exam is foundation level Certification. As such, there is no prerequisite for this course. Anyone who is having a keen interest and familiar with MuleSoft technology is well invited to pursue this certification.
NEW QUESTION 60
A company wants its users to log in to Anypoint Platform using the company's own internal user credentials. To achieve this, the company needs to integrate an external identity provider (IdP) with the company's Anypoint Platform master organization, but SAML 2.0 CANNOT be used. Besides SAML 2.0, what single-sign-on standard can the company use to integrate the IdP with their Anypoint Platform master organization?
- A. Basic Authentication
- B. OAuth 2.0
- C. OpenID Connect
- D. SAML 1.0
Answer: C
Explanation:
As the Anypoint Platform organization administrator, you can configure identity management in Anypoint Platform to set up users for single sign-on (SSO).
Configure identity management using one of the following single sign-on standards:
1) OpenID Connect: End user identity verification by an authorization server including SSO
2) SAML 2.0: Web-based authorization including cross-domain SSO
NEW QUESTION 61
When designing an upstream API and its implementation, the development team has been advised to not set timeouts when invoking downstream API. Because the downstream API has no SLA that can be relied upon. This is the only donwstream API dependency of that upstream API. Assume the downstream API runs uninterrupted without crashing. What is the impact of this advice?
- A. A load-dependent timeout of less than 1000 ms will be applied by the Mule runtime in which the downstream API implementation executes.
- B. A default timeout of 500 ms will automatically be applied by the Mule runtime in which the upstream API implementation executes.
- C. An SLA for the upstream API CANNOT be provided.
- D. The invocation of the downstream API will run to completion without timing out.
Answer: C
Explanation:
An SLA for the upstream API CANNOT be provided.
NEW QUESTION 62
Refer to the exhibit. An organization is designing a Mule application to receive data from one external business partner. The two companies currently have no shared IT infrastructure and do not want to establish one. Instead, all communication should be over the public internet (with no VPN).
What Anypoint Connector can be used in the organization's Mule application to securely receive data from this external business partner?
- A. File connector
- B. SFTP connector
- C. VM connector
- D. Object Store connector
Answer: B
NEW QUESTION 63
A new Mule application under development must implement extensive data transformation logic. Some of the data transformation functionality is already available as external transformation services that are mature and widely used across the organization; the rest is highly specific to the new Mule application.
The organization follows a rigorous testing approach, where every service and application must be extensively acceptance tested before it is allowed to go into production.
What is the best way to implement the data transformation logic for this new Mule application while minimizing the overall testing effort?
- A. Implement transformation logic in the new Mule application using DataWeave, replicating the transformation logic of existing transformation services
- B. Extend the existing transformation services with new transformation logic and invoke them from the new Mule application
- C. Implement and expose all transformation logic as microservices using DataWeave, so it can be reused by any application component that needs it, including the new Mule application
- D. Implement transformation logic in the new Mule application using DataWeave, invoking existing transformation services when possible
Answer: B
NEW QUESTION 64
What metrics about API invocations are available for visualization in custom charts using Anypoint Analytics?
- A. Request size, number of requests, JDBC Select operation response time
- B. Request size, number of requests, JDBC Select operation result set size
- C. Request size, number of requests, response size, response time
- D. Request size, request HTTP verbs, response time
Answer: C
Explanation:
Explanation/Reference: https://docs.mulesoft.com/monitoring/api-analytics-dashboard
NEW QUESTION 65
Refer to the exhibit.
This Mule application is deployed to multiple Cloudhub workers with persistent queue enabled. The retrievefile flow event source reads a CSV file from a remote SFTP server and then publishes each record in the CSV file to a VM queue. The processCustomerRecords flow's VM Listner receives messages from the same VM queue and then processes each message separately.
How are messages routed to the cloudhub workers as messages are received by the VM Listener?
- A. Each message is duplicated to ALL of the Cloudhub workers, thereby SHARING EACH message with ALL the Cloudhub workers.
- B. Each messages routes to ONE of the available Clouhub workers in a NON- DETERMINSTIC non round-robin fashion thereby APPROXIMATELY BALANCING messages among the cloudhub workers
- C. Each message is routed to ONE of the Cloudhub workers in a DETERMINSTIC round robin fashion thereby EXACTLY BALANCING messages among the cloudhub workers
- D. Each message is routed to the SAME Cloudhub worker that retrieved the file, thereby BINDING ALL messages to ONLY that ONE Cloudhub worker
Answer: B
NEW QUESTION 66
Refer to the exhibit.
One of the backend systems invoked by an API implementation enforces rate limits on the number of requests a particular client can make. Both the backend system and the API implementation are deployed to several non-production environments in addition to production.
Rate limiting of the backend system applies to all non-production environments. The production environment, however, does NOT have any rate limiting.
What is the most effective approach to conduct performance tests of the API implementation in astaging (non-production) environment?
- A. Create a mocking service that replicates the backend system's production performance characteristics.Then configure the API implementation to use the mocking service and conduct the performance tests
- B. Include logic within the API implementation that bypasses invocations of the backend system in a performance test situation.Instead invoking local stubs that replicate typical backend system responses then conduct performance tests using this API Implementation
- C. Conduct scaled-down performance tests in the staging environment againstthe rate limited backend system then upscale performance results to full production scale
- D. Use MUnit to simulate standard responses from the backend system then conduct performance tests to identify other bottlenecks in the system
Answer: C
NEW QUESTION 67
A Mule application is being designed to do the following:
Step 1: Read a SalesOrder message from a JMS queue, where each SalesOrder consists of a header and a list of SalesOrderLineltems.
Step 2: Insert the SalesOrder header and each SalesOrderLineItem into different tables in an RDBMS.
Step 3: Insert the SalesOrder header and the sum of the prices of all its SalesOrderLineltems into a table in a different RDBMS.
No SalesOrder message can be lost and the consistency of all SalesOrder-related information in both RDBMSs must be ensured at all times.
What design choice (including choice of transactions) and order of steps addresses these requirements?
- A. 1. Read the JMS message (NOT in an XA transaction)
2. Perform EACH DB insert in a SEPARATE DB transaction
3. Acknowledge the JMS message - B. 1. Read and acknowledge the JMS message (NOT in an XA transaction)
2. In a NEW XA transaction, perform BOTH DB inserts - C. 1. Read the JMS message in an XA transaction
2. In the SAME XA transaction, perform BOTH DB inserts but do NOT acknowledge the JMS message - D. 1. Read the JMS message (NOT in an XA transaction)
2. Perform BOTH DB inserts in ONE DB transaction
3. Acknowledge the JMS message
Answer: C
Explanation:
Explanation
NEW QUESTION 68
A Mule application currently writes to two separate SQL Server database instances across the internet using a single XA transaction. It is proposed to split this one transaction into two separate non-XA transactions with no other changes to the Mule application.
What non-functional requirement can be expected to be negatively affected when implementing this change?
- A. Throughput
- B. Response time
- C. Availability
- D. Consistency
Answer: D
NEW QUESTION 69
An API client is implemented as a Mule application that includes an HTTP Request operation using a default configuration. The HTTP Request operation invokes an external API that follows standard HTTP status code conventions, which causes the HTTP Request operation to return a 4xx status code.
What is a possible cause of this status code response?
- A. The HTTP response cannot be interpreted by the HTTP Request operation of the Mule application after it was received from the external API
- B. An error occurred inside the external API implementation when processing the HTTP request that was received from the outbound HTTP Request operation of the Mule application
- C. The external API reported an error with the HTTP request that was received from the outbound HTTP Request operation of the Mule application
- D. The external API reported that the API implementation has moved to a different external endpoint
Answer: C
NEW QUESTION 70
An integration Mule application is being designed to synchronize customer data between two systems. One system is an IBM Mainframe and the other system is a Salesforce Marketing Cloud (CRM) instance. Both systems have been deployed in their typical configurations, and are to be invoked using the native protocols provided by Salesforce and IBM.
What interface technologies are the most straightforward and appropriate to use in this Mule application to interact with these systems, assuming that Anypoint Connectors exist that implement these interface technologies?
- A. IBM: REST
CRM: REST - B. IBM: DB access
CRM: gRPC - C. IBM: ActiveMQ
CRM: REST - D. IBM: CICS
CRM: SOAP
Answer: C
NEW QUESTION 71
An organization uses a four(4) node customer hosted Mule runtime cluster to host one(1) stateless api implementation. The API is accessed over HTTPS through a load balancer that uses round-robin for load distribution. Each node in the cluster has been sized to be able to accept four(4) times the current number of requests.
Two(2) nodes in the cluster experience a power outage and are no longer available. The load balancer directs the outage and blocks the two unavailable the nodes from receiving further HTTP requests.
What performance-related consequence is guaranteed to happen to average, assuming the remaining cluster nodes are fully operational?
- A. 50% reduction in the throughput of the API
- B. 100% increase in the average response time of the API
- C. 50% increase in the JVM heap memory consumed by each remaining node
- D. 100% increase in the number of requests received by each remaining node
Answer: D
Explanation:
* "100% increase in the throughput of the API" might look correct, as the number of requests processed per second might increase, but is it guaranteed to increase by 100%? Using 4 nodes will definitely increase throughput of system. But it is cant be precisely said if there would be 100% increase in throughput as it depends on many other factors. Also it is nowhere mentioned in the description that all nodes have same CPU/memory assigned. The question is about the guaranteed behavior * Increasing number of nodes will have no impact on response time as we are scaling application horizontally and not vertically. Similarly there is no change in JVM heap memory usage. * So Correct answer is 50% reduction in the number of requests being received by each node This is because of the two reasons. 1) API is mentioned as stateless 2) Load Balancer is used
NEW QUESTION 72
An organization currently uses a multi-node Mule runtime deployment model within their datacenter, so each Mule runtime hosts several Mule applications. The organization is planning to transition to a deployment model based on Docker containers in a Kubernetes cluster. The organization has already created a standard Docker image containing a Mule runtime and all required dependencies (including a JVM), but excluding the Mule application itself.
What is an expected outcome of this transition to container-based Mule application deployments?
- A. Required change to the URL endpoints used by clients to send requests to the Mule applications
- B. Required redesign of Mule applications to follow microservice architecture principles
- C. Guaranteed consistency of execution environments across all deployments of a Mule application
- D. Required migration to the Docker and Kubernetes-based Anypoint Platform - Private Cloud Edition
Answer: B
Explanation:
* Organization can continue using existing load balancer even if backend application changes are there. So option A is ruled out.
* As Mule runtime is within their datacenter, this model is RTF and not PCE. So option C is ruled out.
Mule runtime deployment model within their datacenter, so each Mule runtime hosts several Mule applications -- This mean PCE or Hybird not RTF - Also mentioned in Question is that - Mule runtime is hosting several Mule Application, so that also rules out RTF and as for hosting multiple Application it will have Domain project which need redesign to make it microservice architecture
--------------------------------------------------------------------------------------------------------------- Correct answer: Required redesign of Mule applications to follow microservice
NEW QUESTION 73
The AnyAirline organization's passenger reservations center is designing an integration solution that combines invocations of three different System APIs (bookFlight, bookHotel, and bookCar) in a business transaction. Each System API makes calls to a single database.
The entire business transaction must be rolled back when at least one of the APIs fails.
What is the most idiomatic (used for its intended purpose) way to integrate these APIs in near real-time that provides the best balance of consistency, performance, and reliability?
- A. Implement local transactions within each API implementation
Configure each API implementation to also participate in the same eXtended Architecture (XA) transaction Implement caching in each API implementation to improve performance - B. Implement local transactions in each API implementation
Coordinate between the API implementations using a Saga pattern
Apply various compensating actions depending on where a failure occurs - C. Implement eXtended Architecture (XA) transactions between the API implementations Coordinate between the API implementations using a Saga pattern Implement caching in each API implementation to improve performance
- D. Implement an eXtended Architecture (XA) transaction manager in a Mule application using a Saga pattern Connect each API implementation with the Mule application using XA transactions Apply various compensating actions depending on where a failure occurs
Answer: B
NEW QUESTION 74
What requires configuration of both a key store and a trust store for an HTTP Listener?
- A. Encryption of requests to both subdomains and API resource endpoints fhttPs://aDi.customer.com/ and https://customer.com/api)
- B. Encryption of both HTTP request and HTTP response bodies for all HTTP clients
- C. Support for TLS mutual (two-way) authentication with HTTP clients
- D. Encryption of both HTTP request header and HTTP request body for all HTTP clients
Answer: C
Explanation:
1 way SSL : The server presents its certificate to the client and the client adds it to its list of trusted certificate. And so, the client can talk to the server.
2-way SSL: The same principle but both ways. i.e. both the client and the server has to establish trust between themselves using a trusted certificate. In this way of a digital handshake, the server needs to present a certificate to authenticate itself to client and client has to present its certificate to server.
* TLS is a cryptographic protocol that provides communications security for your Mule app.
* TLS offers many different ways of exchanging keys for authentication, encrypting data, and guaranteeing message integrity Keystores and Truststores Truststore and keystore contents differ depending on whether they are used for clients or servers:
For servers: the truststore contains certificates of the trusted clients, the keystore contains the private and public key of the server. For clients: the truststore contains certificates of the trusted servers, the keystore contains the private and public key of the client.
Adding both a keystore and a truststore to the configuration implements two-way TLS authentication also known as mutual authentication.
* in this case, correct answer is Support for TLS mutual (two-way) authentication with HTTP clients.
NEW QUESTION 75
Refer to the exhibit.
A shopping cart checkout process consists of a web store backend sending a sequence of API invocations to an Experience API, which in turn invokes a Process API. All API invocations are over HTTPS POST. The Java web store backend executes in a Java EE application server, while all API implementations are Mule applications executing in a customer -hosted Mule runtime.
End-to-end correlation of all HTTP requests and responses belonging to each individual checkout Instance is required. This is to be done through a common correlation ID, so that all log entries written by the web store backend, Experience API implementation, and Process API implementation include the same correlation ID for all requests and responses belonging to the same checkout instance.
What is the most efficient way (using the least amount of custom coding or configuration) for the web store backend and the implementations of the Experience API and Process API to participate in end-to-end correlation of the API invocations for each checkout instance?
A)
The web store backend, being a Java EE application, automatically makes use of the thread-local correlation ID generated by the Java EE application server and automatically transmits that to the Experience API using HTTP-standard headers No special code or configuration is included in the web store backend, Experience API, and Process API implementations to generate and manage the correlation ID
B)
The web store backend generates a new correlation ID value at the start of checkout and sets it on the X-CORRELATlON-lt HTTP request header In each API invocation belonging to that checkout No special code or configuration is included in the Experience API and Process API implementations to generate and manage the correlation ID
C)
The Experience API implementation generates a correlation ID for each incoming HTTP request and passes it to the web store backend in the HTTP response, which includes it in all subsequent API invocations to the Experience API.
The Experience API implementation must be coded to also propagate the correlation ID to the Process API in a suitable HTTP request header
D)
The web store backend sends a correlation ID value in the HTTP request body In the way required by the Experience API The Experience API and Process API implementations must be coded to receive the custom correlation ID In the HTTP requests and propagate It in suitable HTTP request headers
- A. Option B
- B. Option D
- C. Option A
- D. Option C
Answer: A
NEW QUESTION 76
An integration Mute application is being designed to process orders by submitting them to a backend system for offline processing. Each order will be received by the Mute application through an HTTPS POST and must be acknowledged immediately. Once acknowledged, the order will be submitted to a backend system. Orders that cannot be successfully submitted due to rejections from the backend system will need to be processed manually (outside the backend system).
The Mule application will be deployed to a customer-hosted runtime and is able to use an existing ActiveMQ broker if needed.
The backend system has a track record of unreliability both due to minor network connectivity issues and longer outages.
What idiomatic (used for their intended purposes) combination of Mule application components and ActiveMQ queues are required to ensure automatic submission of orders to the backend system, while minimizing manual order processing?
- A. Until Successful component ActiveMQ long retry Queue ActiveMQ Dead Letter Queue for manual processing
- B. An On Error scope MuleSoft Object Store ActiveMQ Dead Letter Queue for manual processing
- C. An On Error scope Non-persistent VM ActiveMQ Dead Letter Queue for manual processing
- D. Until Successful component MuleSoft Object Store ActiveMQ is NOT needed or used
Answer: A
NEW QUESTION 77
Additional nodes are being added to an existing customer-hosted Mule runtime cluster to improve performance. Mule applications deployed to this cluster are invoked by API clients through a load balancer.
What is also required to carry out this change?
- A. A new load balancer must be provisioned to allow traffic to the new nodes in a round-robin fashion
- B. New firewall rules must be configured to accommodate communication between API clients and the new nodes
- C. API implementations using an object store must be adjusted to recognize the new nodes and persist to them
- D. External monitoring tools or log aggregators must be configured to recognize the new nodes
Answer: C
Explanation:
Explanation/Reference: https://www.folkstalk.com/2019/11/mulesoft-integration-and-platform.html
NEW QUESTION 78
A set of integration Mule applications, some of which expose APIs, are being created to enable a new business process. Various stakeholders may be impacted by this. These stakeholders are a combination of semi-technical users (who understand basic integration terminology and concepts such as JSON and XML) and technically skilled potential consumers of the Mule applications and APIs.
What Is an effective way for the project team responsible for the Mule applications and APIs being built to communicate with these stakeholders using Anypoint Platform and its supplied toolset?
- A. Capture documentation about the Mule applications and APIs inline within the Mule integration flows and use Anypoint Studio's Export Documentation feature to provide an HTML version of this documentation to the stakeholders
- B. Use Anypoint Exchange to register the various Mule applications and APIs and share the RAML definitions with the stakeholders, so they can be discovered
- C. Create Anypoint Exchange entries with pages elaborating the integration design, including API notebooks (where applicable) to help the stakeholders understand and interact with the Mule applications and APIs at various levels of technical depth
- D. Use Anypoint Design Center to implement the Mule applications and APIs and give the various stakeholders access to these Design Center projects, so they can collaborate and provide feedback
Answer: C
Explanation:
As the stakeholders are semitechnical users , preferred option is Create Anypoint Exchange entries with pages elaborating the integration design, including API notebooks (where applicable) to help the stakeholders understand and interact with the Mule applications and APIs at various levels of technical depth
NEW QUESTION 79
......
Updated Verified MCIA-Level-1 dumps Q&As - Pass Guarantee or Full Refund: https://troytec.itpassleader.com/MuleSoft/MCIA-Level-1-dumps-pass-exam.html