Professional Documents
Culture Documents
2.11
Define how cloud computing fits in with service management and the
Information Technology Infrastructure Library (ITIL) model V3 (ITIL Service
Strategy, ITIL Service Design, ITIL Service Transition, ITIL Service Operation,
ITIL Continual Service Improvement).
Explain the benefits of using the IBM IBM Cloud Computing Reference
Architecture (CCRA) V4 Adoption Patterns.
Explain the Cloud Platform Services Adoption Pattern for CCRA.
Explain the Cloud Service Provider Adoption Pattern for CCRA.
Describe the IBM CCRA V4 Building SaaS cloud adoption pattern.
Explain the Cloud Enabled Data Center Adoption Pattern for CCRA.
Describe the solution integration process detailed in the IBM CCRA V4 to take
an existing environment to an IBM Cloud Computing environment.
Design a secure and reliable cloud computing service model.
Describe high availability and DR as it pertains to cloud computing.
Define four defining principles of Cloud computing as presented in the IBM
CCRA V4.
Describe Cloud Service Consumers, Cloud Service Creators, Cloud Service
Provider, Cloud Services and the Common Cloud Management Platform.
Describe how IBM Service Management can effectively manage a customers
cloud environment.
Describe the Integration and Extensibility models of cloud solutions described
in CCRA V4.
Understand the role of goverance in the CCRA.
Describe non-functional requirements (NFRs) in the context of a cloud
solution.
Describe the objectives of the Mobile Pattern in the CCRA.
4.5
4.6
1.11.3. A hybrid cloud enables the cloud consumer to segregate workloads based upon
security and compliance requirements. For instance, secure data resides on the
private cloud and the non-secure data resides on the public cloud.
1.12. Define the difference between a private cloud, a public cloud, and a hybrid
cloud.
SUBTASK(S):
1.12.1. Define a private cloud.
In a 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.
1.12.2. Define a public cloud.
In a 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.
Public clouds are where IT activities/functions are provided as a service over
the Internet, which allows access to technology-enabled services without
knowledge of, expertise with, or control over the technology infrastructure that
supports them.
1.12.3. Define a hybrid cloud.
In a hybrid cloud, the cloud infrastructure is a composition of two or more
distinct cloud infrastructures (private, community, or public) that remain
independent entities, but are bound together by technology that enables data
and application integration (e.g., cloud bursting for load balancing between
clouds).
Hybrid clouds are where the external and internal service delivery methods are
integrated. Rules and policies are established by the organization based on
factors such as security needs, criticality and underlying architecture, so that
activities and tasks are allocated to external or internal clouds as appropriate.
1.13. Define Software as a Service (SaaS).
SUBTASK(S):
1.13.1. Explain SaaS.
SaaS capability is provided to the consumer is to use the providers applications
running on a cloud infrastructure2. The applications are accessible from various
client devices through either a thin client interface, such as a web browser (e.g.,
web-based email), or a program interface. The consumer does not manage or
control the underlying cloud infrastructure including network, servers, operating
systems, storage, or even individual application capabilities, with the possible
exception of limited user-specific application configuration settings.
1.13.2. Differentiate SaaS from Platform as a Service (PaaS) and IaaS.
SaaS, PaaS, and IaaS represent different delivery models of a cloud computing
environment:
1.13.2.1. SaaS delivers software as a service over the Internet as is.
1.13.2.2. PaaS delivers computing platform and a solution stack as a service.
1.13.2.3. IaaS delivers computer infrastructure as a service.
1.13.3. Provide some examples of SaaS.
1.13.3.1. Google Docs.
1.13.3.2. IBM SmartCloud for Social Business.
1.13.3.3. Salesforce.com.
1.13.3.4. ServiceNow.
1.14. Define PaaS.
SUBTASK(S):
1.14.1. Explain PaaS.
The capability provided to the consumer is to deploy onto the cloud
infrastructure consumer-created or acquired applications created using
programming languages, libraries, services, and tools supported by the
provider. The consumer does not manage or control the underlying cloud
infrastructure including network, servers, operating systems, or storage, but has
control over the deployed applications and possibly configuration settings for
the application-hosting environment
1.14.2. Explain how PaaS related to computing platform.
A computing platform describes some sort of hardware architecture or software
framework (including application frameworks), that allows software to run. A
PaaS delivers a computing platform as a service.
1.15. Define IaaS.
SUBTASK(S):
1.15.1. Explain IaaS.
The capability provided to the consumer is to provision processing, storage,
networks, and other fundamental computing resources where the consumer is
able to deploy and run arbitrary software, which can include operating systems
and applications. The consumer does not manage or control the underlying
cloud infrastructure but has control over operating systems, storage, and
deployed applications; and possibly limited control of select networking
components (e.g., host firewalls).
1.15.2. Explain how IaaS related to utility computing.
Utility computing relates to the business model in which application
infrastructure resources, hardware and/or software are delivered. While cloud
computing relates to the way we design, build, deploy and run applications that
operate in a virtualized environment, sharing resources and boasting the ability
to dynamically grow, shrink, and self-heal.
1.15.3. Explain the difference between a private IaaS and a public IaaS.
Private IaaS are deployed, operated and consumed within the boundaries of the
internal data center; in this model the IT organization standardizes the set of
infrastructural services that it provides and develop the automations to deploy
these services rapidly. The consumers of these IaaS services are business
lines of development organizations in the enterprise that request these services
through a service-catalog. Public IaaS clouds allows to deliver the same ser of
infrastructural services, but outside of the enterprise boundaries to other
companies, to managed accounts, or even to consumer users. Public cloud for
delivering IaaS services combine both the IaaS and cloud service provider
models.
1.15.4. List some examples of IaaS offerings.
1.15.4.1. Amazon Elastic Compute Cloud.
1.15.4.2. CenturyLink.
1.15.4.3. SoftLayer.
1.16. Define Database As A Service (DBaaS)
SUBTASK(S):
1.16.1. A Database-as-a-Service (DBaaS) is a service that is managed by a cloud
operator (public or private) that supports applications, without the application
team assuming responsibility for traditional database administration functions.
1.16.2. There are two common deployment models: users can run databases on the
cloud independently, using a virtual machine image, or they can purchase
access to a database service, maintained by a cloud database provider. Of the
databases available on the cloud, some are SQL-based and some use a
NoSQL data model.
1.16.3. DbaaS use cases: A DbaaS can be used to offset costs of keeping millions of
rows of data locally, data archivals, data backup, and data recovery.
1.17. Explain the benefits of patterns as description of cloud services
SUBTASK(S):
1.17.1. Describe the concept of patterns as description for cloud services:
1.17.1.1. Patterns (aka service templates) describe how cloud services and
applications are deployed, managed and scaled by an engine
supporting the format (domain specific language) of the cloud service.
1.17.1.2. Patterns describe the structure and topology of a cloud service, i.e. the
infrastructure and application components, resources and
relationships and related management processes required to deliver
the cloud service.
1.17.1.3. Pattern components are for instance definition of network and storage
elements, image, software binaries, install scripts and recipes.
1.17.1.4. Patterns can either be described in a declarative (e.g. expressed by
relationships) or imperative manner (e.g. express by a management
plan).
match application demand such that cloud user does not have to allocate
resources manually.
SaaS: In the SaaS model, cloud providers install and operate application
software in the cloud and cloud users access the software from cloud clients. The
cloud users do not manage the cloud infrastructure and platform on which the
application is running. This eliminates the need to install and run the application
on the cloud user's own computers simplifying maintenance and support.
2.3. Demonstrate base knowledge needed to advise on creating a cloud
infrastructure.
SUBTASK(S):
2.3.1. The creation of a cloud infrastructure requires an environment that needs to
address the following areas. A tester must be able to address many of these
topics
2.3.1.1. Hardware/platform: A cloud environment needs to select hardware that
can run virtualization technology. This includes distributed servers and
mainframe solutions with an operating system that supports virtualization
software.
2.3.1.2. Virtualization technology such as KVM, VMWare, zVM, etc.
2.3.1.3. Network topologies that supports the virtualization design,
WAN/LANs/MPLS, etc., as well as a topology in support of a public,
public and/or private cloud.
2.3.1.4. Security framework that meets the requirements of the public, private and
private cloud environment at a minimum. If the application(s) that will run
on the infrastructure is known, the security requirements can be used to
augment that design.
2.3.1.5. Storage and archival needs to manage the data and backup needs
2.3.1.6. Provisioning and orchestration to manage, deploy, spin up, etc.,
environments
2.3.1.7. Monitoring to provide visibility and management of the environment
2.3.1.8. Capacity, availability and performance topics can be addressed as it
relates to creating a cloud infrastructure.
2.4. Explain cloud networking principles.
SUBTASK(S):
2.4.1. Cloud computing networks -- whether they support public, private, or hybrid
clouds must be able to:
2.4.1.1. Burst up and turn down bandwidth on demand.
2.4.1.2. Provide extremely low latency throughput among storage networks, the
data center and the LAN.
2.4.1.3. Allow for non-blocked connections between servers to enable automated
movement of virtual machines (VMs).
2.7.2.
2.7.3.
2.7.4.
2.7.5.
2.7.6.
instances, but it goes without saying that being able to exploit 100% of
the available capacity would be a huge improvement from a data center
network performance point of view.
2.7.7. Optimal Use of Network Awareness:
2.7.7.1. Virtual machines are the new building block in the data center and the
importance of physical NICs for the network architecture fades when
compared to the virtual networking realm inside the server platforms. On
the other hand, it is difficult to manage both the virtual and the physical
network environment with a consistent set of tools and orchestrate
changes in an end-to-end fashion. This trend puts a lot of pressure on
the serviceability and manageability of the data center network and can
also impact its availability if changes are not agreed across different
functional teams in charge of the infrastructure management.
2.7.8. End-to-end network visibility:
2.7.8.1. Server consolidation and virtualization initiatives demand more
bandwidth per physical machine and the same is true on a WAN scale
when consolidating scattered data centers into fewer ones. This and the
fact that it is very difficult to obtain end-to-end visibility of the network
flows (different teams in charge of managing virtual resources inside
servers, Blade switches, LAN switches, and WAN routers) have the risky
consequence that it is becoming increasingly more difficult to spot and
remove network bottlenecks in a timely and seamless fashion. Clearly
this has a significant impact on the performance and even the availability
of the enterprise network if the quality of service (QoS) model is not
designed and enforced properly.
2.8. Identify the role of Web technologies and the importance of Application
Programming Interface (API) in cloud computing.
SUBTASK(S):
2.8.1. Identify the Internet, and more generally Internet-based protocols define the
channels through which cloud computing services are made available and
delivered. Highlight the Web as the primary interface to deliver such a service.
2.8.2. Focus on the concept of API as a generic abstraction through which access cloud
services.
2.8.3. Describe how existing Web service technologies and API can be used by cloud
providers to offer cloud services.
2.8.3.1. Cloud service providers use existing Web technologies such as PHP,
AJAX, REST API, SOAP, XML HTML5 and others to develop a dynamic
Web front-end for its end-users to see and order their cloud service
offerings.
2.8.4. Describe how Web technologies and API can be used by end-users to access
cloud services.
2.8.4.1. In a SaaS model, users will only be required to access to the applications
that are being offered as opposed to the infrastructure platform that the
application is running on. Generally, these applications are provided in
product or service. The model typically allows for unlimited usage during the
subscription period. So that the customer pays the same amount regardless of
the amount of resources they used.
2.10.2. Elastic pricing or Consumption-based pricing model: In this model the cost is
tied to what customer actually use. Under these models you only pay for the
amount of resources/services you actually use such as service functions, disk
space, CPU time and network traffic.
2.10.3. Market-based pricing or Spot pricing for cloud: With market-based pricing there
is a market price for a service, the market price varies over time based on
supply and demand. Market forces govern the spot-pricing model i.e., when
computing and storage resources are in high demand, the spot market will drive
the price of services higher. Conversely, when resources are in low demand,
the spot market will drive the price lower offering opportunities for bargain
hunters. On the other side as a customer you can buy the service at the current
price and use it straight away. Or you can make a bid to use the service at a
lower price and if the market price reaches your price then your workload will be
activated and you will be charged at your bid price.
2.10.4. Cloud chargeback/showback: In this model the consumer pay for the usage. It
correlates utilization back to cloud consumers or corporate departments, so that
usage can be charged if desired.
2.11. Define how cloud computing fits in with service management and the
Information Technology Infrastructure Library (ITIL) model V3 (ITIL Service
Strategy, ITIL Service Design, ITIL Service Transition, ITIL Service Operation,
ITIL Continual Service Improvement).
SUBTASK(S):
2.11.1. Explain how ITIL service strategy pertains to cloud computing.
2.11.1.1. ITIL service strategy provides guidance on clarification and
prioritization of service provider investments in services. It focuses on
helping business improve and develop over the long term, based
upon a market-driven approach. Key topics covered include service
value definition, business case development, market analysis, and
service provider types.
2.11.1.2. The market dynamics and business objectives are essentially same
in a cloud computing model. The differences would be in the
sourcing, packaging and bundling of services, and how service users
are charged for the utilization of services.
2.11.1.3. The service portfolio, which decides on a strategy to serve customers
and to develop the service providers offerings and capabilities, will
include the cloud services.
2.11.2. Explain how ITIL service design pertains to cloud computing.
2.11.2.1. ITIL service design provides good practice guidance on the design
of IT services, processes, and other aspects of the service
management effort. Its scope includes the design of new services, as
well as changes and improvements to existing ones.
2.11.2.2.
2.11.4.1.
ITIL service operation is the part of the lifecycle where the services
and value are actually directly delivered. The monitoring of problems
and balance between service reliability and cost etc. are considered.
2.11.4.2. The functions include technical management, application
management, operations management and service desk as well as,
responsibilities for staff engaging in service operation.
2.11.4.3. ITIL service operation aims to make sure that IT services are
delivered effectively and efficiently. This includes fulfilling user
requests, resolving service failures, fixing problems, as well as
carrying out routine operational tasks.
2.11.4.4. Monitoring for the availability of IT services and security compliance
will pose increased challenges when services are hosted in vendor
cloud environments.
2.11.5. Explain how ITIL continual cervice improvement pertains to cloud computing.
2.11.5.1. ITIL continual service improvement aims to align and realign IT
services to changing business needs by identifying and implementing
improvements to the IT services that support the business
processes.
2.11.5.2. The ITIL continual service improvement process aims to use
methods from quality management in order to learn from past
successes and failures. The CSI process implements a closed-loop
feedback system as specified in ISO 20000 as a means to
continually improve the effectiveness and efficiency of IT services
and processes.
2.11.6. Explain challenges in using the ITIL methodology with cloud computing.
Challenges include:
2.11.6.1. The flexibility and increasingly dynamic nature of a cloud
environment;
2.11.6.2. License management concerns (example: managing software
licenses) for virtual assets;
2.11.6.3. The separation of physical infrastructure from the services provided
by virtual assets that run on that infrastructure.
2.11.7. Explain the benefits of using a ITIL methodology with cloud computing
2.11.7.1. Cloud computing can assist with many areas of ITIL methodology
implementation. (example: using the ability to migrate virtual assets
to meet SLAs and more effectively perform capacity management)
2.11.7.2. Likewise, the fluid nature of a cloud computing environment can
benefit a formal management methodology such as ITIL.
2.11.7.3. Extending service delivery with Enterprise Service Management
(integrated with ITIL process guidelines), which allows to completely
integrated the cloud world with the remaining part of the enterprise by
including the cloud infrastructure and services in the enterprise ITIL
process guidelines.
3.2.1. Describe the roles Consumer (Customer, Partner, Agent), Creator, Provider
and Broker
3.2.1.1. Consumer represents any person or system that can interact with the
cloud computing environment, including customer, partner, developer
and provider employees.
3.2.1.2. Creators create the applications, packaging and definitions that become
the Cloud Services offered by the provider.
3.2.1.3. Provider is the entity that makes the cloud services available and
manages the support systems that manage the cloud services.
3.2.1.4. Broker is the entity to through API the user and the provider.
3.2.2. Describe the domains within the Provider Access, Cloud Services, Common
Cloud Management Platform (BSS, OSS), Infrastructure.
3.2.2.1. The Access domain provides the edge of network infrastructure for the
Provider including security, routing, network optimization and network
protection functions
3.2.3. Describe the functional categories within Business Support Services (BSS).
3.2.3.1. BSS categories are Customer Management, Product Management,
Partner Management, Subscription Management, Metering, Billing,
Rating and Charging, Financial Management, Analytics and Reporting
3.2.4. Describe the functional categories within Operational Support Services (OSS).
3.2.4.1. OSS categories are Service Automation, Package On-boarding, Service
Quality Management, Package Management, Service Operations
Management, VM Management and Resource Management
3.2.5. Describe the five access interfaces Customer Access, Storefront, Customer
Management, Partner Management, and Provider Management.
3.2.5.1. Customer Access provides the interface (visual or non-visual) for
interacting with Cloud Services.
3.2.5.2. Storefront provides the interface for discovering, selecting and ordering
Cloud Services.
3.2.5.3. Customer Management provides the interface for managing customer
accounts, users/groups and existing subscriptions.
3.2.5.4. Partner Management provides the interface for managing partner
accounts and product management by partners.
3.2.5.5. Provider Management provides the interfaces for managing the cloud
and its systems by the provider and its agents.
3.2.6. Describe the aggregated patterns provided by the Platform Services.
3.2.6.1. The Platform Services adoption pattern describes methods to provide
application development and deployment environments, middleware
deployment and management environments, and cloud integration
services where the consumer has access to the data and applications for
the platform, but not the underlying supporting infrastructure.
3.2.6.2. Application Lifecycle Management (ALM) - this pattern covers the
continuum of managing an application through governance,
development, and maintenance. Includes Analyze, On-Board, Develop,
Test, Continuous Deployment, and Manage. Focus areas: Continuous
delivery and DevOps.
3.7.3.
3.7.4.
3.7.5.
3.7.6.
zoning setup, data center setup for DR etc.) and how the cloud services
are implemented.
Examples for security considerations:
3.7.3.1. Some of the examples of security considerations as mentioned in the
IBMs CCRA are:
3.7.3.1.1. Security Event Management.
3.7.3.1.2. Security Policy.
3.7.3.1.3. Threat & Vulnerability Management.
3.7.3.1.4. Software, System & Service Assurance.
3.7.3.1.5. Data and Information Protection.
3.7.3.1.6. Security Entitlement.
3.7.3.1.7. Access & Identity Lifecycle Management.
3.7.3.1.8. Compliance.
3.7.3.1.9. Data Policy Enforcement.
Clients security objectives reflect their responsibilities when adopting
Cloud.
3.7.4.1. SaaS: At CxOs level, Security Responsibilities and Objectives
means.
3.7.4.1.1. Complete visibility to enterprise SaaS usage and risk
profiling.
3.7.4.1.2. Governance of user access to SaaS and identity
federation.
3.7.4.2. PaaS: At Application teams and different LOBs, Security
Responsibilities and Objectives means.
3.7.4.2.1. Enable developers to compose secure cloud applications and
APIs, with enhanced user experience.
3.7.4.2.2. Visibility and protection against fraud and applications threats.
3.7.4.3. IaaS: At CIO and IT teams levels, Security Responsibilities and
Objectives means.
3.7.4.3.1. Protect the cloud infrastructure to securely deploy workloads
and meet compliance objectives.
3.7.4.3.2. Have full operational visibility across hybrid cloud
deployments, and govern usage.
Cloud Security Capabilities.
3.7.5.1. Identity: Manage identities and govern user access
3.7.5.2. Protection: Protect infrastructure, applications, and data from
threats.
3.7.5.3. Insight: Auditable intelligence on cloud access, activity, cost and
compliance.
IaaS specific security considerations.
3.7.6.1. The definition of workload sensitivity will be determined by a Customers:
3.7.6.1.1. Risk management framework.
3.7.6.1.2. Compliance obligations.
3.7.6.2. Typical examples of sensitive workloads include:
3.7.6.2.1. Sensitive personal information of employees, partners and
clients.
3.8.2.
3.8.3.
3.8.4.
3.8.5.
3.9. Define four defining principles of Cloud computing as presented in the IBM
CCRA V4.
SUBTASK(S):
3.9.1. Efficiency Principle - Design for cloud-scale efficiencies:
When realizing cloud characteristics such as elasticity, self-service access, and
flexible sourcing, the cloud design is strictly oriented to high cloud scale
efficiencies and short time-to-delivery/time-to-change.
To implement a cloud following this principle with that high level of efficiency and
flexibility, a very high degree of standardization (i.e. minimal variety in the data
center with respect to numbers of server, storage, network technologies,
operating systems & versions, middleware products, applications, etc.) is
required to enable high degrees of automation. The higher the degree of
standardization / minimization of variety are, the better automation can be
realized (assuming a well-integrated and interoperable set of management
components). In a highly homogeneous public cloud data center this can be
achieved more effectively compared to private cloud enterprise data centers
running a variety of workloads each of them having different requirements, so
there is typically a trade-off between degree of standardization and level of
efficiency.
3.9.2. Lightweightness Principle Support lean service management:
The CCMP fosters lean and lightweight service management policies, processes,
and technologies.
Fundamental restructuring and streamlining of IT management processes is
required to maximize the elimination of manual data center management tasks.
The main factors for reducing operational costs are elimination of tasks which are
not needed any more due to limited scope of managed (e.g. in compute cloud
only managing up to and including the hypervisor) and optimization (e.g. not
immediate repair of a failed physical machine enabled by automated restart of
crashed VMs or nodes or automating the service activation process, which is
typically very time- and cost-intensive in traditional outsourcing environments).
3.9.3. Economies-of-scale Principle Identify and leverage Commonalities:
All commonalities are identified and leveraged in cloud service design.
In this principle the goal is to reuse management/CCMP components and enable
Economies-of-scale (with respect to initial standup & operational costs and
reduced time-to-market) by sharing a single/common management platform to
deliver and manage many cloud services. Examples of components with reuse
potential are metering, monitoring, service automation, management User
Interface (UI) components etc.
3.9.4. Generic Principle Define and manage generically along the lifecycle of
cloud services:
Be generic across IaaS, PaaS, SaaS, BPaaS and provide exploitation
mechanism to support various cloud services by using a shared management
platform. It is essential to introduce a model which allows cloud service
developers to specify how the CCMP functionality gets used in the context of
their specific cloud service and how based on that definition or template
instances of that cloud service get delivered to cloud service consumers. This
has been taken into account in the CCMP RA design. The remaining task for the
cloud management platform architect is to design how the CCMP management
functionality gets exploited in the context of the respective cloud service. This is
achieved by creating a set of service type-specific artifacts as required by the
respective management platform components (e.g. cloud service-specific scripts,
monitoring agents, etc.).
3.10. Describe Cloud Service Consumers, Cloud Service Creators, Cloud Service
Provider, Cloud Services and the Common Cloud Management Platform.
SUBTASK(S):
3.10.1. Explain the role of the Cloud service consumer:
Cloud service consumers require a simplified interface with well-defined service
offerings, pricing and contracts.
3.10.1.1. The cloud service consumer is the individual, organization or system
which consumes service instances delivered by a particular cloud
service.
3.10.1.1.1. Examples of service consumption are requests for virtual
servers, changes to CPU capacity, requests for storage
based on pre-defined templates, etc
3.10.1.2. Cloud service consumers browse the service offering catalog and
trigger service instantiation requests.
3.10.2. Explain the role of the Cloud service provider:
Cloud service providers are the owners of the CCMP, and are responsible for
providing cloud services to the cloud service consumer.
3.10.2.1. The cloud service provider may itself be a consumer of the CCMP (in
a hosted SaaS offering for example), or they may be running the
CCMP themselves.
3.10.3. Explain the role of the Cloud service creator:
Cloud service creators are responsible for creating the services being offering in
the cloud services offering.
3.10.3.1. Cloud service creators produce their cloud services by leveraging and
enhancing functionality exposed by the cloud service provider.
3.10.3.2. Cloud service creators would be responsible for the design, testing,
implementation and maintenance of management artifacts specific to a
cloud service.
3.10.3.3. The cloud service creator can be an organization (e.g., ISV company)
or an individual (e.g., business/technical specialists in the ISV creating
services)
3.10.4. Describe Cloud Services as defined by the IBM CCRA V4:
3.10.4.1. There are 4 categories of cloud services: IaaS, PaaS, SaaS, BPaaS
3.10.4.2. In contrast to traditional IT services, cloud services have attributes
such as pay-per-usage, self-service usage, flexible scaling and
shared-usage.
3.10.5. Describe the CCMP:
3.10.5.1. The CCMP architecture is responsible for delivering instances of cloud
services of any category to cloud service consumers, in an ongoing,
self-service fashion.
3.10.5.2. The infrastructure element layer relates to the hardware infrastructure
such as facilities, servers, storage, and network resources.
3.12.5.2. Use of Cast Iron and integration solutions for exposing services or for
using services from other SaaS environments.
3.13. Understand the role of goverance in the CCRA.
SUBTASK(S):
3.13.1. Define the governance model for a cloud deployment.
3.13.1.1. Utilize existing policies, or define new policies, of the Cloud Service
Provider that have relevance to the Cloud environment.
3.13.1.2. For human governance policies, define the policies in employee
practices to be followed.
3.13.1.3. For business/machine governance policies, define the policies in rules
to be monitored and/or audited.
3.13.2. Deploy the policies.
3.13.2.1. For human policies, produce or extend the employee handbook (or
equivalent).
3.13.2.2. For business policies, include the policies in business processes
(manual and automated).
3.13.2.3. For machine policies, define rules to be deployed to policy definition
and policy enforcement systems.
3.13.2.4. For auditing policies, define rules to be deployed to auditing systems.
3.14. Describe non-functional requirements (NFRs) in the context of a cloud
solution.
SUBTASK(S):
NFRs identify critical aspects of the cloud solution that are not feature/function related.
NFRs impact the solution design by clearing identifying key characteristics of cloud
operations.
3.14.1. Availability and serviceability includes characteristics such as high availability,
DR, acceptable downtime or degradation of services during maintenance. The
availability expectations of a system relate to how many hours in the day, days
per week, and weeks per year the application is going to be available to its
users and how quickly they should be able to recover from failures. Since the
system includes Software (including applications), Hardware and Network
components, this requirement extends to all three types. The serviceability
expectations must integrate with existing support structure and support
processes, provide a ticketing system to log/track problem tickets and that
integrated with an existing ticketing system, support automatic patch download
and installation and provide sufficient diagnostic information (logs, dumps,
traces) to expedite problem resolution and support service level agreements
often measured by key performance indicators (KPIs) like 98.5% availability or
Full restoral to service in < 4 hrs or Maintenance window limited to a two hour
window once per month on second Saturday.
3.14.2. Performance includes UI and VM expected performance. The cloud
infrastructure and services must be able to meet the response time, throughput
3.14.3.
3.14.4.
3.14.5.
3.14.6.
3.15.1. build mobile apps for bringing business functionalities in existing business
applications, new enterprise functionality built for mobile, business solutions,
business processes and business performance on mobile devices
3.15.2. Protect the BYOD devices and the mobile end points and prevents fraud and
secure the mobile ecosystem
3.15.3. Engage with mobile app and Web users at the optimal time and place, and
analyze customer behavior and customer experience
For more information review IBM MobileFirst & Cloud Computing
4.2.3. Explain difference between supporting on prem vs. off prem PaaS development
4.2.3.1. Off-premise PaaS solution means no worries about anything
infrastructure for anyone within the organization. On the other hand, an
off-premise premise PaaS solution comes with the same baggage as offpremise IaaS offerings: a lack of control and visibility into the
infrastructure. Visibility and control that is often considered critical to
maintaining performance of applications and applying appropriate
security and access control policies.
4.2.3.2. On-premise PaaS comes with a larger price tag and a longer time to
implement, both of may be show-stoppers for those organizations that
cannot risk capital or time. Forward looking capable organizations, onpremise PaaS will ultimately offer both the reduction in costs (over time)
as well as the highly desirable operational benefits without compromising
on visibility or control.
4.2.4. List the solutions and products that implement the adoption pattern.
4.2.4.1. The Platform Services adoption pattern describes methods to provide
application development and deployment environments, middleware
deployment and management environments, and cloud integration
services where the consumer has access to the data and applications for
the platform, but not the underlying supporting infrastructure.
4.2.4.2. Solutions prescribed to implement the patterns:
4.2.4.2.1. IBM SmartCloud Continous Delivery
4.2.4.2.2. IBM Bluemix
4.2.4.2.3. IBM Workload Deployer
4.2.4.2.4. IBM PureApplication Systems
4.2.4.2.5. IBM PureApplication Service on SoftLayer
4.2.4.2.6. Rational Asset Manager
4.2.4.2.7. Rational Automation Framework
4.2.4.2.8. IBM Cloud Managed Services for SAP Applications
4.2.4.2.9. IBM Cloud Managed Services for Oracle Applications
4.3. Describe how IBM Cloud Computing products and solutions can be
leveraged to design and provide an effective Software as a Service (SaaS)
solution.
SUBTASK(S):
4.3.1. Implement Existing Applications to be Delivered as SaaS solutions
Includes analysis of a non-cloud application to understand the application's
platform requirements (operating system, middleware, code libraries, etc.) and
cloud characteristics (multi-tenancy, service oriented architecture, etc.);
implementation of application modifications to enable cloud services; and
definition of the required cloud infrastructure and platform environment for the
application. Describes the major logical components that allow to build a SaaS
solution and how the below components map to the corresponding IBM products
that realize them.
4.3.1.1. Cloud Platform Technology.
4.3.1.1.1.
4.3.1.1.2.
4.3.1.1.3.
4.3.1.1.4.
DbaaS use cases: A DbaaS can be used to offset costs of keeping millions of
rows of data locally, data archivals, data backup, and data recovery. Here are
some examples as it relates to cloud adoption patterns
4.4.1.1. PaaS: A DbaaS can serve as a database layer built on open source
databases, noSQL database solutions, data warehouse, master data
management (MDM), and/or enterprise solutions such as DB2 and
MySQL as part of an overall PaaS cloud platform environment in support
of a common computing platform. For example, a database layer is
required fo web application development or a reporting and analytics
PaaS environment. To meet the growing needs of those PaaS
environments, a DbaaS can be used to extend the data layer. IBM's
Cloudant acquistion can provide these capabilities as well as offerings
provided by BlueMix, SoftLayer and IBM's Cloudera business partner.
4.4.1.2. IaaS: DbaaS can serve as a database layer built on open source
databases, noSQL data providers or enterprise solutions such as DB2
and MySQL. The platform selection would be the core infrastructure and
in cloud service provider environment can server as the IaaS. The
appropriated database software would then be installed and any
management clients and tools can also be installed on the infrastructure
or appropriate computing environment to access that database. IBM
SoftLayer can offer bare metal to create the infrastructure for a DbaaS as
well as an IaaS built on Power, x86 and more to create a DbaaS cloud
computing environment.
4.4.1.3. A DbaaS, with database related software that provides a computing
solutions is part of an overall SaaS solution. An example would be MaaS
360 and SmartCloud Control Desk, and Emptoris contract management
software where the a database component can grow and a DbaaS may
be needed to manage data growth.
4.4.2. An on-prem DbaaS cloud computing environment is a a DbaaS environment that
is part of the client's on-site computing environment.
4.4.3. Examples of how a DbaaS environment can solve a client's data layer needs in
an overall computing environment are: Archival solutions, Big Data solutions,
reporting and advanced analytics, and an extended database environment in
support of a business application to offlset the workload.
4.5. Define considerations of storage and data recovery in an IBM Cloud Solution
also taking into consideration the different types of storage and how to use
them in the different cloud environments.
SUBTASK(S):
4.5.1. Explain considerations of storage and data recovery in an IBM Cloud Solution
4.5.1.1. Cloud general storage requirements:
4.5.1.1.1. Scalability; low cost.
4.5.1.1.2. Dynamic, unpredictable workloads.
4.5.1.1.3. Automated management, provisioning, performance
monitoring and tuning.
4.5.1.1.4.
4.5.1.1.5.
4.5.1.1.6.
4.5.1.1.7.
4.5.2.
4.5.3.
4.5.4.
4.5.5.
Next Steps
1. Take the CCRA V4 assessment test using the promotion code ccstudy for $10
($20 USD savings).
2. If you pass the assessment exam, visit pearsonvue.com/ibm to schedule your
testing sessions. Use the promotion code ccguide to receive 20% off.
3. If you failed the assessment exam, review how you did by section. Focus
attention on the sections where you need improvement. Keep in mind that you
can take the assessment exam as many times as you would like ($10 per exam),
however, you will still receive the same questions only in a different order.