Cloud Resume Challenge: AZ-900 to Serverless
This article explains how to build the Cloud Resume Challenge using Microsoft Azure, starting from the AZ-900 certification and ending with a fully serverless application. You will learn the step-by-step architecture, the purpose of each component, and how the challenge maps to real-world cloud skills, with a clear path from foundational knowledge to hands-on implementation.
What Is the Cloud Resume Challenge?
The Cloud Resume Challenge is a free, self-paced project created by Forrest Brazeal. It asks you to build a personal resume website and deploy it using cloud services, with a visitor counter that persists data in a database and updates the page without a traditional server. The challenge is designed to teach you cloud computing by doing, not just by watching videos or passing exams. It is popular among career changers and students because it produces a tangible portfolio piece that demonstrates practical skills to employers.
The original challenge is written for AWS, but the same structure works on Azure. Doing it on Azure is a great way to combine the AZ-900 certification (Azure Fundamentals) with a project that proves you can apply those concepts. The Azure version typically includes: a static website hosted on Azure Storage or Azure Static Web Apps, a serverless API using Azure Functions, a database like Cosmos DB or Azure Table Storage, and a CI/CD pipeline with GitHub Actions or Azure DevOps.
Why Start with AZ-900?
AZ-900 is Microsoft’s entry-level certification for Azure. It covers core concepts like cloud models (IaaS, PaaS, SaaS), Azure architecture components (regions, availability zones, resource groups), and key services (compute, storage, networking, databases). Passing AZ-900 gives you a solid vocabulary and mental model of how Azure works, which is exactly what you need before diving into the Cloud Resume Challenge.
However, AZ-900 is theoretical. You will not learn how to write an Azure Function or set up a CI/CD pipeline from the exam guide. The Cloud Resume Challenge fills that gap by forcing you to apply the concepts. For example, you will learn what a resource group is by creating one, what a serverless function is by deploying one, and what a NoSQL database is by storing visitor counts in Cosmos DB. The certification gives you the map; the challenge gives you the territory.
Architecture: From Static Site to Serverless
The Azure version of the challenge typically follows this architecture:
- Static website – Your resume HTML, CSS, and JavaScript files are hosted on Azure Storage (with static website enabled) or Azure Static Web Apps. This is cheap, fast, and requires no server.
- API endpoint – An Azure Function (HTTP trigger) serves as the backend. It reads the current visitor count from a database and returns it as JSON. It also increments the count when a visitor loads the page.
- Database – Cosmos DB (or Azure Table Storage for a simpler, cheaper option) stores a single document or entity with the visitor count. The function uses the Azure SDK to read and update it.
- CI/CD pipeline – GitHub Actions or Azure Pipelines automatically builds and deploys the static site and the function whenever you push changes to your repository. You can also add a test stage that checks the function’s response.
- Custom domain and HTTPS – Optionally, you can attach a custom domain (like yourname.com) and enable HTTPS via Azure CDN or Azure Front Door.
The JavaScript on your resume page calls the function’s URL (e.g., https://yourfunction.azurewebsites.net/api/count) and updates the counter in the DOM. No page reload is needed, which is what makes it “serverless” from the user’s perspective.
Step-by-Step Implementation Guide
Here is a practical sequence to follow. The exact steps can vary based on the Azure portal’s current UI, but the workflow is stable.
- Prepare your resume – Write your resume as a static HTML file with inline CSS and JavaScript. Keep it simple; you will add the counter later.
- Create a storage account – In the Azure portal, create a storage account with a globally unique name. Enable the “Static website” feature, which gives you a URL for your files. Upload your resume files to the
$webcontainer. - Create a Function App – Create a Function App in the same resource group. Choose the runtime stack (e.g., Node.js, Python, or C#). For the challenge, a simple HTTP trigger is enough. Write a function that:
- Reads the current count from Cosmos DB (or Table Storage).
- Increments it by 1.
- Returns the new count as JSON.
- Set up Cosmos DB – Create a Cosmos DB account (choose the SQL API for simplicity). Create a database and a container with a partition key. Store a single item with an id like
counterand acountproperty. Your function will need the connection string and container name, which you can store in the Function App’s application settings. - Update your resume JavaScript – Add a
fetch()call to your function’s URL. Display the returned count in a span element. Test it locally by opening your HTML file in a browser (you will need to enable CORS on the Function App for local testing). - Deploy via CI/CD – Put your code in a GitHub repository. Create a GitHub Actions workflow that:
- Checks out the code.
- Runs any tests (e.g., a simple script that calls the function and checks the status).
- Deploys the static files to the storage account (using the Azure CLI or a published action).
- Deploys the function code to the Function App (using Azure Functions Core Tools or a published action).
- Add a custom domain (optional) – If you own a domain, point it to your storage account’s static website URL. You will need to validate ownership and add a CNAME record. For HTTPS, you can use Azure CDN or Front Door.
Common Pitfalls and How to Avoid Them
Many people get stuck on a few recurring issues. Here are the most common ones and the fixes:
- CORS errors – When your browser tries to call the function from a different origin (your storage URL), the function must allow it. In the Function App, go to CORS and add your static site’s URL (e.g.,
https://yourstorage.z13.web.core.windows.net). For local testing, addhttp://localhost:5500or whatever port you use. - Function returning 500 – Usually this is a missing environment variable (like the Cosmos DB connection string) or an incorrect container name. Check the Function App’s application settings and the function’s logs in the portal.
- Counter not incrementing – This often happens because the browser caches the function’s response. Add a cache-control header or a query string like
?t=Date.now()to the fetch URL. - Deployment failures in GitHub Actions – The most common cause is missing secrets. You need to add your Azure credentials as GitHub secrets (e.g.,
AZURE_CREDENTIALSor a service principal). Follow the Azure login action’s documentation carefully. - Static site not showing – Make sure you uploaded files to the
$webcontainer, not the default container. Also, the index document must be namedindex.html.
Costs and Free Tier Options
One of the best things about the Cloud Resume Challenge is that it can be done for free or nearly free. Azure offers a free tier for many services:
- Azure Storage – The free tier includes 5 GB of storage and 10,000 read operations per month. Your resume is a few KB, so you will never hit the limit.
- Azure Functions – The consumption plan gives you 1 million executions per month for free. A single visitor triggers one execution, so you would need a million visitors to exceed that.
- Cosmos DB – The free tier includes 1000 RU/s and 25 GB of storage. This is more than enough for a counter.
- GitHub Actions – Public repositories get 2,000 minutes per month free, which is plenty for this project.
If you are using Azure Table Storage instead of Cosmos DB, the cost is even lower (fractions of a cent per operation). The main thing to watch out for is leaving resources running after you finish. Always delete the resource group when you are done to avoid any charges.
Alternatives and Variations
The challenge is flexible. You can swap out services to match your interests or to learn different tools:
- Use Azure Static Web Apps instead of Storage – This service combines static hosting, a built-in API (via Azure Functions), and authentication, all in one. It is arguably easier for the challenge because it reduces the number of separate resources.
- Use Azure Table Storage instead of Cosmos DB – Table Storage is simpler and cheaper, but you lose some features like SQL queries. It is a good choice if you want to minimize costs.
- Use Azure DevOps instead of GitHub Actions – If you prefer Microsoft’s DevOps platform, you can build a similar pipeline with Azure Pipelines.
- Add a visitor location map – Instead of just a counter, you could use the function to log IP addresses and show a map of visitors. This adds complexity but makes the project stand out.
Frequently Asked Questions
Do I need to pass AZ-900 before starting the challenge?
No, but it helps. AZ-900 gives you the terminology and concepts needed to understand what you are doing. Many people study for AZ-900 and do the challenge simultaneously, which reinforces the material. You can start the challenge without the certification, but you may spend more time searching for basic terms like “resource group” or “region.”
Can I use Azure Static Web Apps instead of Storage + Functions separately?
Yes, absolutely. Azure Static Web Apps is a managed service that combines static hosting, an integrated API (Azure Functions), and optional authentication. It simplifies the challenge because you deploy both the frontend and the backend in one go. The trade-off is that you learn less about the individual services, but you still learn the core concepts of serverless and CI/CD.
How long does the challenge take?
It depends on your experience. If you are new to cloud and coding, expect 1-2 weeks of part-time work. If you have some familiarity with HTML, JavaScript, and Git, you can finish in a weekend. The biggest time sinks are usually setting up the CI/CD pipeline and debugging CORS issues.
Is the Cloud Resume Challenge enough to get a cloud job?
No single project guarantees a job, but this challenge is a strong addition to your portfolio. It demonstrates that you can build a full serverless application, use version control, and automate deployments. Recruiters often mention it as a positive signal, especially for entry-level roles. Pair it with the AZ-900 certification and a well-written resume to maximize your chances.
What if I don’t have a custom domain?
You don’t need one. The challenge works perfectly with the default URLs provided by Azure (e.g., https://yourstorage.z13.web.core.windows.net). A custom domain is a nice-to-have for a professional look, but it’s not required. If you do add one, you’ll also need to handle HTTPS, which Azure CDN or Front Door can do for you.
Can I do the challenge on AWS instead and still use AZ-900?
AZ-900 is Azure-specific, so it won’t directly help with AWS. However, the concepts you learn (regions, serverless, databases) are transferable. If you want to use AWS, you should look at the AWS Cloud Practitioner certification instead. But if you’re already studying AZ-900, sticking with Azure is the most efficient path.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.