The answer is to combine Azure Logic Apps and Azure Automation runbooks. This pairing works because Logic Apps can monitor Azure SQL Database metrics like CPU usage and trigger workflows when thresholds are met—such as scaling up after 90% CPU for five minutes or scaling down after 10% CPU for fifteen minutes—while Automation runbooks execute the actual T-SQL or PowerShell commands to alter the service tier. On the DP-300 exam, this scenario tests your understanding that Azure SQL Database lacks native autoscale rules, so you must build custom automation using built-in services. A common trap is choosing elastic jobs, which handle scheduled administrative tasks like index maintenance, not real-time metric-based scaling. Remember the key: Logic Apps sense the metric, runbooks execute the change. For a memory tip, think “Logic listens, runbook runs”—the two work together to deliver cost-effective, event-driven scaling without third-party tools.
DP-300 Configure and manage automation of tasks Practice Question
This DP-300 practice question tests your understanding of configure and manage automation of tasks. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
You are designing an automation strategy for an Azure SQL Database that requires the following: 1) Automatically scale up the service tier when CPU usage exceeds 90% for 5 minutes. 2) Automatically scale down when CPU usage drops below 10% for 15 minutes. 3) The solution must be cost-effective and use built-in Azure features. Which TWO options should you combine? (Choose two.)
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Azure Logic Apps with a metric trigger
Azure Logic Apps can trigger scaling actions based on metrics, and Azure Automation runbooks can execute the scaling commands. Option B is wrong because elastic jobs are for scheduling database tasks, not scaling. Option D is wrong because autoscale rules are not directly available for Azure SQL Database; you need custom automation. Option E is wrong because Azure Functions can also be used, but Logic Apps and Automation are the recommended combination.
Key principle: NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Elastic Database Jobs
Why it's wrong here
Elastic jobs are for administrative tasks, not scaling.
✗
Azure Monitor autoscale
Why it's wrong here
Autoscale is not available for Azure SQL Database; it's for App Service, VMSS, etc.
✗
Azure Functions
Why it's wrong here
Functions can also scale, but Logic Apps + Automation is the typical combination.
✓
Azure Logic Apps with a metric trigger
Why this is correct
Logic Apps can monitor metrics and trigger actions.
Related concept
Static NAT maps one inside address to one outside address.
✓
Azure Automation runbook
Why this is correct
Runbooks can execute PowerShell to scale the database.
Related concept
Static NAT maps one inside address to one outside address.
Common exam traps
Common exam trap: NAT rules depend on direction and matching traffic
NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.
Detailed technical explanation
How to think about this question
NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.
KKey Concepts to Remember
Static NAT maps one inside address to one outside address.
PAT allows many inside hosts to share one public address using ports.
Inside local and inside global describe the private and translated addresses.
NAT ACLs identify traffic for translation, not always security filtering.
TExam Day Tips
→Identify inside and outside interfaces first.
→Check whether the scenario needs static NAT, dynamic NAT or PAT.
→Do not confuse NAT matching ACLs with normal packet-filtering intent.
Key takeaway
NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.
Real-world example
How this comes up in practice
A startup's cloud architect reviews their monthly bill and notices costs are higher than expected for a long-running batch job. Switching from on-demand instances to Reserved Instances — or using Spot/Preemptible VMs — can reduce compute costs by up to 72 %. Questions like this test whether you understand the tradeoffs between commitment, flexibility, and cost across cloud pricing models.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this DP-300 question in full detail.
Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related DP-300 NAT questions on configuration and troubleshooting.
Configure and manage automation of tasks — This question tests Configure and manage automation of tasks — Static NAT maps one inside address to one outside address..
What is the correct answer to this question?
The correct answer is: Azure Logic Apps with a metric trigger — Azure Logic Apps can trigger scaling actions based on metrics, and Azure Automation runbooks can execute the scaling commands. Option B is wrong because elastic jobs are for scheduling database tasks, not scaling. Option D is wrong because autoscale rules are not directly available for Azure SQL Database; you need custom automation. Option E is wrong because Azure Functions can also be used, but Logic Apps and Automation are the recommended combination.
What should I do if I get this DP-300 question wrong?
Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related DP-300 NAT questions on configuration and troubleshooting.
What is the key concept behind this question?
Static NAT maps one inside address to one outside address.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This DP-300 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the DP-300 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.