How azurementor/azure-az-900-study-guide works
Project type and purpose
• This repository is not an application or service in the traditional sense but a set of Markdown‑based study materials for the Microsoft AZ‑900 Azure Fundamentals exam.
• It consists of three topic files covering cloud concepts, Azure architecture & services, and Azure management & governance, plus a README that ties them together.
File structure
• Top‑level files:
• 1-Describe cloud concepts (25–30%).md
• 2-Describe Azure architecture and services (35–40%).md
• 3-Describe Azure management and governance (30–35%).md
• README.md
• No code, no “src” or “tests” directories—this is purely content.
• No build scripts appear here, but in a typical publishing workflow these files would be fed into a Static Site Generator (SSG) or documentation framework.
README for additional insights
• It lists the three skill categories and links to Microsoft Learn paths and a free practice assessment.
• It’s clearly intended to be used as an adjunct to official Microsoft Learn resources.
Main components
a. Content Layer
– Markdown files (3 topic files + README)
b. Build/Publish Pipeline
– Example: MkDocs, Hugo, Jekyll or another SSG
– Continuous Integration (GitHub Actions, Azure DevOps)
c. Hosting/Delivery
– GitHub Pages or Azure Static Web Apps (with optional CDN)
d. End Users
– Candidates studying for AZ‑900, accessing via web browser
e. External Services
– Microsoft Learn links and Practice Assessment URLs
Relationships and interactions
• Markdown files → (piped into) Static Site Generator → Builds HTML/CSS/JS
• CI Pipeline triggers on push → Deploys static assets to hosting environment
• End user accesses the hosted site → Follows links to external Microsoft Learn resources and practice assessment
• Optional: CDN caches assets for global performance
Architectural patterns and design principles
• Static Site Generation: decouples content from presentation, ensures fast performance and low cost
• Git‑based workflow: content changes trigger automated builds and deployments
• Single‑Page or Multi‑Page approach: depending on chosen SSG, could be served as an SPA or classic MPA
• Idempotent, repeatable builds for consistency between environments
Technologies and frameworks (examples)
• Content: Markdown
• SSG: MkDocs (with Material theme) / Hugo / Jekyll
• CI/CD: GitHub Actions or Azure Pipelines
• Hosting: GitHub Pages or Azure Static Web Apps
• CDN: Azure CDN or GitHub’s built‑in CDN
Detailed but not over‑engineered
• Logical layer without trying to force microservices or complex databases.
• How simple Markdown files evolve into a published study guide website and how users interact with both the local content and linked external resources.