The AWS SAP-C01 exam preparation guide is designed to provide candidates with necessary information about the AWS-SAP exam. It includes exam summary, sample questions, practice test, objectives and ways to interpret the exam objectives to enable candidates to assess the types of questions-answers that may be asked during the AWS Certified Solutions Architect - Professional exam.
It is recommended for all the candidates to refer the SAP-C01 objectives and sample questions provided in this preparation guide. The AWS-SAP certification is mainly targeted to the candidates who want to build their career in Architect domain and demonstrate their expertise. We suggest you to use practice exam listed in this cert guide to get used to with exam environment and identify the knowledge areas where you need more work prior to taking the actual AWS Solutions Architect Professional exam.
AWS SAP-C01 Exam Summary:
|
Exam Name
|
AWS Solutions Architect Professional (AWS-SAP) |
| Exam Code | SAP-C01 |
| Exam Price | $300 USD |
| Duration | 180 minutes |
| Number of Questions | 75 |
| Passing Score | 750 / 1000 |
| Recommended Training / Books | Advanced Architecting on AWS |
| Schedule Exam | PEARSON VUE |
| Sample Questions | AWS SAP-C01 Sample Questions |
| Recommended Practice | AWS Certified Solutions Architect - Professional Practice Test |
AWS-SAP Syllabus:
| Section | Objectives |
|---|---|
Design for Organizational Complexity - 12.5% |
|
| Determine cross-account authentication and access strategy for complex organizations. |
- Analyze the organizational structure - Evaluate the current authentication infrastructure - Analyze the AWS resources at an account level - Determine an auditing strategy for authentication and access |
| Determine how to design networks for complex organizations. |
- Outline an IP addressing strategy for VPCs - Determine DNS strategy - Classify network traffic and security - Determine connectivity needs for hybrid environments - Determine a way to audit network traffic |
| Determine how to design a multi-account AWS environment for complex organizations. |
- Determine how to use AWS Organizations - Implement the most appropriate account structure for proper cost allocation, agility, and security - Recommend a central audit and event notification strategy - Decide on an access strategy |
Design for New Solutions - 31% |
|
| Determine security requirements and controls when designing and implementing a solution. |
- Implement infrastructure as code - Determine prevention controls for large-scale web applications - Determine roles and responsibilities of applications - Determine a secure method to manage credentials for the solutions/applications - Enable detection controls and security services for large-scale applications - Enforce host and network security boundaries - Enable encryption in transit and at rest |
| Determine a solution design and implementation strategy to meet reliability requirements. |
- Design a highly available application environment - Determine advanced techniques to detect for failure and service recoverability - Determine processes and components to monitor and recover from regional service disruptions with regional failover |
| Determine a solution design to ensure business continuity. |
- Architect an automated, cost-effective back-up solution that supports business continuity across multiple AWS Regions - Determine an architecture that provides application and infrastructure availability in the event of a service disruption |
| Determine a solution design to meet performance objectives. |
- Design internet-scale application architectures - Design an architecture for performance according to business objectives - Apply design patterns to meet business objectives with caches, buffering, and replicas |
| Determine a deployment strategy to meet business requirements when designing and implementing a solution. |
- Determine resource provisioning strategy to meet business objectives - Determine a migration process to change the version of a service - Determine services to meet deployment strategy - Determine patch management strategy |
Migration Planning - 15% |
|
| Select existing workloads and processes for potential migration to the cloud. |
- Complete an application migration assessment - Classify applications according to the six Rs (re-host, re-platform, re-purchase, refactor, retire, and retain) |
| Select migration tools and/or services for new and migrated solutions based on detailed AWS knowledge. |
- Select an appropriate database transfer mechanism - Select an appropriate data transfer service - Select an appropriate data transfer target - Select an appropriate server migration mechanism - Apply the appropriate security methods to the migration tools |
| Determine a new cloud architecture for an existing solution. |
- Evaluate business applications and determine the target cloud architecture - Break down the functionality of applications into services - Determine target database platforms |
| Determine a strategy for migrating existing on-premises workloads to the cloud. |
- Determine the desired prioritization strategy of the organization - Analyze data volume and rate of change to determine a data transfer strategy - Evaluate cutover strategies - Assess internal and external compliance requirements for a successful migration |
Cost Control - 12.5% |
|
| Select a cost-effective pricing model for a solution. |
- Purchase resources based on usage requirements - Identify when to use different storage tiers |
| Determine which controls to design and implement that will ensure cost optimization. |
- Determine an AWS-generated cost allocation tags strategy that allows mapping cost to business units - Determine a mechanism to monitor when underutilized resources are present - Determine a way to manage commonly deployed resources to achieve governance - Define a way to plan costs that do not exceed the budget amount |
| Identify opportunities to reduce cost in an existing architecture. |
- Distinguish opportunities to use AWS Managed Services - Determine which services are most cost-effective in meeting business objectives |
Continuous Improvement for Existing Solutions- 29% |
|
| Troubleshoot solutions architectures. |
- Assess an existing application architecture for deficiencies - Analyze application and infrastructure logs - Test possible solutions in non-production environment |
| Determine a strategy to improve an existing solution for operational excellence. |
- Determine the most appropriate logging and monitoring strategy - Recommend the appropriate AWS offering(s) to enable configuration management automation |
| Determine a strategy to improve the reliability of an existing solution. |
- Evaluate existing architecture to determine areas that are not sufficiently reliable - Remediate single points of failure - Enable data replication, self-healing, and elastic features and services - Test the reliability of the new solution |
| Determine a strategy to improve the performance of an existing solution. |
- Reconcile current performance metrics against performance targets - Identify and examine performance bottlenecks - Recommend and test potential remediation solutions |
| Determine a strategy to improve the security of an existing solution. |
- Evaluate AWS Secrets Manager strategy - Audit the environment for security vulnerabilities - Enable manual and/or automated responses to the detection of vulnerabilities |
| Determine how to improve the deployment of an existing solution. |
- Evaluate appropriate tooling to enable infrastructure as code - Evaluate current deployment processes for improvement opportunities - Test automated deployment and rollback strategies |