Google Professional Data Engineer
Get started today
Ultimate access to all questions.
Deep dive into the quiz with AI chat providers.
We prepare a focused prompt with your quiz and certificate details so each AI can offer a more tailored, in-depth explanation.
NO.13 You are troubleshooting your Dataflow pipeline that processes data from Cloud Storage to BigQuery. You have discovered that the Dataflow worker nodes cannot communicate with one another. Your networking team relies on Google Cloud network tags to define firewall rules. You need to identify the issue while following Google-recommended networking security practices. What should you do?
Real Exam
Community
LLeetQuiz
A
Determine whether your Dataflow pipeline has a custom network tag set.
B
Determine whether there is a firewall rule set to allow traffic on TCP ports 12345 and 12346 for the Dataflow network tag.
C
Determine whether your Dataflow pipeline is deployed with the external IP address option enabled.
D
Determine whether there is a firewall rule set to allow traffic on TCP ports 12345 and 12346 on the subnet used by Dataflow workers.
Explanation:
Explanation:
Option B is the correct answer because:
- Dataflow worker nodes need to communicate with each other and with the Dataflow service on TCP ports 12345 and 12346
- These ports are used for data shuffling and streaming engine communication
- By default, Dataflow assigns a network tag called
dataflowto worker nodes and creates appropriate firewall rules - If using custom network tags, you must create firewall rules that allow traffic on these ports for your custom network tag
Why other options are incorrect:
- Option A: Knowing if there's a custom network tag doesn't tell you if the required firewall rules exist
- Option C: External IP address affects internet access, not internal worker communication
- Option D: Firewall rules should be based on network tags (more secure) rather than subnets
Best Practice: Always use network tags for firewall rules as they provide more granular and secure access control compared to subnet-based rules.
Comments
Loading comments...