MENU
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.
Suggested Answer: D, E
Get Premium ACSCA Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
38 comments · newest first
LA
Lashaun
11 months ago
Daily ingestion load is crucial, gotta plan for that!
CE
Cecilia
11 months ago
I disagree, C seems less likely than D in this case.
MI
Mireya
11 months ago
Surprised that index size wasn't considered, that's basic stuff!
EL
Elmira
12 months ago
I think B is a big factor too, can't ignore metadata!
DA
Davida
12 months ago
Definitely A and E, those are common oversights.
LI
Ligia
1 year ago
I vaguely remember a scenario where load testing didn't match real-world conditions, which could explain the resource overuse. That might be option E.
ZO
Zona
1 year ago
I feel like average content size might be important too, but I can't recall if it was specifically mentioned in our practice questions.
CO
Cory
1 year ago
I think option B makes sense because if we didn't account for transactional metadata queries, it could definitely overload the server.
LA
Lauryn
1 year ago
I remember we discussed how not considering the index size could lead to performance issues, but I'm not entirely sure if it's one of the answers here.
GE
Genevieve
1 year ago
I'm feeling pretty confident about this one. The index size and transactional metadata queries are the two factors that stand out to me as the most likely causes of the performance issues.
AN
Anthony
1 year ago
Daily ingestion load and the transactional scenario used for load testing seem like the most likely culprits here. I'll focus on those two options.
JA
Jannette
1 year ago
Okay, I think I've got a handle on this. The index size, transactional metadata queries, and content size are all important factors to consider during capacity planning.
LE
Lenny
1 year ago
This looks like a tricky one. I'll need to think carefully about the factors that could lead to over-utilization of server resources.
EL
Elliot
1 year ago
Hmm, I'm a bit confused on this one. I'll need to review the capacity planning considerations more closely to identify the key issues.
RU
Ruth
1 year ago
Hmm, this seems like a tricky one. I'll need to carefully read through the user story and think about what other objects might be involved in handling the legacy data.
LY
Lynette
1 year ago
Okay, let's see. First, I need to create a new cluster with the specified HA properties. Then I need to configure Fault Tolerance on a VM. I've done this before, so I feel pretty confident.
TR
Truman
1 year ago
Hmm, I'm not sure about this one. I know the `ls` command, but I'm not familiar with the specific options to get information on its usage.
CR
Crissy
1 year ago
This question seems pretty straightforward. I'm pretty confident I can figure out the purpose of the Request Rationalization component.
ST
Steffanie
1 year ago
I'm a little confused on the differences between the financial statements. I'll need to review my notes to make sure I understand which one provides the information asked for in the question.
AN
An
2 years ago
Candidate 6: Definitely, all these factors not being considered properly during planning could lead to performance issues.
JA
Jarvis
2 years ago
Candidate 5: I think the average content size may also have played a role in over-using the resources.
LA
Lashawna
2 years ago
Candidate 4: Yes, that could definitely contribute to the performance issues.
MI
Micaela
2 years ago
Candidate 3: I believe the transactional scenario used may not have been tested properly under real-world conditions.
NO
Norah
2 years ago
Candidate 2: I agree, but it could also be because the daily ingestion load was not considered.
EL
Eleonora
2 years ago
Candidate 1: I think the over-use of server resources could be due to not considering the index size during capacity planning.
PE
Pearlie
2 years ago
Do you think the index size not being considered could have also contributed to the performance issues?
ST
Stefany
2 years ago
Yes, it's important to test the system with realistic loads to ensure it can handle actual usage.
DE
Della
2 years ago
I believe also that the transactional scenario used not closely resembling real-world conditions could be another reason for the server resources being over-used.
AL
Aliza
3 years ago
I agree, not factoring in the size of the daily ingestion load can definitely lead to performance issues.
KE
Kerry
3 years ago
I think the daily ingestion load not being considered could be a major factor in over-using server resources.
SH
Sherman
3 years ago
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.
VE
Verlene
3 years ago
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.
RE
Renay
3 years ago
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?
LO
Louis
3 years ago
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.
EM
Emerson
3 years ago
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.
ST
Stevie
3 years ago
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.
LA
Latia
2 years ago
E) The transactional scenario used didn't closely resemble real-world conditions using load testing.
VA
Valene
2 years ago
A) The index size was not considered during capacity planning.