WGU - Cloud Foundations - C849 with 100% correct answers

Multitenacy

Allowing multiple systems to run on a more powerful server.

Private clouds

Provisioned for use by a single user or group of users within an organization, the private cloud is owned, managed, and operated by the organization. Private clouds reside on a private network owned or managed by the organization itself. The private cloud is often the first entry into this technology for the data center, providing flexibility and resource consumption monitoring across cloud hosts located in organizational data centers. Private clouds are often selected when external mandates such as regulations and legislative requirements require a high degree of access accountability, control, and governance.

Community clouds

Provisioned for use by a group of related organizations with shared concerns, such as a group of governmental or educational institutions that choose to share a common cloud of services not available to the general public, community clouds may reside as local, private cloud resources for the hosting organization and be accessed remotely as a community cloud by its partner organizations. Partitioned public clouds are examples of community clouds, with public cloud services isolated from general consumption through limitations restricting access to specified network address schemes or other forms of access specification. Community clouds can be used to gain improved reuse and sharing of information resources, such as an online call center application that can be transferred between geographically distributed support staff members to provide 24/7 coverage using the same application technology base.

Public clouds

Provisioned for use for the general public, public cloud services represent the most thoroughly virtualized cloud infrastructural design, removing data center information resources partially or completely. Public clouds reside on hosting data center resources and are accessed via public internet connectivity by users located anywhere in the world. Transparent redirection of public cloud services to data centers in variable locations presents concerns for organizations with regulatory or legislative mandates demanding data accountability and governance.

Hybrid clouds

Provisioned using components of private, community, or public clouds, the hybrid cloud provides access to two or more infrastructures bridged by standardized technologies or proprietary cloud services. Hybrid clouds are simply a mixture of cloud types, such as a private cloud customer relationship management (CRM) application together with public cloud Google Apps services used to integrate CRM data into an organization's collaboration services.

Cloud bursting

A hybrid cloud implementation where local private cloud resources are used in support of an application until a spike in demand exceeds local resource limits, at which point the app "bursts" out of the private cloud into designated public cloud resources to manage the overrun. Designated cloud providers must be running a compatible platform to support cloud bursting from the private cloud.

Sharding

Cloud-based database services can break up a large data set into a number of sub-data sets to be distributed across hosting servers to improve performance and data throughput for very large business applications. MongoDB, for example, is used to manage high-volume transaction databases for SAP's content management service, EA's game download manager, and the New York Times's story submission application. Scaling resources to meet such demands for submission rates in traditional application models would have required specialized and costly high-performance computing solutions for transaction load balancing and high data throughput.

Database profiling

The potential for unanticipated or undesirable data modification increases with the volume of processed data, requiring database and data analysis to support the integrity aspect of data security. Some DBaaS cloud services such as MondoDB have a built-in database profiling tool that can review big data sets and data to identify predictable issues that may arise so that application design alternatives can be developed.

Database as a Service (DBaaS)

Database as a Service represents an element of Infrastructure as a Service (IaaS) implementation, providing for the storage and processing of extremely large data sets using cloud resource scalability.

Everything as a Service (XaaS)

Everything as a Service represents the continued expansion of cloud-service-level combinations and integration between cloud and traditional services. This is not a clearly defined term but a living reference used to describe whatever the current level of integration provides.

Vertical scaling

Involves adding resources to a single node, such as memory, processing power, or redundant components. Also referred to as Scaling up.

Horizontal scaling

Involves adding more nodes to a distributed system. Also referred to as Scaling out.

Vertical and horizontal scaling note

If both vertical and horizontal scaling are used to address a performance or reliability issue, it is referred to as diagonal scaling.

Direct costs

Are those that can be assigned to a particular process, product, or service. For example, if a company wanted to implement a document imaging system, the cost of scanners would be considered a direct cost.

Indirect costs

Support multiple processes, products, or services. Continuing with the same example, if the imaging system's storage was on the storage area network (SAN), along with files, email, and databases, the cost of the SAN would be indirect.

Federation

The collection of multiple cloud resource pools into a single manageable whole.

Fabric

Underlying infrastructure used for cloud computing. For instance, storage fabric is used to represent all storage available to provision VMs on a cloud; network fabric represents the physical network used by virtualization hosts in a cloud environment.

Service-oriented architecture (SOA)

A set of interface programming standards that allow software-to-software interoperability between applications written using differing API standards.

Stateful applications

Stateful applications require information about objects to be maintained between calls to a server. Because in a distributed environment, especially in a cloud environment, there is no guarantee that the same server will answer subsequent requests from a client, stateful objects should be avoided at all costs.

Stateless objects

A stateless object represents just one state for its whole life cycle. Modeling this as an immutable object, whose fields are initialized only once during construction and then remain unchanged, seems to be the most straightforward design technique.

Incident/incident management

Any event which is not part of the standard operation of a service and which causes, or may cause, an interruption to or a reduction in, the quality of that service. The stated ITIL objective when dealing with incidents is to "restore normal operations as quickly as possible with the least possible impact on either the business or the user, at a cost-effective price."

ITIL Service Strategy

The ITIL Service Strategy volume provides guidance on classification of service provider investments in services. The most important topics covered in service strategy are service value definition, service assets, market analysis, business case development, and service provider types. The following processes are covered in Service Strategy:

Strategy management

Demand management

Service portfolio management

Financial management

Business relationship management

ITIL Service Design

ITIL Service Design provides guidance on the design of IT services, processes, and service management. Design in ITIL focuses more specifically on services provided to the organization instead of individual technologies. The following processes are covered in Service Design:

Design coordination

Service management catalog

Service level management

Availability management

Capacity management

IT service continuity management

Information security management

Supplier management

ITIL Service Transition

ITIL Service Transition provides guidance on the deployment of services required by an organization into a production environment. The following processes are covered in Service Transition:

Transition planning and support

Change management

Service asset and configuration management

Release and deployment management

Service validation and testing

Change evaluation

Knowledge management

ITIL Service Operation

ITIL Service Operation provides guidance on achieving the delivery of agreed levels of service to end users and the organization. The following processes are covered in Service Operation:

Event management

Incident management

Problem management

Request fulfillment

Access management

ITIL Continual Process Improvement

ITIL Continual Process Improvement provides guidance on aligning and realigning IT services to changing business needs by identifying and implementing improvements to the IT services used to support the business. Continual Process Improvement needs to be planned and scheduled as a process with well-defined activities, inputs, outputs, and roles.

Synthetic transaction

Synthetic transactions are prerecorded actions taken on a service that mimic a user accessing the service and executing regular tasks. They are executed from locations where a user would normally connect to the service. That way, you are able to tell if the service is available to the user at a given facility and, if it's available, how long it takes to execute predefined actions.

Operational-level agreement (OLA)

A formal, negotiated document that defines (or attempts to define) in quantitative (and perhaps qualitative) terms the service being offered to an internal customer, such as a different department in your organization. Similar to a SLA.

Warranty

Warranty, as defined by ITIL, measures the availability, capacity, continuity, and security of a service.

Management Security Controls

Management controls include guidelines, standards, and policies. They align with an organization's goals and regulatory requirements and provide a framework for operational procedures.

Technical Security Controls

Technical controls are those applied directly to and executed by information technology resources. Examples include access control, authentication, firewalls, and encryption.

Operational Security Controls

Operational controls generally involve processes and procedures enacted by individuals. They are based on management controls and incorporate technical controls. Examples include disaster recovery planning, configuration management, incident response, and physical security.

Information security management system (ISMS)

A system of policies, processes, and controls used to identify, implement, monitor, and update appropriate and cost-effective security measures based on current business needs.