Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Associate Cloud Engineer practice bank has an additional 2,014 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
An administrator manages a multi-tenant Google Kubernetes Engine (GKE) cluster where workloads are logically partitioned across separate namespaces for different development teams. The administrator needs to inventory the running application components for a tenant residing in the team-a namespace while also checking the underlying cluster infrastructure.
Which statement correctly distinguishes between namespace-scoped and cluster-wide resources in the cluster?
team-a, while Services and ConfigMaps are cluster-wide resources that span the entire cluster.This option groups Pods with Nodes as namespace-scoped entities, while categorizing Services and ConfigMaps as cluster-wide infrastructure objects.
team-a is discoverable within that namespace using its local DNS name (e.g., my-service) or cross-namespace using the fully qualified domain name (e.g., my-service.team-a.svc.cluster.local).Network routing rules and configuration objects were globally shared across all projects and teams, while hardware instances were dedicated on a per-namespace basis.
team-a, while Pods and Deployments are cluster-wide resources that span the entire cluster.This option incorrectly asserts that Nodes and Services are confined to specific namespaces, whereas Pods and Deployments operate as cluster-wide objects.
kubectl get nodes, you query the global pool of compute instances; passing a -n namespace flag to a node query has no scoping effect.default if unspecified).Kubernetes placed actual compute instances into isolated tenant partitions by default and managed container runtime instances as global shared entities across all tenants, which is the opposite of how Kubernetes architecture is designed.
This option asserts that all Kubernetes API objects and infrastructure resources are namespace-scoped without exception.
kubectl api-resources displays all supported Kubernetes object kinds and explicitly indicates whether each kind is namespaced (true or false).Kubernetes operated as a fully shared-nothing architecture where every physical node, storage class, and role definition were cloned and encapsulated strictly inside individual tenant namespaces.
team-a, while Nodes and Namespaces are cluster-wide resources that span the entire cluster.In Google Kubernetes Engine (GKE) and Kubernetes, resources are architecturally divided into two distinct scopes: namespace-scoped resources and cluster-wide (cluster-scoped) resources. Namespaces provide a mechanism for isolating groups of resources and dividing cluster resources between multiple users, teams, or environments.
team-a, these resources are isolated within that specific partition and can be targeted directly using namespace filtering (such as kubectl get pods -n team-a or kubectl get services -n team-a).
team-a and team-b can have a Service named frontend).Roles and RoleBindings).Distinguishing between namespace-scoped objects (Pods, Services) and cluster-scoped objects (Nodes, Namespaces) reflects the core Kubernetes resource model. It allows operators to accurately inspect tenant-specific workloads while maintaining a global view of shared underlying hardware.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated