Pass the IBM Certified Advocate - Cloud v2 C1000-142 Questions and answers with ValidTests

Multi Cloud is a combination of two or more cloud services from different cloud providers. In-Correct Answers : Private Cloud : The cloud infrastructure is provisioned for exclusive use by a single organization comprising multiple consumers (e.g., business units). It may be owned, managed, and operated by the organization, a third party, or some combination of them, and it may exist on or off premises. Community Cloud : The cloud infrastructure is provisioned for exclusive use by a specific community of consumers from organizations that have shared concerns (e.g., mission, security requirements, policy, and compliance considerations). It may be owned, managed, and operated by one or more of the organizations in the community, a third party, or some combination of them, and it may exist on or off premises. Public Cloud : The cloud infrastructure is provisioned for open use by the general public. It may be owned, managed, and operated by a business, academic, or government organization, or some combination of them. It exists on the premises of the cloud provider. Hybrid Cloud : The cloud infrastructure is a composition of two or more distinct cloud infrastructures (private, community, or public) that remain unique entities, but are bound together by standardized or proprietary technology that enables data and application portability (e.g., cloud bursting for load balancing between clouds).

Microservices architecture is an approach in which a single application is composed of many loosely coupled and independently deployable smaller services.

Containers are lightweight and portable executable units (images) of software. They supply portability between different platforms and clouds. Containers are self-contained units that are designed to hold applications as well as all libraries and dependencies that the application requires. Containers can be run on physical computers or in the cloud.

Containers do not have an operating system of their own. Instead, they access the operating system of the device they are running on using a hypervisor. This allows them to be more light-weight, easier to provision, and much smaller than traditional virtual machines.

Virtual machine is a virtual re-presentation of physical computer, you can understand it as a computer inside a computer. Each individual virtual machine behaves exactly as though it were its own computer. It has its own operating system, memory, storage, and compute and is totally unaware of other virtual machines that could be running on the same host.

How do containers differ from a traditional VM?

Traditional virtualization leverages a hypervisor to virtualize physical hardware. Each VM contains:

- A guest operating system (OS)

- A virtual copy of the hardware that the OS requires to run

- An application and its associated libraries and dependencies

- Containers, on the other hand, virtualize the operating system. Each container only contains:

- The application

- Its libraries

- Its dependencies

Explanation

IBM Cloud Hyper Protect DBaaS for MongoDB is a LinuxONE-powered cloud database solution for enterprise workloads with sensitive data. Hyper Protect DBaaS for MongoDB currently contains MongoDB Enterprise Advanced Edition 4.4. This leading-edge solution offers a highly secure database environment for enterprise workloads with sensitive data. With IBM Cloud™ Hyper Protect DBaaS, you can provision, manage, maintain and monitor multiple database types like MongoDB and PostgreSQL through standardized APIs. Hyper Protect DBaaS is built on LinuxONE technology which provides built-in data encryption along with excellent vertical scalability and performance. It helps protect against threats of data breaches and data manipulation by privileged users and provides a high level of data confidentiality for data owners.

Object Storage enable you to store and access unstructured data anywhere in the world with a self-service portal backed by RESTful APIs.

Object Storage supports exponential data growth and cloud-native workloads with built-in high-speed file transfer capabilities, cross-region offerings and integrated services.

Use cases: Backup and recovery, Data archiving, Cloud-native application, AI and big data analytics.

Explanation

IBM API Connect® Service provides API creation and management with security-rich features and centralized governance. You can use IBM API Connect for IBM Cloud to quickly create APIs for microservices based on Node.js and Java runtimes. When APIs are hosted on API Connect: Consumers can locate, understand, learn, and experiment with the APIs they need before committing to use them. They can also self-subscribe to them using revocable keys. Providers can hide the exact locations of API implementations, enable version-based routing, and throttle inbound requests to the API on a per-consumer basis. These capabilities are helpful while packaging data for partners. Consumers and providers can track use and response times, which allows them to tie resource use to their business model. In-Correct Answers IBM Event Streams for IBM Cloud is a high-throughput message bus built with Apache Kafka and was previously known as Message Hub. In Event Streams, applications send data by creating a message and sending it to a topic. It uses availability support from IBM Kubernetes services to maintain high availability and resilience. Integration is available with IBM Cloud services as well as Watson Internet of Things® (IoT). Key Features Fully Managed: Built on Apache Kafka, IBM Cloud Event Streams is a fully managed service. Intuitive UX: Deploy your Event Streams in minutes using the benefits of IBM Design Thinking. Event-Driven: Use integrations with IBM Cloud services like Watson IoT platform, IBM Streaming Analytics, and IBM Cloud Functions to easily create your event-driven architecture. IBM App Connect® is a powerful all-in-one tool for easily connecting apps, integrating data, building APIs, and acting on events. App Connect can connect any endpoint, map your data, and move data fast. With IBM App Connect, you can reliably access and combine data assets across all your enterprise applications, databases, and systems and expose them as APIs. You can connect to any application or endpoint, from the latest SaaS apps to mainframe systems. IBM App Connect allows you to connect applications together using a common platform. It enables you to build automation triggers between applications and automate workflows and integrate data using the included 75+ connectors and 50+ templates. Key Features Intuitive Development Tools: Easily create APIs, thoroughly test them, then share them with others both inside and outside your organization. Easy Yet Powerful Security: Use pre-defined security policies to protect your API or customize your own. Lifecycle Management: Manage the entire lifecycle of your APIs for your internal team, external consumers, and third parties. Customizable Developer Portal: Share your APIs with other developers using the built-in fully-customizable portal. The portal includes the ability to communicate with API consumers using a variety of modalities including blogs, forums, and messaging. IBM® MQ on Cloud provides enterprise-grade messaging capabilities to allow the flow of information between different applications. This service is fully managed so you can focus on integrating MQ applications rather than upgrades and patches. Key Features Deduplication: Messages are delivered without duplicates. Connectivity: Connectivity issues are handled by MQ. Encryption: End-to-end data encryption is used to ensure the security of your data. [Exam Tips] Remember following points: If you need to create, secure, and manage APIs use API Connect If you need to connect, copy, and sync application data across platforms use APP Connect If you need to deliver reliable, secure messaging, either on-premises or over the cloud use MQ If you need to build adaptive smart apps that react to events as soon as they happen use IBM Event Streams

IBM® Cloud Continuous Delivery provides two types of delivery pipelines (Classic & Tekton) that you can use to build, test, and deploy your applications. Classic delivery pipelines are created graphically, with the status embedded in the pipeline diagram. These pipelines can run on shared workers in the cloud or on private workers that run on your own Kubernetes cluster. Tekton delivery pipelines are created within yaml files that define pipelines as a set of Kubernetes resources. You can edit those yaml files to change the behaviour of a pipeline.