The product has a controller which is hosted on the AWS cloud, and we have three cloud data centers. From the main controller, we can administer the customer's devices, QoS, network, and traffic. We can monitor it and we can change and create policies as well as upgrade the software. We can totally control a customer's network from one site, the Prisma SD-WAN portal. Prisma SD-WAN has a lot of advanced features, one of which is Zero Touch Provisioning. If you want to migrate to the cloud, or you want to migrate your office to a high-end router or an edge router, it is too difficult. It would require a lot of planning, a lot of implementation, and a lot of headaches and operational burdens. But with Prisma SD-WAN's Zero Touch Provisioning, we can collect the customer's infra and analyze it. According to that, we can prepare a diagram and implement high availability with two devices. That way, if one of the devices is down, the other will take an active role with the forwarded traffic. And whenever we are required to make any changes, we can make them to multiple devices at the same time. Suppose we want to change the IP address, or create a static cloud. We can create a template and can use it for multiple uses. If we want to upgrade software, in GitHub there is a lot of code uploaded by Prisma SD-WAN developers that we can download to schedule the upgrade onsite, and it will automatically upgrade the software and reboot the devices. If there is only a single device involved, traffic will definitely be cut off for some time, but if you have implemented high-availability, with two devices onsite, there is no traffic interruption during a software upgrade. It will be shifted to the second device while rebooting the first device. Other features include event, security, network, and path policies. Regarding path policies, suppose you have two internet circuits and you want one circuit to be the primary and the second circuit to be the backup. Using an SD circuit would be too costly in a normal situation. But whenever the primary circuit is down, since the office should definitely not have an outage, we have to ship the traffic to the SD circuit. In that scenario, we can create a path policy, so that whenever the primary circuit is down, this traffic will forward automatically to the other circuit. Also, suppose I have very critical business applications hosted on the cloud and I want to prioritize these applications. For example, if there are two people working with SAP while other people are just casually browsing the internet, using Facebook or Gmail. I want to give priority to the SAP customers. I can set this kind of priority with four levels of traffic or QoS, platinum, gold, silver, and bronze. I can put the SAP traffic in the platinum level and it will get more bandwidth and the application will perform fast. Its traffic is prioritized immediately, over the other levels. And if you have two internet circuits and you want to direct your SAP traffic to the fastest primary circuit and your Gmail and Facebook traffic to the secondary circuit, that is also possible with Prisma SD-WAN. In Prisma SD-WAN there are three modes: Control, Analytics, and Disabled. If you disable the site the site is completely down and inactive. If you are in Analytics mode, that means the site is being monitored. But mostly, we are using that for DC sites to get the traffic metrics. In Control mode, the site is fully functional. And WAN management is very flexible. We can create multiple WANs in a site and we can customize a WAN. We can move traffic around, depending on the customer's requirements and internet availability.