Computer Knowledge
Cloud Computing Management
2,340 Questions
Cloud computing management involves administering web based services, data storage, and network security protocols. This subject is heavily featured in the computer aptitude sections of banking and government recruitment tests. The practice questions address SaaS backup, cross region storage replication, and serverless application designs.
SaaS data backupPaaS use casesCloud storage replicationServerless applicationsCloud security tools
Cloud Computing Management Questions
-
Node Agent
-
Web server Plug-in
-
Caching proxy
-
Deployment Manager
-
Load Balancer
B,E
Correct answer
Explanation
Web server plug-ins distribute incoming requests across multiple application server instances, while load balancers distribute network traffic across multiple servers. Both are essential for managing workload distribution and preventing overload on any single component.
-
Create a design using multiple machines that handle the full production load, enabling the use
-
Utilize load balancers between the Web servers and the application servers to provide failover
-
Place the Authentication servers outside of the intrusion firewall with the Web servers, since
-
Use the largest processor engines and least number of physical machines for the application
A
Correct answer
Explanation
The best practice for high availability is using multiple machines each capable of handling the full production load, allowing for failover when one machine fails. Load balancers alone between web and app servers don't provide complete HA. Authentication servers should be behind firewalls, not outside. Using fewer, larger machines creates a single point of failure.
-
a) To transport the messages between software components
-
b) contains information (metadata) about all the components that the SOA supports.
-
c) provides reference information about software components that are running or available for use
-
d) All the above
A
Correct answer
Explanation
The Enterprise Service Bus (ESB) is the communication backbone that transports messages between different software components in an SOA architecture. It provides routing, transformation, and protocol mediation capabilities.
-
a) The enterprise service bus (ESB)
-
b) The SOA registry
-
c) Workflow engine
-
d) SOA supervisor
C
Correct answer
Explanation
The Workflow Engine is the central orchestration point in SOA, responsible for coordinating all service interactions and business process execution. It manages the sequence and flow of service invocations to complete business processes.
-
a) Logic is divided into services with the intention of promoting reuse
-
b) Services maintain a relationship that minimizes dependencies and only requires that they maintain an awareness of each other
-
c) Services have control over the logic they encapsulate
-
d) Beyond what is described in the service contract, services hide logic from the outside world
B
Correct answer
Explanation
Service loose coupling in SOA means services maintain relationships that minimize dependencies and only require awareness of each other. This allows services to be modified or replaced without breaking the entire system. Option A refers to service reuse, C to service autonomy, and D to service abstraction - different SOA principles.
-
a) Logic is divided into services with the intention of promoting reuse
-
b) Services maintain a relationship that minimizes dependencies and only requires that they maintain an awareness of each other
-
c) Services have control over the logic they encapsulate
-
d) Beyond what is described in the service contract, services hide logic from the outside world
B
Correct answer
Explanation
Service loose coupling in SOA means services maintain relationships that minimize dependencies and only require awareness of each other. This allows services to be modified or replaced without breaking the entire system. Option A refers to service reuse, C to service autonomy, and D to service abstraction - different SOA principles.
-
a) Services minimize retaining information specific to an activity
-
b) Logic is divided into services with the intention of promoting reuse
-
c) Collections of services can be coordinated and assembled to form composite services
-
d) Beyond what is described in the service contract, services hide logic from the outside world
A
Correct answer
Explanation
Service statelessness in SOA means services minimize retaining information specific to an activity. This improves scalability by reducing memory requirements and allowing any service instance to handle any request. Statelessness is a key design principle in cloud and distributed systems.
-
a) Enterprise Message Model is usually not mandatory
-
b) Vendor not depending, it requires less hardware to run.
-
c) Both a & b
-
d) None of the Above
D
Correct answer
Explanation
The disadvantages of an Enterprise Service Bus (ESB) include increased architectural complexity and high hardware overhead. Since none of the options accurately describe these drawbacks, 'None of the Above' is correct.
-
a) The enterprise service bus (ESB)
-
b) The SOA registry
-
c) Workflow engine
-
d) SOA supervisor
D
Correct answer
Explanation
The SOA Supervisor is the central control point for all SOA orchestration, overseeing service levels, performance, and compliance across the ecosystem. The ESB handles messaging; Registry manages metadata; Workflow engine manages specific business processes.
-
a) Logic is divided into services with the intention of promoting reuse
-
b) Services maintain a relationship that minimizes dependencies and only requires that they maintain an awareness of each other
-
c) Services have control over the logic they encapsulate
-
d) Beyond what is described in the service contract, services hide logic from the outside world
B
Correct answer
Explanation
Service loose coupling means services minimize dependencies and only maintain awareness of each other through their contracts. This allows independent evolution and deployment. Option A describes service division, not coupling. Option C describes autonomy. Option D describes abstraction.
-
Well-defined interfaces
-
Loose coupling
-
Service granularity
-
Stateless service design
A,B
Correct answer
Explanation
Well-defined interfaces (A) specify contracts without revealing implementation, allowing services to interact through public interfaces only. Loose coupling (B) means services have minimal dependencies on each other's internal details. Service granularity (C) is about functional scope size, not implementation hiding. Stateless design (D) avoids maintaining conversation state but doesn't address implementation awareness.
-
Loose coupling
-
Object based
-
Synchronous
-
Fine-grained
A
Correct answer
Explanation
Loose coupling is the defining characteristic that distinguishes SOA from previous distributed approaches like CORBA, DCOM, or tight monolithic architectures. Loose coupling means services can evolve independently without breaking consumers. Object-based (B) is not unique to SOA, synchronous (C) isn't required, and SOA typically uses coarse-grained (not fine-grained) services.
-
Domain Service and Licensing Service
-
Gateway Service and Log Service
-
Authentication Service and Admin Service
-
Integration Service and Repository Service
B
Correct answer
Explanation
In Informatica PowerCenter, Gateway Service and Log Service are classified as Core Services that run on every node in the domain to manage basic node operations and logging.
-
Domain Service and Licensing Service
-
Gateway Service and Log Service
-
Authentication Service and Admin Service
-
Integration Service and Repository Service
B
Correct answer
Explanation
Gateway Service and Log Service are core services that can be configured by administrators. Domain Service, Licensing Service, Authentication Service, Admin Service, Integration Service, and Repository Service are either not user-configurable or are system-managed core services.
-
Library Services
-
Federated Services
-
Content Storage Services
-
Application Integration Services
C
Correct answer
Explanation
Content Storage Services (CSS) is the Documentum service that enables automated movement of content between different storage tiers based on policies. This allows organizations to optimize storage costs by moving less frequently accessed content to cheaper storage tiers.