Deployment Architecture

Splunk Practical Deployment Lab

shabamichae
Path Finder

I am a Splunk Enterprise Certified Admin who has an opportunity to advance to Splunk Architect. Im planning on taking the Splunk Lab. I am preparing for my Splunk architect practical Lab. Please i want to ask ,

In the  practical Lab exam, is it acceptable to have only one instance run as The Deployment Server, License Master and the Monitoring Console on the same port  on  the management system 

Or I am  expected to run different Three Splunk instances working on different ports (Deployment server, License Master and on the monitoring console) on the Management System 

 

0 Karma
1 Solution

kiran_panchavat
Influencer

@shabamichae 

I think this is a small deployment, installing the LM and MN on the same instance will work.  This approach is practical for lab environments and smaller deployments, as it reduces resource overhead.

Did this help? If yes, please consider giving kudos, marking it as the solution, or commenting for clarification — your feedback keeps the community going!

View solution in original post

shabamichae
Path Finder

In the practical Lab environment, how important is it to configure TLS on Splunk servers during the practical Lab, is it mandatory to configure TLS on my environments?

0 Karma

gcusello
SplunkTrust
SplunkTrust

Hi @shabamichae ,

as also @isoutamo said: do only the requested things not anything else!

Ciao.

Giuseppe

isoutamo
SplunkTrust
SplunkTrust
If they don’t tell it, then you should ask it or make assumption 🤔
0 Karma

shabamichae
Path Finder

Thanks

0 Karma

isoutamo
SplunkTrust
SplunkTrust
When you are doing those labs, please remember that you are doing that work for "customer"!

This means that Client have given you already some instructions/plan/architecture how he/she see the result. When there is something confusing or not described enough clearly you should ask it from your Client just like in real life. It's always best to discuss with Client and ensure that both parties have exactly same understanding what you are doing! Worst think what you could do in those labs is make some guesses 😉 Always ask if you are not sure what client wants. You should know how you do it after that.

gcusello
SplunkTrust
SplunkTrust

Hi @shabamichae ,

this is a lab environment so it isn't mandatory to have different servers for the three roles.

Also because you need a dedicated DS only if you need to manage more than 50 clients and in the lab you have few clients.

In addition, in general only the DS requires a dedicated server, License Master and Monitoring Console can share the same machine.

Anyway, in the lab, the exercise says to you which solution you have to use. and they are both useful (in the lab!).

Ciao.

Giuseppe

shabamichae
Path Finder

@gcusello 
So, if I get you correctly, In the practical Lab exam, I can run Deployment Server, License Master and the Monitoring Console on the same instance with same port

0 Karma

gcusello
SplunkTrust
SplunkTrust

Hi @shabamichae ,

yes, you can do it.

Ciao and happy splunking

Giuseppe

P.S.: Karma Points are appreciated by all the contributors 😉

shabamichae
Path Finder

@gcusello Thanks

0 Karma

kiran_panchavat
Influencer

@shabamichae 

I think this is a small deployment, installing the LM and MN on the same instance will work.  This approach is practical for lab environments and smaller deployments, as it reduces resource overhead.

Did this help? If yes, please consider giving kudos, marking it as the solution, or commenting for clarification — your feedback keeps the community going!

shabamichae
Path Finder

Thanks @kiran_panchavat 
So, if I get you correctly, In the practical Lab exam, I can run Deployment Server, License Master and the Monitoring Console on the same instance with same port

0 Karma

kiran_panchavat
Influencer

@shabamichae 

Yes, you can run the Deployment Server, License Master, and Monitoring Console on the same Splunk instance using the same port (default port 8089 for management). However, there are a few things to consider:

Resource Efficiency: Good for lab environments or small deployments where resources are limited.

Simpler Management: easier to manage since all roles are on a single instance.

Did this help? If yes, please consider giving kudos, marking it as the solution, or commenting for clarification — your feedback keeps the community going!
Get Updates on the Splunk Community!

Uncovering Multi-Account Fraud with Splunk Banking Analytics

Last month, I met with a Senior Fraud Analyst at a nationally recognized bank to discuss their recent success ...

Secure Your Future: A Deep Dive into the Compliance and Security Enhancements for the ...

What has been announced?  In the blog, “Preparing your Splunk Environment for OpensSSL3,”we announced the ...

New This Month in Splunk Observability Cloud - Synthetic Monitoring updates, UI ...

This month, we’re delivering several platform, infrastructure, application and digital experience monitoring ...