Organization A has been expanding and, as a result, is outgrowing the processing capacity of its on-premise Service A im
Posted: Mon Aug 08, 2022 4:00 pm
Organization A has been expanding and, as a result, is outgrowing the processing capacity of its on-premise Service A implementation. It is determined that this is due to usage
A. A failover system can be implemented in a hybrid architecture comprised of Organization A's existing on-premise environment and a public cloud environment. The failover system would span both environments so that when Service A is unable to process request messages from Service Consumers A, B or C, the failover system can automatically route messages to a redundant implementation of Service A residing in the public cloud. Similarly, when Database A is unable to process a data access request from
B. The state management database and resource replication mechanisms can be implemented to establish redundant implementations of Service A and Database A in both on-premise and cloud environments. Using resource replication, a cloud-based duplicate of Service A (Cloud Service A) will be established in a public cloud and will remain in synch with Service A via regular replication cycles. Using the resource replication mechanism together with the state management database mechanism allows for Databa
C. A cloud bursting solution can be implemented, whereby a redundant copy of Service A is implemented within a public cloud. This cloud-based, redundant implementation of Service A is referred to as Cloud Service A. A copy of Database A is also implemented within the cloud and both the on-premise and cloud-based copies of Database A are redesigned to be nonrelational in order to improve data access performance. Service A continues to act as a first point of contact for Service Consumers A, B and
C.
D. None of the above
A. A failover system can be implemented in a hybrid architecture comprised of Organization A's existing on-premise environment and a public cloud environment. The failover system would span both environments so that when Service A is unable to process request messages from Service Consumers A, B or C, the failover system can automatically route messages to a redundant implementation of Service A residing in the public cloud. Similarly, when Database A is unable to process a data access request from
B. The state management database and resource replication mechanisms can be implemented to establish redundant implementations of Service A and Database A in both on-premise and cloud environments. Using resource replication, a cloud-based duplicate of Service A (Cloud Service A) will be established in a public cloud and will remain in synch with Service A via regular replication cycles. Using the resource replication mechanism together with the state management database mechanism allows for Databa
C. A cloud bursting solution can be implemented, whereby a redundant copy of Service A is implemented within a public cloud. This cloud-based, redundant implementation of Service A is referred to as Cloud Service A. A copy of Database A is also implemented within the cloud and both the on-premise and cloud-based copies of Database A are redesigned to be nonrelational in order to improve data access performance. Service A continues to act as a first point of contact for Service Consumers A, B and
C.
D. None of the above