Cloud Technology and Services
Ways to Access, Deploy, and Operate AWS
ImportantChoose among interactive, programmatic, and infrastructure-as-code methods, and recognize cloud, hybrid, and on-premises deployment models.
Aligned to the current CLF-C02 exam guide, verified August 15, 2026.
Why this matters
CLF-C02 expects you to select an AWS access or deployment method from the business need—not to memorize commands or write templates.
Must Know
- The AWS Management Console is a browser-based interface that is useful for exploration, visual inspection, and occasional operations.
- AWS APIs are the underlying programmatic interfaces. The AWS CLI invokes them from a command line, while AWS SDKs let application code invoke them in a programming language.
- Infrastructure as code (IaC), such as AWS CloudFormation templates, defines resources so environments can be created and updated consistently.
- A cloud deployment runs in a cloud environment. A hybrid deployment connects cloud resources with retained on-premises systems. An on-premises deployment remains in facilities operated by the organization.
Compare and Distinguish
- Console vs CLI: use the console for human, visual, or one-time work; use the CLI when a repeatable script or command-line workflow is the better fit.
- CLI vs SDK: the CLI is a command-line tool; an SDK embeds AWS service calls in application code. Both use AWS APIs.
- Programmatic access vs IaC: a script can perform operations, while IaC declares the desired infrastructure and manages it as a repeatable stack.
- Hybrid vs multi-Region: hybrid describes use of both on-premises and cloud environments; multi-Region describes use of more than one AWS Region.
Scenario examples
- Scenario: An administrator wants to inspect one resource visually and make an occasional change. Think: The AWS Management Console is a natural fit.
- Scenario: A development team must create the same network and application resources for test and production. Think: Define the resources with infrastructure as code such as AWS CloudFormation.
- Scenario: A factory keeps latency-sensitive systems on its premises while using AWS analytics services. Think: This is a hybrid deployment model.
Exam traps
- Programmatic does not automatically mean IaC. An SDK call can change a resource without declaring the complete desired environment.
- Using AWS services from an on-premises application makes the overall model hybrid; it does not make the on-premises servers an Availability Zone.
- IaC improves consistency and repeatability, but permissions, testing, and change review still matter.
Key takeaways
- Human visual task: console. Repeatable command workflow: CLI. Application integration: SDK or API.
- Repeatable resource environments: infrastructure as code.
- Cloud plus retained on-premises systems: hybrid.
How it works
- A person or process authenticates, receives authorization through AWS permissions, and invokes service operations through a chosen interface.
- With IaC, the template becomes a repeatable definition. AWS compares requested changes with the managed stack and coordinates resource operations.
When to use it
- Use the console to learn, inspect, and perform infrequent visual tasks.
- Use the CLI, SDKs, or APIs for repeatable operations and application integration.
- Use CloudFormation when the infrastructure itself must be recreated or updated consistently.
- Use a hybrid model when business or technical constraints require both on-premises and AWS environments.
Security and governance implications
- Every access method is governed by authentication and authorization. Prefer temporary role credentials and least privilege over embedded long-lived keys.
- Review IaC changes because repeatable automation can also repeat an unsafe configuration.
Troubleshooting signals
- When an operation fails, first distinguish authentication, authorization, region selection, and resource-state issues from a problem with the interface itself.
- When environments drift, compare the deployed resources with the IaC definition instead of relying on manual recollection.
More detail
- AWS service operations are exposed through APIs. The console, CLI, SDKs, and automation services provide different interfaces to those capabilities.
- CloudFormation templates describe resources and their relationships. CloudFormation creates a stack, tracks its resources, and applies reviewed updates.
- AWS Outposts can place AWS infrastructure and services at an on-premises location for supported hybrid needs. At this level, recognize its hybrid role rather than implementation details.
Ready for the quiz?
- Can you explain why an SDK and CloudFormation solve different kinds of automation?
- Which method would you choose for a one-time visual inspection?
- Can you distinguish a hybrid deployment from a multi-Region deployment?
Related objectives
- D3.1