Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Microsoft DP-300 Exam - Topic 4 Question 96 Discussion

Actual exam question for Microsoft's DP-300 exam
Question #: 96
Topic #: 4
[All DP-300 Questions]

You have an Azure SQL database named DB1.

You need to display the estimated execution plan of a query by using the query editor in the Azure portal.

What should you do first?

Show Suggested Answer Hide Answer
Suggested Answer: D, E

by Delmy at Jul 16, 2024, 01:00 AM

Limited Time Offer

25%

Off

Get Premium DP-300 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Lindsey
5 months ago
Seems like B is also an option, but D is more straightforward.
upvoted 0 times
...
Ryan
5 months ago
Wait, you can't just run a T-SQL statement for this?
upvoted 0 times
...
Bulah
5 months ago
I thought A was the answer, but I guess not.
upvoted 0 times
...
Candra
5 months ago
Definitely D! That's the way to go.
upvoted 0 times
...
Vi
6 months ago
You need to enable Query Store first.
upvoted 0 times
...
Viki
6 months ago
I'm leaning towards option D, but I also have a nagging feeling about the set showplan_all statement being important too.
upvoted 0 times
...
Haley
6 months ago
I practiced a similar question where we had to display execution plans, and I feel like running a Transact-SQL statement was involved.
upvoted 0 times
...
Agustin
6 months ago
I remember something about setting QUERY_CAPTURE_MODE, but I can't recall if that comes before or after enabling Query Store.
upvoted 0 times
...
Queenie
6 months ago
I think we need to enable Query Store first, but I'm not completely sure if that's the right first step.
upvoted 0 times
...
Anastacia
6 months ago
I'm pretty confident that the answer is option D, enabling Query Store for the database. That should give us the ability to view the execution plan directly in the Azure portal, which is what the question is asking for.
upvoted 0 times
...
Tracey
6 months ago
Okay, let me think this through. We need to display the estimated execution plan in the Azure portal, so we'll want to do something that integrates with the portal. Enabling Query Store seems like the most logical choice here.
upvoted 0 times
...
Marge
6 months ago
Hmm, I'm a bit confused. I thought we needed to use the SET SHOWPLAN_ALL statement to get the execution plan. I'm not sure if that's the right approach for this question.
upvoted 0 times
...
Barb
6 months ago
I think the key here is to enable Query Store for the database. That should give us the ability to view the estimated execution plan in the Azure portal.
upvoted 0 times
...
Cheryll
7 months ago
Option C with Flow seems like a good way to create a custom data entry wizard. That could help streamline the process and ensure data quality. I'll make sure to review the Flow functionality before the exam.
upvoted 0 times
...
Alexis
7 months ago
I'm a bit confused about how to calculate the confidence interval here; I think I need to find the mean first, but I'm not sure how to do that with this data.
upvoted 0 times
...
Minna
11 months ago
D is the answer, no doubt. Trying to use Transact-SQL statements is like trying to open a jar with a sledgehammer. Just enable Query Store and let the Azure portal do the work!
upvoted 0 times
Gene
10 months ago
I agree, using Query Store simplifies the process. No need to complicate things with Transact-SQL statements.
upvoted 0 times
...
Aleisha
11 months ago
Exactly! Enabling Query Store for DB1 is the way to go. It makes it much easier to view the estimated execution plan.
upvoted 0 times
...
Rosendo
11 months ago
D is the answer, no doubt. Trying to use Transact-SQL statements is like trying to open a jar with a sledgehammer. Just enable Query Store and let the Azure portal do the work!
upvoted 0 times
...
...
Lavonda
11 months ago
I'm torn between B and D, but I think D is the way to go. Enabling Query Store is the most direct approach to get the estimated execution plan.
upvoted 0 times
Tijuana
10 months ago
Let's go with option D and enable Query Store for DB1.
upvoted 0 times
...
Viola
11 months ago
I agree, enabling Query Store for DB1 is the correct first step.
upvoted 0 times
...
Hillary
11 months ago
I think D is the way to go. Enabling Query Store is the most direct approach to get the estimated execution plan.
upvoted 0 times
...
...
Lashawn
12 months ago
I'm going with D. Enabling Query Store is the way to go here. Trying to use Transact-SQL statements seems a bit overkill for this task.
upvoted 0 times
Lindsay
10 months ago
User3: D) Enable Query Store for DB1.
upvoted 0 times
...
Dulce
11 months ago
User2: I agree, enabling Query Store for DB1 is the first step.
upvoted 0 times
...
Catalina
11 months ago
User1: I'm going with D. Enabling Query Store is the way to go here.
upvoted 0 times
...
...
Nichelle
12 months ago
B looks promising, but I'm not sure if setting the QUERY_CAPTURE_MODE is necessary to just view the execution plan. D seems like the more straightforward option.
upvoted 0 times
Ammie
10 months ago
Agreed, let's go with enabling Query Store for DB1.
upvoted 0 times
...
Annice
11 months ago
D) Enable Query Store for DB1.
upvoted 0 times
...
Lilli
11 months ago
I think D) Enable Query Store for DB1 is the better option.
upvoted 0 times
...
Alpha
12 months ago
B) For DB1, set QUERY_CAPTURE_MODE of Query Store to All.
upvoted 0 times
...
...
Freida
1 year ago
Hmm, I think the correct answer is D. Enabling Query Store for DB1 should allow me to view the estimated execution plan in the Azure portal. No need for any additional Transact-SQL statements.
upvoted 0 times
...
Yoko
1 year ago
I think running the set showplan_all Transact-SQL statement is the correct first step to display the estimated execution plan.
upvoted 0 times
...
Phung
1 year ago
I agree with An. Enabling Query Store will allow us to capture the execution plan.
upvoted 0 times
...
An
1 year ago
I think the first thing to do is to enable Query Store for DB1.
upvoted 0 times
...

Save Cancel