Pratica di Shadowing: .NET Mock Interview - Scenario Based - 7+ Years Experienced Candidate - Impara a parlare inglese con i video

Scegli una modalità di pratica

Ogni modalità apre una sala di pratica a schermo intero.

233 frasi

Se le frasi sono troppo corte o troppo lunghe, clicca su Edit per modificarle.

So this is an example of eager loading.

So we are just iterating one by one and it is increasing the round trip with the database and to avoid these,

it is a good because if we are not more than more rows in the database,

but if we have a 5 lakhs to 2 lakhs rows in the database, it is not a good.

So now what I will do is I will show you a piece of code.

So this is a simple get user method.

Okay.

We are getting the user details based on the user ID from database.

And this is an async method here and user service or async method.

And we are getting the result and we are assigning it to a variable user.

And then just we are returning the user.

This is the API simple method.

Okay.

Can you tell me is there any problem?

Can you improve this code?

Is there any missing in this code?

Do you think it is?

No, if we are using async, then we will have to apply the await and async keywords.

After the public, we need to add the await and we are getting the result.

User equals to await.

We need to write here.

yeah okay all right so yes so you are right

so basically the problem is that dot result this result will block the thread

so basically what will happen one thread will execute this port right

and your answer is right i'm just elaborating it okay so

but if this method that third is executing

if they get by idsing method is taking too much time then what will happen the thread will be blocked

and if the thread will block it is waiting

because then what will happen your application will be blocked

so the correct way to do is as you said and

that is here i have already written i don't want to type

so here a sync

and await keyword we have to use now what will happen this await will release the thread

so for example the thread one is executing this board okay now what will happen

if we are using uh a great the thread one will be released okay

because get by id async is taking time

so thread one will be released

and it will go back to the thread pool your thread one

and from the thread pool it will be allowed to do some different operation action function whatever okay

so your application will not be blocked the thread one keep on working on something else

and when the response is available then the thread one

or thread one or even some different thread okay whatever thread will be available will get the response

and it to the user and your recall in short your your operation will work smoothly

okay so this is the benefit of using a sync

and update here are you an experienced dotnet developer

but struggling to clear interviews knowing definition is not enough answering

scenario based questions can decide your selection in my free live.net interview workshop

i will explain how to prepare for interviews

if you are preparing for your next.net interview

then this workshop is for you register for free workshop on

6 september sunday 8 pm using the link in the description

we'll see you live suppose your application requires a user service which will

user service

which will handle the information about the user user class user service class you have you need a class

or a service you can say now how would you implement

and inject the service using dependency induction

so you can say can you tell the steps what you will do to from creating

this user service how you will create

and how you will inject in the uh you will use in your application

so user service i will inject using the adpob lifetime so

that means user service the instance of

that service needs only once in every user means every user request will create the new instance

so http request when the user login so every user means every user with each

So we will use scoped lifetime for dependency injections.

So if you talk about the practical thing,

build.add.service and we can add scope as injection and inside the bracket we can add the service name and then

then the parent test is we can apply okay okay so it's like uh

Basically, there is a series of steps when we are implementing some service.

First of all, we have to create an interface of that service.

I'm telling you because I asked the steps.

Okay, you asked some points which were part of the process,

but the complete process is like first we have to create one interface like i user service

and then we have to create the service itself by implementing

that interface okay so i user service

and we will class create the class user service implementing the i user service interface

then what we will do we will register the service the user service in the program.csv okay

so that by using how add scope which you have said correctly

but you will use a discord

and inside the type the angular brackets we will use i user service from my user service like this

so and we will register the service we could be we call this thing the three steps

so first interface second service third register the service

then fourth is inject the service by the controller oh sorry by the constructor

so for example you want the user service inside the user controller okay

there is a user controller

now either one way is you can create directly the object of the user service inside the user controller

but we will not create the object using the new keyword we will inside the user controller

we will call the user controller constructor

and there we will inject the user service as a parameter okay

and as soon as we uh in inject then the object will be created by the dotnet in the background

and that object underscore user service that so basically four steps

interface service register the service in the program

and finally constructor uh inside wherever

you want to use the user controller uh product controller in whatever controller you want to use it okay

so support those for a sp.net core application has a user service okay that manages

about user data use related things user service class okay user related functions are inside it

and then there is a logger service

that basically manages whenever you want something log there are function inside

which will managing the logs like if you want to log something then that kind of of functions are inside logger service.

Now, which dependency detection lifetime will you choose for user service, and which you will use for logger service?

100

For user service, I will choose scoped, because every user will create login with its credentials.

101

So every user can see their own application, their own information, not other.

102

If other user will logged in, the new instance will be generated.

103

And for logged, we will use singleton.

104

So singleton will be okay.

105

So it is create the once and it will use the lifetime of the application.

106

Yeah, correct.

107

So very much accurate.

108

For whenever we don't want to share the data, like in the user service case,

109

we don't want to share the user data of one request with another request.

110

Okay.

111

So that time we will use a scoped.

112

So one instance per HTTP request, one HTTP request, one instance.

113

But in logger service, it's okay to share the instance

114

across the application because we are just logging the information throughout the application.

115

There is nothing like, no critical information is there.

116

okay so singleton is better and singleton will make it more but there will be only one instance

117

then it will be good for performance because

118

if there are multiple instances for example in scope also for multiple requests there will be multiple instances one right

119

so performance will be slightly less but singleton performance will be very high

120

and transient is there where in

121

that case performance will be very much multiple instances will be there inside the request also okay suppose

122

you have a dotnet core application okay

123

and a request is coming to your dotnet application

124

and now in your dot application you have to check whether the request is containing some valid api key

125

or some valid authentication token some thing you have to check and if that

126

api key is for example missing

127

or invalid then your application should not process the request

128

and return an error response to the front end or from wherever the request is coming okay

129

so how you will implement some idea like how you will implement using the uh using the middleware

130

and the the idea is you have to use these method user

131

and map in a in a proper way so indication is different

132

that authentication before that authentication first you will check the whether the api has received some token

133

or not right first you have to it should not be blank right

134

when it have some token then the jwd authentication will start working to validate

135

that token that whether the token is correct or not okay so if the request don't have any token

136

then why to send it for disability authentication

137

you can initially using the middle words you can check it no idea okay okay no problem

138

so uh i will i will give one one minute

139

i will give some idea okay let me share my screen okay

140

so inside your program.cs file

141

so imagine this is your program.cs file here

142

you will use the use method okay

143

this is completely your use method up up until here let me make it short

144

so inside it you will check

145

this thing whether the you will try to extract the api key from the request header okay

146

this is the request this is the context request header and

147

if it has api

148

if you will receive the api key then you will run

149

this await next method have any idea about next method

150

that is also the part of the middleware

151

so next method will then run this map controllers okay but

152

if there is no api key then so

153

if this condition has api key is not means there is no api key then this code will be executed

154

and it will basically it's a sample don't just like it this code can be changed

155

but the logic you have to understand that use map

156

then we will return to stop the pipeline

157

we will not execute for the we will return back to the from the to the front end

158

that we don't have any if we don't get the API key with your request

159

so it's an invalid request API key is missing

160

or invalid okay okay

161

so we the short answer is we will use the app dot use method

162

and next method to to handle

163

this situation whether we have a we have to proceed with the request there is a valid API key

164

if there is a valid API key then yes awaited up next will execute this this map controllers

165

last line of code okay and if there is no api key then it's written just written it blank okay

166

this code is executing

167

and getting all the customers from the database okay this dot customers from the database

168

and then assigning this customer details to a list this now customer variable is a list

169

which will have all the list of the customers okay then we are iterating the customers list one by one

170

and getting the orders of the customers each customer okay and so that is the code now

171

you have to tell me we is there any problem with this code

172

or is we can can we make this better

173

can we optimize this is there anything you have noticed like

174

so this is an example of eager loading

175

so we are just iterating one by one and it is increasing the round trip with the database

176

and to avoid these with it is a good because

177

if we are not more than more rows in the database

178

but if we have a five likes to two lakhs rows in the database it is not a good

179

because it will increase the latency and roundtrip, it can increase.

180

Instead of we can use explicit loading, so we can use the include keyword and get the data.

181

And we can get the particular data, whatever that we want to need.

182

We can use the include keyword and these iteration will need to remove.

183

One by the iteration we need to remove.

184

Yeah, so correct.

185

Your answer is correct correct so basically uh i'm just elaborating

186

or i'm just rephrasing what you have said

187

so what is happening here is first we are making one this query

188

and getting a query hitting the database so this is one

189

and suppose we get 100 customers in this list

190

then for 100 each of those customers we are making one query for each customer

191

so it's like 100 queries again we are making

192

so total we have this 100 plus 1

193

which is 100 plus 1 1 0 1 database hits

194

so this is also called n plus 1 problem okay

195

so the solution is again what you have said and

196

that is we have to use the include method okay and include method will get the customer and order details

197

like this you do not with only a single head to the database okay

198

so this is one way and we call it

199

equal loading this only okay another approach is using the select method

200

this is the select method now forget about this code uh

201

you can forget like uh yeah control z let just forget about this code here ctrl x

202

so this is the select method that we also called projection

203

the benefit of select over include is in select

204

you can give the sorry control z give the columns specific columns

205

which you want okay with include you have to have get all you will get all the columns by default

206

but with select you can give the columns also like this id name

207

and inside order what you want order id order i getting my mind yes yes okay so

208

that is the difference

209

and there is the these are the co-options okay are you an experienced dotnet developer

210

but struggling to clear interviews knowing definition is not enough

211

answering scenario based questions can decide your selection in my free live.net interview workshop

212

i will explain how to prepare for interviews

213

if you are preparing for your next.net interview

214

then this workshop is for you register for free workshop on 6 september sunday 8 pm

215

using the link in the description we'll see you live in your application you have a controller and that contains validation code,

216

that contains business logic methods, that contains properties, that also contains database code.

217

So how you will refactor your application, how you will refactor that controller to make it better?

218

So firstly, I will divide my application, my controller into the layers,

219

like repository and service and interface and business logic should be different and database logics should be different.

220

Means I will use a repository pattern to divide the application into the layers.

221

Like my business logic will be in the services and database,

222

data DB context means the database things will be in the repository.

223

Yes, so basically we have to divide the things we should not keep like single responsibility principle uh solid

224

or principle single responsibility so one controller or any file class file

225

or any should not can be responsible for multiple things single responsibility controller should only receive the request

226

and return the http response

227

then from there there will be domains dto's for your properties entities different class for them

228

which will be responsible for property then validation for validation you should have a different data annotation

229

or different model fluent validation then there will be service layer for the business logic then yes

230

that access layer or you can say the repository

231

layer also you can say it for entity framework or ado.net

232

so if you will add like single responsibility thing to these kinds of you can relate able to relate then

233

that will be sound good but yeah that is also the same thing you are saying okay

Scarica l'app

Tutto ciò che serve per parlare fluentemente

Pronuncia con IAVoto per ogni frase

Pratica IPAPadroneggia ogni suono

VocabolarioCostruisci il tuo lessico

Gioco di vocabolarioImpara giocando

Scansiona QR

Download on theApp Store Get it onGoogle Play

FOR YOU

Video consigliato

324 frasi

Excellent 2 Years AWS DevOps Engineer Mock Interview with Questions and Answers | Cloud | Docker

Business EnglishInterview EnglishUniversity Students

75 frasi

The unfair way I got good at Leetcode

Interview EnglishUniversity StudentsWorking Adults

95 frasi

API Gateways in System Design Interviews w/ Ex-Meta Staff Engineer

Business EnglishInterview EnglishUniversity Students

674 frasi

FULL Data Science Mock Interview | SQL, Statistics, Business

Interview EnglishUniversity StudentsWorking Adults

356 frasi

Concurrency in Low-level Design Interviews w/ Staff Engineer

Business EnglishInterview EnglishUniversity Students

160 frasi

[2026] TOEFL iBT Speaking Take an Interview | Step-by-Step Strategies #0008

TOEFL PrepBusiness EnglishInterview English

Vocabolario e note di pronuncia per questa lezione

Questa lezione di conversazione si basa sul video “.NET Mock Interview - Scenario Based - 7+ Years Experienced Candidate”. Le parole che ritornano più spesso: user, request, method, application, controller. Questo video contiene 233 frasi e 2805 parole da ripetere con lo shadowing. Il parlato dura 20:13. Chi parla mantiene un ritmo costante di circa 139 parole al minuto, comodo per lo shadowing. Il 86% delle parole rientra nelle 3.000 più comuni dell’inglese; conviene studiare le altre prima di iniziare.

Vocaboli chiave di questo video

15 parole del video che vale la pena imparare, con pronuncia e significato:

Parola	Pronuncia	Significato
thread sostantivo	/ˈθɹɛd/	filo, refe
database sostantivo	/ˈdeɪtəˌbeɪs/	database, base di dati
controller sostantivo	/kənˈtɹoʊlɚ/	controllore, revisore
interface sostantivo	/ˈɪn(t)ɚˌfeɪs/	interfaccia
execute verbo	/ˈɛksɪˌkjuːt/	giustiziare
await verbo	/əˈweɪt/	aspettare, attendere
select verbo	/sɪˈlɛkt/	scegliere, selezionare
scope sostantivo	/skəʊp/	ambito, scopo
implement verbo	/ˈɪmpləmənt/	mettere in pratica, attuare
workshop sostantivo	/ˈwɝk.ʃɑp/	laboratorio, bottega
token sostantivo	/ˈtoʊkən/	simbolo, segno
layer sostantivo	/ˈleɪ̯ɚ/	strato
lifetime sostantivo	/ˈlaɪf.taɪm/	durata, vita utile
valid aggettivo	/ˈvælɪd/	valido
log sostantivo	/lɔɡ/	tronco

Frasi da ripetere

Frasi brevi e complete del video che puoi riutilizzare nella conversazione di tutti i giorni:

Can you tell me is there any problem?
Can you improve this code?
Do you think it is?
I'm telling you because I asked the steps.

La grammatica di questo video

Le strutture che chi parla usa di più, con le parole esatte del video:

Struttura	Nel video
Frasi condizionali if + frase, will/would + verbo — una condizione e il suo risultato	if the thread will block · If other user will logged
Forma passiva be + participio passato — conta ciò che accade, non chi lo fa	will be blocked · will be released · will be allowed
Present perfect have/has + participio passato — un’azione passata che conta ancora adesso	have already written · have said · has received
Frasi relative who / which + frase — un’informazione in più su una persona o una cosa	service which will · points which were

Pronuncia a cui fare attenzione

Chi parla usa 13 contrazioni e forme ridotte, come don't, I'm, we'll. Pronunciale nella forma breve, così come le senti.

I suoni “th”: thread /ˈθɹɛd/, smoothly /ˈsmuːðli/, authentication /ɔːˌθɛntɪˈkeɪʃn̩/
I suoni “sh” e “zh”: workshop /ˈwɝk.ʃɑp/, validation /ˌvæl.əˈdeɪ.ʃən/, injection /ɪnˈd͡ʒɛk.ʃən/, detection /dɪˈtɛk.ʃən/, indication /ɪndɪˈkeɪʃən/
Parole lunghe — attenzione all’accento: validation /ˌvæl.əˈdeɪ.ʃən/, dependency /dɪˈpɛndənsi/, developer /dɪˈvɛləpɚ/, entity /ˈɛn.tə.ti/ [-tʰi], elaborate /ɪˈlæb.ə.ɹeɪt/

I suoni difficili per chi parla italiano:

/h/ — va soffiata, non è muta: wherever /(h)wɛɹˈɛvɚ/, header /ˈhɛdɚ/
Consonante finale — senza aggiungere una vocale dopo: thread /ˈθɹɛd/, database /ˈdeɪtəˌbeɪs/, interface /ˈɪn(t)ɚˌfeɪs/, execute /ˈɛksɪˌkjuːt/, await /əˈweɪt/
/æ/ — più aperta della “e”: valid /ˈvælɪd/, validation /ˌvæl.əˈdeɪ.ʃən/, blank /ˈblæŋk/, variable [ˈvæɹ.i.ə.bl̩], elaborate /ɪˈlæb.ə.ɹeɪt/

Come esercitarsi con questo video

Ascolta tutto il video una volta senza parlare e annota le parole che non conosci.
Fai shadowing frase per frase a velocità normale, ripetendo ognuna finché il tuo ritmo coincide con quello di chi parla.
Registrati e confronta con l’originale, facendo attenzione a parole come thread, database, controller.

Cos'è la tecnica dello Shadowing?

Shadowing è una tecnica di apprendimento delle lingue supportata da studi scientifici, originariamente sviluppata per la formazione dei traduttori professionisti e resa popolare dal poliglotta Dr. Alexander Arguelles. Il metodo è semplice ma potente: ascolti un audio in inglese di madrelingua e lo ripeti immediatamente ad alta voce — come un'ombra che segue il parlante con un ritardo di solo 1–2 secondi. A differenza dell'ascolto passivo o degli esercizi di grammatica, lo shadowing costringe il tuo cervello e i muscoli della bocca a elaborare e riprodurre simultaneamente i modelli di discorso reale. La ricerca dimostra che migliora significativamente la precisione della pronuncia, l'intonazione, il ritmo, il discorso connesso, la comprensione dell'ascolto e la fluidità del parlato — rendendolo uno dei metodi più efficaci per la preparazione alla prova di speaking dell'IELTS e per la comunicazione reale in inglese.

Tecnica dello shadowing: leggi la guida completa passo dopo passo →

Pratica di Shadowing: .NET Mock Interview - Scenario Based - 7+ Years Experienced Candidate - Impara a parlare inglese con i video

Scegli una modalità di pratica

Scarica l'app

Distributed Task Scheduler: System Design Interview (Stripe & Amazon Offers)

Next JS Interview Questions and Answers 2026 | Top 20 Most Asked Questions

Mastering iOS Development: Mock Interview with Ramiro Neto

Uber Data Engineering Mock Interview - Ride-Sharing Data Warehouse Schema

FullStack Interview Questions (Junior & Mid)

🚫 Java Deadlock Explained: Why Your Code is Stuck 😱 (Beginners Must Watch!)

Excellent 2 Years AWS DevOps Engineer Mock Interview with Questions and Answers | Cloud | Docker

The unfair way I got good at Leetcode

API Gateways in System Design Interviews w/ Ex-Meta Staff Engineer

FULL Data Science Mock Interview | SQL, Statistics, Business

Concurrency in Low-level Design Interviews w/ Staff Engineer

[2026] TOEFL iBT Speaking Take an Interview | Step-by-Step Strategies #0008

Vocabolario e note di pronuncia per questa lezione

Vocaboli chiave di questo video

Frasi da ripetere

La grammatica di questo video

Pronuncia a cui fare attenzione

Come esercitarsi con questo video

Cos'è la tecnica dello Shadowing?