Start with 7 free days of training.

Gain instant access to our entire IT training library, free for your first week.
Train anytime on your desktop, tablet, or mobile devices.

This Microsoft Azure video training course with Ben Finkel covers the topics and material required to fully understand how to develop, implement, monitor, and troubleshoot resilient and scalable solutions on the Azure platform....
This Microsoft Azure video training course with Ben Finkel covers the topics and material required to fully understand how to develop, implement, monitor, and troubleshoot resilient and scalable solutions on the Azure platform.

70-532: Developing Microsoft Azure Solutions is an introduction to the various components that make up the Microsoft Azure platform. As a developer-focused course, these Nuggets address these features from the perspective of an aspiring or experienced web developer. This course also helps you prepare for the certification exam, by covering each course objective, as well as demonstrating practical applications for using these features.

The 70-532 exam and this course cover the following general topics: Implementing Websites, Creating Virtual Machines, Implementing Cloud Services, Designing an Azure Storage Strategy, and Azure Virtual Networks.

Note: Microsoft recently updated many of its exams, including those associated with Azure. CBT Nuggets plans to update this course to align it with the new exam objectives and technology advances, but please note that this course is currently aligned with outdated exam objectives.

Recommended Experience Recommended Equipment
  • A desktop computer running Microsoft Windows version 7, 8, or 10
  • Microsoft Visual Studio 2013
Related Certifications
  • MCSE: Cloud Platform and Infrastructure
  • MCSA: Cloud Platform
  • MCSD: App Builder
Related Job Functions
  • Web development
  • Application engineer/team lead
Ben Finkel has been a CBT Nuggets trainer since 2014. His areas of expertise and certifications include Google Developer Expert, Google Certified Trainer, Microsoft ASP.NET (WebForms and MVC), Data Analysis and Design, Relational Database Architecture, MS SQL Server, Microsoft C#.NET, Javascript, jQuery, Microsoft Visual Basic .NET & 6.0, .NET Reporting Services, MS Access, and Python.
 show less
1. Introduction to Azure Websites (21 min)
2. Azure Websites: Deployment Slots (17 min)
3. Azure Websites: Hosting Plans (13 min)
4. Azure Websites: Site Settings (17 min)
5. Azure Websites: Custom Domains and SSL (15 min)
6. Azure Websites: Diagnostics and Debugging (21 min)
7. Azure Websites: Monitoring and Alerts (14 min)
8. Azure Websites: Scaling (12 min)
9. Azure Websites: Traffic Manager (17 min)
10. Azure Websites: Resilience Patterns (11 min)
11. Azure Websites: WebJobs (8 min)
12. Introduction to Azure Virtual Machines (10 min)
13. Azure Virtual Machines: Creating New VMs (10 min)
14. Azure Virtual Machines: VHDs, Disks, and Images (16 min)
15. Azure Virtual Machines: Custom Extensions (11 min)
16. Azure Virtual Machines: Networks and Cloud Services (12 min)
17. Azure Virtual Machines: Endpoints, ACLs, and Load Balancing (19 min)
18. Azure Virtual Machines: Scaling and Availability (13 min)
19. Azure Virtual Machines: Storage Planning (19 min)
20. Azure Virtual Machines: Diagnostic Measurements (10 min)
21. Introduction to Azure Cloud Services (14 min)
22. Azure Cloud Services: Building Cloud Services (14 min)
23. Azure Cloud Services: Scaling Cloud Services (13 min)
24. Azure Cloud Services: Endpoints (15 min)
25. Azure Cloud Services: Network Traffic and ACLs (9 min)
26. Azure Cloud Services: Networking (17 min)
27. Azure Cloud Services: Managing Websites (12 min)
28. Azure Cloud Services: Local Storage (11 min)
29. Azure Cloud Services: Diagnostics and Debugging (12 min)
30. Introduction to Azure Storage (10 min)
31. Azure Storage: Storage Accounts (9 min)
32. Azure Storage: Containers and Blobs (12 min)
33. Azure Storage: Advanced Blob Features (11 min)
34. Azure Storage: Tables (13 min)
35. Azure Storage: Queues (11 min)
36. Azure Storage: Access Control (16 min)
37. Azure Storage: Monitoring (10 min)
38. Azure Storage: SQL Databases (9 min)
39. Azure Integration: Azure Active Directory (19 min)
40. Azure Integration: Virtual Networks (8 min)
41. Azure Integration: Service Bus (16 min)

Introduction to Azure Websites


Introduction to Azure Websites. Hello, everybody. This is Ben Finkel. And in this Nugget, we're going to introduce the concept of Azure Websites, which is Azure's platform-as-a-service that allows us as developers to write our code and deploy it out into the cloud into a fully managed platform.


No getting our fingers dirty with the infrastructure. No worrying about scaling up or scaling down resources. Azure Websites handles all of that for us. Azure Websites, the name, implies that it might just be a simple place to host websites inside of Microsoft Azure up in Microsoft's cloud service.


That would really be underselling. It wouldn't get anywhere near the complexity. The formal definition, Azure Websites is a fully managed platform-as-a-service, a PAAS-- get used to that term-- that enables you to build, deploy, and scale enterprise-grade web applications.


So we're not just talking about websites, we're talking about web apps. We're talking about anything that you want online that needs to be responsive to your clients, to your consumers. And it does this as a platform-as-a-service, a PAAS. And the idea behind a PAAS is, just like everything else in the cloud, it is delivered as a service.


Databases as a service. Virtual machines as a service. Platform-as-a-service sort of takes that to the extreme, and gives you the entire hosting platform fully managed and fully segregated by Microsoft from you, the developer. So you spend all your time locally developing your website, writing your code, then you deploy it out to the cloud, and it's out of your hands.


It runs. Its scales up. It scales down dynamically as much as you need. It's backed up. It's restored. It's globally deployed. There's a ton of great features when you deal with PAAS, when you deal with platform-as-a-service, because you are no longer worried about all of this different stuff, all the mechanics of the infrastructure, of hosting a service.


Do I have enough servers? Do I have enough memory in those servers? Do I have those servers in the right geographic location to serve my customers and my clients? Forget about all that. It's all taken out of your hands. It's fully managed for you, in this case, by Microsoft Azure.


So there's a whole host of different features that Microsoft Azure as PAAS gives you. For starters, it's integrated with WebJobs, Azure WebJobs. If you're not familiar with Azure WebJobs, those are just hands off jobs that run right alongside your Azure Websites, but in the background.


On same virtual machines that interact with your websites, they can do all sorts of automated tasks that you might need to perform. You get to write in whatever your favorite language is. You're not stuck with writing in .NET, although it certainly supports .


NET. Obviously, they strongly encourage that. But Python, PHP, Node.js, there's a ton of different options there. Whatever language you're used to using, you're used to coding in, you're going to be able write in, and then just deploy it up into the cloud, into Azure Websites' PAAS, so that it's served up for you.


There's a whole host of different Azure storage options available for you out there. So not just SQL database, but document data stores and NoSQL options. Tons of different things that are ideally suited to whatever your problem is, whatever solution you need for data storage.


On top of that, because it's in Microsoft's cloud, because it is in Azure, it means that you're going to have a real high bandwidth, low latency connection to that data. So you're not going to have to worry about data traveling very far or across really thin pipes in order to get to your application.


Like I mentioned before, Azure Websites dynamically scale. That's a really big deal. You can set up under certain parameters for your website to automatically grow as traffic increases, and also descale, automatically shrink, as traffic decreases. So if you've got an application that's going to be the next big thing, the next SnapChat, the next Instagram, and you know that the minute you release it, it's going to blow up, it's going to be a viral sensation, don't worry about it, because Azure Websites can scale up to handle global demand without any interaction from you.


It can just automatically turn on and do it, and you're going to have 100% up time, or near 100% percent uptime on your websites without any hands-on access. And of course, because your data and your information is out on Microsoft Azure servers, you know that disaster recovery is completely built-in for you.


Even a large scale natural disaster, say an earthquake, that brought down a whole data center, wouldn't impact the availability of your websites and your data, because everything is being georeplicated across many different data centers on the planet.


Microsoft is obviously a large organization, and they have a global infrastructure to back up and secure your data. And you can always, absolutely, of course, bring data down from the cloud to local on-site storage if you need to do that as well. So you've always got a lot of disaster recovery options available to you, and you don't need to worry about losing your data.


Another neat feature of working with Microsoft Azure is you might think, oh, now I've got to go learn a whole new set of tools, a whole new suite of things that I've never learned before. Well, actually, no you don't, because Azure is built right into a ton of client side tools that you're already used to working with.


The biggest and most notable, of course, is Visual Studio. You can use Visual Studio to both write your code, as well as deploy it up to Microsoft Azure Cloud and manage a lot of the features, a lot of the things that are going on, inside of your Azure Websites.


You've also got the option to use WebMatrix, which is a cool, lightweight web development tool that Microsoft has developed, more or less explicitly for working with Azure websites. We'll take a look briefly at it later in this Nugget. But for the most part, we're going to pay attention to Visual Studio, because that's the tool that most of us are familiar with using.


You know what? Maybe you're not using Visual Studio so much, but you are used to using PowerShell. Well, PowerShell has a ton of great features, and we'll often talk about those throughout both this Nugget and this entire course, how you can deploy and build Azure Websites and WebJobs using PowerShell.


They have a command line interface that you can download and install called XPLAT-CLI. I like saying XPLAT. That's funny. But it stands for cross-platform command line interface, XPLAT. And that's going to allow you to use these tools both from Microsoft Windows, as well as OSX.


You can use it on your Macintosh. So you can get into it from a number of different operating systems even. And of course, lastly, like all self-respecting the cloud services, there's all these features built into the web browser. A lot of the management and even the coding can be done right from a web interface.


We'll take a look at that at the Azure Portal. If you're already a little bit familiar with Microsoft Azure, you may have stumbled across a number of the different features or options that they offer out in the Azure Platform. And those are not just Azure Websites, but Azure Cloud Services and Azure VMs.


And they may seem like they're all kind of the same thing. Because after all, your Websites are actually spinning up VMs, and running on VMs. So how are Website different from VMs and cloud services? Those have to execute somewhere. Where do they execute, and how are they different from these things?


So maybe the easiest way to think about it is Azure Websites are your simplest, easiest, most straightforward way into Microsoft Azure. Websites allow for fast and easy deployment in a fully managed platform. That's really the key there. Azure Websites are fully managed for you by Microsoft.


You don't choose what VMs to spin up. You set the rules about when VMs should be spun up, and when they should be spun down, and Microsoft Azure handles all of that for you. So it's all being managed for you according to some of the parameters and the options you choose and you set.


Cloud Services, on the other hand, allow for slightly finer control. So now, you're still just deploying code out to VMs, but you have a little more control over the web server. You can actually remote desktop into the server that your cloud service is running on, and you can manipulate things on your Cloud Services Server, like you can set start-up scripts in order to load libraries and get scripts running that you need running when that VM spins up.


Lastly, Azure VMs are the most traditional sort of framework. And it's something that a lot infrastructure folks are probably used to dealing with. If you're a developer like me, Azure Websites is kind of what appeals to you. But if you're coming from the infrastructure side, if you're coming from the operation side of the house, then virtual machines that allow you to have full control over them are what you're going to be interested in.


That's Azure VMs. Those are remote desktops that you simply spin up, and you have complete control over them. You have to choose when they spin up, when they spin down, how many of them are running, what software is running on them, et cetera. So Azure VMs are the most controlled, but the least easy to use.


Right now, we're talking Azure Websites, though, and some of the use cases for Azure Websites include a simple web page for small business. If you run a haircut business, or you sell flowers for a living, you need to get your web presence updated. Well, you know what?


Azure Websites. Just build a simple website, deploy it out to Azure, you're good to go. You can also set up a web application with global reach. Say you've got something that you know clients, or customers, or colleagues in different parts of the world are going to need to use and need to access.


Well, set that up with Azure Websites. Set your application running. In Azure Websites, it's going to be georeplicated to a number of different centers, and you know that it's going to have a global reach. Azure Websites is also, believe it or not, real good for migrating up IIS6 web applications into the cloud.


So Azure Websites, as of the recording this Nugget, actually run on IIS7, I believe, inside of their VMs, but they do have a feature built-in for migrating up websites from Windows Server 2003. So you don't need to go to a full on virtual machine that's fully managed by you to get an older website, an IIS6 website, migrated up into the cloud.


And you can use Azure Websites for hosting a rest API as well. It's another great use case for Azure Websites. To understand this visually, we have little chart here taken from the documentation, which is linked down here. Feel free to go right to that link and read a little bit more in-depth about these different services and how they relate to one another.


But notice down here, Websites have a lot of agility, and a lot of ease of management, while virtual machines have a lot of control and a lot of support for legacy applications. Cloud services kind of fall in between those two extremes. Now all of this is well and good, but if it's priced out in the stratosphere, if you can't afford to interact with and use Microsoft Azure, it's not going to do anyone any good.


If it's too expensive, it's just not worth it. So pricing is always a big question that comes up. Thankfully, Microsoft Azure has a pretty aggressive, pretty friendly pricing scheme. For starters, your pricing is going to be broken down into one of four different tiers that you might have, and that's the free tier, the shared tier, the basic tier, and the standard tier.


And these tiers enable and disable different features, depending on which one you use. Obviously, the free tier doesn't cost any money. You can have things running in the free tier, and you don't have to worry about accruing any charges, because it's all free.


It's a pretty generous little way to get involved and get started in Azure. Particularly as you're following along with this Nugget course, you may want to have a lot of things inside of the free tier. Now, a lot of the features that we're going to need to demonstrate are going to be in the higher tiers, not available on the free tier, so you will have to flip-flop up and down between these different tiers.


But it's good to know that the free tier is there. Now, just slightly different from the free tier is the shared tier. And what they mean there by shared tier is that your VMs are shared when things are in the shared tier. Same thing in the free tier.


These are actually shared spaces, shared virtual machines, so you're sharing your memory space, your CPU time, with other free and shared tier websites from other people. Totally secure. There's no interaction between them and yours. Just know that you don't have a dedicated machine for your applications.


Now, that's not true for the basic and standard tier. These are dedicated for your services. So when you're in the basic and standard tier, you're going to pay a little bit more money, but you're going to get some dedicated options. You've also got within the basic and standard tiers different suboptions, so you can have B1, 2, 3, or S1, 2, 3, which are like this.


Say I'm going to be small, medium, and large dedicated VMs within those tiers. So you get some pretty fine-grain control over exactly how much power you need on your VMs, and how much you want to pay for those. Now, it can be a little bit confusing the first time you get into this, because you might think, OK, I'm going to set up a free website, and a shared website, and a basic website, but it doesn't exactly work like that.


The way they group the tiers are inside what's called a web-hosting plan. So your web hosting plan is what your tiers apply to. So you might have a free web hosting plan. You might have a second web hosting plan that's basic. Your websites then go inside of that web hosting plan, and all of websites that are inside of a web hosting plan, a given individual web hosting plan, which is part of a larger resource group, by the way, are going to share the same equipment.


So if you have a B2 hosting plan, and you've got three or four websites there, every website is going to run on every instance that gets spun up inside of that B2 basic tier hosting plan. Your resource groups, on the other hand, are how you group multiple web hosting plans together, like we indicate here, as well as other resources across Microsoft Azure.


And that allows you to sort of deal with an entire infrastructure for maybe an application or a deployment, all as a cohesive, singular unit. You can go to the documentation and check out the pricing details for the different web hosting plans. Here's a chart that just shows some of different things.


You can see exactly what you get with free versus shared, basic, and standard web hosting plans, what they allow you to have. One important thing here. Standard has five slots per site. None of the other tiers have any deployment slots for you, so that's going to be a big one that we're going to look at early, are deployment slots for your website.


You need the standard tier web hosting plan in order to utilize those. We'll take a look at those. But for the most part, you're going to be able to do what you want to do, at least for demonstrating and learning about Microsoft Azure inside of the free and the shared tiers.


Now as big and limitless as using a cloud service like Microsoft Azure can seem, there are actually some quotas and some constraints, some limitations on ultimately what you can do. It is after all, a shared environment, and they need to ensure that any one client doesn't overwhelm all the resources.


And at a very macrolevel, there is obviously, of course, some limitations on what they can provide to all their clients in order to meet their SLA. You're probably not going to run into these. But just understand that you have limits, quotas, and constraints that apply both at the subscription level up here-- and that's things like the number of cores, the number of administrators, on your particular project, et cetera.


But then there's also, more interestingly, there are a few limitations at the website level, specifically the number of websites you can have. The number of hosting plans you can have inside of your subscription. The number of instances you can have for a website.


The amount of storage and CPU time, memory bandwidth, the number of connections you can have at one time, and as well as some additional features. All of these things change and upgrade as you increase pricing tiers. So the free tier's going to have the fewest number of these, but as you go up to the standard tier, you're going to add the number of websites, CPU time, et cetera, that you can use, as well as get access to additional features like the deployment slots that we just talked about.


What those limitations are detailed very in-depth out here in the documentation in Microsoft Azure. I encourage you to go check that out. And there is one a little confusing point that sometimes trips people up. They have two limitations. They have their default and their ultimate limitation.


The default limitation is what is going to apply 99.9% of the time. That's your limit on the number of x that you can have, the amount of CPU time you can have. But they also have an ultimate limitation, which is a more global limitation that they absolutely cannot go over.


If you want to increase your limit to something above the default but below that ultimate limitation, you are allowed to if you submit a support ticket, right here on Microsoft support site. Talk to them, explain your reasoning. Microsoft's very good about getting back to you and understanding your use case.


And if you actually need to the increased limits, they will allow you to purchase more service from them. But they don't just offer that to anybody to just turn on, again, because they need to meet their SLA for all of their clients in a shared environment.


Now, let's finish up this Nugget by taking a quick look at just how easy it is to deploy a site in Microsoft Azure. I'm Going to bring up Visual Studio 2013 here. It's what I want to use for most of this course. And notice that I'm logged in up here as CBT Azure.


That's my Microsoft Azure account. I had to create a Microsoft account and register it at portal.azure.com. So you need to do that ahead of time before you can do any of this. Then you can log in with that account right here on Visual Studio, and that's going to make our deployment all that much easier.


So we're going to go here and click New Project. And all I want to do is start a new C# MVC 4 application. I'll call it DemoWebsite. And this is just going to give me a website that I know is going to run and execute, and I can deploy up into the cloud.


And once it's finished being built here, I can actually click the Run button up here, and I can see it Execute. It's going to compile my code, launch my local web server here. And just to make sure that the website is, in fact, running the way I hoped, there it is.


Nothing fancy, but your logo here, a couple links, like a Contact link, that work. So we have a good, functioning MVC website here. Let me go ahead and close that, and stop the project. Now in order to deploy this up into Azure, I can use the tools built right into Visual Studio.


It's real easy to do. I'm going to right click my project and choose Publish. Now I can fill in all the connection profile information myself if I want to, or I can get it right from the web. It's really easy to do. I'm going to import a Publish profile.


And I'm going to choose Import from a Microsoft Windows Azure Website. Say I want to add a Windows Azure Subscription, and I'm going to download the subscription file. That's going to launch a web browser for me. If I look it up here, I can see that it logged in, since I was already logged into the browser and my account, and it downloaded this Free Trial Publish Settings file.


Perfect. So I'm going to come back here to this guy, and browse to my Downloads, where it should have downloaded it. And I will say Import. And now, I've got my Windows Azure subscription connected to my Publish. It's looking for any existing websites out there.


I know I don't have any, because this is a brand new subscription, so I'm going to click New. And my site name will be DemoWebsite. And the location, doesn't like that. DemoWebsiteCBT. It's got to be unique across the entire Microsoft Azure Platform there.


My location. We'll go ahead and say Eastern US, because that's where I am. I don't need a database setup. Database server, I'll click Create. It's going to create the site, and then allow me to publish this application right up to that website, that deployment slot that I'm creating in Azure right now.


Perfect. There it is, ad we import from there. Click OK. Now I've got all of the connection information filled in for me, including username, password, the name of the server, which I didn't have to figure out my own. Click Validate Connection. It's going to check and ensure that all this information is correct.


It better be. It just downloaded it for me. And it is. Good. Then I'm going to click Publish. Down here, I can see it's building and publishing, and I can follow the entire log down here on the output pane, if I want, and see it upload the entire site to the cloud.


Now, I'm going to jump over and look at the cloud itself. Here's the Microsoft Azure Portal. And if I come down to my browse option here, I can see Websites is one of the things that I can browse. I'll bring that up. It's going to load my websites here in the right-hand pane.


And I should see-- it's trying to launch my website there as well, but over here, I should see that website come up. Yep. There it is. DemoWebsiteCBT. I can tell that it's running. It's in US East. It's in the free pricing tier, so I'm not worried about accruing any charges while I do this.


And over here, you can see that my URL, DemoWebsiteCBT.azurewebsites. I've got my website running. So, awesome. Just like that with a few mouse clicks, importing a couple profile settings, we actually built a web deploy XML file in the background there, even if you couldn't tell, and we got our website running live in the cloud.


If you're going to be using Microsoft WebMatrix, that's the lightweight web development interface that Microsoft provides. Brought it up right here. It's just the same way. You got to log in with your Microsoft account, which I'll go ahead and do. And once it's connected and finished importing my account, I'll be able to create a new project if I want.


Let's just create a new empty site. No big deal. Site name will be EmptySiteCBT. The location, I want it to be in Eastern US. So what that's actually going to do is go ahead and provision that site out in Azure Websites. And then when I build out my site here locally, whenever I'm ready to deploy, I'm just going to click the Publish button up here.


So right now, it's provisioning the site in the portal. I can go and actually see that happen back here. It's going to list, along with DemoWebsiteCBT is going to be EmptyWebsiteCBT, the website that I just created. So I've created a second website, almost like a second deployment slot, a second place for a website to live, inside of my free subscription there.


There it is. Empty site CBT. It can come down here. And now that it's up and running, I can actually-- if I wanted to, I coud create a new file, add some HTML to this. Click the Publish button, and it's going to go ahead and upload that for me. So with WebMatrix, it's even easier to do.


WebMatrix is designed from ground up to work with Azure, and it works really, really well. That concludes this Nugget on introduction to Azure Websites. So just to recap, we talked about what Azure Websites are. How they're a platform-as-a-service, a PAAS, that you can deploy your code up to, and it's going to be fully managed for you.


All the dynamic scaling, and hosting of that website, making sure that it's always responsive, that it's being backed up, that it's secure, all of that is handled for you by the Microsoft Azure team. All you need to worry about is writing your code and deploying it up through one of the many tools that Microsoft Azure offers.


I hope this has been informative for you, and I'd like to thank you for viewing.

Azure Websites: Deployment Slots

Azure Websites: Hosting Plans

Azure Websites: Site Settings

Azure Websites: Custom Domains and SSL

Azure Websites: Diagnostics and Debugging

Azure Websites: Monitoring and Alerts

Azure Websites: Scaling

Azure Websites: Traffic Manager

Azure Websites: Resilience Patterns

Azure Websites: WebJobs

Introduction to Azure Virtual Machines

Azure Virtual Machines: Creating New VMs

Azure Virtual Machines: VHDs, Disks, and Images

Azure Virtual Machines: Custom Extensions

Azure Virtual Machines: Networks and Cloud Services

Azure Virtual Machines: Endpoints, ACLs, and Load Balancing

Azure Virtual Machines: Scaling and Availability

Azure Virtual Machines: Storage Planning

Azure Virtual Machines: Diagnostic Measurements

Introduction to Azure Cloud Services

Azure Cloud Services: Building Cloud Services

Azure Cloud Services: Scaling Cloud Services

Azure Cloud Services: Endpoints

Azure Cloud Services: Network Traffic and ACLs

Azure Cloud Services: Networking

Azure Cloud Services: Managing Websites

Azure Cloud Services: Local Storage

Azure Cloud Services: Diagnostics and Debugging

Introduction to Azure Storage

Azure Storage: Storage Accounts

Azure Storage: Containers and Blobs

Azure Storage: Advanced Blob Features

Azure Storage: Tables

Azure Storage: Queues

Azure Storage: Access Control

Azure Storage: Monitoring

Azure Storage: SQL Databases

Azure Integration: Azure Active Directory

Azure Integration: Virtual Networks

Azure Integration: Service Bus

Please help us improve by sharing your feedback on training courses and videos. For customer service questions, please contact our support team. The views expressed in comments reflect those of the author and not of CBT Nuggets. We reserve the right to remove comments that do not adhere to our community standards.

comments powered by Disqus
Intermediate 9 hrs 41 videos


Training Features

Practice Exams
These practice tests help you review your knowledge and prepare you for exams.

Virtual Lab
Use a virtual environment to reinforce what you are learning and get hands-on experience.

Offline Training
Our iOS and Android mobile apps offer the ability to download videos and train anytime, anywhere offline.

Accountability Coaching
Develop and maintain a study plan with one-to-one assistance from coaches.

Supplemental Files
Files/materials that supplement the video training.

Speed Control
Play videos at a faster or slower pace.

Included in this course
Pick up where you left off watching a video.

Included in this course
Jot down information to refer back to at a later time.

Closed Captions
Follow what the trainers are saying with ease.
Ben Finkel
Nugget trainer since 2014