Skip to content

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 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

Compute Architecture Options

Storage Architecture Options

Database Architecture Options

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

  1. Loose Coupling: Design independent, loosely coupled components
  2. High Cohesion: Group related functionality together
  3. Separation of Concerns: Separate different aspects of the system
  4. Single Responsibility: Each component has one well-defined purpose
  5. DRY (Don't Repeat Yourself): Avoid duplication
  6. KISS (Keep It Simple, Stupid): Prefer simple solutions
  7. YAGNI (You Aren't Gonna Need It): Don't over-engineer
  8. Fail Fast: Detect and handle errors early

Well-Architected Framework Pillars

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

  1. Study Reference Architectures: Understand IBM's reference architectures thoroughly
  2. Hands-On Practice: Design and implement architectures in IBM Cloud
  3. Case Studies: Review real-world customer case studies
  4. Trade-Offs: Understand architectural trade-offs and decision criteria
  5. 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

  1. Read each question twice before answering
  2. Identify the primary requirement in scenario questions
  3. Eliminate obviously wrong answers
  4. Consider all aspects: performance, security, cost, scalability
  5. Look for best practices in answer choices
  6. Watch for keywords like "most," "best," "least expensive"
  7. Flag uncertain questions for review
  8. Manage time - don't spend too long on single questions
  9. Review flagged questions if time permits
  10. Trust your architectural judgment

Additional Learning Resources

IBM Cloud Architecture Center

Training and Courses

Case Studies and Customer Stories

Community and Support

Books and Whitepapers

Important Exam Topics by Priority

High Priority (Study First)

  1. VPC architecture and design
  2. Multi-zone high availability patterns
  3. Security architecture and IAM design
  4. Compute service selection (IKS, OpenShift, Code Engine)
  5. Database architecture and selection
  6. Network architecture (load balancers, gateways, connectivity)
  7. Disaster recovery planning
  8. Microservices architecture patterns
  9. Storage architecture and selection
  10. Cost optimization strategies

Medium Priority (Study Second)

  1. Serverless architecture patterns
  2. Hybrid cloud connectivity (Direct Link, VPN)
  3. Event-driven architecture
  4. API management architecture
  5. DevOps and CI/CD architecture
  6. Monitoring and observability architecture
  7. Data architecture and analytics
  8. Multi-cloud architecture
  9. Performance optimization techniques
  10. Compliance and governance architecture

Lower Priority (If Time Permits)

  1. Specific Watson service architectures
  2. IoT architecture patterns
  3. Edge computing with Satellite
  4. Advanced networking scenarios
  5. VMware solutions architecture
  6. Blockchain architecture
  7. 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.