A team is deploying a microservice to multiple environments (dev, staging, prod). They want to use the same container image in all environments but have different configuration values, such as database URLs and feature flags. Which approach should they use?

Externalize configuration using environment variables or configuration files mounted at runtime

Use a compile-time flag to include the correct configuration in the binary

Build a separate image for each environment with the configuration baked in

Store configuration in a shared database and have the service read it at startup

A team manages a critical payment service that must maintain 99.99% availability. They need to deploy a new version that changes the database schema. The database migration is backward-incompatible. The team wants to minimize the risk of a full outage while ensuring that if the new version fails, they can quickly revert. Which deployment strategy should they use?

Canary deployment with a shared database and a schema migration that runs before the new version is released

Rolling deployment with a database migration that runs after all pods are updated

Recreate deployment with a maintenance window and a full database backup

Blue-green deployment with a database that supports both schemas during the transition

In a microservices architecture, how is data typically managed?

All services read and write to one shared database schema.

Data is replicated to every service instance for consistency.

Each service owns its own database or data store.

Data is stored in a global cache accessible to all services.

A development team is deploying microservices to multiple environments (dev, staging, production). They need to manage configuration such as database connection strings and API keys without embedding them in container images. The configuration must be consistent across environments but allow environment-specific overrides. Which approach should they use?

Store configuration in a public GitHub repository

Embed configuration in the container image at build time

Externalize configuration using a configuration server and inject secrets via environment variables

Use a shared configuration file mounted from a network drive

A team is building a CI/CD pipeline for a microservice. They want to automatically build a container image, run unit tests, scan the image for vulnerabilities, and deploy to a staging environment. Which sequence of steps should the pipeline follow?

Run unit tests, build image, deploy to staging, scan image

Build image, scan image, run unit tests, deploy to staging

Build image, run unit tests, scan image, deploy to staging

Deploy to staging, run unit tests, build image, scan image

GIAC Cloud Security Automation

Domain 4Objective 2

Microservices Architecture and Deployment GCSA Practice Questions (Page 1)

Part of the Container and Microservices Lifecycle domain, which makes up ~17% of our current practice bank. GIAC (SANS) does not publish an official question count, but from its 120-minute exam (~50–80 total, ~9–14 in this domain), expect 3–5 from this objective — we provide 37 practice questions to prepare you well beyond it. (estimate)

37questions here

8free pages

10concepts

Questions 1–5

1application · medium
A team is deploying a microservice to multiple environments (dev, staging, prod). They want to use the same container image in all environments but have different configuration values, such as database URLs and feature flags. Which approach should they use?
Select an answer first
2expert · hard
A team manages a critical payment service that must maintain 99.99% availability. They need to deploy a new version that changes the database schema. The database migration is backward-incompatible. The team wants to minimize the risk of a full outage while ensuring that if the new version fails, they can quickly revert. Which deployment strategy should they use?
Select an answer first
3foundation · easy
In a microservices architecture, how is data typically managed?
Select an answer first
4application · medium
A development team is deploying microservices to multiple environments (dev, staging, production). They need to manage configuration such as database connection strings and API keys without embedding them in container images. The configuration must be consistent across environments but allow environment-specific overrides. Which approach should they use?
Select an answer first
5application · medium
A team is building a CI/CD pipeline for a microservice. They want to automatically build a container image, run unit tests, scan the image for vulnerabilities, and deploy to a staging environment. Which sequence of steps should the pipeline follow?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to GCSA

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by GIAC (SANS). “GCSA” is a trademark of its owner, used for identification only.

Microservices Architecture and Deployment GCSA Practice Questions (Page 1)

Questions 1–5

A team is deploying a microservice to multiple environments (dev, staging, prod). They want to use the same container image in all environments but have different configuration values, such as database URLs and feature flags. Which approach should they use?

In a microservices architecture, how is data typically managed?

A team is building a CI/CD pipeline for a microservice. They want to automatically build a container image, run unit tests, scan the image for vulnerabilities, and deploy to a staging environment. Which sequence of steps should the pipeline follow?

Keep studying — Container and Microservices Lifecycle