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.

Observability and Monitoring Architecture

Building visibility into infrastructure and services: metrics, logs, and traces, dashboards and alerting, SLIs/SLOs, and the design of an observability stack. Covers instrumenting systems for actionable signal, reducing alert noise, and diagnosing production issues from telemetry. Infrastructure-wide observability, distinct from network-specific monitoring.

1 questions

Infrastructure as Code and Automation

Defining, provisioning, and automating infrastructure programmatically. Covers declarative IaC with Terraform and comparable tools like CloudFormation (resource and provider model, state management and remote backends, module design and reuse, workspaces, drift detection, and safe plan/apply workflows), plus the broader automation discipline: provisioning pipelines, golden-image and machine-image building, scripting glue, self-service platforms, and end-to-end environment stand-up. The authoring, lifecycle, and automation of infrastructure code that reduces manual toil across provisioning workflows.

13 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

Containerization and Docker Fundamentals

Packaging applications into containers: images and layers, Dockerfiles, registries, image optimization and security, and the container runtime model. Covers how containers differ from virtual machines, image build and management, and the fundamentals that underpin any orchestration platform. The container primitive before orchestration.

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.

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

12 questions
Page 1/2