Azure Database for PostgreSQL - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create an Azure Database for PostgreSQL server using Azure CLI.

Azure

az postgres server create --resource-group myResourceGroup --name mypgserver --location eastus --admin-user myadmin [1] --sku-name B_Gen4_1

Drag options to blanks, or click blank then click option'

A--admin-password MyPassword123

B--admin-password

C--adminpass

D--password-admin

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect option names like --password-admin or --adminpass.

Omitting the password value after the option.

The --admin-password option is required to set the administrator password when creating the PostgreSQL server.

2fill in blank

medium

Complete the code to configure the firewall rule to allow access from a specific IP address.

Azure

az postgres server firewall-rule create --resource-group myResourceGroup --server-name mypgserver --name AllowMyIP --start-ip-address [1] --end-ip-address [1]

Drag options to blanks, or click blank then click option'

A255.255.255.255

B0.0.0.0

Clocalhost

D192.168.1.1

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'localhost' which is not a valid IP address for firewall rules.

Using 0.0.0.0 or 255.255.255.255 which are not specific IPs.

The start-ip-address and end-ip-address define the IP range allowed. To allow a single IP, both should be the same IP address.

3fill in blank

hard

Fix the error in the command to scale the Azure Database for PostgreSQL server to 4 vCores.

Azure

az postgres server update --resource-group myResourceGroup --name mypgserver --sku-name [1]

Drag options to blanks, or click blank then click option'

AGP_Gen5_4

BB_Gen5_2

CGP_Gen5_2

DB_Gen5_4

Attempts:

3 left

💡 Hint

Common Mistakes

Using a SKU with fewer vCores than required.

Using a SKU from a different tier unintentionally.

The GP_Gen5_4 SKU name represents 4 vCores in the General Purpose tier. Using this SKU scales the server to 4 vCores.

4fill in blank

hard

Fill both blanks to create a PostgreSQL database and assign it to the server.

Azure

az postgres db create --resource-group myResourceGroup --server-name mypgserver --name [1] --charset [2]

Drag options to blanks, or click blank then click option'

Amydatabase

Butf8

Clatin1

Dtestdb

Attempts:

3 left

💡 Hint

Common Mistakes

Using an invalid charset like 'latin1' which is not recommended for PostgreSQL.

Confusing database name with server name.

The --name option specifies the database name, and --charset sets the character encoding, commonly 'utf8' for PostgreSQL databases.

5fill in blank

hard

Fill all three blanks to configure a connection string for the PostgreSQL server.

Azure

postgresql://[1]:[2]@[3].postgres.database.azure.com:5432/mydatabase?sslmode=require

Drag options to blanks, or click blank then click option'

Amyadmin

BMyPassword123

Cmypgserver

Dmydatabase

Attempts:

3 left

💡 Hint

Common Mistakes

Putting the database name in the server name blank.

Mixing up username and password positions.

The connection string format requires the username, password, and server name. Here, myadmin is the username, MyPassword123 is the password, and mypgserver is the server name.

Practice

1. What is the main benefit of using Azure Database for PostgreSQL?

easy

A. It only supports PostgreSQL version 9.6.

B. It requires manual installation of PostgreSQL on virtual machines.

C. It is only available for on-premises servers.

D. It manages database setup, scaling, and maintenance automatically.

Solution

1. Step 1: Understand Azure Database for PostgreSQL service

   This service is managed by Azure, which means it handles setup, scaling, and maintenance for you.

2. Step 2: Compare options

   Limited version support, manual installation on VMs, and on-premises availability do not match the managed nature of this cloud service.

3. Final Answer:

   It manages database setup, scaling, and maintenance automatically. -> Option D

4. Quick Check:

   Managed service = automatic management [OK]

Hint: Managed means Azure handles setup and scaling for you [OK]

Common Mistakes:

• Thinking you must install PostgreSQL manually
• Assuming only old versions are supported
• Confusing cloud service with on-premises

2. Which Azure CLI command correctly creates a new PostgreSQL server named myserver in resource group mygroup?

easy

A. az postgres server new --name myserver --resource-group mygroup --admin-user admin --admin-password Pass@123

B. az postgres create server --resource-group mygroup --name myserver --admin-user admin --admin-password Pass@123

C. az postgres server create --name myserver --resource-group mygroup --location eastus --admin-user admin --admin-password Pass@123

D. az create postgres server --name myserver --resource-group mygroup --admin-user admin --admin-password Pass@123

Solution

1. Step 1: Identify correct Azure CLI syntax

   The correct command to create a PostgreSQL server uses az postgres server create with required parameters.

2. Step 2: Check options for syntax errors

   Other options use incorrect command structures, order, or omit required parameters like location, making them invalid.

3. Final Answer:

   az postgres server create --name myserver --resource-group mygroup --location eastus --admin-user admin --admin-password Pass@123 -> Option C

4. Quick Check:

   Correct CLI command = az postgres server create --name myserver --resource-group mygroup --location eastus --admin-user admin --admin-password Pass@123 [OK]

Hint: Use 'az postgres server create' to make a new server [OK]

Common Mistakes:

• Mixing command order or keywords
• Using 'az create' instead of 'az postgres server create'
• Omitting required parameters like location

3. Given this Azure CLI command:

az postgres server show --name myserver --resource-group mygroup

What output should you expect?

medium

A. Details of the PostgreSQL server named 'myserver' in 'mygroup'.

B. Creates a new PostgreSQL server named 'myserver'.

C. Deletes the PostgreSQL server named 'myserver'.

D. Lists all PostgreSQL servers in the subscription.

Solution

1. Step 1: Understand the 'az postgres server show' command

   This command retrieves and displays details about a specific PostgreSQL server.

2. Step 2: Compare with other options

   Creating, deleting, or listing all servers require different commands. This 'show' command displays details of the specific server.

3. Final Answer:

   Details of the PostgreSQL server named 'myserver' in 'mygroup'. -> Option A

4. Quick Check:

   'show' command = server details [OK]

Hint: 'show' means display info about one server [OK]

Common Mistakes:

• Confusing 'show' with 'create' or 'delete'
• Expecting a list of all servers
• Not specifying resource group or server name

4. You run this command to create a PostgreSQL server but get an error:

az postgres server create --name myserver --resource-group mygroup --admin-user admin --admin-password Pass123

What is the likely cause?

medium

A. The admin user name 'admin' is not allowed.

B. The admin password does not meet Azure's complexity requirements.

C. The server name 'myserver' is already in use.

D. The resource group 'mygroup' does not exist.

Solution

1. Step 1: Check password complexity rules

   Azure requires strong passwords with uppercase, lowercase, numbers, and symbols. 'Pass123' lacks symbols.

2. Step 2: Evaluate other options

   Resource group existence or server name conflicts cause different errors. 'admin' is allowed as admin user.

3. Final Answer:

   The admin password does not meet Azure's complexity requirements. -> Option B

4. Quick Check:

   Password complexity error = The admin password does not meet Azure's complexity requirements. [OK]

Hint: Check password has uppercase, lowercase, number, symbol [OK]

Common Mistakes:

• Ignoring password complexity rules
• Assuming resource group or name errors without checking
• Thinking 'admin' username is invalid

5. You want to enable high availability for your Azure Database for PostgreSQL server. Which configuration should you choose?

hard

A. Create a server with the 'Zone-redundant HA' option enabled.

B. Use a single server with no replicas.

C. Manually set up replication between two separate servers.

D. Deploy PostgreSQL on a VM and configure failover clustering.

Solution

1. Step 1: Understand Azure's built-in high availability options

   Azure Database for PostgreSQL offers a 'Zone-redundant HA' option that automatically replicates data across availability zones.

2. Step 2: Evaluate other options

   A single server with no replicas lacks HA. Manual replication between separate servers requires manual setup and is not recommended. Deploying on a VM with failover clustering is outside the managed service scope.

3. Final Answer:

   Create a server with the 'Zone-redundant HA' option enabled. -> Option A

4. Quick Check:

   Zone-redundant HA = automatic high availability [OK]

Hint: Use zone-redundant HA for built-in high availability [OK]

Common Mistakes:

• Choosing single server without HA
• Trying manual replication instead of managed HA
• Using VMs instead of managed service for HA