1V0-71-21 Certified Technical Associate - Application Modernization (VCTA-AM) Practice Questions

Microservices offer several advantages over monoliths: 1) Improved fault isolation, as services are independent processes. 2) Technology heterogeneity, as each service can choose the best tech stack for its job. 3) Independent scalability, allowing cost-effective scaling of only the services that need it. In contrast, monoliths have a single deployment unit (which can be simpler initially but harder to manage at scale) and often have more complex, distributed communication and data consistency challenges.

The final argument in the docker build command specifies the build context. The build context is the set of files at the specified location (URL or path) that are sent to the Docker daemon. The . signifies that the build context is the current working directory. This allows instructions in the Dockerfile, like COPY ./app /app, to refer to files within that directory.

This statement is false. The ClusterIP service type, which is the default, exposes the service on an internal IP within the cluster. This IP is only reachable from within the cluster. To expose a service to the outside world, one must use a NodePort, LoadBalancer, or an Ingress resource.

Tanzu Service Mesh's Global Namespace (GNS) feature allows services with the same name, deployed across different clusters and clouds, to be treated as a single, logical service. GNS provides capabilities like global service discovery and load balancing (GSLB) with automated failover. By defining a GNS for the 'user-profile' service, TSM can monitor the health of instances in both AWS and Azure and automatically route traffic to the healthy instance, enabling seamless cross-cluster failover.

Kubernetes Secrets are specifically designed to hold small amounts of sensitive data such as passwords, tokens, or keys. They are stored in the cluster (by default, base64 encoded in etcd, with options for encryption at rest) and can be mounted into pods as files or exposed as environment variables, but separately from the pod definition. This decouples sensitive information from the application code and configuration, aligning with security best practices.

The most efficient and standard Kubernetes-native way to switch traffic in a blue-green deployment is to update the selector of the existing Service. A kubectl patch or kubectl apply on the service manifest achieves this atomically, redirecting all traffic from the old pods to the new ones without any downtime or DNS changes. Deleting and recreating the service would cause a service outage. Using port-forward is for debugging, not production traffic. Modifying the deployment's labels would not change where the existing service is pointing.

The ImagePullBackOff status indicates that the kubelet on the worker node failed to pull the container image. The two most common reasons for this when pulling from a private repository are authentication failure or the specified image/tag not existing. Authentication is handled via an imagePullSecret associated with the pod's ServiceAccount. If the secret is missing, incorrect, or expired, the pull will fail. Similarly, a simple typo in the image tag will also result in a pull failure. Insufficient CPU/memory or a missing Ingress controller are unrelated to the image pull process.

This statement is false. While the Cluster API's primary role within a TKG management cluster is to manage the lifecycle of workload clusters, the management cluster itself is typically deployed using tools like the Tanzu CLI, which bootstraps a temporary kind cluster to then provision the full management cluster using Cluster API controllers. Therefore, CAPI is integral to the creation of the management cluster itself, not just the workload clusters it subsequently manages.

Tanzu Mission Control's Custom Policies leverage the Open Policy Agent (OPA) Gatekeeper framework. This allows administrators to write fine-grained rules using the Rego language to enforce custom constraints on any Kubernetes resource. The requirement to block the creation of ClusterRoleBinding resources by a specific user group is a classic use case for a custom admission control policy, which is implemented in TMC as a Custom Policy. Other policy types like Network, Quota, or Image Registry are for more specific, pre-defined use cases.

A StatefulSet is the ideal Kubernetes workload API object for managing stateful applications. It provides guarantees about the ordering and uniqueness of its pods. This includes stable, unique network identifiers (e.g., pod-0, pod-1), stable persistent storage linked to each pod's identity, and ordered, graceful deployment and scaling. Deployments are designed for stateless applications where pods are interchangeable.