EHR Healthcare - Cloud Migration and Scalability

Cloud Migration and Scalability for EHR Healthcare

Question

EHR Healthcare is a leading provider of electronic health record software to the medical industry.

EHR Healthcare provides their software as a service to multi- national medical offices, hospitals, and insurance providers.

Solution concept - Due to rapid changes in the healthcare and insurance industry, EHR Healthcare's business has been growing exponentially year over year.

They need to be able to scale their environment, adapt their disaster recovery plan, and roll out new continuous deployment capabilities to update their software at a fast pace.

Google Cloud has been chosen to replace their current colocation facilities.

Existing technical environment - EHR's software is currently hosted in multiple colocation facilities.

The lease on one of the data centers is about to expire.

Customer-facing applications are web-based, and many have recently been containerized to run on a group of Kubernetes clusters.

Data is stored in a mixture of relational and NoSQL databases (MySQL, MS SQL Server, Redis, and MongoDB)

EHR is hosting several legacy file- and API-based integrations with insurance providers on-premises.

These systems are scheduled to be replaced over the next several years.

There is no plan to upgrade or move these systems at the current time.

Users are managed via Microsoft Active Directory.

Monitoring is currently being done via various open source tools.

Alerts are sent via email and are often ignored.

Business requirements - On-board new insurance providers as quickly as possible.

Provide a minimum 99.9% availability for all customer-facing systems.

Provide centralized visibility and proactive action on system performance and usage.

Increase ability to provide insights into healthcare trends.

Reduce latency to all customers.

Maintain regulatory compliance.

Decrease infrastructure administration costs.

Make predictions and generate reports on industry trends based on provider data.

Technical requirements - Maintain legacy interfaces to insurance providers with connectivity to both on-premises systems and cloud providers.

Provide a consistent way to manage customer-facing applications that are container-based.

Provide a secure and high-performance connection between on-premises systems and Google Cloud.

Provide consistent logging, log retention, monitoring, and alerting capabilities.

Maintain and manage multiple container-based environments.

Dynamically scale and provision new environments.

Create interfaces to ingest and process data from new providers.

Executive statement -

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

D.

The question is asking for the most appropriate solution for EHR Healthcare to replace their current colocation facilities with Google Cloud, while considering their technical and business requirements. The proposed solution needs to address their needs to scale their environment, adapt their disaster recovery plan, and roll out new continuous deployment capabilities to update their software at a fast pace.

Option A: Configure two Partner Interconnect connections in one metro (City), and make sure the Interconnect connections are placed in different metro zones.

Partner Interconnect is a service offered by Google Cloud that allows customers to connect to Google Cloud through a supported service provider. This option proposes configuring two Partner Interconnect connections in one metro (city) and making sure the Interconnect connections are placed in different metro zones.

This option addresses the technical requirement to provide a secure and high-performance connection between on-premises systems and Google Cloud. By having two Partner Interconnect connections, it provides redundancy and resilience in case one connection fails. However, it does not address the need to maintain legacy interfaces to insurance providers with connectivity to both on-premises systems and cloud providers. Additionally, it does not provide consistent logging, log retention, monitoring, and alerting capabilities, as required by the technical requirements.

Option B: Configure two VPN connections from on-premises to Google Cloud, and make sure the VPN devices on-premises are in separate racks.

VPN (Virtual Private Network) is a service that provides a secure connection between an on-premises network and a cloud provider over the public internet. This option proposes configuring two VPN connections from on-premises to Google Cloud, and ensuring that the VPN devices on-premises are in separate racks.

This option addresses the technical requirement to provide a secure and high-performance connection between on-premises systems and Google Cloud. By having two VPN connections, it provides redundancy and resilience in case one connection fails. However, it does not address the need to maintain legacy interfaces to insurance providers with connectivity to both on-premises systems and cloud providers. Additionally, it does not provide consistent logging, log retention, monitoring, and alerting capabilities, as required by the technical requirements.

Option C: Configure Direct Peering between EHR Healthcare and Google Cloud, and make sure you are peering at least two Google locations.

Direct Peering is a service offered by Google Cloud that allows customers to connect to Google Cloud directly, bypassing the public internet. This option proposes configuring Direct Peering between EHR Healthcare and Google Cloud and making sure to peer at least two Google locations.

This option addresses the technical requirement to provide a secure and high-performance connection between on-premises systems and Google Cloud. By using Direct Peering, it provides a dedicated, private connection with high bandwidth and low latency. It also addresses the need to maintain legacy interfaces to insurance providers with connectivity to both on-premises systems and cloud providers. Additionally, it provides consistent logging, log retention, monitoring, and alerting capabilities, as required by the technical requirements. However, it does not provide redundancy or resilience in case of a failure, which is required by the business requirement to provide a minimum 99.9% availability for all customer-facing systems.

Option D: Configure two Dedicated Interconnect connections in one metro (City) and two connections in another metro, and make sure the Interconnect connections are placed in different metro zones.

Dedicated Interconnect is a service offered by Google Cloud that allows customers to connect to Google Cloud through a dedicated physical connection. This option proposes configuring two Dedicated Interconnect connections in one metro (city) and two connections in another metro, and making sure the Interconnect connections are placed in different metro zones.

This option addresses both the technical and business requirements. By having four Dedicated Interconnect connections in