IP Strategy for Connecting Hadoop to GCP
Question
Case study - This is a case study.
Case studies are not timed separately.
You can use as much exam time as you would like to complete each case.
However, there may be additional case studies and sections on this exam.
You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study.
Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study.
Each question is independent of the other questions in this case study.
At the end of this case study, a review screen will appear.
This screen allows you to review your answers and to make changes before you move to the next section of the exam.
After you begin a new section, you cannot return to this section.
To start the case study - To display the first question in this case study, click the Next button.
Use the buttons in the left pane to explore the content of the case study before you answer the questions.
Clicking these buttons displays information such as business requirements, existing environment, and problem statements.
If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs.
When you are ready to answer a question, click the Question button to return to the question.
Company Overview - HipLocal is a community application designed to facilitate communication between people in close proximity.
It is used for event planning and organizing sporting events, and for businesses to connect with their local communities.
HipLocal launched recently in a few neighborhoods in Dallas and is rapidly growing into a global phenomenon.
Its unique style of hyper-local community communication and business outreach is in demand around the world.
Executive Statement - We are the number one local community app; it's time to take our local community services global.
Our venture capital investors want to see rapid growth and the same great experience for new local and virtual communities that come online, whether their members are 10 or 10000 miles away from each other.
Solution Concept - HipLocal wants to expand their existing service, with updated functionality, in new regions to better serve their global customers.
They want to hire and train a new team to support these regions in their time zones.
They will need to ensure that the application scales smoothly and provides clear uptime data.
Existing Technical Environment - HipLocal's environment is a mix of on-premises hardware and infrastructure running in Google Cloud Platform.
The HipLocal team understands their application well, but has limited experience in global scale applications.
Their existing technical environment is as follows: " Existing APIs run on Compute Engine virtual machine instances hosted in GCP.
" State is stored in a single instance MySQL database in GCP.
" Data is exported to an on-premises Teradata/Vertica data warehouse.
" Data analytics is performed in an on-premises Hadoop environment.
" The application has no logging.
" There are basic indicators of uptime; alerts are frequently fired when the APIs are unresponsive.
Business Requirements - HipLocal's investors want to expand their footprint and support the increase in demand they are seeing.
Their requirements are: " Expand availability of the application to new regions.
" Increase the number of concurrent users that can be supported.
" Ensure a consistent experience for users when they travel to different regions.
" Obtain user activity metrics to better understand how to monetize their product.
" Ensure compliance with regulations in the new regions (for example, GDPR)
" Reduce infrastructure management time and cost.
" Adopt the Google-recommended practices for cloud computing.
Technical Requirements - " The application and backend must provide usage metrics and monitoring.
" APIs require strong authentication and authorization.
" Logging must be increased, and data should be stored in a cloud analytics platform.
" Move to serverless architecture to facilitate elastic scaling.
" Provide authorized access to internal apps in a secure manner.
HipLocal has connected their Hadoop infrastructure to GCP using Cloud Interconnect in order to query data stored on persistent disks.
Which IP strategy should they use?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.A.
The IP strategy that HipLocal should use to connect their Hadoop infrastructure to GCP using Cloud Interconnect in order to query data stored on persistent disks depends on various factors such as security, scalability, and cost.
Option A: Create manual subnets Creating manual subnets is a possible option, but it might not be the best fit for HipLocal's requirements. Manual subnets require manual configuration and management of IP ranges, which can become cumbersome as the number of regions and subnets grow. It can also increase the risk of IP conflicts and misconfigurations, which can result in downtime.
Option B: Create an auto mode subnet Creating an auto mode subnet is another option for HipLocal. It is a scalable and easy-to-use option that can simplify the management of IP addresses. Auto mode subnets automatically allocate IP addresses within the specified range, which can reduce the risk of IP conflicts and misconfigurations. However, auto mode subnets might not be the best option for HipLocal since it requires the creation of subnets within a VPC, and they might require more granular control over their IP address allocation.
Option C: Create multiple peered VPCs Creating multiple peered VPCs can provide HipLocal with greater control over their IP address allocation and can help to increase security by isolating resources into separate VPCs. This option can help to scale HipLocal's application by distributing it across multiple VPCs, but it also adds complexity and management overhead. It can also increase costs since peered VPCs require interconnectivity fees.
Option D: Provision a single instance for NAT Provisioning a single instance for NAT can provide HipLocal with a simpler and more cost-effective solution for IP address management. A NAT instance can handle the translation of IP addresses for traffic that is going out of the VPC, which can reduce the risk of IP conflicts and misconfigurations. This option can also help HipLocal to ensure a consistent experience for users when they travel to different regions, by providing a single IP address for their application. However, it might not be the best fit for HipLocal's scalability requirements since it requires manual management of IP addresses and might not scale well for high traffic applications.
Based on the requirements and constraints mentioned in the case study, the best IP strategy for HipLocal would be to provision a single instance for NAT. This option can provide a simple and cost-effective solution for IP address management while ensuring a consistent experience for users when they travel to different regions. However, HipLocal should consider other options if their requirements change in the future, such as creating multiple peered VPCs if they require greater control over IP address allocation and security.
