AWS Cloud Practitioner CLF-C02 vs Azure Fundamentals AZ-900: Cloud Foundations Compared

 

AWS Certified Cloud Practitioner CLF-C02 and Microsoft Azure Fundamentals AZ-900 are both entry-level cloud certifications, but “fundamentals” should not be confused with “identical.” Each credential teaches the language of cloud computing through a different provider ecosystem, a different service catalog, and a somewhat different balance of business, security, architecture, governance, and operational concepts.

CLF-C02 is AWS’s foundational certification for candidates who need overall AWS Cloud knowledge without being tied to a specific technical job role. Its current blueprint is divided across Cloud Concepts, Security and Compliance, Cloud Technology and Services, and Billing, Pricing, and Support. AWS explicitly places hands-on architecture design, coding, implementation, troubleshooting, and performance testing outside the target candidate scope.

AZ-900 is Microsoft’s cloud-fundamentals exam. The current skills measured focus on cloud concepts, Azure architecture and services, and Azure management and governance. It is designed to help candidates understand what Azure is, how core service categories work, and how organizations manage cloud resources, security, cost, policy, and compliance.

Both are useful first certifications. Neither is a substitute for administrator, developer, security, data, or architecture experience. The right choice depends on the cloud you need to understand, the job direction you want next, and whether you want a general business-and-cloud vocabulary or a direct starting point into a specific provider ecosystem.

Both exams begin with the same cloud ideas

Before provider services matter, candidates need to understand why cloud computing exists.

That means recognizing the difference between capital and operational spending, understanding elasticity and scalability, distinguishing high availability from disaster recovery, and knowing how shared responsibility changes security ownership. Candidates should be able to explain why a managed service can reduce operational burden, why global infrastructure supports resilience and performance, and why cloud pricing depends on consumption patterns rather than only hardware ownership.

These concepts transfer between AWS and Azure. A virtual machine is still a virtual machine even when the service names differ. Object storage still serves different access patterns than block storage. Identity still requires authentication and authorization. Networks still need routing, segmentation, name resolution, and controlled exposure.

This portability is why a fundamentals certification can be valuable even if your employer later changes platforms. The product names may change, but the architectural categories remain.

CLF-C02 gives security and cloud-service categories significant weight

The current CLF-C02 blueprint places substantial emphasis on Security and Compliance and on Cloud Technology and Services. That makes the exam more than a list of business benefits.

Candidates need to understand the AWS shared responsibility model, basic identity and security concepts, compliance resources, core cloud services, and when common service categories are appropriate. They also need billing, pricing, and support knowledge.

The target is awareness rather than implementation. A Cloud Practitioner candidate should recognize that an identity policy controls permissions, but the exam is not designed to prove that the candidate can build a complex least-privilege policy for production. The candidate should understand why multiple Availability Zones improve resilience without needing to design a sophisticated multi-region recovery architecture.

This distinction matters when studying. If you spend all your time following administrator-level labs, you may learn useful AWS skills but allocate preparation inefficiently for CLF-C02. Foundational study should focus on concepts, service purpose, responsibility boundaries, security awareness, and business decisions.

AZ-900 connects cloud concepts to Azure architecture and governance

AZ-900 also starts with cloud concepts, then moves into Azure architecture and services and the mechanisms organizations use to manage and govern Azure.

That means candidates should recognize major compute, networking, storage, identity, security, management, monitoring, and governance concepts. They should understand Azure’s organizational structures and why policy, cost management, resource organization, and access control matter.

The exam is not an Azure Administrator exam. You do not need the operational depth expected in AZ-104. But AZ-900 can be particularly useful for people who work around Azure teams because it teaches the vocabulary used in architecture discussions, support requests, governance reviews, and cloud-budget conversations.

For example, a project manager may not configure a virtual network, but understanding why a workload needs private connectivity helps them recognize dependencies and timelines. A procurement leader may not deploy storage, but understanding redundancy tiers and consumption pricing helps them ask better cost questions. A developer new to Azure can use the fundamentals as a map before learning implementation.

The strongest comparison is ecosystem orientation

CLF-C02 and AZ-900 overlap conceptually, but each teaches you to navigate a different provider’s worldview.

AWS organizes much of its ecosystem around services that can be composed into architectures. A foundational candidate becomes familiar with common AWS service families, global infrastructure, security responsibility, pricing, and support.

Azure is deeply integrated with Microsoft identity, management, governance, enterprise applications, and hybrid environments. AZ-900 introduces the Azure resource hierarchy and management concepts that become important in later Microsoft certifications.

This difference is not a statement that one cloud is more enterprise or more technical than the other. Both operate at massive enterprise scale. It simply means the mental landmarks are different.

If your organization uses Microsoft Entra ID, Microsoft 365, Windows Server, Power Platform, and Azure, AZ-900 terminology will connect naturally to systems you already see. If your environment is AWS-centered, CLF-C02 will give you more immediately useful vocabulary.

Foundational does not mean memorizing logos

A common study mistake is to turn both exams into flash-card contests.

Knowing that a service belongs to compute, storage, networking, or analytics is useful, but the stronger skill is recognizing when the service category solves a requirement.

Suppose a company needs to store large numbers of infrequently accessed documents for long retention at low cost. You do not need an architect-level design to identify that archival object storage is a better conceptual fit than high-performance block storage.

Suppose a company needs to give an employee read-only access to a group of resources. The important concept is least-privilege identity authorization, not memorizing every permission syntax.

Suppose leadership wants to reduce the risk of a single data-center failure. The foundational concept is distribution across failure domains, not the details of an advanced active-active multi-region design.

Study the “why” behind each category. Service names become easier to remember when they are attached to problems.

Security is a major foundation for both paths

Cloud security starts with understanding who is responsible for what.

The provider secures the underlying cloud infrastructure, but customers remain responsible for many elements of identities, data, configuration, and workloads. The exact division depends on the service model. A customer managing virtual machines retains more operating-system responsibility than a customer using a highly managed SaaS offering.

Both AWS and Azure fundamentals candidates should be able to reason about this boundary.

Identity is another portable concept. Users, groups, roles, service identities, authentication methods, and authorization policies determine who or what can access resources. Least privilege reduces unnecessary permissions. Multi-factor authentication helps protect human accounts. Logging and monitoring help detect misuse.

Encryption, network exposure, compliance, and governance also belong in a foundational understanding. Candidates do not need to become security engineers, but they should recognize that secure cloud adoption is an ongoing operating responsibility rather than a checkbox completed by the vendor.

Pricing knowledge is useful even for technical candidates

Cloud spending can grow quickly when teams do not understand how consumption is measured.

CLF-C02 explicitly includes billing, pricing, and support. Candidates should understand the general logic of pay-as-you-go consumption, pricing models, support choices, cost-estimation tools, and mechanisms that help organizations track spending.

AZ-900 similarly expects awareness of cost management and governance. Candidates should understand that region, service tier, data movement, storage class, runtime, licensing, and reserved or committed consumption can affect spending.

You do not need to memorize a price list. Prices change. The durable skill is recognizing which architectural decisions influence cost and where to look for current estimates.

A useful exercise is to take a small web application and list its cost drivers: compute runtime, database capacity, storage volume, outbound data transfer, monitoring retention, backups, and any premium security or network services. That habit makes later architecture training much easier.

High availability and disaster recovery are different ideas

Fundamentals candidates often encounter reliability terms before they have operated production systems. It is important to distinguish them early.

High availability reduces interruption from expected component failures. Redundant instances, zones, load balancing, and automated replacement can help a service stay available.

Disaster recovery addresses larger failures and restoration after significant disruption. It involves backups, replication, alternate locations, recovery procedures, and business recovery objectives.

A system can be highly available within one region but still have a regional recovery gap. A system can have backups without meeting a short recovery-time objective. These distinctions apply equally to AWS and Azure.

Understanding them at a conceptual level prepares you for later SAA-C03, AZ-104, AZ-305, and other role-based exams.

Governance is where cloud scale becomes an organizational problem

One team can often manage a few cloud resources informally. A large organization cannot.

As usage grows, companies need ways to organize resources, apply policy, control access, track ownership, manage cost, and demonstrate compliance. Both AWS and Azure provide structures and services for these concerns, though the names and implementation models differ.

AZ-900 gives governance a visible place in the fundamentals blueprint. AWS Cloud Practitioner also expects candidates to understand security, compliance, account-related concepts, and cost management at a high level.

The underlying problem is portable: cloud makes resource creation easy, so organizations need guardrails that keep speed from becoming chaos.

A foundational candidate should understand why tags or labels matter, why policy can be preferable to manual review, why centralized logging helps compliance, and why separate environments reduce accidental impact.

Which exam is better for a nontechnical professional?

Both can work, but the answer should follow the environment you work in.

A salesperson, project manager, recruiter, finance professional, business analyst, or compliance stakeholder working with AWS teams may get more immediate value from CLF-C02. It provides a broad AWS vocabulary and includes pricing, support, security, and service awareness without expecting implementation skills.

The same types of professionals in a Microsoft-centered organization may prefer AZ-900. Azure terminology, management structures, identity concepts, governance, and service categories will appear in many enterprise conversations.

If you regularly interact with both vendors, taking one certification deeply and then studying the other may be more useful than trying to memorize both catalogs simultaneously. The second becomes easier because the underlying cloud concepts are already familiar.

Which exam is better for an aspiring cloud engineer?

Again, the next role matters more than the badge.

If you plan to pursue AWS architecture, development, operations, security, or data work, CLF-C02 can be a gentle introduction. However, technically experienced candidates may choose to move directly into a role-based AWS certification if they already understand foundational concepts.

If you plan to become an Azure administrator, network engineer, architect, security professional, data specialist, or AI developer, AZ-900 provides a map of Azure before role-specific study. Experienced professionals may also skip it and move directly to AZ-104, AZ-305, or another relevant path.

Neither foundational certification is a mandatory prerequisite for advanced exams. Treat it as a learning tool, not a gate.

Hands-on practice should remain lightweight but real

Even though these are foundational exams, small practical exercises improve retention.

In AWS, create a sandbox account under appropriate controls, browse the management console, inspect regions, examine identity concepts, explore object storage, view cost tools, and observe monitoring interfaces. You do not need to build a complex application to understand how the categories connect.

In Azure, explore subscriptions, resource groups, regions, the portal, identity, storage, networking, monitoring, policy, and cost-management concepts. Create a few low-cost or free resources if appropriate, then delete them and observe how resource organization works.

The point is not to become an administrator. The point is to replace abstract vocabulary with concrete mental models.

Avoid overstudying retired or advanced details

Cloud platforms change quickly. A foundational study plan should prioritize current official objectives and stable concepts.

Do not memorize every service announcement. Do not spend hours on advanced networking features that belong in professional engineering exams. Do not build a study guide from old screenshots and assume the provider has not changed names or interfaces.

Instead, use the current blueprint as a boundary. Learn enough surrounding context to understand the objective, but keep the depth proportional to the exam.

This is also why internal comparison resources can be useful. ExamSnap’s AWS, Azure, and Google Cloud comparison can help place the two providers in a broader context without turning foundational preparation into a multi-cloud architecture project.

CLF-C02 has published exam logistics that can guide pacing

AWS currently publishes a 90-minute duration and 65 questions for CLF-C02, with the official guide indicating 50 scored and 15 unscored questions and a minimum scaled passing score of 700.

Those numbers can help candidates plan practice sessions, but they should not become a rigid seconds-per-question rule. Some questions are simple recognition; others require careful reading of a short scenario.

A better approach is to build enough concept fluency that straightforward questions are answered efficiently, leaving time for ambiguous wording. During review, focus on questions where you changed your answer because that often reveals a weak distinction.

For AZ-900, use Microsoft’s current exam page and exam-experience guidance for logistics near your scheduled date rather than relying on old blog posts. The most stable preparation target is the current skills-measured outline.

The next certification should follow the role you want

The real value of a fundamentals exam is what it helps you do next.

After CLF-C02, a candidate interested in AWS architecture might prepare for SAA-C03. Someone interested in operations may pursue the current CloudOps path. Developers, data engineers, security specialists, and AI professionals have different AWS routes.

After AZ-900, an Azure operations candidate may move toward AZ-104. An architecture candidate can build toward AZ-305 after gaining the necessary design context. Networking, security, data, Power Platform, and AI each have their own Microsoft role tracks.

Do not build a certification plan as a ladder where everyone must climb the same rungs. Build it as a map from current skill to target responsibility.

Multi-cloud learners should compare concepts, not memorize translations

A common multi-cloud study technique is to create a table saying “AWS service X equals Azure service Y.” That can be helpful at the category level, but exact one-to-one mappings are often misleading.

Two services may both be called serverless but differ in triggers, scaling behavior, integration, networking, deployment model, or operational limits. Two database products may look similar yet make different consistency or management trade-offs.

For fundamentals, compare categories: identity, compute, storage, databases, networking, observability, governance, security, analytics, and cost management. Learn the provider-specific examples inside each category.

This preserves portability while avoiding false equivalence.

A four-week foundation plan can be simple

During the first week, learn cloud concepts, shared responsibility, elasticity, availability, service models, and the basic economics of cloud.

During the second week, learn the major service categories for your chosen provider and practice identifying which category fits common scenarios.

During the third week, focus on identity, security, governance, monitoring, pricing, support, and compliance concepts. These are often where candidates who only memorize compute and storage names become weak.

During the fourth week, use practice questions diagnostically. Track why incorrect answers were wrong. Revisit weak objective areas, then complete a timed mock that resembles the current exam format.

If you are studying both CLF-C02 and AZ-900, do not duplicate the portable concepts. Study them once, then create separate provider-specific notes for terminology and ecosystem details.

Service categories should become mental models

One of the most durable outcomes of fundamentals study is a set of mental models that survive vendor changes.

Compute asks: where does application code run, how much control does the customer need, and how should capacity scale? Storage asks: how is data accessed, how durable must it be, how quickly must it be retrieved, and how long should it be retained? Networking asks: which systems need to communicate, which paths should remain private, and where should access be restricted? Databases ask: what consistency, query, transaction, scale, and operational characteristics does the workload need?

Identity asks who or what is making a request and what that identity should be allowed to do. Observability asks how the team knows whether a system is healthy. Governance asks how an organization applies rules consistently. Cost management asks how usage maps to financial responsibility.

When candidates learn categories this way, service names stop feeling arbitrary. AWS and Azure become two implementations of recognizable cloud problems.

A practical exercise is to take ten common requirements and solve them first without provider terms. Only after the category is clear should you map the answer to AWS or Azure. This reduces memorization and improves scenario reasoning.

Shared responsibility changes with the service model

Many entry-level candidates can repeat the phrase “shared responsibility” but struggle to apply it.

The key is that responsibility shifts depending on how much of the stack the provider manages. With infrastructure-style services, the customer retains substantial responsibility for operating systems, applications, identity, configuration, and data. With a managed database, the provider manages more of the underlying infrastructure, but the customer still owns access, data classification, application behavior, and many configuration choices. With SaaS, the provider manages even more of the stack, yet customers still control users, data, configuration, and business processes.

This is important for both CLF-C02 and AZ-900 because security questions often hinge on the boundary.

A useful test is to choose any cloud service and ask five questions: Who patches the operating system? Who controls user access? Who chooses the data classification? Who configures network exposure? Who monitors suspicious activity? The answers will not always be identical, and that is the point.

Understanding the boundary prepares candidates for more advanced security and architecture exams because it prevents the dangerous assumption that “cloud provider managed” means “customer has no security responsibility.”

Availability concepts should be connected to failure domains

Cloud platforms use regions, zones, and distributed infrastructure to give customers architectural choices. Fundamentals candidates should understand the purpose without getting lost in provider-specific implementation details.

A failure domain is a boundary within which components can fail together. Placing redundant application instances in the same failure domain may protect against one process crash but not a larger infrastructure outage. Spreading components across independent zones can reduce correlated risk. Using multiple regions can address broader failures but increases complexity and cost.

This reasoning helps candidates interpret terms such as high availability, redundancy, durability, and disaster recovery.

It also prevents a common mistake: assuming that because a provider service is “highly available,” the entire application automatically is. Application dependencies, identity, DNS, databases, networking, and deployment practices all affect availability.

At a fundamentals level, you do not need to design a global recovery topology. You should be able to identify why redundancy exists and why a workload’s architecture determines the protection it receives.

Compliance services do not transfer accountability

Both AWS and Microsoft publish compliance programs, certifications, documentation, and tooling that can help customers meet regulatory requirements. A foundational candidate should understand what that assistance means and what it does not mean.

A provider may operate infrastructure that has been assessed against a standard, but the customer still needs to configure workloads appropriately, control access, classify data, retain evidence, and follow the organization’s own compliance processes.

A compliant cloud platform does not make every workload compliant by default.

This distinction matters in scenarios involving healthcare data, financial records, government requirements, or privacy obligations. The right answer often includes selecting appropriate services and regions, applying security controls, maintaining logs, and following governance processes rather than simply choosing a provider that advertises a certification.

Support and operational responsibility become more important after the exam

CLF-C02 explicitly includes support knowledge, while AZ-900 introduces management and monitoring concepts that lead into day-to-day operations. These topics can feel less exciting than compute or AI, but they are part of real cloud use.

An organization needs to know what assistance is available when a production service fails, who can open support cases, what telemetry should be collected, and how incidents are escalated. It also needs cost alerts, ownership tags, policy controls, and documented responsibilities.

Foundational candidates should therefore resist the idea that cloud is purely a technical product catalog. Cloud adoption is an operating model. People need roles, processes, budgets, controls, and support mechanisms.

This becomes obvious in larger environments where dozens of teams share the same provider. Without governance and operational processes, a technically flexible platform can become difficult to control.

Fundamentals study can improve interview performance

Even when an employer does not require CLF-C02 or AZ-900, the preparation can strengthen early-career interviews if the candidate turns memorized concepts into clear explanations.

Instead of saying “I know S3” or “I know Azure Storage,” explain why object storage is appropriate for large-scale unstructured data, how access should be controlled, and why lifecycle policies can reduce cost. Instead of saying “I know IAM,” explain authentication, authorization, least privilege, and why workload identities should not rely on hard-coded credentials.

For a support or junior cloud role, being able to explain these concepts clearly demonstrates that you can reason about systems rather than only repeat documentation.

The certification badge may help a résumé pass a filter, but the interview value comes from the underlying understanding.

Be careful with certification comparisons based only on exam price or question count

Candidates often compare foundational exams by fee, duration, or number of questions. Those details matter for scheduling, but they do not determine career value.

The better comparison is learning relevance. Which provider appears in the jobs you want? Which platform can you practice in? Which certification leads naturally into the next role you want? Which ecosystem does your current employer use?

An exam that is slightly cheaper but unrelated to your work may deliver less value than the one that connects directly to your next project.

Logistics also change over time. Use current provider pages when scheduling rather than making a long-term learning decision based on an old fee or test format.

The best foundation is a small real project plus a clear explanation

A simple project can make either exam’s concepts tangible.

Build a static site or tiny API. Store a file. Create an identity with limited access. Enable basic monitoring. Review the bill or cost-estimation interface. Add a tag or organizational label. Write down what the cloud provider manages and what you manage.

Then explain the architecture to someone who has never used the platform. If you can describe the purpose of each component without relying on acronyms, you probably understand it.

The project does not need to be impressive. Its value is that it connects cloud concepts to observable behavior. That connection makes later role-based study much faster because compute, storage, identity, networking, governance, and cost no longer feel abstract.

Build a decision matrix instead of asking which exam is “better”

Choose CLF-C02 if your organization uses AWS, you need AWS vocabulary for a business or technical role, or you plan to continue into AWS certifications.

Choose AZ-900 if your organization uses Azure, you work in the Microsoft ecosystem, or your next certification is likely to be Azure role-based.

Choose both if you genuinely work across both platforms, support multi-cloud customers, or need to compare cloud proposals from multiple vendors.

Skip a fundamentals exam if you already have strong cloud experience and the credential does not add meaningful learning or career value. A more advanced role-based exam may be a better use of time.

The goal is not to accumulate the easiest badges. It is to create a learning sequence that makes your next responsibility easier to perform.

Cloud foundations are most valuable when they change how you reason

A candidate who finishes CLF-C02 or AZ-900 should be able to hear a cloud discussion and ask better questions.

Where is the workload running? What data does it store? Who can access it? How does it recover? How is it monitored? What drives its cost? Which responsibilities belong to the customer? Which policy or compliance requirements constrain the design?

Those questions are more valuable than knowing hundreds of product names. They are the beginning of cloud architecture thinking.

CLF-C02 teaches that language through AWS. AZ-900 teaches it through Azure. Either can be a strong first step when it is connected to hands-on curiosity and a clear next role.