MENU
What is the best method for sizing or scaling a search head cluster?
Suggested Answer: B
Get Premium SPLK-2002 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
35 comments · newest first
ME
Melissa
10 months ago
D is interesting, but I’d need more info on that approach.
SA
Samira
11 months ago
Wait, are we really dividing indexers by three? Sounds weird.
LE
Leah
11 months ago
C seems a bit off, not sure about that one.
GE
Geraldo
11 months ago
Totally agree, B is the way to go!
AL
Alonso
11 months ago
I think option B makes the most sense for scaling.
HE
Helaine
12 months ago
Dividing the number of indexers by three seems off to me; I don't think that's a standard method for sizing search heads.
KE
Kerry
12 months ago
I practiced a similar question where we had to consider CPU cores, but I can't remember if it was about ingest volume or searches.
MA
Matthew
12 months ago
I think option D sounds familiar; it might be about concurrent searches, but I can't recall the exact details.
LA
Lawanda
1 year ago
I remember something about estimating searches per day, but I'm not sure if that's the best approach.
JI
Jillian
1 year ago
This seems straightforward. I'll go with option D - estimating the maximum concurrent searches and dividing by the CPU cores.
JI
Jill
1 year ago
I'm a bit confused by the wording of the question. I'll need to make sure I understand the concepts before attempting to answer.
GE
Gene
1 year ago
Okay, I think I've got this. The key is to focus on the maximum daily ingest volume and the number of CPU cores per search head.
CI
Ciara
1 year ago
Hmm, I'm not sure about this one. I'll have to review the material on search head clustering again.
GE
Geraldo
1 year ago
This looks like a tricky question. I'll need to think through the different options carefully.
NI
Nikita
1 year ago
Okay, I've got this. The issue is that the artifacts are currently accessible to anyone with an AWS account, so we need to lock that down. Option C, creating an S3 bucket policy to grant read access to the relevant accounts and deny access to everyone else, is definitely the way to go.
KA
Kassandra
1 year ago
Okay, I think I know the answer to this one. I'll go with option C and convert the trigger to use the future annotation.
AL
Altha
1 year ago
Hmm, I'm a bit unsure about this one. I know we need to be careful when testing a cloud-based app, but I'm not sure if option B is the right way to go. Trying to evade the provider's detection systems could get us in trouble.
FI
Filiberto
1 year ago
Hmm, that's an interesting perspective. I can see how that method could also work well for sizing a search head cluster.
TH
Theron
1 year ago
I disagree, I believe option D) Estimate the maximum concurrent number of searches and divide by the number of CPU cores per search head is the way to go.
FI
Filiberto
1 year ago
I think the best method is A) Estimate the maximum daily ingest volume in gigabytes and divide by the number of CPU cores per search head.
AD
Adelina
1 year ago
I personally think option B) Estimate the total number of searches per day and divide by the number of CPU cores available on the search heads makes the most sense.
TO
Tom
1 year ago
Haha, C is just ridiculous. Might as well just roll a dice to determine the number of search heads.
KR
Krissy
1 year ago
B) Estimate the total number of searches per day and divide by the number of CPU cores available on the search heads.
HA
Harley
1 year ago
A) Estimate the maximum daily ingest volume in gigabytes and divide by the number of CPU cores per search head.
AM
Amber
1 year ago
B) Estimate the total number of searches per day and divide by the number of CPU cores available on the search heads.
SI
Sina
1 year ago
A) Estimate the maximum daily ingest volume in gigabytes and divide by the number of CPU cores per search head.
FL
Fletcher
1 year ago
Hey, I was going to pick C, but that sounds like a total guess. Dividing indexers by 3? What kind of magic number is that?
SH
Sherly
1 year ago
I disagree, I believe option D) Estimate the maximum concurrent number of searches and divide by the number of CPU cores per search head is the way to go.
MI
Michell
1 year ago
I was about to choose B, but D makes more sense. Gotta account for those peak concurrency numbers, not just total volume.
AB
Abel
2 years ago
Hmm, D seems like the most reasonable approach. Sizing the search head cluster based on the maximum concurrent searches makes the most sense to me.
BU
Bulah
1 year ago
User4: D does seem like a logical choice for scaling the search head cluster.
MA
Margot
1 year ago
User3: I would go with D as well. Sizing based on concurrent searches is practical.
SI
Silvana
1 year ago
User2: I agree, it seems like the most reasonable approach.
EM
Emerson
1 year ago
User1: I think D is the way to go. Sizing based on maximum concurrent searches makes sense.
VI
Viki
2 years ago
I think the best method is A) Estimate the maximum daily ingest volume in gigabytes and divide by the number of CPU cores per search head.