Your company's Google Cloud-deployed, streaming application supports multiple languages.
The application development team has asked you how they should support splitting audio and video traffic to different backend Google Cloud storage buckets.
They want to use URL maps and minimize operational overhead.
They are currently using the following directory structure: /fr/video /en/video /es/video /../video /fr/audio /en/audio /es/audio /../audio Which solution should you recommend?
Click on the arrows to vote for the correct answer
A. B. C. D.D.
The application development team wants to split audio and video traffic to different backend Google Cloud storage buckets while minimizing operational overhead. They are currently using a directory structure that includes directories for different languages and separate directories for audio and video files. To achieve their goal, they want to use URL maps.
A URL map is used to direct incoming requests to a specific backend service based on the requested URL. To create a URL map that supports splitting audio and video traffic to different backend Google Cloud storage buckets, we need to ensure that the URL pattern matches the requested URL and directs the request to the appropriate backend service.
Option A: Rearrange the directory structure, create a URL map and leverage a path rule such as /video/* and /audio/* This option suggests that we should rearrange the directory structure, create a URL map, and use a path rule such as /video/* and /audio/* to direct the incoming requests to the appropriate backend service. This would require changing the directory structure to include separate subdirectories for video and audio files. While this option can work, it would require a lot of changes to the directory structure and may not be the most efficient solution.
Option B: Rearrange the directory structure, create DNS hostname entries for video and audio and leverage a path rule such as /video/* and /audio/* This option suggests that we should rearrange the directory structure and create DNS hostname entries for video and audio. We can then use a path rule such as /video/* and /audio/* to direct incoming requests to the appropriate backend service. This option would require less restructuring of the directory and is a viable solution.
Option C: Leave the directory structure as-is, create a URL map and leverage a path rule such as /[a-z]{2}/video and /[a-z]{2}/audio This option suggests that we should leave the directory structure as it is and use a URL map with a path rule such as /[a-z]{2}/video and /[a-z]{2}/audio. The regular expression /[a-z]{2}/ matches the language code in the URL, and the path rule directs the request to the appropriate backend service. This option would not require any restructuring of the directory and is a viable solution.
Option D: Leave the directory structure as-is, create a URL map and leverage a path rule such as //video and //audio This option suggests that we should leave the directory structure as it is and use a URL map with a path rule such as //video and //audio. This would direct all requests to the appropriate backend service based on the file type, but it would not differentiate between different languages. Therefore, this option is not a viable solution.
In summary, Option A and Option B would require restructuring the directory structure and may not be the most efficient solution. Option D does not consider language, so it is not a viable solution. Option C is the best solution because it does not require restructuring the directory, considers language, and is a viable solution. Therefore, the recommended solution is Option C: Leave the directory structure as-is, create a URL map and leverage a path rule such as /[a-z]{2}/video and /[a-z]{2}/audio.