Cloud Paks Foundations Fundamentals - L1 Quiz

19/25 za prolaz

1.

What needs to be available in order for IBM Cloud Paks Satellite to become a reality?

Vendors need to be willing for IBM to pre-install IBM Cloud Private on their servers.

IBM Cloud Satellite will only be available exclusively on IBM Cloud.

Vendors need to support IBM Watson (our AI offerings) on their platform in order for IBM Cloud
Satellite to operate.

IBM needs to first deliver Cloud Paks as a Service (CPaaS) so that IBM Cloud Satellite can benefit from
the "as-a-service" delivery model and automation.

2.

The architecture of IBM Cloud Paks has changed from a series of siloed "verticals" to...

Always-online containers

Disconnected environments

Discrete architectures

Horizontally-integrated environments

3.

Foundational Services can be organized into five pillars or grouping of capabilities, services, and
components. Which pillar focuses on metering and licensing?

Data and Event Services

User Experience Services

Operational Services

Application Services
4.

The notion of "write once, run anywhere" is key to IBM's strategic vision of Cloud Paks, Foundational
Services, and Red Hat OpenShift. Which statement best summarizes our approach to the hybrid
multicloud market?

Cloud is not a place or destination, but a capability.

Cloud investments need to be all-in on a single vendor in order to be successful.

Cloud is outdated.

Cloud only makes sense for businesses that are cloud-native and born-in-the-cloud.

5.

What is the name of the offering that will deliver fully-managed instances of IBM Cloud Paks on the
IBM Cloud?

IBM Cloud Paks as a Service (CPaaS)

IBM Cloud Satellite

IBM Cloud Private (ICP)

IBM Cloud OpenShift

6.

Which core pillar does the IBM Cloud Pak for Watson AIOps belong to?

Automate

Analyze

Predict

Secure

7.

Which of the following priorities helps to provide Cloud Paks and Foundational Services with
consistency in operations and delivery?

Community-sourced projects.
Standards and certification.

Blockchain provenance.

Metered API usage.

8.

When talking to customers and to the marketplace about the common set of services that support
IBM Cloud Paks, we must always refer to them by their proper name: IBM Cloud Paks Foundational
Services (or "Foundational Services" for short). However, internally at IBM you may come across old
documentation that references them by a different name. Of the following, which one is another
common— but outdated —name for the Foundational Services?

Slate

Bedrock

Alpine

Summit

9.

What is the best way to sell IBM Cloud Paks Foundational Services?

Email your IBM sales representative for pricing information.

Look up the SKU numbers in the IBM Catalog.

Since the Foundational Services aren't something we sell directly, it's best to focus on their value to
the IBM Cloud Paks and improved customer experience they offer.

Look up the cost per API call to Foundational Services on Seismic.

10.

Which one of the following statements is NOT a core "pillar" or aggregate of Cloud Paks capabilities?

Predict

Analyze

Automate

Secure
11.

There are three core axioms in IBM and Red Hat's philosophy towards the Cloud Paks Platform we
are building towards. Of the four statements below, which is NOT one of those core values?

Run any workload

Run in containers

Run transparently

Run anywhere

12.

What statement best describes the new generation of IBM Cloud Paks?

A return to the drawing board

Just another rebranding

A complete reboot

A logical evolution

13.

Foundational Services interoperate and sit between which layers of the Cloud Paks Platform
architecture?

Foundational Services are only available on-premises (private Infrastructure).

Between Infrastructure and Red Hat OpenShift.

Between individual IBM Cloud Paks only.

Between Red Hat OpenShift and IBM Cloud Paks.

14.

Why did IBM choose to re-organize the Cloud Paks and Foundational Services architecture into 3 core
pillars?

One pillar is targeted at "do it yourself" (DIY) deployments, a second pillar at customer-managed
deployments, and a third pillar is for IBM-managed deployments.
Going forward, there will only be 3 IBM Cloud Paks offered to the market.

Conversations with customers should first focus on what are the use cases and who are the personas
of interest, then afterwards identify the relevant Cloud Paks.

One pillar is for on-premises, a second for public cloud, and a third pillar is for hybrid multicloud.

15.

Why does IBM consider earlier iterations of the IBM Cloud Paks architecture as too "vertical"?

The individual Cloud Paks were too siloed and not as tightly integrated as our customers desired.

The early Cloud Paks had such a steep learning curve that few were able to get started.

Infrastructure requirements to run early versions of Cloud Paks were too expensive.

Customers were getting too lost in the depth of capabilities packed into every Cloud Pak.

16.

Foundational Services can be organized into five pillars or grouping of capabilities, services, and
components. Which pillar focuses on repositories and engines?

Operational Services

Data and Event Services

Application Services

User Experience Services

17.

Which core pillar does the IBM Cloud Pak for Integration belong to?

Analyze

Secure

Predict

Automate
18.

Foundational Services can be organized into five pillars or grouping of capabilities, services, and
components. Which pillar focuses on APIs and endpoint libraries?

Operational Services

User Experience Services

Application Services

Data and Event Services

19.

What is the name of the platform that IBM and Red Hat are ultimately building towards?

Cloud Paks Platform

Cloud Paks Private

Foundational Services Pak

Private Foundational Services

20.

Which core pillar does the IBM Cloud Pak for Data belong to?

Automate

Predict

Secure

Analyze

21.

You're talking to an existing IBM customer who had previously invested in IBM Cloud Paks. As you
bring up the substantial evolution of our Cloud Paks architecture, you see some skeptical looks across
the room — perhaps the customer is concerned this might mean having to learn a whole new
interface or scrap everything they've learned about the platform already? How would you describe
the benefit of the next generation of Cloud Paks and put your customer's mind at ease?
Cloud Pak capabilities will be less siloed. Foundational Services will make it easier to integrate and
work across multiple Cloud Paks.

Future iterations of Cloud Paks will all have identical (uniform) pricing.

Cloud Paks can no longer be purchased individually and will instead come bundled through a single
purchase order.

Every Cloud Pak will now run on a separate OpenShift cluster.

22.

What is the name of the offering which will deliver public IBM Cloud services, managed by IBM, to
any public cloud vendor (or customer's cloud)?

IBM Cloud Private (ICP)

IBM Cloud Satellite

IBM Cloud OpenShift

IBM Cloud Paks as a Service (CPaaS)

23.

What is the name of the service which has made it possible for IBM to untangle the string of
dependencies for current and future releases of the common Foundational Services?

Istio

CRUD Operations

Red Hat Operators

Red Hat OpenShift

24.

Foundational Services inherit enterprise-centric features like metering, monitoring, and IAM from
what earlier version of the service?

PaaS

RHEL

ICP

NoSQL
25.

Many of you will have worked with enterprise customers who have apprehensions about
modernizing their legacy applications and services using containers. To demonstrate the benefits of
containers, we as sellers need to first identify the sources of concern for our customers. What is a
common misconception to moving applications into containers that you should be prepared to
dispell?

The customer believes that virtual machines (VMs) will always be superior to containers.

The customer believes that non-fungable tokens (NFTs) are a superior option to containers.

The customer has no desire to operate in the cloud.

The customer has unique requirements for availability, resiliency, and security — and they are
uncertain whether containers are up to the task.