IBM Cloud Solution Architect Certification - Fact Sheet¶
Quick Reference¶
- Certification: IBM Certified Solution Architect - Cloud v2
- Exam Code: C1000-172
- Duration: 90 minutes
- Questions: 60 multiple choice
- Passing Score: 70%
- Cost: $200 USD
- Language: English
- Delivery: Pearson VUE (online or test center)
- Prerequisites: None (recommended 3+ years architecture experience)
- Recertification: Every 3 years
- Target Audience: Cloud architects, solution architects, technical architects, enterprise architects
Official Resources¶
- π Exam Homepage
- π IBM Cloud Architecture Center
- π IBM Cloud Documentation
- π IBM Cloud Reference Architectures
- π IBM Cloud Best Practices
- π IBM Cloud Well-Architected Framework
- π IBM Cloud Garage Method
- π IBM Cloud Learning
- π Pearson VUE Testing
- π IBM Cloud Certification Hub
Exam Domains¶
1. Architecture Design Principles (25%)¶
- Well-Architected Framework principles
- Cloud-native architecture patterns
- Microservices and service-oriented architecture
- Event-driven architecture
- Serverless architecture patterns
- Multi-tier application architecture
- API-first design approach
- Domain-driven design principles
- Architecture trade-offs and decision making
Domain Resources: - π IBM Cloud Architecture Framework - π Cloud Architecture Principles - π Microservices Architecture - π Event-Driven Architecture - π Serverless Architecture - π API-First Design - π Domain-Driven Design - π Architecture Decision Records
2. Infrastructure Architecture (20%)¶
- VPC design and implementation
- Network architecture (subnets, routing, VPNs)
- Load balancing strategies
- Compute service selection (VMs, Kubernetes, serverless)
- Storage architecture (Block, File, Object)
- Hybrid and multi-cloud connectivity
- Edge computing and CDN
- Infrastructure as Code (Terraform, Schematics)
Infrastructure Resources: - π VPC Architecture - π Network Architecture - π VPC Documentation - π VPC Design Guide - π Load Balancer Best Practices - π Compute Services - π Storage Solutions - π Hybrid Cloud Architecture - π Direct Link - π Transit Gateway - π VPN Gateway - π Terraform on IBM Cloud - π Schematics
3. Application and Data Architecture (20%)¶
- Application architecture patterns
- Container orchestration (Kubernetes, OpenShift)
- Serverless computing (Code Engine, Functions)
- Database selection and design
- Data persistence strategies
- Caching architectures
- Message queuing and event streaming
- API gateway and management
- Integration patterns
Application Architecture Resources: - π Application Architecture - π Container Architecture - π Kubernetes Service - π OpenShift on IBM Cloud - π Code Engine - π Cloud Functions - π Database Services - π Data Architecture - π Caching Strategies - π Event Streams Architecture - π API Management - π Integration Architecture
4. Security Architecture (15%)¶
- Zero Trust security model
- Identity and Access Management (IAM) design
- Network security architecture
- Data protection and encryption
- Key management strategies
- Security compliance and governance
- Threat detection and response
- Security monitoring and logging
- DDoS protection and WAF
Security Architecture Resources: - π Security Architecture - π Zero Trust Architecture - π IAM Architecture - π IAM Best Practices - π Network Security - π Security Groups - π Data Encryption - π Key Protect - π Hyper Protect Crypto Services - π Secrets Manager - π Security and Compliance Center - π Certificate Manager - π Cloud Internet Services - π Activity Tracker
5. High Availability and Disaster Recovery (10%)¶
- Multi-zone region (MZR) architecture
- Disaster recovery strategies
- Backup and restore planning
- Business continuity planning
- RTO and RPO requirements
- Failover and failback procedures
- Data replication strategies
- Testing and validation
HA/DR Resources: - π High Availability Architecture - π Disaster Recovery Architecture - π High Availability Overview - π Disaster Recovery Overview - π Regions and Zones - π Backup Services - π Veeam Backup - π Database Backup Strategies
6. Performance and Scalability (10%)¶
- Scalability patterns (horizontal, vertical)
- Auto-scaling strategies
- Performance optimization techniques
- Caching strategies
- CDN and edge computing
- Database performance tuning
- Application performance monitoring
- Capacity planning
- Load testing strategies
Performance Resources: - π Scalability Architecture - π Auto-Scaling - π Performance Optimization - π CDN with Cloud Internet Services - π Caching Best Practices - π Monitoring - π Log Analysis
Core Architecture Components¶
Network Architecture Components¶
- π Virtual Private Cloud (VPC)
- π Subnets and IP Addressing
- π Security Groups
- π Network ACLs
- π Application Load Balancer
- π Network Load Balancer
- π Public Gateway
- π Floating IPs
- π VPN Gateway
- π Direct Link
- π Transit Gateway
- π Cloud Internet Services
- π Virtual Private Endpoints
Compute Architecture Options¶
- π Virtual Servers for VPC
- π Bare Metal Servers
- π Kubernetes Service
- π OpenShift
- π Satellite
- π Code Engine
- π Cloud Functions
- π VMware Solutions
Storage Architecture Options¶
- π Block Storage for VPC
- π File Storage for VPC
- π Object Storage
- π Backup for VPC
- π Mass Data Migration
Database Architecture Options¶
- π Db2 on Cloud
- π Db2 Warehouse
- π Cloudant
- π Databases for PostgreSQL
- π Databases for MySQL
- π Databases for MongoDB
- π Databases for Redis
- π Databases for Elasticsearch
- π Databases for etcd
- π DataStax
Integration and Messaging¶
DevOps and Automation¶
Observability Services¶
Architecture Scenarios and Solutions¶
Scenario 1: Multi-Tier Web Application Architecture¶
Challenge: Design a highly available, scalable web application for e-commerce.
Architecture Components: - VPC with multi-zone deployment (3 zones) - Application Load Balancer for traffic distribution - Auto-scaling instance groups for web tier - Kubernetes cluster for application tier - PostgreSQL with High Availability for data tier - Redis for session and cache management - Object Storage for static assets and media - CDN (Cloud Internet Services) for global content delivery - Event Streams for asynchronous processing - Code Engine for background jobs - Monitoring and Log Analysis for observability - Activity Tracker for audit logging
Architecture Decisions: - Use MZR for 99.99% availability - Implement auto-scaling based on CPU and memory metrics - Use read replicas for database read operations - Implement circuit breakers and retry logic - Enable encryption at rest and in transit - Use IAM policies with least privilege
Resources: - π Web Application Reference Architecture - π E-Commerce Architecture
Scenario 2: Hybrid Cloud Architecture¶
Challenge: Connect on-premises data center with IBM Cloud securely and reliably.
Architecture Components: - VPC in IBM Cloud - Direct Link Dedicated or Connect for private connectivity - VPN Gateway as backup connection - Transit Gateway for multi-VPC connectivity - Satellite for extending IBM Cloud to on-premises - VMware Solutions for workload migration - Hybrid Cloud Mesh for application connectivity - Key Protect for key management - Secrets Manager for credential management
Architecture Decisions: - Use Direct Link for high-bandwidth, low-latency connectivity - Implement redundant connections for high availability - Use VPN as backup for Direct Link - Deploy firewall appliances in VPC - Implement consistent IAM across environments - Use Cloud Internet Services for DNS and DDoS protection
Resources: - π Hybrid Cloud Architecture - π Hybrid Cloud Connectivity - π Satellite Architecture
Scenario 3: Microservices on Kubernetes¶
Challenge: Migrate monolithic application to microservices architecture.
Architecture Components: - OpenShift cluster with multi-zone deployment - Service mesh (Istio) for service-to-service communication - Container Registry for image management - API Connect for API gateway - Event Streams for event-driven communication - PostgreSQL for transactional databases - Cloudant for document storage - Redis for distributed caching - Object Storage for file storage - Continuous Delivery for CI/CD - Monitoring and Log Analysis - Security and Compliance Center
Architecture Decisions: - Decompose monolith using domain-driven design - Implement API gateway pattern - Use event-driven communication for loose coupling - Implement circuit breaker and bulkhead patterns - Use container health checks and readiness probes - Implement distributed tracing - Use GitOps for deployment automation
Resources: - π Microservices Reference Architecture - π Container Workload Architecture
Scenario 4: Serverless Event-Driven Architecture¶
Challenge: Build scalable event-driven system for IoT data processing.
Architecture Components: - Code Engine for event processing - Cloud Functions for real-time transformations - Event Streams (Kafka) for event ingestion - Cloudant for storing processed data - Object Storage for raw data archival - Watson IoT Platform for device management - Time Series Database for metrics - Grafana for visualization - API Connect for external API access
Architecture Decisions: - Use serverless for automatic scaling - Implement dead letter queues for failed events - Use event sourcing pattern - Implement CQRS for read/write separation - Use partitioning for parallel processing - Implement data retention policies - Use monitoring for function execution metrics
Resources: - π Serverless Reference Architecture - π Event-Driven Architecture - π IoT Architecture
Scenario 5: Data Lake and Analytics Architecture¶
Challenge: Build scalable data lake for analytics and machine learning.
Architecture Components: - Object Storage for data lake storage - SQL Query for serverless SQL analytics - Watson Studio for data science and ML - Db2 Warehouse for data warehousing - DataStage for ETL processes - Cognos Analytics for business intelligence - Watson Machine Learning for model deployment - Databases for PostgreSQL for metadata - Event Streams for real-time data ingestion - Data Refinery for data preparation
Architecture Decisions: - Use zone-based storage tiers for cost optimization - Implement data catalog and metadata management - Use partitioning and bucketing for query performance - Implement data governance and lineage - Use encryption for sensitive data - Implement access controls with IAM - Use monitoring for query performance
Resources: - π Data Architecture - π Analytics Architecture - π Machine Learning Architecture
Scenario 6: Multi-Cloud Architecture¶
Challenge: Design architecture spanning IBM Cloud, AWS, and Azure.
Architecture Components: - VPC in each cloud provider - Satellite for consistent control plane - Transit Gateway for IBM Cloud connectivity - VPN or Direct Connect for AWS connectivity - ExpressRoute for Azure connectivity - Multi-cloud API gateway - Centralized monitoring and logging - Centralized identity management - Multi-cloud backup and DR
Architecture Decisions: - Use Satellite for consistent Kubernetes experience - Implement cloud-agnostic abstractions - Use Terraform for infrastructure as code - Implement centralized logging aggregation - Use global load balancing - Implement data sovereignty requirements - Use cost optimization across clouds
Resources: - π Multi-Cloud Architecture - π Satellite Architecture
Architecture Best Practices¶
Design Principles¶
- Loose Coupling: Design independent, loosely coupled components
- High Cohesion: Group related functionality together
- Separation of Concerns: Separate different aspects of the system
- Single Responsibility: Each component has one well-defined purpose
- DRY (Don't Repeat Yourself): Avoid duplication
- KISS (Keep It Simple, Stupid): Prefer simple solutions
- YAGNI (You Aren't Gonna Need It): Don't over-engineer
- Fail Fast: Detect and handle errors early
Well-Architected Framework Pillars¶
- π Operational Excellence
- π Security
- π Reliability
- π Performance Efficiency
- π Cost Optimization
Network Design Best Practices¶
- Design IP address space carefully (avoid overlap)
- Use multiple availability zones for high availability
- Implement network segmentation with subnets
- Use security groups and ACLs for defense in depth
- Implement bastion hosts for secure access
- Use private endpoints for IBM Cloud services
- Implement DNS resolution strategy
- Plan for network bandwidth requirements
- Use load balancers for traffic distribution
- Implement network monitoring and logging
Compute Selection Guidelines¶
| Workload Type | Recommended Service | Reason |
|---|---|---|
| Legacy Apps | Virtual Servers, VMware | Lift and shift |
| Container Apps | Kubernetes, OpenShift | Orchestration needed |
| Event-Driven | Code Engine, Functions | Auto-scaling, pay-per-use |
| Batch Processing | Code Engine | Job-based execution |
| High Performance | Bare Metal | Raw compute power |
Database Selection Guidelines¶
| Use Case | Recommended Database | Reason |
|---|---|---|
| Transactional | PostgreSQL, Db2 | ACID compliance |
| Document Store | Cloudant, MongoDB | Flexible schema |
| Caching | Redis | In-memory performance |
| Search | Elasticsearch | Full-text search |
| Time Series | Time Series DB | Time-based queries |
| Graph | Custom solution | Relationship queries |
Security Architecture Best Practices¶
- π Security Best Practices Guide
- Implement defense in depth strategy
- Use IAM for fine-grained access control
- Enable encryption at rest and in transit
- Use Key Protect or HPCS for key management
- Implement network segmentation
- Use security groups and ACLs
- Enable audit logging with Activity Tracker
- Implement vulnerability scanning
- Use Secrets Manager for credentials
- Implement DDoS protection
- Regular security assessments
- Implement least privilege principle
High Availability Best Practices¶
- Deploy across multiple availability zones
- Use managed services with built-in HA
- Implement health checks and auto-recovery
- Use load balancers for traffic distribution
- Design for stateless applications
- Implement auto-scaling
- Use managed databases with automatic failover
- Test failover procedures regularly
- Implement graceful degradation
- Monitor availability metrics
Performance Optimization Best Practices¶
- Right-size compute resources
- Use caching at multiple layers
- Implement CDN for static content
- Optimize database queries and indexes
- Use connection pooling
- Implement asynchronous processing
- Use message queues for decoupling
- Optimize network latency
- Implement compression
- Monitor performance metrics
Cost Optimization Best Practices¶
- π Cost Optimization Guide
- Right-size resources based on actual usage
- Use reserved capacity for predictable workloads
- Implement auto-scaling to match demand
- Delete unused resources
- Use appropriate storage tiers
- Implement data lifecycle policies
- Use serverless for variable workloads
- Tag resources for cost tracking
- Set budget alerts
- Review costs regularly
Architecture Documentation¶
Architecture Decision Records (ADRs)¶
- π ADR Templates
- Document important architectural decisions
- Include context, decision, and consequences
- Capture alternatives considered
- Keep ADRs version controlled
- Review and update as needed
Architecture Diagrams¶
- π IBM Cloud Architecture Diagrams
- Use standard notation (e.g., UML, C4)
- Include different views (logical, physical, deployment)
- Show data flows and integrations
- Highlight security boundaries
- Document network topology
- Use tools like draw.io or Lucidchart
Technical Specifications¶
- System context and boundaries
- Component descriptions
- Interface specifications
- Data models and schemas
- Security controls
- Performance requirements
- Scalability requirements
- Disaster recovery procedures
Exam Tips and Strategies¶
General Preparation¶
- Study Reference Architectures: Understand IBM's reference architectures thoroughly
- Hands-On Practice: Design and implement architectures in IBM Cloud
- Case Studies: Review real-world customer case studies
- Trade-Offs: Understand architectural trade-offs and decision criteria
- Best Practices: Learn IBM Cloud best practices for each domain
Key Study Areas¶
- VPC architecture and networking design
- Multi-zone and multi-region deployment strategies
- Compute service selection criteria
- Database and storage architecture patterns
- Security architecture and IAM design
- High availability and disaster recovery planning
- Microservices and container orchestration
- Serverless architecture patterns
- Hybrid and multi-cloud connectivity
- Performance and scalability strategies
- Cost optimization techniques
- DevOps and automation architecture
Common Pitfalls to Avoid¶
- Overlooking network design and IP address planning
- Not considering availability zone failures
- Ignoring data residency and compliance requirements
- Under-provisioning for peak loads
- Over-architecting simple solutions
- Not planning for disaster recovery
- Ignoring security in architecture design
- Not considering cost implications
- Missing integration and data flow requirements
- Not documenting architectural decisions
Scenario-Based Questions¶
- Read scenarios carefully - identify key requirements
- Look for keywords: "high availability," "cost-effective," "secure," "scalable"
- Consider all architecture layers (network, compute, data, security)
- Think about trade-offs between options
- Consider operational complexity
- Evaluate cost implications
- Think about future scalability needs
Exam Day Tips¶
- Read each question twice before answering
- Identify the primary requirement in scenario questions
- Eliminate obviously wrong answers
- Consider all aspects: performance, security, cost, scalability
- Look for best practices in answer choices
- Watch for keywords like "most," "best," "least expensive"
- Flag uncertain questions for review
- Manage time - don't spend too long on single questions
- Review flagged questions if time permits
- Trust your architectural judgment
Additional Learning Resources¶
IBM Cloud Architecture Center¶
- π All Reference Architectures
- π Architecture Patterns
- π Best Practices
- π Solution Guides
Training and Courses¶
- π IBM Cloud Training Catalog
- π Coursera IBM Cloud Courses
- π IBM Skills Network
- π edX IBM Courses
Case Studies and Customer Stories¶
Community and Support¶
- π IBM Cloud Architecture Forum
- π IBM Developer
- π Stack Overflow IBM Cloud
- π IBM Cloud Blog
Books and Whitepapers¶
Important Exam Topics by Priority¶
High Priority (Study First)¶
- VPC architecture and design
- Multi-zone high availability patterns
- Security architecture and IAM design
- Compute service selection (IKS, OpenShift, Code Engine)
- Database architecture and selection
- Network architecture (load balancers, gateways, connectivity)
- Disaster recovery planning
- Microservices architecture patterns
- Storage architecture and selection
- Cost optimization strategies
Medium Priority (Study Second)¶
- Serverless architecture patterns
- Hybrid cloud connectivity (Direct Link, VPN)
- Event-driven architecture
- API management architecture
- DevOps and CI/CD architecture
- Monitoring and observability architecture
- Data architecture and analytics
- Multi-cloud architecture
- Performance optimization techniques
- Compliance and governance architecture
Lower Priority (If Time Permits)¶
- Specific Watson service architectures
- IoT architecture patterns
- Edge computing with Satellite
- Advanced networking scenarios
- VMware solutions architecture
- Blockchain architecture
- Quantum computing integration
Architecture Checklists¶
Architecture Review Checklist¶
- Requirements clearly defined and documented
- Architecture aligns with business objectives
- All functional requirements addressed
- Non-functional requirements considered (performance, security, scalability)
- Multi-zone deployment for high availability
- Security controls at all layers
- Disaster recovery plan defined
- Cost estimates and optimization considered
- Monitoring and observability planned
- Integration points identified
- Data flows documented
- Compliance requirements addressed
- Scalability strategy defined
- Migration plan (if applicable) documented
- Operational procedures defined
Security Architecture Checklist¶
- IAM policies defined with least privilege
- Network segmentation implemented
- Encryption at rest enabled
- Encryption in transit enforced
- Key management strategy defined
- Secrets management implemented
- Security groups and ACLs configured
- Audit logging enabled
- DDoS protection configured
- Vulnerability scanning planned
- Security monitoring implemented
- Incident response plan defined
- Compliance requirements mapped
- Data classification performed
- Access reviews scheduled
High Availability Checklist¶
- Multi-zone deployment configured
- Load balancers implemented
- Auto-scaling configured
- Health checks defined
- Database replication configured
- Backup strategy defined
- Failover procedures documented
- RTO and RPO defined
- DR testing scheduled
- Monitoring and alerting configured
- Stateless application design
- Circuit breakers implemented
- Retry logic with exponential backoff
- Graceful degradation planned
- Chaos engineering considered
Final Preparation Checklist¶
- Review all reference architectures
- Study IBM Cloud Well-Architected Framework
- Understand VPC networking thoroughly
- Review compute service selection criteria
- Study database and storage options
- Understand security architecture patterns
- Review HA and DR strategies
- Study microservices patterns
- Understand serverless architectures
- Review hybrid cloud connectivity options
- Study cost optimization techniques
- Practice scenario-based questions
- Review architecture decision-making process
- Understand trade-offs between options
- Take practice exams
- Schedule exam appointment
Good luck with your IBM Cloud Solution Architect certification exam!
Remember: Architecture is about making informed trade-offs. Focus on understanding the "why" behind architectural decisions, not just the "what." Consider multiple dimensions - functionality, performance, security, cost, and operational complexity - when evaluating solutions.