H13-821_V3.0 · Question #210
The implementation of cloud-native applications is usually based on the micro-service architecture. Which of the following descriptions about the underlying technology of the micro- service…
The correct answer is A. Non-intrusive service governance can be achieved through Istio B. Agile infrastructure can be realized through unified scheduling of OpenStack resources D. Containerized deployment can be realized through Kubernetes container orchestration and. Istio is a service mesh that injects sidecar proxies alongside application containers to handle traffic management, security, and observability without changing application code, making A correct for non-intrusive governance. OpenStack provides unified scheduling and management…
Question
The implementation of cloud-native applications is usually based on the micro-service architecture. Which of the following descriptions about the underlying technology of the micro- service architecture is correct? (Multiple choice)
Options
- ANon-intrusive service governance can be achieved through Istio
- BAgile infrastructure can be realized through unified scheduling of OpenStack resources
- CContinuous development and integration can be achieved through the microservice framework
- DContainerized deployment can be realized through Kubernetes container orchestration and
How the community answered
(62 responses)- A84% (52)
- C16% (10)
Explanation
Istio is a service mesh that injects sidecar proxies alongside application containers to handle traffic management, security, and observability without changing application code, making A correct for non-intrusive governance. OpenStack provides unified scheduling and management of compute, storage, and network resources, enabling the on-demand, scalable infrastructure that defines agile cloud environments, making B correct. Kubernetes automates the deployment, scaling, and management of containerized workloads, directly enabling containerized deployment as described in D. Option C is wrong because continuous development and integration is the domain of CI/CD pipelines and tools such as Jenkins or GitLab CI, not the microservice framework itself; the microservice framework handles concerns like service discovery, communication, and resilience, not build and release automation.
Memory tip: Match each tool to its layer - Istio governs traffic between services (service mesh layer), OpenStack manages the raw infrastructure (IaaS layer), Kubernetes orchestrates containers (container layer), and CI/CD tools handle the development pipeline (delivery layer). C fails because it assigns a delivery-pipeline responsibility to an application-framework tool.
Topics
Community Discussion
No community discussion yet for this question.