How do I approach System Design interview questions?

System Design questions require understanding of core concepts and practice. PracHub provides solutions with explanations to help you master system design interviews.

What difficulty level is this interview question?

This is a medium difficulty System Design question, commonly asked during Technical Screen rounds at Salesforce.

What role is this question designed for?

This question is commonly asked for Software Engineer candidates at Salesforce during technical interviews.

Compare GCP vs AWS and testing strategy | Salesforce Interview Question

Quick Overview

This question evaluates a candidate's understanding of public cloud architecture, including compute models (virtual machines, containers, serverless), storage and networking building blocks, testing and deployment strategies, and trade-offs around portability and vendor lock-in within the System Design domain.

Public Cloud Building Blocks, Compute Choice, and Testing Strategy

Context

Assume you are designing a new stateless HTTP microservice that exposes REST or gRPC endpoints. It will have spiky traffic (for example, a 10x burst during peak hours), aims for 99.9 percent availability, p95 latency under 150 ms, and should be easy to operate by a small team. If your answer depends on different constraints, state how the choice would change.

Tasks

Explain the core building blocks of a public cloud:
- Compute models: virtual machines, containers, serverless
- Storage: object, block, file, databases, cache
- Networking: VPC, subnets, routing, load balancing, API gateway, DNS, security
For the new microservice above, choose among compute options and justify the trade offs. Include when you would pick a different option.
Outline a pragmatic cloud testing strategy covering unit, integration, load and performance, chaos, and delivery strategies such as canary and blue green deployments.
Map roughly equivalent services in GCP and AWS for this workload, and discuss portability, interoperability, and vendor lock in. Provide concrete tactics to reduce lock in and note the trade offs.

Quick Overview

Context

Tasks

Explain the core building blocks of a public cloud:

Compute models: virtual machines, containers, serverless
Storage: object, block, file, databases, cache
Networking: VPC, subnets, routing, load balancing, API gateway, DNS, security

For the new microservice above, choose among compute options and justify the trade offs. Include when you would pick a different option.

Outline a pragmatic cloud testing strategy covering unit, integration, load and performance, chaos, and delivery strategies such as canary and blue green deployments.

Map roughly equivalent services in GCP and AWS for this workload, and discuss portability, interoperability, and vendor lock in. Provide concrete tactics to reduce lock in and note the trade offs.

Compare GCP vs AWS and testing strategy

Quick Overview

Public Cloud Building Blocks, Compute Choice, and Testing Strategy

Context

Tasks

Solution

Comments (0)

Compare GCP vs AWS and testing strategy

Quick Overview

Public Cloud Building Blocks, Compute Choice, and Testing Strategy

Context

Tasks

Solution

Comments (0)