Q: 2
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?
Options
Discussion
A . Official GCP docs and practice exams focus on path rules using wildcards, but not regex, so you'd need to adjust the structure. Worth reviewing the official guide for these URL map constraints.
A. since GCP path rules only allow wildcards like /video/*, so directory structure needs tweaking.
Practice exams often mention D as a close fit, so I'd try D here.
Saw a very similar question in recent practice sets, A matches what GCP supports. URL maps in GCP don't do regex, only wildcard after the slash, so you have to rearrange dirs if you want those path rules. Correct me if I'm missing anything.
Just to clarify, is minimizing operational overhead more important than preserving the current directory structure? If keeping the structure unchanged is a hard requirement, that could change which option makes sense.
D imo. Since the directory already has /fr/video style, I'd think using /*/video path rules would be simple and keep overhead low. Not totally sure about the wildcard position with GCP but this makes sense to me. Disagree?
Its A. GCP URL maps only let you use wildcards at the end, so you can't match /*/video. D is a common trap, but won't work with GCP rules. Think this is what similar practice questions expect, but open to corrections.
C/D? I get why people are picking D since it matches the current structure, but GCP URL maps don't support wildcards in the middle, so you can't use /*/video. On the other hand, C uses regex which isn't supported either. So neither seems quite right without changing the directories. Maybe A is technically best, but still not 100% sure since the question talks about minimizing operational overhead. Am I missing something small in how path rules work?
D imo, since the existing structure already has the language as a path segment, you could just use /*/video and /*/audio for the URL map rules. Don't see why you'd need to rearrange. Maybe missing something in GCP docs so open to being corrected.
I remember a similar scenario from labs, and A fits with what GCP URL maps actually support for path rules. Agree?
Be respectful. No spam.
