CV0-004 Deployment — All Questions With Answers

Refer to the exhibit.

```bash
$ kubectl rollout status deployment/myapp
Waiting for deployment "myapp" rollout to finish: 0 of 3 updated replicas are available...
Error: deployment "myapp" exceeded its progress deadline
```

Refer to the exhibit.

```
$ kubectl get pods -n production
NAME                      READY   STATUS    RESTARTS   AGE
frontend-5d8f4d9c7-cm2xr   0/1     Pending   0          10m
backend-6b9f7d5e4-lp9qz    1/1     Running   0          15m
$ kubectl describe pod frontend-5d8f4d9c7-cm2xr -n production
...
Events:
  Type     Reason            Age   From               Message
  ----     ------            ----  ----               -------
  Warning  FailedScheduling  10m   default-scheduler  0/3 nodes are available: 1 Insufficient cpu, 2 Insufficient memory.
```

Refer to the exhibit.

```
resource "aws_instance" "web" {
  ami           = "ami-0abcdef1234567890"
  instance_type = "t2.micro"
  subnet_id     = "subnet-abc123"
  vpc_security_group_ids = ["sg-12345678"]
  user_data     = <<-EOF
                  #!/bin/bash
                  yum install -y httpd
                  systemctl start httpd
                  EOF
}
```

StackStatus: "ROLLBACK_IN_PROGRESS"
StackEvents:
  - ResourceStatus: "CREATE_FAILED"
    ResourceType: "AWS::EC2::Instance"
    ResourceStatusReason: "Value of property ImageId is invalid. Please use a valid AMI."

IAM Policy:
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": "s3:PutObject",
      "Resource": "arn:aws:s3:::example-bucket/*",
      "Condition": {
        "StringEquals": {
          "s3:x-amz-server-side-encryption": "AES256"
        }
      }
    }
  ]
}

Bucket Policy:
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Deny",
      "Principal": "*",
      "Action": "s3:PutObject",
      "Resource": "arn:aws:s3:::example-bucket/*",
      "Condition": {
        "StringNotEquals": {
          "s3:x-amz-server-side-encryption": "aws:kms"
        }
      }
    }
  ]
}

frontend web_frontend
   bind *:80
   default_backend web_servers

backend web_servers
   balance roundrobin
   server web1 10.0.1.10:80 check
   server web2 10.0.1.11:80 check

Health check configuration (excerpt):
   option httpchk GET /health
   http-check expect status 200

Refer to the exhibit.

```
$ terraform plan
...
  # aws_instance.web will be created
  + resource "aws_instance" "web" {
      + ami                          = "ami-0c55b159cbfafe1f0"
      + instance_type                = "t2.micro"
      + subnet_id                    = "subnet-06e3d2f8a8b9c1234"
      + vpc_security_group_ids       = [
          + "sg-0123456789abcdef0",
        ]
      + associate_public_ip_address  = true
      + user_data                    = <<-EOT
          #!/bin/bash
          apt-get update
          apt-get install -y nginx
          systemctl enable nginx
          EOT
      + tags                          = {
          + "Name" = "web-server"
        }
    }

Plan: 1 to add, 0 to change, 0 to destroy.
```