You are deploying a new storage system for your mobile application, which is a media streaming service. You decide the best fit is Google Cloud Datastore. You have entities with multiple properties, some of which can take on multiple values. For example, in the entity 'Movie' the property 'actors' and the property 'tags' have multiple values but the property 'date released' does not. A typical query would ask for all movies with actor= ordered by date _ released or all movies with tag=Comedy date_released. How should you avoid a combinatorial explosion in the number of indexes? A) Manually configure the index in your index config as follows: C) Set the following in your entity options: exclude_from_indexes = 'actors, tags' Set the following in your entity options: exclude_from_indexes = 'actors, tags' D) Set the following in your entity options: exclude_from_indexes = 'date_published' exclude_from_indexes = 'date_published'

Question

You are deploying a new storage system for your mobile application, which is a media streaming service. You decide the best fit is Google Cloud Datastore. You have entities with multiple properties, some of which can take on multiple values. For example, in the entity 'Movie' the property 'actors' and the property 'tags' have multiple values but the property 'date released' does not. A typical query would ask for all movies with actor=<actorname> ordered by date _ released or all movies with tag=Comedy date_released. How should you avoid a combinatorial explosion in the number of indexes?
A) Manually configure the index in your index config as follows: 
C) Set the following in your entity options: exclude_from_indexes = 'actors, tags' Set the following in your entity options: exclude_from_indexes = 'actors, tags' 
D) Set the following in your entity options: exclude_from_indexes = 'date_published' exclude_from_indexes = 'date_published'

Quizplus · Accepted Answer

The Answer of You are deploying a new storage system for your mobile application, which is a media streaming service. You decide the best fit is Google Cloud Datastore. You have entities with multiple properties, some of which can take on multiple values. For example, in the entity 'Movie' the property 'actors' and the property 'tags' have multiple values but the property 'date released' does not. A typical query would ask for all movies with actor=<actorname> ordered by date _ released or all movies with tag=Comedy date_released. How should you avoid a combinatorial explosion in the number of indexes?
A) Manually configure the index in your index config as follows: 
C) Set the following in your entity options: exclude_from_indexes = 'actors, tags' Set the following in your entity options: exclude_from_indexes = 'actors, tags' 
D) Set the following in your entity options: exclude_from_indexes = 'date_published' exclude_from_indexes = 'date_published'

You Are Deploying a New Storage System for Your Mobile