Cloud Service A is hosted by Virtual Server A. Cloud Storage Device A contains LUN A. Cloud Storage Device A is a multi-tiered cloud storage device with different types of disk groups that perform at different levels. LUN A is located in the disk group with the highest performance level. Cloud Service B is hosted by Virtual Server B. Virtual Servers A and B are hosted by HypervisorA, which is installed on a physical server (not shown) that resides in Cloud A. A redundant implementation of LUN A is replicated synchronously to Cloud Storage Device C. Cloud Storage Device C does not support multiple types of disk groups and resides in Cloud B, which is located in a different geographic region than Cloud A. Requests that cloud service consumers send to Cloud Services A and B are intercepted by an automated scaling listener responsible for initiating scaling activities.
Cloud Service Consumer A issues a request to Cloud Service A (1). To process the request, Cloud Service A accesses LUN Aon Cloud Storage Device A (2). Cloud Service Consumer B issues a request to Cloud Service B (3). To process the request, Cloud Service B accesses LUN B on Cloud Storage Device B (4). When Cloud Service Consumer A accesses Cloud Service A, there is usually no noticeable performance fluctuation, even during peak usage periods. However, recently, Cloud Storage Device A became unexpectedly unavailable, requiring that Cloud Service A access LUN A on Cloud Storage Device C instead. During the following outage period for Cloud Storage Device A, Cloud Service Consumer A encounters inconsistent performance from Cloud Service A, including unusual delays that occur whenever the data requested by Cloud Consumer A isn't cached and Cloud Service A is required to retrieve the data from LUN A. Which of the following statements describes a solution that can address this problem?
Free C90.06 Practice Test Questions and Answers (2026)
Cloud Service A and Cloud Service B perform different functions but both share access to Cloud Storage Device A when fulfilling requests from cloud service consumers that require data access. Cloud Services A and B are hosted by Virtual Server A, which is hosted by Hypervisor A on Physical Server A. Cloud Service Consumer A accesses Cloud Service A to issue a request for data (1). Cloud Service A queries a database in Cloud Storage Device A to retrieve the data (2). Upon receiving the requested data, Cloud Service Consumer A combines it with additional data to form a new collection of data. Cloud Service Consumer A then accesses Cloud Service B and provides it with the new data (3). Cloud Service B accesses a different database in Cloud Storage Device A to store the new data (4). Cloud Consumer B accesses the usage and administration portal to upload new data (5). The data is uploaded to Cloud Storage Device B (6). Cloud Service Consumer A belongs to Organization A. Cloud Consumer B belongs to Organization B. 
A cloud provider has two cloud environments (Cloud A and Cloud B) that are in different geographical regions. Cloud Service A resides in Cloud A. A redundant implementation of Cloud Service A resides in Cloud B. An automated scaling listener is used in Cloud A to automatically balance the workload of requests for Cloud Service A across the two redundant implementations. Cloud Service A is required to access Cloud Storage Device A, which also resides in Cloud A. A redundant implementation of Cloud Storage Device A is located in Cloud B. A failover system is used to ensure that if the Cloud Storage Device A implementation in Cloud A fails, the Cloud Storage Device A implementation in Cloud B takes its place. Cloud Service Consumer A is owned by Organization A. Cloud Service Consumer A sends a request to Cloud Service A (1). The automated scaling listener intercepts the request and directs it to the Cloud Service A implementation in Cloud A (2). This Cloud Service A implementation attempts to access Cloud Storage Device A in Cloud A, but Cloud Storage Device A fails (3). The failover system redirects the request to Cloud Storage Device A in Cloud B (4). Cloud Service Consumer B sends a request to Cloud Service A (5). The automated scaling listener intercepts the request and directs it to the Cloud Service A implementation in Cloud B (6). This Cloud Service A implementation accesses Cloud Storage Device A in Cloud B to fulfil the request (7). 
Ready-Made Environment A is hosted by Virtual Server A and Ready-Made Environments is hosted by Virtual Server B. Virtual Servers A and B are hosted by Hypervisor A, which is part of a hypervisor cluster. An automated scaling listener intercepts cloud consumer requests and automatically invokes the on-demand generation of additional instances of ready-made environments, as required. A self-service portal and a usage and administration portal are also available to cloud consumers. The self-service portal can be used to request the provisioning of a new ready-made environment. Any cloud consumer that has already had a ready-made environment provisioned can configure and view information about that ready-made environment via the usage and administration portal. Cloud Consumer A accesses Ready-Made Environment A to work on the development of a new cloud service (1). Cloud Consumer B accesses Ready-Made Environment B to test a recently completed application comprised of three cloud services (2). Cloud Consumer C accesses the self-service portal to request the creation of a new ready-made environment (3). 
Cloud Sen/ice A is hosted by Virtual Server A, which is hosted by Hypervisor A on Physical Server A. Cloud Service B is hosted by Virtual Server B. Virtual Server C hosts Cloud Services C and D. Virtual Server B and Virtual Server C are hosted by Hypervisor B on Physical Server B. Cloud Service Consumer A accesses Cloud Service A (1). Cloud Service Consumer B accesses Cloud Service A (2). Cloud Service Consumer C accesses Cloud Service A (3) and then accesses Cloud Service B (4). 
Physical Server A hosts Hypervisor A which hosts Virtual Server A, Virtual Server B and an active cluster comprised of three virtual servers. Virtual Server A hosts Ready-Made Environment A. Ready- Made Environment A uses Cloud Storage Device A to store data related to the ready-made environment and its users. Cloud Service A is hosted by a high-availability (HA) virtual server cluster. Hypervisor A is a cluster-enabled hypervisor. 
Cloud Service A is installed on Virtual Server A and the database it accesses is located on Cloud Storage Device A. Both Virtual Servers A and B are hosted by Hypervisor A. Requests from cloud service consumers are intercepted by an automated scaling listener that automatically routes subsequent requests to additional instances of Cloud Service A whenever the given usage of an instance exceeds two concurrent requests. 
Virtual Server A and Virtual Server B are hosted by Hypervisor A, which resides on Physical Server A. Virtual Server A hosts Cloud Service A. Virtual Server C. Virtual Server D, Virtual Server E and Virtual Server F are hosted by Hypervisor B on Physical Server B. Physical Server C, which hosts Hypervisor C, is currently not being used. Cloud Service Consumer A accesses Cloud Service A (1), which accesses files stored in a folder on Virtual Server A (2). Cloud Consumer B uses Proprietary User Portal A to administer legacy software (not shown) installed on Virtual Server D (3). Proprietary User Portal B and Proprietary User Portal C are also available for accessing additional legacy systems located on Virtual Server F; however, they are not often used. 
Virtual Server A is hosted by Hypervisor A, which resides on Physical Server A. Virtual Server A hosts Cloud Services A and B. Virtual Server B is hosted by Hypervisor B on Physical Server B. Physical Server C is currently not being used. Cloud Service Consumer A sends a request to Cloud Service A that is intercepted by Pay-Per-Use Monitor A (1), which collects billing-related usage data that is later forwarded to the billing management system (2). Cloud Service A receives and processes the request (3). Cloud Consumer B accesses the usage and administration portal (4) to access data on Cloud Storage Device B. Pay-Per-Use Monitor B intercepts the data access to collect and forward billing-related usage data to the billing management system (5). Cloud Storage Device B processes the data access request from Cloud Consumer B (6). 
Cloud Service A is hosted by Virtual Server A, which is hosted by Hypervisor A that resides on Physical Server A. Cloud Storage Device A is used to store media library data that is continuously replicated with a redundant, secondary implementation of Cloud Storage A (not shown). Access to Cloud Service A is monitored by Pay-Per-Use Monitor A. Access to Cloud Storage Device A is monitored by Pay-Per-Use Monitor B. Pay-Per-Use Monitors A and B capture billing-related usage data that is forwarded to a billing management system that is hosted by Physical Server B. Cloud Service Consumer A accesses Cloud Service A and the usage data is captured by Pay-Per-Use Monitor A (1). Cloud Consumer B accesses Cloud Storage Device A via a usage and administration portal that it uses to upload media data (2). This usage is captured by Pay-Per-Use Monitor B (3). Pay- Per-Use Monitors A and B store collected usage data in the billing management system (4), which is later used by the cloud provider to bill for the usage of Cloud Service A and Cloud Storage Device A. 