Cloud Computing Management

SharePoint requires all three components: .NET Framework for the application runtime, SQL Server for the content database, and a Windows Server operating system as it cannot run on client Windows versions.

Concurrency issues, memory leaks, and CPU resource contention on multi-core systems cannot be predicted by scaling down data on a single-CPU machine. Results from a single-core environment do not extrapolate linearly to highly parallel 24-CPU systems under heavy production load.

SOA (Service-Oriented Architecture) delivers functionality as services - reusable business capabilities accessible via standard interfaces. This shifts from monolithic applications to composable services. 'Software as service' refers to SaaS delivery model, while 'Infrastructure as service' is cloud computing.

SOA services are typically heterogeneous, using different technologies, programming languages, and platforms, communicating through standardized interfaces. This heterogeneity is a key feature - services can be implemented in Java, .NET, Python, etc., and still interoperate.

The primary goal of web services is interoperability - enabling different applications and systems to communicate regardless of their underlying platforms or languages. While security and reliability are important, they are quality attributes, not the fundamental purpose. Efficiency is often traded for interoperability.

High availability systems require multiple components to ensure continuous operation. Resilience allows the system to recover from failures, failover provides automatic switching to backup systems, and recovery procedures restore normal operations after an outage. All three (Resilience, Failover, Recovery) are fundamental components of a high-availability architecture.

Failover is the service that automatically switches to a standby system when the primary system fails, thereby reducing service outage duration. Recovery is about restoring after an incident, Monitoring tracks health, and Analysis Support provides insights, but only Failover actively reduces outage time by maintaining continuity through redundant systems.

Cloud computing reduces hardware costs by eliminating the need for local infrastructure - you rent resources from providers. It also enables universal access to data and applications from any location with internet connectivity. Option B is incorrect because cloud computing follows a pay-as-you-go model, not high upfront investments.

The description matches cloud computing precisely: centralized shared infrastructure (like power plants) that users access on-demand, paying only for what they use. Grid computing (B) is about distributed resource sharing across organizations. Utility computing (D) is the billing model, not the architecture.

Google App Engine, Microsoft Azure, and Force.com are all major Platform-as-a-Service (PaaS) offerings. PaaS provides a platform for developers to build applications without managing underlying infrastructure. Option D correctly identifies that all three are PaaS providers.

The standard cloud deployment models are Public, Private, Community, and Hybrid clouds. 'On premise private cloud' is not a distinct classification - it's simply describing where a private cloud is deployed (on-premise vs. hosted), but the classification itself remains 'Private cloud'. The deployment location is an implementation detail, not a separate category.

Cloud computing delivers services through three primary models: IaaS (Infrastructure as a Service - e.g., AWS EC2, Azure VMs), PaaS (Platform as a Service - e.g., Heroku, Google App Engine), and SaaS (Software as a Service - e.g., Gmail, Salesforce). Since all three are valid cloud service models, 'All the above' is the correct answer.