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 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== | ||
| Line 55: | Line 54: | ||
Identify where to find AWS compliance information: | Identify where to find AWS compliance information: | ||
*Locations of lists of recognized available compliance controls (for example, [[HIPPA]], | *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 74: | Line 73: | ||
* [[Multi-Factor Authentication]] (MFA) | * [[Multi-Factor Authentication]] (MFA) | ||
* [[AWS Identity and Access Management]] (IAM) | * [[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 [[AWS Trusted Advisor]] | Know that security checks are a component of [[AWS Trusted Advisor]] | ||
| Line 100: | Line 99: | ||
Identify different types of cloud deployment models: | Identify different types of cloud deployment models: | ||
* All in with cloud/cloud native | * All in with cloud/cloud native | ||
| − | * | + | * Hybrid |
| − | * | + | * On-premises |
Identify connectivity options: | Identify connectivity options: | ||
| Line 109: | Line 108: | ||
===3.2 Define the AWS global infrastructure=== | ===3.2 Define the AWS global infrastructure=== | ||
| − | Describe the relationships among | + | Describe the relationships among Regions, Availability Zones, and Edge Locations. |
Describe how to achieve high availability through the use of multiple Availability Zones: | Describe how to achieve high availability through the use of multiple Availability Zones: | ||
| − | * Recall that high availability is achieved by using multiple | + | * Recall that high availability is achieved by using multiple Availability Zones |
* Recognize that Availability Zones do not share single points of failure | * Recognize that Availability Zones do not share single points of failure | ||
Describe when to consider the use of multiple AWS Regions: | Describe when to consider the use of multiple AWS Regions: | ||
| − | * | + | * Disaster recovery/business continuity |
| − | * | + | * Low latency for end-users |
| − | * | + | * Data sovereignty |
Describe at a high level the benefits of Edge Locations: | Describe at a high level the benefits of Edge Locations: | ||
| Line 129: | Line 128: | ||
Identify AWS compute services: | Identify AWS compute services: | ||
* Recognize there are different compute families | * Recognize there are different compute families | ||
| − | * Recognize the different services that provide compute (for example, | + | * Recognize the different services that provide compute (for example, AWS Lambda |
| − | compared to Amazon Elastic Container Service (Amazon | + | compared to Amazon Elastic Container Service (Amazon ECS), or Amazon EC2, etc.) |
* Recognize that elasticity is achieved through [[Auto Scaling]] | * Recognize that elasticity is achieved through [[Auto Scaling]] | ||
* Identify the purpose of load balancers | * Identify the purpose of load balancers | ||
Advertising:
