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 -
Click on the arrows to vote for the correct answer
A. B. C. D.D.
The executive statement in the question does not mention any specific requirements related to networking, so we need to analyze the technical and business requirements to determine the most appropriate solution.
One of the technical requirements is to provide a secure and high-performance connection between on-premises systems and Google Cloud. This requirement suggests the need for a reliable and high-bandwidth network connection between the on-premises systems and Google Cloud.
The existing technical environment mentions that EHR Healthcare is currently hosting several legacy file- and API-based integrations with insurance providers on-premises, and these systems are scheduled to be replaced over the next several years. However, there is no plan to upgrade or move these systems at the current time. This suggests that the on-premises systems will continue to be used for some time, and there is a need for a connection between the on-premises systems and Google Cloud.
The technical requirements also state the need to maintain legacy interfaces to insurance providers with connectivity to both on-premises systems and cloud providers. This requirement suggests that a hybrid network architecture may be necessary to support both on-premises systems and cloud providers.
Based on these requirements, the most appropriate solution is to add a new Dedicated Interconnect connection. Dedicated Interconnect provides a private, high-bandwidth connection between on-premises infrastructure and Google Cloud. This connection can be used to transfer large volumes of data, such as database backups or virtual machine images, between the on-premises infrastructure and Google Cloud.
Dedicated Interconnect also supports hybrid architectures by allowing on-premises systems to communicate with cloud resources over a private, dedicated network connection. This enables EHR Healthcare to maintain their legacy interfaces to insurance providers with connectivity to both on-premises systems and cloud providers.
Upgrading the bandwidth on the existing Dedicated Interconnect connection to 100 Gbps (option B) may improve network performance, but it is not necessary based on the requirements described in the question. Adding three new Cloud VPN connections (option C) would provide secure access to Google Cloud from multiple locations, but it does not provide the dedicated and private connectivity required to meet the technical requirements. Adding a new Carrier Peering connection (option D) would allow EHR Healthcare to exchange traffic directly with Google at one of Google's network edge locations, but this is not necessary based on the requirements described in the question.
In summary, the most appropriate solution based on the requirements described in the question is to add a new Dedicated Interconnect connection.