Pass Your Mulesoft MCPA - Level 1 Exam Easy!

Mulesoft MCPA - Level 1 MuleSoft Certified Platform Architect - Level 1 exam dumps vce, practice test questions, study guide & video training course to study and pass quickly and easily. Mulesoft MCPA - Level 1 MuleSoft Certified Platform Architect - Level 1 exam dumps & practice test questions and answers. You need avanset vce exam simulator in order to study the Mulesoft MCPA - Level 1 certification exam dumps & Mulesoft MCPA - Level 1 practice test questions in vce format.

Foundations

1. C4E

Hi, welcome to the new section in this course. In this section, we will learn about the foundations or pillars of an ABA project and the platform. You have learned a lot of important basics or concepts so far, which are actually required to proceed forward. So, now that you understand the APA terminology, its operating model, and various platform capabilities, let us move on and understand the foundations of an APA project on the platform. So far, what we have seen is the It alignment, which is very important for the new It operating model, where it has central It teams and app developers. So we've talked about how Central it contributes, Lob it teams contribute, and the app develops, contributes, and maps them all as part of the three-layered architecture. But the main one more foundation that the newoperating model recommends is to have a C FourE team which is centre for Enablement. So, what is this team? What is the C? Four E team So, a C4A team is similar to Steam in that it serves as a link between the other teams, which are the central It Lobit and the App Developer Teams. So they act as a bridge, and what does the enablewhy centre for enablement do? What does the TD team enable? So, while lob It teams, central Itteams and developer teams are busy withtheir own focus and ownership areas. Remember, we discussed about the ownershipof each of these teams, right? So they'll be busy with their own work. Then someone has to take responsibility for the other parameters we discussed for the operational model, which emphasises consumption, then governance, then making sure the assets are reusable, and all.So, if we leave the responsibility to the individual teams, then there will be a shared responsibility among them. And I'm sure you all know what happens when there is a shared responsibility. It looks good, but in reality, because they have other ownership and focus areas, they'll always be ignoring this part and thinking, "Okay, they have delivered what they have to do, and they will do minimal about the shared responsibility part." So, this is where C for E comes in. C for E enables these other criteria, which are also important for the effect of its operating model and its deliveries: enforcing the emphasising of consumption, enforcing reusability, governance of the APIs, monitoring, management, et cetera. So, C-4 is the focus, and the ownership area is this particular part. So they act as bridges between all these three parts. So let us discuss in detail what the responsibilities of the C-four-A team are. C four A team ensures that the APIled connectivity is going very well or not. So they are the responsible team who has to make sure that, OK, the API connectivity principles are being implemented correctly by these different ifferent teamsIt allocated and app developers teams, thenc four E also has to ensure thatthe assets are self service and consumed. So remember, we discussed this. The asset should be self-serviceable, which means that anyone can come in and discover and then find the API they want, self-service them, gain access, and begin using them. So whether the assets are in a self-service manner or not is something C-40 has to make sure of, and they also have to ensure that the assets are being properly reused or not. So it's not just aboutthe self service and discoverability. They also make sure that whether they are being reused or not, or if any duplicates are being created duplicate APIs or duplicate assets), So it's their responsibility to make sure they don't happen. And the last one is that they ensure there is increased integration delivery speed. So, what is the point in ensuring all the above things that we discussed? The main point is to make the delivery gap smaller, right? not reduce the IT delivery gap, which means there is increased integration delivery speed. That is why they have to make sure that all the points are met, they're self-serviceable, they are reused, and they are being built with proper Apple connectivity and all, so that there is a speed of delivery, right? So these are the responsibilities forimportant responsibilities of C four team. So who are the people who are part of the "C" for regeneration? So there are some key roles or designations in C for Edin; the main one will be the flat format, which you are going to be soon. Because if you're looking at this course and learning a lot of things, then I'm sure you're an aspiring platform marketer. So the platform manager is one of the key members in the C-suite who has knowledge of the platform functionality and the organization's alignment. And he or she is someone who understands the business's needs and wants and effectively establishes the foundations. Then the second one is an integration architect. An integration architect is someone who is very experienced in integrating various systems via different interfaces. It could be file-based Web services. Rest. So he's here—someone who is very experienced in integrating systems and implements various integration solutions. The third one is a DevOps engineer. DevOps engineer is self-explanatory; I need not explain. Everyone knows what DevOps teams do, right? So a DevOps engineer is someone who actually bridges between the dev and ops teams, builds different scripts, automates stuff, integrates test suites, and makes things auto deployable.All this stuff will be done by the DevOps engineers. So this is what a C is for a team at a high level. We will go into detail and discuss in various videos what everything C-F-E actually does and how it effectively aligns the entire organization. However, at a higher level, this is what a team captain does. I hope you understood "happy learning."

2. Deployment Options

Hi. The next important foundation is identifying various deployment scenarios in your project or organization. So, after deciding the IP alignment process and establishing theCFOR As a team, the next thing to focus on is to identify the deployment scenarios in your environment. So, in order to identify the scenarios as an architect, you should first know what models Mule Soft offers and, among those, what best fits you and your organization. So let's have a look at these offerings from MuleSoft. So, MuleSoft offers its components as two separate functionalities to separate their concerns, and all.So an easy tip to remember is how to distinguish a component, determine whether it falls under which functionality, and determine whether a component is directly involved in the execution of a new application or not. So let me give you an example. Say if someone asks you, "Okay, hey, any Point exchange falls under which category?" OK, then you need to just think, "Okay, is it directly involved in the execution of the Mule application?" No, right? Because nothing on the Any Point Exchange actually runs on a hosted execution environment. Right? So that is how we identify. So your next question would be: What are we identifying here? Okay, yes, I know it is not directly linked to the execution of your application. So now what? How do I know? So let me tell you. The two separate functionalities are the control plane and the runtime plane. Okay? So the control plane is a place where you control your entire platform. So the components that are inside the control plane or that belong to the control plane category or functionality will help you to control the platform. Whereas the components that are under the umbrella of "runtime" help you to actually run the stuff. It is straightforward, right? So you see what I mean when I say that you can tell which plane a component belongs to. So now again, let's say for the same example, someone asks you, "Hey, is there any PointExchange runtime plane or control plane?" So you know that now, oh, any point exchanged does not have to do anything with the runtime part; it does not have to do anything with the execution of your application. It's a published asset or itis for maintaining the assets. Examples: centipedes and all. Right? So this is part of the control plane. What if someone now asks you about the VPC or any point MQ? So then they are linked to the runtime execution because at any point in MQ, all the inflight messages will be published and subscribed. VPC is the virtual private cloud that is required for aligning your new runtimes, and all right, so that is the runtime plane, understood? times, and So if you remember, we had a look at one diagram during the demonstration of various components of the platform, I think two weeks ago. So there we see the segregated Mule components, right? So like any point management center, design center, runtime service, and all.So, to make it easy for you, what I have done is taken the same diagram and drawn a line between the components so that you can clearly know which section falls under the runtime plane and which all fall under the control plane. So if you see this diagram, the upper part falls under the control plane: the management center, design centre, exchange, and all, whereas the lower part, which is the runtime services VPC, fabric at any point IQ, and all, and connectors, are all under the runtime plane because they are linked to the execution of Mule applications, right? So now that we know there are two parts: runtime and control planes, let us see in how many ways this can be set up. So this is where, again, your role comes into the picture. In the early phase of the project, based on your customer's requirements, their current set-up, what they have on premises already, what they want to have in the cloud, or how they're licencing this, With these combinations, you have to assess and come up with a deployment scenario. So to come up with the best deployment scenario, you have to understand the next part, which is how a control plan can be set up and how a runtime plan can be set up. So in the next slide, let us see the high level, whatkind of control plan and runtime planes can be set up. Then we will have a look at each combination in detail in the coming videos. So the control plane is offered by MuleSoft and can be hosted in two ways. One is MuleSoft hosted, which means it's in the cloud offered by MuleSoft and ready to use. You have to subscribe and then start using it. There is also a customer-hosted control plane, which means you can have your own private cloud edition, your own cloud hosting like AWS, whatever, and you can host the control plane yourself, rather than having it managed by new software. There are two types like now on the runtimeplane side, again, there are two types of hosting,MuleSoft hosted one and the customer hosted one. However, you can have a different mix of combinations within these two MuleSoft hosted runtime planes; you can have a publiccloud one, which means your runtimes are shared among the public, other specific clients, and other tenants. And there is an AWS VPC implementation you can do with the museum hosted on timeplan with the help of the anypoint VPC. Okay, so it will be your own private cloud and private network within the museum-hosted runtime plane. And the second one categories are customer hosted. So even there, again, it can be two different ways. One is that you can completely host your mural runtimes on your own physical machines, physical blades, or your own VMs on the blades, like how typically old projects run, right? Or some of the Etude legacy systems runso you can install and maintain from scratch. And that is one option. The second option is if you do not want to take that much level down the level control and invest time in it. There is MuleSoft-provided software for customers hosted on time plans that is called Any Point Runtime Fabric. So what is the difference You may think, "Okay, anyway, it's customer-hosted. What's the difference if you install runtimes on your own on direct machines, servers, or VMs?" And what is this point in the timeframe? How does it help? Yes, let me explain. So the bare minimum wage for how the customer has to install is entirely the customer's responsibility. It depends on the knowledge their teams hold and how they know the best way to set up, and all these combinations come in, and it is very tedious, as you their teamHowever, the runtime fabric is useful because it comes with the cobernetes Kubernetes cluster and the Docker container concept. It doesn't come with the physical Kubernetes cluster or Docker container; it comes with the technology behind that. Okay? That is, the customer must still have their Kubernetes cluster and Docker containers set up and available. But runtime fabrics, once your view application is ready, can containerize your particular application to a Docker container and then host it on the node or make it part of the cooperative cluster so that each mule application is one node or a Docker container containing container technology. Fine. They all came from a covenant cluster. So you can relate it to something like a cloud hub. In cloud hub also, each of our applications runs as one Mule Cloud Hub application, which is like one image Docker container, and then you have many such applications running, right? And the workers are like a cluster of workers. Similarly here. Kubernetes Maintenance. So, rather than being one-to-one, the concept of a load hub is introduced into your customer-hosted environment via this one-time fabric. So these are different combinations, right? So now, like you said, in runtime planning there are four ways. Two mules are hosted by two customer-hosted vans, and there are two control plane options: mulesFT hosted and customer-hosted private cloud. Now, combined together, you can have something like six combinations to set up. Like one MuleSoft hosted, you can have amulesft hosted control plane with a runtime hostedMuleSoft plane and you can have MuleSoft hostedcontrol plane with a customer hosted runtime planeand you can have a customer hosted controlplane with the customer hosted runtime plane. So you have permissions combinations between these two, correct? So this is what we are going to look at in the next video. We will take each combination and see how the setupwould look at high level and whether it is thebest fit or not is something that as an architectyou can decide for your organisation alright happy learning.

3. Both MuleSoft-Hosted Control and Runtime Planes

Hi. In the next three videos, let us see and understand all six combinations of hosting control plane and runtime plane that we saw in the last video. In this video, we will see both the MuleSoft-hosted control plane and runtime plane. As we discussed earlier, on the runtimeplan side, there are two further variations in the museum-hosted setup. Also, one is the public cloud, and the second one is the virtual private cloud, which is the VPC. So let us see the public cloud setup first. As you are seeing in front of you, this is a high-level setup of the control plane and the runtime plan in the MuleSoft hosted cloud, which is completely maintained by MuleSoft. On the left, what you see are the control plane components, which are the API manager and the runtime manager. And you can see them connected to the runtime plane via dash notation. It's just a notation to say that OK, this is how they are connected to the runtime plane. And on the runtime plane, you see a very simple representation of an application running on a multi-user runtime with the two workers on the cloud hub. And because there are two workers, they are being load balanced by a cloud hub load balancer, and all the consumer services hit the load balancer, which is a load balancer URL, and that then divides the traffic to the individual worker nodes. So now what is it that you have to understand when we say this is a public cloud setup? So when we say public cloud setup, you have to understand that point number one: these applications, which are running on the Cloud Hub now in a public cloud setup, actually do not have any dedicated network range or anything for that particular customer, okay? They are shared; our applications are hosted in a shared environment on the CloudHub among different other tenants as well. So you cannot guarantee that, okay? I always get my apps running on this range of IP addresses or things like that, okay? like how you do on premises. On premise, you can make sure that these are your servers that can run on a particular network range, right? As a result, such control will not be available in the public cloud; they will be hosted, there will be activity, and consumers will be able to call and obtain the relevant functional behavior. But on the network topology side or on the control level, you have to be sharing with the other public tenants as well. Okay? And the second point is the Cloud Hub load balancer, right? So this load-balanced URL again will not be able to be controlled by the customer. The Cloud Hub will generate a load balancer for you. It will always generate a suitable one to ensure load balance. There is no functional difference except for the URL, or if you want to have a customer's DNS name and all on your load balancer URL because you may be sharing it with consumers over whom you have no control. You have to use whatever is generated by the club hub. Okay, so you might think, then, what is the use of this model? You're an architect, so, you know, there could be a number of reasons why you have to go with it. So if you think this fits your modelor in your closet for a specific scenario,okay, then you can go with this. But if it does not fit, then you can very well review the other five setups as well to see which one is the best fit. Now the second combination of the Mulesoft-hosted control plane and the runtime plane is the runtime side's Musaft-hosted VPC setup. Again, you are seeing a high-level representation of the setup where on the left side you see the API manager and runtime manager, which are control plane components, and they are communicating with the runtime plane on the right. The setup looks almost identical to the previous one, which was the public cloud one. But the difference is that you can see that squarebox notation saying it's a virtual private cloud, right? So this "virtual private cloud," which you might know very well what it is, is called the VPC and all.But if you do not, then the VPC is a dedicated network range allocated for you or for your But if you So, when you first set up the VPC with the help of a network expert or network architect, you will be deriving the IP ranges or network ranges using the CIDR notation and formulas. Then, if you know what IP range you want, you can create a VPC in the Mule Soft Cloud. So once you create your virtual private cloud thenlike on premise network range you will be havingyour dedicated network range even on the Mule softcloud which is backed up by AWS anyway. And in AWS also, there is a VPC concept on Azure; it is called VNet. So it's the same thing. The cloud providers support the backend, and newspapers refer to it as any point VPC on top of it. Okay? So now, on the development side, there is no change. Your day teams will develop the apps; they will be deployed, but they will be deployed to the Cloud Hub. Now, if you have your own VPC, then they will always be allocated with the IP addresses in the range of the IP range that you have in your VPC, okay? so that you have control. So for example, Now, you can confidently say from the control plane's APA manager that you want to whitelist the IP addresses from which IPS can call your Syslayer APIs or Process Layer APIs. Right then. Because now you know the IP range. You can put IP whitelisting policy on all of your systemlayer and Process layer API's saying if the IP incoming IPaddress is in the range of some 10 ing policy on aSlash this range. Right? Then load request rejected because you know thatso you can achieve such kind of thingsusing because of the private cloud. And the second point is the dedicated load balancer, like the name says. Now you can have your own dedicated load balancer with a particular DNS name or notation so that you can have your representation in the URL. You can share it with your consumers, right? So these are the Mulesoft House control panel combinations as well as the long-term use of hosted combinations. Now let's move on to the next video and see the other combinations. Happy learning.

4. MuleSoft-Hosted Control Plane and Customer-Hosted Runtime Planes

Hi. In this video we will see the mule soft hostedcontrol plane with the customer hosted runtime plane setup. Okay, as described earlier on the runtime plane site, there are further down two variations in the customer-hosted setup, one being the bear installation on top of the on-premises infrastructure, and the second being the use of the any-point fabric software provided by the mule software. Okay, let us look at the first one. the first setup. So again, it's a high-level representation. You can see the control plane, which is hosted in the cloud and contains the pay manager and retail manager, in front of you. Actually, there are many components, as you can see in the diagram in the last video. But just for a simple notation, the only API manager and runtime manager are represented on the control plane here, which is on the cloud. And on the right, what you see is the runtime plane in a local environment, which means it's a customer-hostile environment. Okay? So what you're seeing here is the complete on-premises managed customer managed setup. Customers must install their runtimes on their own physical blades, physical machines, or even virtual machines, and they must do the cluster setup and everything else on their own premises. And all networking components, such as load balancers—everything that is typical of large legacy projects. The projects which we were doing a decade back areimplemented same where the setup has to be cade back aYou might think that we have to go with this model because the entire world is moving toward clouds, but there can be a number of reasons. You might be a very high-profile bank customer or work for an organisation where they do not have anything on the cloud, okay? Maybe they have some secret operations—we do not know. So they want to maintain or they haveenough capacity or money or expertise to manageeverything on their local environment, okay? They already have all the resources they don't want to give away, right? So for any reason, that is when this setup would come into play. But it needs a lot of expertise not only on the infrastructure resources side but also on the mules side because even the mules' runtime maintenance and the on-premises issues must be dealt with by the proper mules of experts, okay? As a result, they can leverage only the control plane on the cloud side to manage entire environments even though the data resides on-premise systems, all enterprise systems that integrate reside on-premise systems, nothing is on the cloud, and only controls will go to the cloud. Okay? Now the next combination is again a cloud-based control plane, a museum-hosted control plane, and a customer-hosted runtime plane. But here the customer-hosted runtime plan is the second variant, which is not exactly the complete bare-bones scratch implementation of the new runtimes. Instead, the customer can continue to host his runtime on physical discs or on his own cloud hosting. Meaning when we say customer hosted, itdoes not always meet an on premise. It could be another cloud, such as AWS or Azure, okay? But customers are managing it here. It's the responsibility we are talking about, not the type of cloud or on-premises deployment. So the customer-hosted runtime plan means that the customer manages the runtime plane, but he can still choose an on-premises blade or AWS custom AWS hosting or Azure hosting any cloud he wants, right? So, when we say this, what we mean is that the customer can get this pass functionality by using, as we discussed in the previous video, any point runtime fabric, a software provided by MuleSoft. He can host the runtime management. The customer can host the runtime plane in an iPad-functional way, which is similar to the cloud hub. Remember how we explained how the cloud hub runs new applications, orchestrates, and creates worker clusters? Same way it can be done using the newpointfabric in the last video, the introduction video. So, same kind of iPad functionality canbe implemented by customer managed by customersusing this fabric software runtime fabric sothat the same product behaviour can come. But on Customer side he can manage either hecan host on or he can host on theAzure cloud platform or AWS cloud platform. like we described before. This setup will leverage this Kubernetes cluster by having Docker containers. All the runtimes and applications we develop will be converted into Dockerized containers, which will form a network of clusters using Kubernetes. And this can be hosted again, like on customer VMs or on AWS or Azure. Can customers host wherever they want and manage it okay? It's just functionality. So again, it depends how your customer or productrequirement is and you have to choose one ofthese setups which best fits for your your customeNow in the next video, let us see the last two combinations, which are both customer-hosted. Happy learning!

Go to testing centre with ease on our mind when you use Mulesoft MCPA - Level 1 vce exam dumps, practice test questions and answers. Mulesoft MCPA - Level 1 MuleSoft Certified Platform Architect - Level 1 certification practice test questions and answers, study guide, exam dumps and video training course in vce format to help you study with ease. Prepare with confidence and study using Mulesoft MCPA - Level 1 exam dumps & practice test questions and answers vce from ExamCollection.