Cloud-computing idea
1 linked question families · 1 variants. Variants are not separate syllabus objectives.
What still needs work
- Selected service-delivery distinction; full deployment taxonomy and hands-on provisioning not exhaustively assessed.
Azure Fundamentals · COVERAGE & GAPS
Azure Fundamentals: Coverage Map & Learning Gaps
Selected foundations: 64 original practice tasks, 14 lessons, 42 retrieval cards and four standalone guides. Official coverage remains partial; not a full syllabus, official mock or score predictor.
A partial map, not a completion score.
Official scope: AZ-900 skills measured July 20, 2026. Public titles paraphrase official bullets; local row numbers and anchor/bullet locators are not Microsoft numeric objective codes. A family groups related reasoning tasks, not an official knowledge point. Partial means an actual taught/assessed subset with visible gaps, not complete official coverage.
Mapping describes the available practice, not your mastery or readiness for the exam. Reviewed 2026-11-03.
57Objectives in this map
55Have partial practice
2Have no mapped practice
Partial practice
Provider/customer duty boundary
2 linked question families · 4 variants. Variants are not separate syllabus objectives.
What still needs work
- Selected IaaS/PaaS/SaaS and Functions duty boundaries; not every shared control or service-specific exception.
Public, private and hybrid models
1 linked question families · 2 variants. Variants are not separate syllabus objectives.
What still needs work
- Public/private/hybrid distinctions; not all deployment variants or governance obligations.
Match a deployment model to a need
1 linked question families · 2 variants. Variants are not separate syllabus objectives.
What still needs work
- Selected connected private/public case; not a universal cloud-model selection framework.
Usage-based consumption
3 linked question families · 5 variants. Variants are not separate syllabus objectives.
What still needs work
- Capacity/expenditure patterns and toy models; not actual price commitments or complete economics.
Pricing-model comparison
What still needs work
- CapEx/OpEx and consumption are taught in lesson14/question063 under consumption; they do not substantively compare concrete pricing models. Pay-as-you-go/commitment/spot comparisons remain not covered.
Serverless meaning
2 linked question families · 4 variants. Variants are not separate syllabus objectives.
What still needs work
- Managed event-driven execution and responsibility meaning; not all serverless limits, plans or operations.
Availability versus scalable capacity
1 linked question families · 2 variants. Variants are not separate syllabus objectives.
What still needs work
- Selected failure-model and vertical/horizontal scaling distinctions; not complete architecture or service SLA validation.
Reliability and predictable outcomes
1 linked question families · 2 variants. Variants are not separate syllabus objectives.
What still needs work
- Selected recovery and performance/cost investigations; no calibrated predictions or exhaustive failure scenarios.
Security/governance benefits
1 linked question families · 1 variants. Variants are not separate syllabus objectives.
What still needs work
- Standards-aligned repeatable configuration subset; not a comprehensive security/governance or compliance assessment.
Managing cloud resources
1 linked question families · 1 variants. Variants are not separate syllabus objectives.
What still needs work
- Templates and management automation purposes only; full management operations and configuration remain outside scope.
Infrastructure-service boundary
1 linked question families · 2 variants. Variants are not separate syllabus objectives.
What still needs work
- Selected guest-OS/control case; not complete IaaS operations.
Managed-platform boundary
1 linked question families · 2 variants. Variants are not separate syllabus objectives.
What still needs work
- Selected managed-platform/app-hosting boundary; not all PaaS services or security.
Finished-software service boundary
1 linked question families · 2 variants. Variants are not separate syllabus objectives.
What still needs work
- Finished software and retained identity decisions; not all SaaS configuration or contracts.
Match a service layer to a workload
2 linked question families · 4 variants. Variants are not separate syllabus objectives.
What still needs work
- Selected three-layer cases; not exhaustive service selection.
Region, pair and sovereign placement concepts
1 linked question families · 2 variants. Variants are not separate syllabus objectives.
What still needs work
- Regions and selected pair/mapping caveats; sovereign-region requirements and service-specific geography are not comprehensively taught.
Availability-zone boundary
1 linked question families · 2 variants. Variants are not separate syllabus objectives.
What still needs work
- Selected zone/failure and subscription logical-mapping concepts; not an implemented resilient design or SLA.
Datacenter role
What still needs work
- No substantive authored teaching or assessment for this official leaf in the bounded module. A related term, source capture or planned object is not counted as coverage.
Resource and resource-group organization
1 linked question families · 2 variants. Variants are not separate syllabus objectives.
What still needs work
- Administrative/lifecycle grouping and location distinction; not complete resource-group operations.
Subscription role
1 linked question families · 2 variants. Variants are not separate syllabus objectives.
What still needs work
- Subscription administrative scope/inheritance; not all billing/account models.
Management-group scope
1 linked question families · 2 variants. Variants are not separate syllabus objectives.
What still needs work
- Management-group hierarchy purpose; not complete policy/inheritance exceptions.
Administrative resource hierarchy
1 linked question families · 2 variants. Variants are not separate syllabus objectives.
What still needs work
- Selected hierarchy/scope cases; not every resource type or deployment scope.
VM, container and function execution
1 linked question families · 2 variants. Variants are not separate syllabus objectives.
What still needs work
- Selected VM/container/function traits; not full orchestration, scaling or runtime options.
VM options and grouped capacity
2 linked question families · 2 variants. Variants are not separate syllabus objectives.
What still needs work
- Selected scale-set and availability-set contrasts; complete VM options, sizing and workload design remain incomplete.
VM supporting resources
1 linked question families · 1 variants. Variants are not separate syllabus objectives.
What still needs work
- Selected NIC/VNet/private-IP building blocks only; complete compute/storage deployment prerequisites and detailed configuration remain incomplete.
Hosting an application
2 linked question families · 4 variants. Variants are not separate syllabus objectives.
What still needs work
- Selected managed-web/VM/container roles; not all hosting options or configuration.
Virtual-network and connectivity purposes
1 linked question families · 2 variants. Variants are not separate syllabus objectives.
What still needs work
- Virtual-network and DNS purposes; subnet, peering, VPN Gateway and ExpressRoute details remain deferred.
Public/private endpoint meaning
1 linked question families · 2 variants. Variants are not separate syllabus objectives.
What still needs work
- Selected private/public endpoint and authorization distinction; not full network security or access configuration.
Storage-service interface choices
1 linked question families · 2 variants. Variants are not separate syllabus objectives.
What still needs work
- Blob, Files and block/message interface distinctions; not all Storage services/features.
Access-tier purpose
1 linked question families · 2 variants. Variants are not separate syllabus objectives.
What still needs work
- Selected Hot/Cool/Cold/Archive access profiles; not current prices or full tier restrictions.
Storage redundancy choices
1 linked question families · 2 variants. Variants are not separate syllabus objectives.
What still needs work
- LRS versus ZRS boundary taught; replica/history practice selected. Other redundancy options, failover behavior and recovery implementation remain deferred.
Account and storage-type options
1 linked question families · 1 variants. Variants are not separate syllabus objectives.
What still needs work
- Selected GPv2 and premium service-combination contrast only; not every account option or performance/cost scenario.
File movement tools
3 linked question families · 3 variants. Variants are not separate syllabus objectives.
What still needs work
- AzCopy/Explorer/File Sync purposes and authorization boundary only; supported transfer modes/options need practical validation.
Migration approaches
2 linked question families · 2 variants. Variants are not separate syllabus objectives.
What still needs work
- Selected Data Box and Migrate purposes only; not complete migration planning, execution or all approaches.
Identity-directory service purposes
1 linked question families · 1 variants. Variants are not separate syllabus objectives.
What still needs work
- Managed domain legacy-protocol subset; complete Entra ID/Domain Services purposes and operations remain incomplete.
Sign-in methods and factors
1 linked question families · 2 variants. Variants are not separate syllabus objectives.
What still needs work
- Authentication and MFA factor classification; SSO/passwordless breadth remains deferred.
External-identity use
1 linked question families · 1 variants. Variants are not separate syllabus objectives.
What still needs work
- B2B existing external-identity collaboration only; complete external-identity scenarios and configuration remain incomplete.
Conditional-access decisions
1 linked question families · 1 variants. Variants are not separate syllabus objectives.
What still needs work
- Selected device/MFA condition reasoning only; not full policy configuration, licensing or evaluation.
Resource-role actions and scope
2 linked question families · 4 variants. Variants are not separate syllabus objectives.
What still needs work
- Selected role/action/scope and additive-grant cases; not full evaluation, data-plane or deny-assignment coverage.
Zero Trust idea
1 linked question families · 1 variants. Variants are not separate syllabus objectives.
What still needs work
- Selected explicit-verification and least-privilege changes; not a complete Zero Trust implementation or assurance.
Layered security defenses
1 linked question families · 1 variants. Variants are not separate syllabus objectives.
What still needs work
- Complementary-layer reasoning only; full security controls and operations remain incomplete.
Defender for Cloud purpose
1 linked question families · 1 variants. Variants are not separate syllabus objectives.
What still needs work
- Selected security posture recommendation purpose; not all Defender plans, protections or operational workflows.
Inputs affecting resource cost
2 linked question families · 4 variants. Variants are not separate syllabus objectives.
What still needs work
- Fictional quantity/rate/fixed-component reasoning; not actual prices, discounts, taxes or complete billing.
Planning with the pricing calculator
1 linked question families · 2 variants. Variants are not separate syllabus objectives.
What still needs work
- Pre-use scenario-estimate purpose; not full calculator operation or quote acceptance.
Recorded-cost management capabilities
2 linked question families · 4 variants. Variants are not separate syllabus objectives.
What still needs work
- Recorded-cost evidence/allocation and notification boundaries; not every Cost Management feature.
Cost and organization metadata tags
1 linked question families · 2 variants. Variants are not separate syllabus objectives.
What still needs work
- Tag metadata/allocation and noninheritance caveats; not every tag/report behavior or automation.
Purview governance purpose
1 linked question families · 1 variants. Variants are not separate syllabus objectives.
What still needs work
- Selected Data Map/catalog purpose; connector support, detailed lineage and complete governance workflows remain incomplete.
Resource-property policy evaluation
2 linked question families · 4 variants. Variants are not separate syllabus objectives.
What still needs work
- Allowed-location/required-tag deny rules and role interaction; not all Policy effects or remediation.
Accidental-change protection with locks
1 linked question families · 2 variants. Variants are not separate syllabus objectives.
What still needs work
- CanNotDelete/ReadOnly management purposes and data-plane distinction; not every service-specific lock effect.
Portal interaction
1 linked question families · 2 variants. Variants are not separate syllabus objectives.
What still needs work
- Graphical management purpose; no actual portal/account operation.
Hosted shell and command interfaces
1 linked question families · 2 variants. Variants are not separate syllabus objectives.
What still needs work
- Hosted-shell and CLI/PowerShell distinctions; not comprehensive commands or environment behavior.
Arc management purpose
1 linked question families · 1 variants. Variants are not separate syllabus objectives.
What still needs work
- Supported external-resource management vs migration only; not all Arc resource types, deployment or management capabilities.
Repeatable declared infrastructure
1 linked question families · 2 variants. Variants are not separate syllabus objectives.
What still needs work
- Repeatable declaration versus interaction evidence; not complete IaC tooling/testing.
Resource Manager and template purpose
2 linked question families · 4 variants. Variants are not separate syllabus objectives.
What still needs work
- ARM/template purpose, parameters and declared state; not full template authoring or deployment.
Advisor recommendations
1 linked question families · 2 variants. Variants are not separate syllabus objectives.
What still needs work
- Recommendation role and selected evidence boundary; not complete Advisor checks or verified savings.
Azure service-health evidence
1 linked question families · 2 variants. Variants are not separate syllabus objectives.
What still needs work
- Global/personalized/resource-health distinctions; not every event or availability scenario.
Workload metrics, logs, alerts and application evidence
1 linked question families · 2 variants. Variants are not separate syllabus objectives.
What still needs work
- Selected metrics/logs, Log Analytics, Application Insights and alert purposes; not full instrumentation, KQL, diagnosis or remediation.
Use the map with care.
- Selected foundations: 64 original practice tasks, 14 lessons, 42 retrieval cards and four standalone guides. Official coverage remains partial; not a full syllabus, official mock or score predictor.
- Every mapped objective is partial. No current row claims full official coverage, professional approval or learner-validated mastery.