Azure dashboards - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

Understanding Azure Dashboard Sharing Behavior

You create a dashboard in Azure and share it with a colleague by assigning them Reader role on the dashboard resource. What will your colleague be able to do?

A Edit the dashboard layout and add new tiles.

B View the dashboard and interact with its tiles but cannot edit or delete it.

C Delete the dashboard from the Azure portal.

D Share the dashboard with other users.

💡 Hint

Think about what the Reader role allows in Azure.

The Reader role allows viewing resources but does not permit editing or deleting. Therefore, your colleague can see and interact with the dashboard but cannot change or share it.

❓ Architecture

intermediate

Best Practice for Organizing Multiple Azure Dashboards

You manage multiple Azure dashboards for different teams in your organization. What is the best way to organize and manage these dashboards to ensure proper access and easy maintenance?

A Create dashboards in a shared resource group and assign team-specific access using Azure RBAC on each dashboard.

B Create all dashboards under your personal subscription and share the dashboard URL with teams.

C Export dashboards as JSON files and email them to each team for local use.

D Create dashboards only in the default Azure portal dashboard and rely on portal filters.

💡 Hint

Consider how Azure RBAC and resource groups help with access control and organization.

Creating dashboards in a shared resource group and assigning team-specific access via RBAC ensures proper security and easier management compared to personal subscriptions or manual sharing.

❓ Configuration

advanced

JSON Configuration for a Tile Showing VM CPU Usage

Which JSON snippet correctly configures an Azure dashboard tile to show the average CPU usage of a specific virtual machine over the last 24 hours?

A { "type": "Metrics", "resourceId": "/subscriptions/123/resourceGroups/rg1/providers/Microsoft.Compute/virtualMachines/vm1", "metricNamespace": "Microsoft.Compute/virtualMachines", "metricName": "CPUPercentage", "timeRange": "PT24H", "aggregation": "Average" }

B { "type": "Metrics", "resourceId": "/subscriptions/123/resourceGroups/rg1/providers/Microsoft.Compute/virtualMachines/vm1", "metricNamespace": "Microsoft.Compute/virtualMachines", "metricName": "CPU Usage", "timeRange": "P1D", "aggregation": "Average" }

C { "type": "Metrics", "resourceId": "/subscriptions/123/resourceGroups/rg1/providers/Microsoft.Compute/virtualMachines/vm1", "metricNamespace": "Microsoft.Compute/virtualMachines", "metricName": "Percentage CPU", "timeRange": "24h", "aggregation": "Avg" }

D { "type": "Metrics", "resourceId": "/subscriptions/123/resourceGroups/rg1/providers/Microsoft.Compute/virtualMachines/vm1", "metricNamespace": "Microsoft.Compute/virtualMachines", "metricName": "Percentage CPU", "timeRange": "PT24H", "aggregation": "Average" }

💡 Hint

Check the exact metric name and time range format used by Azure Monitor metrics.

The correct metric name is "Percentage CPU" and the time range uses ISO 8601 duration format "PT24H" for 24 hours. Aggregation should be "Average".

❓ security

advanced

Preventing Unauthorized Dashboard Modifications

You want to ensure that only specific users can modify an Azure dashboard, while others can only view it. Which approach enforces this securely?

A Assign <strong>Owner</strong> role to users who can modify and <strong>Reader</strong> role to users who can view the dashboard resource.

B Share the dashboard URL with all users and rely on portal UI to restrict editing.

C Assign <strong>Contributor</strong> role to all users and instruct them not to edit unless authorized.

D Create separate dashboards for each user and do not share them.

💡 Hint

Think about Azure RBAC roles and their permissions.

Owner role allows full management including editing, while Reader role only allows viewing. This separation enforces permissions securely.

🧠 Conceptual

expert

Impact of Dashboard Resource Location on Access and Performance

You create an Azure dashboard resource in the East US region but most users accessing it are located in West Europe. What is the likely impact of this setup?

A Dashboard data will automatically replicate to West Europe to improve performance.

B Users in West Europe will be denied access because the dashboard is in a different region.

C Dashboard load times may be slower for West Europe users due to network latency, but access permissions remain unaffected.

D Azure will charge extra for cross-region dashboard access.

💡 Hint

Consider how Azure handles resource location and user access globally.

Azure dashboards are regional resources, but access is global. Network latency can affect load times, but permissions are based on Azure AD and RBAC, not region.