Google Cloud SQL - Cloud SQL for PostgreSQL JSONB support MCQ

Google Cloud SQL – 24 – Cloud SQL for PostgreSQL JSONB support MCQ

1 / 25

1. What is the primary data type for working with structured and semi-structured data in PostgreSQL?

BLOB

JSONB

XML

JSON

2 / 25

2. What distinguishes JSONB from the standard JSON data type in PostgreSQL?

JSONB supports XML data

JSONB enforces strict schema rules

JSONB stores data in a binary format

JSONB is for binary data

3 / 25

3. Which feature of JSONB makes it more efficient for storage and retrieval compared to plain JSON?

Textual representation

Encrypted storage

Binary encoding

No difference in efficiency

4 / 25

4. In Google Cloud SQL for PostgreSQL, do you need to enable JSONB separately, or is it available by default?

JSONB is available by default

JSONB must be enabled using a separate command

JSONB requires a special license

JSONB is not supported

5 / 25

5. How can you create a table with a JSONB column in PostgreSQL?

JSONB columns are created automatically

JSONB tables are not supported

Using the CREATE TABLE statement with a JSONB data type

Using the CREATE JSONB TABLE statement

6 / 25

6. What is the primary advantage of using JSONB to store semi-structured data?

Reduced storage space

Improved security

Flexibility in handling evolving data structures

Simplified data validation

7 / 25

7. Which PostgreSQL operator is used to extract specific elements from a JSONB document?

->>

8 / 25

8. How can you query JSONB data for records where a specific JSON key has a value greater than 25?

SELECT * FROM table WHERE json_column->'key' = 25;

SELECT * FROM table WHERE json_column->>'key' > 25;

SELECT * FROM table WHERE json_column->'key' > 25;

SELECT * FROM table WHERE json_column->>'key' = 25;

9 / 25

9. What is the purpose of creating an index on a JSONB column in PostgreSQL?

To add security layers

To improve query performance

To enforce data consistency

To reduce storage space

10 / 25

10. What is a typical use case for storing configuration settings using JSONB in PostgreSQL?

Managing application configuration settings

Storing binary data

Managing user authentication

Managing log files

11 / 25

11. In the context of JSONB, what does “schema-less” mean?

Data must always conform to a predefined structure

Data is always encrypted

Data does not have a predefined structure

Data is stored as plain text

12 / 25

12. When designing a schema for JSONB data, what is an important consideration for efficient querying?

Applying strict data validation rules

Storing all data in a single JSONB column

Using plain JSON data types

Designing for efficient querying and indexing

13 / 25

13. What best practice should you follow when dealing with JSONB data in PostgreSQL?

Create separate tables for each JSONB key-value pair

Avoid creating tables with JSONB columns

Store JSONB data in external files

Implement data validation and consistency checks

14 / 25

14. How can you ensure clarity and maintainability when working with JSONB data in PostgreSQL?

Use plain text instead of JSONB

Avoid using JSONB data types

Document the structure of JSONB data

Implement strict schema rules

15 / 25

15. What type of data can JSONB efficiently store in PostgreSQL?

Structured and semi-structured data

Numerical data only

Binary data only

Plain text only

16 / 25

16. What is the primary benefit of indexing JSONB data in PostgreSQL?

Enforcing strict schema rules

Improving query performance

Reducing storage space

Simplifying data validation

17 / 25

17. What does the -> operator do when used with JSONB data in PostgreSQL?

Extracts specific elements from a JSONB document

Concatenates JSON keys

Performs data encryption

Converts JSONB to plain text

18 / 25

18. In Google Cloud SQL for PostgreSQL, how can you create an index on a JSONB column?

CREATE JSONB INDEX statement

CREATE INDEX statement with the GIN method

CREATE TABLE INDEX statement

JSONB columns cannot be indexed

19 / 25

19. What is the primary purpose of a JSONB index in PostgreSQL?

To improve the performance of JSONB data queries

To store JSONB data

To encrypt JSONB data

To enforce strict schema rules

20 / 25

20. When designing a schema for JSONB data in PostgreSQL, what should you consider regarding data validation?

Implement strict data validation rules to ensure consistency

Use plain text instead of JSONB to avoid validation issues

No data validation is required for JSONB data

JSONB data cannot be validated

21 / 25

21. In PostgreSQL, how can you query JSONB data to find records where a specific JSON key exists?

Use the EXISTS operator with a subquery

Use the -> operator with a null check

JSONB data cannot be queried for key existence

Use the ->> operator with a null check

22 / 25

22. Which of the following is a practical use case for JSONB in PostgreSQL?

Managing dynamic content with variable attributes

Running complex mathematical calculations

Managing log files

Storing binary data

23 / 25

23. In PostgreSQL, what does the @ operator do when used with JSONB data?

Calculates the average of JSONB values

Compares JSONB values for equality

Converts JSONB data to plain text

Checks if a specific JSON key exists

24 / 25

24. What is a recommended best practice for maintaining JSONB data in PostgreSQL?

Periodically test JSONB queries

Use external files for JSONB storage

Avoid using JSONB for semi-structured data

Implement version control for JSONB data

25 / 25

25. In PostgreSQL, what is the primary benefit of using JSONB for storing structured data?

Flexibility in handling evolving data structures

Simplified data validation

Enhanced security

Reduced storage space

Your score is

Google Cloud SQL – Cloud SQL for PostgreSQL JSONB support MCQ