Editing AWS Cloud Practitioner
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 1: | Line 1: | ||
| − | + | : https://d1.awsstatic.com/training-and-certification/Docs%20-%20Cloud%20Practitioner/AWS%20Certified%20Cloud%20Practitioner_Exam_Guide_v1.4_FINAL.PDF | |
| − | |||
| − | |||
==Domain 1: Cloud Concepts== | ==Domain 1: Cloud Concepts== | ||
| Line 32: | Line 30: | ||
* Benefits of automation | * Benefits of automation | ||
* Reduce compliance scope (for example, reporting) | * Reduce compliance scope (for example, reporting) | ||
| − | * Managed services (for example, | + | * Managed services (for example, RDS, ECS, EKS, DynamoDB) |
===1.3 Explain the different cloud architecture design principles=== | ===1.3 Explain the different cloud architecture design principles=== | ||
| Line 39: | Line 37: | ||
* Design for failure | * Design for failure | ||
* Decouple components versus monolithic architecture | * Decouple components versus monolithic architecture | ||
| − | * Implement elasticity in the cloud versus | + | * Implement elasticity in the cloud versus on-premises |
* Think parallel | * Think parallel | ||
| + | Version 2.1 CLF-C01 4 | PAGE | ||
==Domain 2: Security and Compliance== | ==Domain 2: Security and Compliance== | ||
===2.1 Define the AWS shared responsibility model=== | ===2.1 Define the AWS shared responsibility model=== | ||
Recognize the elements of the Shared Responsibility Model | Recognize the elements of the Shared Responsibility Model | ||
| − | Describe the customer’s responsibility on | + | Describe the customer’s responsibility on AWS |
* Describe how the customer’s responsibilities may shift depending on the service used | * Describe how the customer’s responsibilities may shift depending on the service used | ||
| − | (for example with | + | (for example with RDS, Lambda, or EC2) |
* Describe AWS responsibilities | * Describe AWS responsibilities | ||
| Line 54: | Line 53: | ||
===2.2 Define AWS Cloud security and compliance concepts=== | ===2.2 Define AWS Cloud security and compliance concepts=== | ||
Identify where to find AWS compliance information: | Identify where to find AWS compliance information: | ||
| − | *Locations of lists of recognized available compliance controls (for example, | + | *Locations of lists of recognized available compliance controls (for example, HIPPA, |
| − | + | SOCs) | |
* Recognize that compliance requirements vary among AWS services | * Recognize that compliance requirements vary among AWS services | ||
At a high level, describe how customers achieve compliance on AWS | At a high level, describe how customers achieve compliance on AWS | ||
| − | * Identify different | + | * Identify different encryption options on AWS (for example, In transit, At rest) |
Describe who enables encryption on AWS for a given service | Describe who enables encryption on AWS for a given service | ||
| Line 66: | Line 65: | ||
* Recognize that logs exist for auditing and monitoring (do not have to understand the | * Recognize that logs exist for auditing and monitoring (do not have to understand the | ||
logs) | logs) | ||
| − | * Define | + | * Define Amazon CloudWatch, AWS Config, and AWS CloudTrail |
Explain the concept of least privileged access | Explain the concept of least privileged access | ||
| Line 72: | Line 71: | ||
Understand the purpose of User and Identity Management: | Understand the purpose of User and Identity Management: | ||
* Access keys and password policies (rotation, complexity) | * Access keys and password policies (rotation, complexity) | ||
| − | * | + | * Multi-Factor Authentication (MFA) |
| − | * | + | * AWS Identity and Access Management (IAM) |
| − | ** | + | ** Groups/users |
| − | ** | + | ** Roles |
| − | ** | + | ** Policies, managed policies compared to custom policies |
* Tasks that require use of root accounts | * Tasks that require use of root accounts | ||
| Line 83: | Line 82: | ||
===2.4 Identify resources for security support=== | ===2.4 Identify resources for security support=== | ||
Recognize there are different network security capabilities: | Recognize there are different network security capabilities: | ||
| − | *Native | + | *Native AWS services (for example, security groups, Network ACLs, AWS WAF) |
* 3 | * 3 | ||
| − | rd party security products from the | + | rd party security products from the AWS Marketplace |
* Recognize there is documentation and where to find it (for example, best practices, | * Recognize there is documentation and where to find it (for example, best practices, | ||
whitepapers, official documents) | whitepapers, official documents) | ||
* AWS Knowledge Center, Security Center, security forum, and security blogs | * AWS Knowledge Center, Security Center, security forum, and security blogs | ||
| − | * | + | * Partner Systems Integrators |
| − | Know that security checks are a component of | + | Know that security checks are a component of AWS Trusted Advisor |
| + | |||
| + | Version 2.1 CLF-C01 5 | PAGE | ||
==Domain 3: Technology== | ==Domain 3: Technology== | ||
| − | + | 3.1 Define methods of deploying and operating in the AWS Cloud | |
| − | Identify at a high level different ways of provisioning and operating in the AWS cloud | + | Identify at a high level different ways of provisioning and operating in the AWS cloud |
| − | + | o Programmatic access, APIs, SDKs, AWS Management Console, CLI, Infrastructure as | |
| − | + | Code | |
| − | Identify different types of cloud deployment models | + | Identify different types of cloud deployment models |
| − | + | o All in with cloud/cloud native | |
| − | + | o Hybrid | |
| − | + | o On-premises | |
| − | + | Identify connectivity options | |
| − | Identify connectivity options | + | o VPN |
| − | + | o AWS Direct Connect | |
| − | + | o Public internet | |
| − | + | 3.2 Define the AWS global infrastructure | |
| − | + | Describe the relationships among Regions, Availability Zones, and Edge Locations | |
| − | + | Describe how to achieve high availability through the use of multiple Availability Zones | |
| − | Describe the relationships among | + | o Recall that high availability is achieved by using multiple Availability Zones |
| − | + | o Recognize that Availability Zones do not share single points of failure | |
| − | Describe how to achieve high availability through the use of multiple Availability Zones | + | Describe when to consider the use of multiple AWS Regions |
| − | + | o Disaster recovery/business continuity | |
| − | + | o Low latency for end-users | |
| − | + | o Data sovereignty | |
| − | Describe when to consider the use of multiple AWS Regions | + | Describe at a high level the benefits of Edge Locations |
| − | + | o Amazon CloudFront | |
| − | + | o AWS Global Accelerator | |
| − | + | 3.3 Identify the core AWS services | |
| − | + | Describe the categories of services on AWS (compute, storage, network, database) | |
| − | Describe at a high level the benefits of Edge Locations | + | Identify AWS compute services |
| − | + | o Recognize there are different compute families | |
| − | + | o Recognize the different services that provide compute (for example, AWS Lambda | |
| − | + | compared to Amazon Elastic Container Service (Amazon ECS), or Amazon EC2, etc.) | |
| − | + | o Recognize that elasticity is achieved through Auto Scaling | |
| − | Describe the categories of services on AWS (compute, storage, network, database) | + | o Identify the purpose of load balancers |
| − | + | Identify different AWS storage services | |
| − | Identify AWS compute services | + | o Describe Amazon S3 |
| − | + | o Describe Amazon Elastic Block Store (Amazon EBS) | |
| − | + | o Describe Amazon S3 Glacier | |
| − | compared to Amazon Elastic Container Service (Amazon | + | o Describe AWS Snowball |
| − | + | o Describe Amazon Elastic File System (Amazon EFS) | |
| − | + | o Describe AWS Storage Gateway | |
| − | + | Identify AWS networking services | |
| − | Identify different AWS storage services | + | o Identify VPC |
| − | + | o Identify security groups | |
| − | + | o Identify the purpose of Amazon Route 53 | |
| − | + | o Identify VPN, AWS Direct Connect | |
| − | + | Identify different AWS database services | |
| − | + | o Install databases on Amazon EC2 compared to AWS managed database | |
| − | |||
| − | |||
| − | Identify AWS networking services | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | Identify different AWS database services | ||
| − | |||
== See also == | == See also == | ||
Advertising:
