Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Google Professional Cloud Architect (PR000213) Exam - Topic 3 Question 67 Discussion

You have found an error in your App Engine application caused by missing Cloud Datastore indexes. You have created a YAML file with the required indexes and want to deploy these new indexes to Cloud Datastore.What should you do?
D) Create an HTTP request to the built-in python module to send the index configuration file to your application
A) Point gcloud datastore create-indexes to your configuration file
B) Upload the configuration file the App Engine's default Cloud Storage bucket, and have App Engine detect the new indexes
C) In the GCP Console, use Datastore Admin to delete the current indexes and upload the new configuration file

Google Professional Cloud Architect (PR000213) Exam - Topic 3 Question 67 Discussion

Actual exam question for Google's Professional Cloud Architect (PR000213) exam
Question #: 67
Topic #: 3
[All Professional Cloud Architect (PR000213) Questions]

You have found an error in your App Engine application caused by missing Cloud Datastore indexes. You have created a YAML file with the required indexes and want to deploy these new indexes to Cloud Datastore.

What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: D

https://cloud.google.com/kubernetes-engine/docs/concepts/multi-cluster-ingress#how_works

https://github.com/GoogleCloudPlatform/k8s-multicluster-ingress

https://cloud.google.com/blog/products/gcp/how-to-deploy-geographically-distributed-services-on-kubernetes-engine-with-kubemci


by Edna at Apr 01, 2023, 06:07 AM

Limited Time Offer

25%

Off

Get Premium Professional Cloud Architect (PR000213) Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Luisa
10 months ago
I had no idea there was a built-in python module for this!
upvoted 0 times
...
Andrew
10 months ago
Wait, D? That seems overly complicated for this task.
upvoted 0 times
...
Laquanda
10 months ago
C sounds risky, deleting current indexes could cause issues.
upvoted 0 times
...
Raylene
11 months ago
I think B might be easier, just upload it to Cloud Storage.
upvoted 0 times
...
Basilia
11 months ago
A is the way to go for deploying indexes!
upvoted 0 times
...
Irma
11 months ago
I don’t recall seeing anything about using an HTTP request for this, so option D seems unlikely to be the right choice.
upvoted 0 times
...
Launa
11 months ago
I’m a bit confused about option C; I thought we didn’t need to delete existing indexes to add new ones, but maybe I’m mistaken.
upvoted 0 times
...
Art
11 months ago
I remember practicing a question similar to this, and I feel like uploading to the Cloud Storage bucket might be the way to go, so option B could be correct.
upvoted 0 times
...
Shizue
11 months ago
I think option A sounds familiar, but I'm not entirely sure if that's the right command to use for deploying indexes.
upvoted 0 times
...
Simona
11 months ago
Ah, I think I've got it! The term they're looking for is "Guaranteed Late Arrival."
upvoted 0 times
...
Frederica
11 months ago
I'm a little confused by the wording here. Does the fact that the "Product" object was extended mean we need to access the attribute through some kind of wrapper or subclass? I'm leaning towards B or D, but I'm not entirely sure.
upvoted 0 times
...
Vallie
1 year ago
If only there was a 'None of the above' option. That would be my pick for this question.
upvoted 0 times
...
Carlene
1 year ago
Creating an HTTP request to a Python module? That's just weird. Definitely not the correct approach here.
upvoted 0 times
Alishia
1 year ago
A) Point gcloud datastore create-indexes to your configuration file
upvoted 0 times
...
Jolene
1 year ago
C) In the GCP Console, use Datastore Admin to delete the current indexes and upload the new configuration file
upvoted 0 times
...
Derick
1 year ago
B) Upload the configuration file the App Engine's default Cloud Storage bucket, and have App Engine detect the new indexes
upvoted 0 times
...
Tayna
1 year ago
A) Point gcloud datastore create-indexes to your configuration file
upvoted 0 times
...
...
Steffanie
1 year ago
Using the Datastore Admin in the GCP Console to delete current indexes and upload a new configuration file is overkill for this task.
upvoted 0 times
...
Rolland
1 year ago
Uploading the configuration file to the App Engine's default Cloud Storage bucket doesn't seem right, since that's not how you deploy indexes.
upvoted 0 times
Pa
1 year ago
B) Upload the configuration file the App Engine's default Cloud Storage bucket, and have App Engine detect the new indexes
upvoted 0 times
...
Lamonica
1 year ago
C) In the GCP Console, use Datastore Admin to delete the current indexes and upload the new configuration file
upvoted 0 times
...
Josue
1 year ago
A) Point gcloud datastore create-indexes to your configuration file
upvoted 0 times
...
...
Misty
1 year ago
Option A is the correct answer. The gcloud datastore create-indexes command allows you to deploy new indexes defined in a YAML file.
upvoted 0 times
Venita
1 year ago
Option A is the correct answer. The gcloud datastore create-indexes command allows you to deploy new indexes defined in a YAML file.
upvoted 0 times
...
Claudia
1 year ago
A) Point gcloud datastore create-indexes to your configuration file
upvoted 0 times
...
...
Marion
1 year ago
But wouldn't it be easier to just use Datastore Admin in the GCP Console to delete the current indexes and upload the new configuration file?
upvoted 0 times
...
Dominic
1 year ago
I disagree, I believe the answer is B) Upload the configuration file to the App Engine's default Cloud Storage bucket.
upvoted 0 times
...
Marion
1 year ago
I think the correct answer is A) Point gcloud datastore create-indexes to your configuration file.
upvoted 0 times
...

Save Cancel