Immediately after deployment of a transaction ACS deployment the environment started to suffer performance issues. The cause was traced to the server resources being over-used. What would be causing these resources to be over-used? Select Two.
I'm gonna go with the daily ingestion load and the transactional scenario not matching real-world conditions. Those sound like the most likely culprits to me.
Dude, you're so right. That's like the first thing you think about in capacity planning. 'How much data am I going to be dealing with?' Rookie mistake for sure.
Haha, yeah, the 'average content size' one is a classic. I bet the exam writers are just trying to trip us up with that one. Like, who forgets to plan for the actual content?
You know, I was just reading about a case where the average content size was the issue. If you're not accounting for that, your servers can get bogged down pretty quickly.
I agree, capacity planning is key. I think the index size and transactional metadata queries are probably the main culprits here. Those can really eat up server resources if you're not prepared for them.
Oh man, this question is a tough one. I bet the answer has to do with the capacity planning process. We really need to make sure we consider all the factors that can impact performance during that phase.
upvoted 0 times
...
Log in to Pass4Success
Sign in:
Report Comment
Is the comment made by USERNAME spam or abusive?
Commenting
In order to participate in the comments you need to be logged-in.
You can sign-up or
login
Sherman
8 days agoVerlene
10 days agoRenay
11 days agoLouis
12 days agoEmerson
14 days agoStevie
15 days ago