Intermediate Code Reading #yaml #config #devops

⚙️ Reading Config Files

3 exercises — read YAML and configuration files and describe them in plain English. Essential for documentation, onboarding, and code reviews.

0 / 3 completed

Describing config files — key phrases

"This setting tells the application to listen on / use / enable…"
"This value is read from an environment variable, so it can differ between environments."
"The service will restart automatically / wait for X before starting…"
"Data is persisted in a named volume, meaning it survives container restarts."
"The workflow triggers when code is pushed to / a pull request is opened against…"

1 / 3

Read this CI/CD pipeline configuration. Which plain-English description is most accurate?

name: Deploy to Production
on:
  push:
    branches: [main]
jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Install dependencies
        run: npm ci
      - name: Run tests
        run: npm test
      - name: Build
        run: npm run build
      - name: Deploy
        run: ./scripts/deploy.sh
        env:
          SSH_KEY: ${{ secrets.SSH_KEY }}

2 / 3

A junior developer asks you to explain this YAML configuration during onboarding. Choose the best explanation:

server:
  host: 0.0.0.0
  port: 8080
  timeout: 30s

database:
  url: ${DATABASE_URL}
  max_connections: 20
  idle_timeout: 300s

logging:
  level: info
  format: json
  output: stdout

3 / 3

Your team lead asks you to document this docker-compose snippet for the team wiki. Which description is most suitable?

services:
  api:
    image: myapp:latest
    ports:
      - "3000:3000"
    environment:
      NODE_ENV: production
      PORT: 3000
    depends_on:
      - db
    restart: unless-stopped

  db:
    image: postgres:16
    volumes:
      - pgdata:/var/lib/postgresql/data
    environment:
      POSTGRES_PASSWORD: ${DB_PASSWORD}