Splunk SPLK-3003 Exam - Topic 6 Question 14 Discussion

Actual exam question for Splunk's SPLK-3003 exam

Question #: 14
Topic #: 6

A customer has a multisite cluster (two sites, each site in its own data center) and users experiencing a slow response when searches are run on search heads located in either site. The Search Job Inspector shows the delay is being caused by search heads on either site waiting for results to be returned by indexers on the opposing site. The network team has confirmed that there is limited bandwidth available between the two data centers, which are in different geographic locations.

Which of the following would be the least expensive and easiest way to improve search performance?

AConfigure site_search_factor to ensure a searchable copy exists in the local site for each search head.

BMove all indexers and search heads in one of the data centers into the same site.

CInstall a network pipe with more bandwidth between the two data centers.

DSet the site setting on each indexer in the server.conf clustering stanza to be the same for all indexers regardless of site.

Show Suggested Answer

Suggested Answer: A

by Howard at May 10, 2022, 03:41 AM

Limited Time Offer

25%

Off

Get Premium SPLK-3003 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Inocencia

4 months ago

D seems like a workaround, but not sure it’ll help much.

upvoted 0 times

...

Nichelle

4 months ago

More bandwidth (C) would be ideal, but it's probably expensive.

upvoted 0 times

...

Cassie

4 months ago

Wait, can you really just change the site_search_factor? Sounds too simple!

upvoted 0 times

...

Altha

4 months ago

I disagree, moving indexers (B) might be better for performance.

upvoted 0 times

...

Helga

4 months ago

A is definitely the easiest option!

upvoted 0 times

...

Bette

5 months ago

Setting the site settings on indexers (Option D) could help, but I’m not clear on how that would directly impact search performance. It seems a bit complicated.

upvoted 0 times

...

Tenesha

5 months ago

I feel like installing a network pipe (Option C) could be effective, but it sounds expensive and might take time to implement.

upvoted 0 times

...

Jerry

5 months ago

I think moving all indexers and search heads to one site (Option B) could solve the problem, but it might be more disruptive than just adjusting the search factor.

upvoted 0 times

...

Kenda

5 months ago

I remember we discussed the importance of having local searchable copies to reduce wait times. Option A seems like a good choice, but I'm not entirely sure if it's the easiest solution.

upvoted 0 times

...

Tiera

5 months ago

The key here is to think about how the length of the accumulation and retirement phases are impacted by retiring early. I'm pretty confident that B is the correct answer.

upvoted 0 times

...

Lavonne

5 months ago

I've got this one! The fixed width format is the only one that would require pre-processing or parsing after import. The other delimited formats should be handled automatically by Marketing Cloud. I'm confident that A is the correct answer.

upvoted 0 times

...

Yaeko

5 months ago

I think creating a line chart with the MAE could give us some insights over time. We did a practice question like that, but I'm not totally certain.

upvoted 0 times

...

Raymon

5 months ago

This looks like a pretty straightforward question. I'd suggest going with option A - including multiple rows with each request. That should help improve the efficiency and reduce the overhead of making individual requests.

upvoted 0 times

...