Knowledge Check - Container Workflows and CI/CD

Test your understanding of the key concepts from Module 3. Select the best answer for each question, then submit to see your results. You need to score at least 60% to pass.

1.

A developer creates a token for TaskBoard's CI pipeline with this Terraform block. docker login succeeds, but docker push to taskboard/api is denied.

resource "ionoscloud_container_registry_token" "ci" {
  registry_id = ionoscloud_container_registry.taskboard.id
  name        = "taskboard-ci"
  scopes {
    name    = "taskboard/*"
    type    = "repository"
    actions = ["push"]
  }
}

What should the developer change?

2.

A developer applies this Service on a public node pool of Managed Kubernetes and expects a new load balancer in the data center:

apiVersion: v1
kind: Service
metadata:
  name: taskboard-web
spec:
  type: LoadBalancer
  selector: { app: taskboard-web }
  ports:
    - port: 80

What actually happens?

3.

TaskBoard's cluster runs Kubernetes 1.33. A developer sets k8s_version to a 1.35 release on the ionoscloud_k8s_node_pool resource only and runs terraform apply. The API rejects the change. Which sequence upgrades the cluster correctly?

4.

Two pull requests that change TaskBoard's infrastructure are merged a minute apart. Both start the GitHub Actions job below, and the second terraform apply fails with a state error.

on:
  push:
    branches: [main]
jobs:
  terraform:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - run: terraform init -input=false
      - run: terraform apply -input=false -auto-approve

Which change prevents this?

5.

TaskBoard's nightly release pipeline fails at docker push every Sunday at around 03:00 UTC. The other nights succeed. The registry was created with this block:

garbage_collection_schedule {
  days = ["Sunday"]
  time = "03:00:00+00:00"
}

What is the cause and the fix?