Download EMCO 2021 Committer Practice Exam and more Exams Technology in PDF only on Docsity!
Question 1. Which EMCO component is responsible for orchestrating the deployment of Composite Apps across multiple clusters? A) Distributed Cloud Manager (DCM) B) Generic Action Controller (GAC) C) Orchestrator D) Network Management Service (NMS) Answer: C Explanation: The Orchestrator coordinates the end‑to‑end deployment workflow, invoking DCM, GAC, and other services as needed. Question 2. In EMCO terminology, what does a “Logical Cloud” primarily provide? A) Physical hardware resources B) Isolation and multi‑tenancy for applications C) Network routing tables D) Persistent storage volumes Answer: B Explanation: Logical Clouds are virtual partitions that isolate resources and enable multi‑tenant deployments within the same physical cluster set. Question 3. When registering a new edge cluster with EMCO, which file is mandatory for authentication? A) kubeconfig B) Dockerfile C) Helm chart D) manifest.json Answer: A
Explanation: The kubeconfig contains the credentials and cluster endpoint needed for EMCO to communicate with the edge cluster. Question 4. Which API protocol does EMCO use for internal service‑to‑service communication? A) SOAP B) REST only C) gRPC D) GraphQL Answer: C Explanation: EMCO leverages gRPC for high‑performance, binary‑encoded communication between its microservices. Question 5. A Composite App consists of several sub‑applications. What EMCO feature defines the order in which these sub‑applications are installed? A) Placement Intent B) Dependency Mapping C) Profile Override D) Cluster Group Answer: B Explanation: Dependency Mapping specifies explicit install order, ensuring that required components are present before dependent ones are deployed. Question 6. Which EMCO resource model sits directly under a Project in the hierarchy? A) Logical Cloud B) Composite App C) Deployment Intent
B) Cluster label key/value pairs C) Docker image digest D) Service Mesh policy name Answer: B Explanation: Placement Intents use cluster labels (or other selectors) to target specific edge nodes for deployment. Question 10. What is the primary function of the Network Management Service (NMS) in EMCO? A) Store secret data B) Manage logical cloud definitions C) Define connectivity requirements between applications D) Perform health checks on clusters Answer: C Explanation: NMS allows authors to declare network intents such as required services, policies, and connectivity across clusters. Question 11. Which state indicates that an application deployment has been approved but not yet started? A) Created B) Instantiating C) Approved D) Instantiated Answer: C Explanation: The Approved state signals that the intent has passed validation and awaits execution.
Question 12. In EMCO, what does a “Profile” primarily allow you to do? A) Change the underlying hardware of a cluster B) Override specific configuration values for a particular cluster or environment C) Register new users for the project D) Define network policies for all clusters globally Answer: B Explanation: Profiles provide per‑cluster or per‑environment overrides (e.g., values.yaml) without altering the base Composite App. Question 13. Which of the following best describes a “Cluster Group” in EMCO? A) A set of physical servers located in a data center B) A logical collection of clusters sharing common labels or geographic attributes C) A Kubernetes namespace used for isolation D) A collection of Helm repositories Answer: B Explanation: Cluster Groups aggregate clusters based on labels, geography, or functional criteria for easier intent application. Question 14. When EMCO’s Status Query API aggregates health data, which component primarily supplies the per‑cluster health metrics? A) GAC B) DCM C) rsync service on the edge cluster D) NMS Answer: C Explanation: The rsync sidecar runs on each edge cluster, collecting and reporting health and resource status back to EMCO.
Explanation: After the orchestrator finishes provisioning, the deployment moves from Instantiating to Instantiated. Question 18. What is the purpose of the “Priority” field in a Placement Intent? A) To decide the order of network policy application B) To resolve conflicts when multiple intents target the same cluster resources C) To select the Helm chart version automatically D) To control the logging verbosity of the deployment Answer: B Explanation: Priority helps EMCO resolve contention by preferring higher‑priority intents when resources overlap. Question 19. Which of the following best describes “Preemption” in EMCO’s resource management? A) Deleting a Logical Cloud automatically removes all its applications B) Reclaiming resources from a lower‑priority intent to satisfy a higher‑priority one C) Rolling back a failed deployment to the previous version D) Shutting down clusters that are idle for more than 30 days Answer: B Explanation: Preemption allows EMCO to reallocate resources from lower‑priority deployments to higher‑priority intents when needed. Question 20. How does EMCO support secret propagation across multiple clusters? A) By copying secret objects directly via rsync B) By storing secrets in a central Vault and injecting them at runtime through GAC actions C) By embedding secrets in Helm chart values files D) By using Kubernetes Service Accounts only
Answer: B Explanation: EMCO can integrate with external secret stores (e.g., HashiCorp Vault) and use GAC to inject secrets into target clusters securely. Question 21. Which label is commonly used to identify clusters belonging to a specific geographic region in EMCO? A) region=<value> B) environment=<value> C) app=<value> D) cluster-id=<value> Answer: A Explanation: The region label is a conventional key for geographic grouping, enabling placement intents based on location. Question 22. When creating a Composite App, which file typically defines the Helm chart dependencies? A) Chart.yaml B) values.yaml C) requirements.yaml (or Chart.yaml dependencies section) D) deployment.yaml Answer: C Explanation: Helm dependencies are listed in requirements.yaml (or the dependencies section of Chart.yaml) to pull in sub‑charts. Question 23. What is the primary benefit of using “override profiles” in EMCO deployments? A) They reduce the size of the Docker images. B) They allow per‑cluster configuration without modifying the base Composite App.
A) It requires a separate EMCO instance per cloud provider. B) It abstracts connectivity through Network Intents, allowing uniform policies across clouds. C) It only supports a single cloud at a time. D) It uses VPN tunnels exclusively for inter‑cloud traffic. Answer: B Explanation: Network Intents let users declare connectivity requirements that EMCO translates into appropriate configurations on each cloud. Question 27. What is the purpose of the “rsync” component in EMCO’s architecture? A) To synchronize Helm chart repositories across clusters. B) To transfer files, manifests, and status information between EMCO and edge clusters. C) To replicate Kubernetes API server logs. D) To manage user authentication tokens. Answer: B Explanation: rsync runs as a sidecar on edge clusters, handling bidirectional file and status sync with the EMCO controller. Question 28. Which of the following actions can GAC NOT perform during deployment? A) Patch a ConfigMap B) Create a new Kubernetes Namespace C) Modify a Helm chart version on the fly D) Delete a Secret Answer: C Explanation: GAC works on already‑deployed resources; it does not alter the Helm chart version itself during runtime.
Question 29. When a Logical Cloud is deleted, what happens to the Composite App Instances that reside within it? A) They are automatically terminated. B) They continue running but become unmanaged. C) They are migrated to a default Logical Cloud. D) Deletion is blocked until all instances are manually removed. Answer: A Explanation: Deleting a Logical Cloud triggers termination of all associated Composite App Instances to maintain consistency. Question 30. Which field in a Placement Intent determines the specific clusters that will receive the deployment? A) metadata.name B) spec.clusterSelector C) spec.version D) spec.profile Answer: B Explanation: spec.clusterSelector uses label selectors to match target clusters for the intent. Question 31. How does EMCO ensure that a Deployment Intent does not exceed the quota of a Logical Cloud? A) By checking the quota during the “Approved” state and rejecting if exceeded. B) By automatically scaling down other deployments. C) By ignoring quota limits entirely. D) By creating a new Logical Cloud on demand. Answer: A
Answer: B Explanation: NMS processes network intents and translates them into concrete network policies on the target clusters. Question 35. What is the effect of setting preemptible: true in a Placement Intent? A) The intent can be preempted by a higher‑priority intent. B) The intent will ignore resource quotas. C) The intent will automatically retry on failure. D) The intent will be executed on all clusters regardless of selectors. Answer: A Explanation: preemptible: true marks the intent as eligible for preemption, allowing higher‑priority intents to claim its resources. Question 36. Which of the following best describes the role of “Composite App Versioning” in upgrade scenarios? A) It forces a full redeployment of all sub‑applications. B) It enables selective upgrade of individual sub‑applications while keeping others unchanged. C) It creates a new Project for each upgrade. D) It disables all existing intents until the upgrade completes. Answer: B Explanation: Versioning allows a new Composite App version to be deployed, and only the changed sub‑applications need to be updated. Question 37. When EMCO’s Orchestrator receives a deployment request, which sequence of actions occurs first? A) GAC actions → DCM resource allocation → rsync sync B) DCM resource validation → Placement Intent evaluation → GAC execution
C) Status Query → Network Intent → Profile selection D) Cluster registration → Logical Cloud creation → Deployment Intent approval Answer: B Explanation: The Orchestrator first validates resources via DCM, then evaluates Placement Intents, and finally runs any GAC actions. Question 38. Which security feature does EMCO provide to protect secret data during transit? A) AES‑256 encryption of ConfigMaps B) Mutual TLS between EMCO components and edge clusters C) Storing secrets in plain text within Helm values D) Using HTTP Basic Auth for all APIs Answer: B Explanation: Mutual TLS encrypts all communication, ensuring that secrets transferred via rsync or APIs are protected in transit. Question 39. In EMCO, a “Project” can contain multiple Composite Apps. Which attribute uniquely identifies a Composite App within a Project? A) metadata.uid B) metadata.name combined with spec.version C) spec.clusterGroup D) status.phase Answer: B Explanation: The combination of name and version uniquely distinguishes a Composite App inside a Project. Question 40. What is the primary purpose of the “Generic Action Controller” (GAC) template files?
Question 43. Which component of EMCO is responsible for persisting the data model (Projects, Composite Apps, etc.)? A) etcd cluster embedded in the Orchestrator B) MySQL database deployed as a microservice C) Redis cache used for fast lookups D) Flat files on the host node Answer: B Explanation: EMCO uses a MySQL (or compatible) database to store its hierarchical data model persistently. Question 44. In EMCO, what does the “Cluster Label” edge=true typically signify? A) The cluster runs the latest Kubernetes version. B) The cluster is designated as an edge node eligible for deployment. C) The cluster is a control‑plane only node. D) The cluster is part of a testing environment. Answer: B Explanation: The edge=true label is a common convention to mark clusters that are edge devices where workloads can be placed. Question 45. Which of the following is a valid reason to use multiple Logical Clouds within a single Project? A) To separate workloads belonging to different customers or tenants. B) To increase the number of Helm charts that can be stored. C) To enable faster rsync synchronization. D) To bypass Kubernetes RBAC restrictions. Answer: A
Explanation: Logical Clouds provide tenant isolation, making them suitable for multi‑tenant scenarios within one Project. Question 46. What does the “Network Intent” field serviceMesh: istio instruct EMCO to do? A) Deploy Istio sidecars on all workloads automatically. B) Create a Service Mesh configuration using Istio for the specified services. C) Replace any existing Service Mesh with Linkerd. D) Disable all network policies. Answer: B Explanation: Setting serviceMesh: istio tells EMCO to generate the necessary Istio resources (VirtualServices, DestinationRules, etc.) for the defined services. Question 47. Which of the following best describes the purpose of “Composite App Instance” metadata? A) To store the raw Helm chart files. B) To record the runtime state, version, and associated Logical Cloud of a deployed Composite App. C) To define user access policies. D) To list all available Cluster Groups. Answer: B Explanation: Instance metadata captures the operational details of a deployed Composite App, including its version and the Logical Cloud it belongs to. Question 48. How does EMCO’s “Preemption” mechanism affect a running deployment with lower priority when a higher‑priority intent requests the same resources? A) The lower‑priority deployment is paused until resources become free. B) The lower‑priority deployment is terminated and its resources reclaimed.
A) gRPC provides built‑in authentication. B) gRPC offers lower latency and binary serialization, improving performance between microservices. C) REST cannot be used over TLS. D) gRPC automatically generates Helm charts. Answer: B Explanation: gRPC’s binary protocol and streaming capabilities make it more efficient for high‑frequency internal calls. Question 52. What is the impact of setting spec.preemptible: false on a Placement Intent? A) The intent will never be preempted, even by higher‑priority intents. B) The intent will ignore all resource quotas. C) The intent will be automatically deleted after 24 hours. D) The intent will be executed on all clusters regardless of selectors. Answer: A Explanation: preemptible: false marks the intent as non‑preemptible, protecting its resources from being reclaimed. Question 53. Which of the following statements about EMCO’s “Cluster Group” selector is true? A) It can select clusters based on the version of the deployed Composite App. B) It works only with static IP address ranges. C) It uses label selectors similar to Kubernetes nodeSelector. D) It must be defined in the Helm chart’s values.yaml. Answer: C Explanation: Cluster Group selectors rely on label queries, analogous to Kubernetes node selectors.
Question 54. How does EMCO ensure that a user can only view Deployment Intents belonging to a specific Logical Cloud? A) By encrypting all intents with a per‑Logical Cloud key. B) By applying RBAC policies scoped to the Logical Cloud via the Access Control Service. C) By storing intents in separate databases per Logical Cloud. D) By requiring a separate EMCO instance per Logical Cloud. Answer: B Explanation: RBAC policies tied to Logical Clouds restrict visibility and actions for users. Question 55. Which of the following is a valid use case for an “Override Profile” in EMCO? A) Changing the Kubernetes API version globally. B) Setting a different Docker image tag for a specific edge cluster. C) Adding a new Cluster Group without affecting existing groups. D) Deleting a Logical Cloud automatically. Answer: B Explanation: Override Profiles allow per‑cluster modifications such as using a different image tag. Question 56. In the EMCO lifecycle, what does the “Terminating” state indicate? A) The deployment is being rolled back to a previous version. B) Resources are being cleaned up after a successful deployment. C) The Composite App Instance is being deleted and its resources are being removed. D) The deployment is paused due to insufficient resources. Answer: C Explanation: “Terminating” is entered when an instance is being removed, and EMCO is orchestrating resource cleanup.
