InterviewStack.io LogoInterviewStack.io
☁️

Cloud & Infrastructure Topics

Cloud platform services, infrastructure architecture, Infrastructure as Code, environment provisioning, and infrastructure operations. Covers cloud service selection, infrastructure provisioning patterns, container orchestration (Kubernetes), multi-cloud and hybrid architectures, infrastructure cost optimization, and cloud platform operations. For CI/CD pipeline and deployment automation, see DevOps & Release Engineering. For cloud security implementation, see Security Engineering & Operations. For data infrastructure design, see Data Engineering & Analytics Infrastructure.

Google Cloud Platform Services and Architecture

Google Cloud Platform's core services and architecture: Compute Engine, Cloud Run, GKE, Cloud Storage, VPC, and BigQuery-adjacent managed services. Covers GCP service selection, networking and IAM specifics, and reference patterns for building on the platform. For provider-agnostic compute, storage, or networking concepts, see the cross-cloud entries.

0 questions

Infrastructure Scaling, Capacity Planning, and High Availability

Making infrastructure grow and stay up: horizontal and vertical scaling, autoscaling, load balancing, capacity planning and forecasting, and high-availability and redundancy design. Covers sizing systems for demand, distributing load, and eliminating single points of failure so services remain available as they scale. The reliability-and-growth discipline.

0 questions

Cloud Service and Deployment Models

The foundational service models (IaaS, PaaS, SaaS, FaaS) and deployment models (public, private, hybrid, community cloud) and when each is appropriate. Covers the shared-responsibility boundary, on-demand elasticity, the core value proposition of cloud versus on-premises, and how service-model choice shifts operational ownership. The conceptual entry point before any provider-specific or architectural depth.

0 questions

AWS Core Services and Architecture

Amazon Web Services' core service catalog and how the pieces compose into a working system: EC2, Lambda, S3, VPC, IAM, RDS, and the managed-service ecosystem. Covers service selection within AWS, common reference architectures, the AWS Well-Architected Framework pillars, and operational patterns specific to the platform. For provider-agnostic compute or storage trade-offs, see the cross-cloud entries.

0 questions

Cloud Compute Options and Trade-offs

Choosing among compute abstractions independent of provider: virtual machines, containers, managed container services, serverless functions, and bare metal. Covers the cost, control, cold-start, scaling, and operational trade-offs of each model, and how workload characteristics (latency, statefulness, burstiness) drive the decision. Managed-versus-self-managed reasoning lives here.

0 questions

Infrastructure Strategy and Technology Selection

Setting technical direction for infrastructure and deciding what to build on. Covers infrastructure vision and long-term roadmap, modernization and technical-debt strategy, platform decisions, and organizational and governance considerations, alongside the decision framework for adopting or retiring technology: build-versus-buy-versus-cloud-versus-on-premises trade-offs, vendor and platform evaluation, technology-portfolio rationalization, requirements-driven service selection, and weighing total cost of ownership and risk. The leadership-altitude discipline of directing an infrastructure estate over time and justifying its major technology choices to stakeholders.

0 questions

Cloud Architecture Design Principles and Trade-offs

The reasoning patterns for architecting cloud systems: reliability, scalability, security, performance, and cost as competing pillars, plus resilience patterns, well-architected design reviews, and scenario-based decision making. Covers how to justify architectural choices, evaluate trade-offs under real constraints, and design for failure. Provider-agnostic design thinking rather than a specific service catalog.

0 questions

Cloud Cost Optimization and FinOps

Controlling and optimizing cloud spend: cost modeling and forecasting, rightsizing, reserved capacity and savings plans, autoscaling for cost, tagging and chargeback, and the FinOps operating model. Covers building the business justification for infrastructure spend and continuously driving efficiency at scale without sacrificing reliability. Cost as a first-class architectural concern.

18 questions

Multi-Cloud and Hybrid Cloud Architecture

Designing systems that span multiple cloud providers or bridge cloud and on-premises. Covers cloud-agnostic abstraction, workload placement, cross-cloud networking and identity, data gravity, resilience across regions and providers, and the operational cost of avoiding lock-in versus the risk of accepting it. Includes multi-region resilience patterns.

0 questions
Page 1/2