Your code is running on Cloud Functions in project A. It is supposed to write an object in a Cloud Storage
bucket owned by project B. However, the write call is failing with the error "403 Forbidden".
What should you do to correct the problem?
Suggested Answer: B
Get Premium Professional Cloud Developer Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
11 comments · newest first
LE
Lera
1 year ago
Wait, why would you grant roles to the user account? That seems off.
TA
Tanesha
1 year ago
No way, it's all about permissions here.
BR
Brice
1 year ago
I thought enabling the API was enough?
LE
Leonor
1 year ago
Definitely option C! That’s the correct service account.
AN
Anabel
1 year ago
You need to grant the right roles for access.
SA
Sanda
1 year ago
I’m leaning towards A, but I remember that sometimes the service account needs specific roles too. This is tricky!
RO
Rosendo
1 year ago
I feel like enabling the Cloud Storage API could be important, but I don't think that's the main issue here. It seems more related to permissions.
AL
Alana
1 year ago
I remember something about service accounts needing the right permissions, so maybe it's C? But I'm not entirely sure.
CA
Cammy
1 year ago
I think I saw a similar question where we had to grant roles to a service account, but I can't recall if it was for the user account or the service account itself.
YU
Yuki
1 year ago
This looks like a straightforward Azure Application Gateway configuration question. I think I can handle this - I just need to remember the key components like backend pools, listeners, and routing rules.
DA
Daniela
1 year ago
Hmm, I'm a bit confused on the best approach here. Should we really be discussing the change during the baseline approval meeting? That seems risky.