SPLK-1005 · Splunk Cloud Certified Admin

SPLK-1005 Study Guide & Practice Exam

Master Splunk Cloud Platform administration — Victoria vs. Classic Experience, ACS API v2, forwarders and IDM, Self-Service App Install, DDAA/DDSS, and Federated Search.

Start Free Course📝 Practice Exam (83+ questions)

SPLK-1005 Quick Facts

The SPLK-1005 exam (Splunk Cloud Certified Admin): 60 questions, 75 minutes, passing score 70%, cost $130 USD ($500 for 5-exam bundle). Prerequisites: SPLK-1002 Splunk Core Certified Power User (required).

Exam codeSPLK-1005
CertificationSplunk Cloud Certified Admin
Questions60 questions
Time limit75 minutes
Passing score70%
FormatMultiple choice
Cost$130 USD ($500 for 5-exam bundle)
PrerequisitesSPLK-1002 Splunk Core Certified Power User (required)
Free prep on Splunky24 lessons, 83+ practice questions

Exam details can change. Confirm on Splunk's official page before booking: official SPLK-1005 exam page ›

🏰
7
Floors
📖
24
Lessons
📝
83+
Practice Qs
🎉
FREE
Price

About the SPLK-1005 Certification

The Splunk Cloud Certified Admin (SPLK-1005) certification validates your ability to administer day-to-day Splunk Cloud Platform operations within Splunk's SaaS shared-responsibility model. Unlike on-premises Splunk Enterprise administration, Cloud admins do not receive SSH or OS-level access; instead, you manage stacks through Splunk Web, the Admin Config Service (ACS) API v2 and CLI, Self-Service App Install (SSAI), and the Cloud Monitoring Console (CMC).

This free SPLK-1005 study guide and interactive Splunky course cover every core exam domain plus modern Cloud operations: Victoria vs. Classic Experience architecture, Universal and Heavy Forwarder onboarding (splunkclouduf.spl and on-prem Deployment Servers), HTTPS port 443 HEC endpoints, Data Manager, props.conf/transforms.conf parsing and raw data masking, DDAA vs. DDSS archiving, sc_admin RBAC and SAML SSO, Federated Search (Standard, Transparent, and FS-S3), and _internal/_audit troubleshooting.

📚 What's on the SPLK-1005 Exam

1. Splunk Cloud Architecture & Experiences

Victoria Experience vs. Classic Experience topology, IDM deprecation and migration onto the Search Head tier, SmartStore multi-AZ indexers, single-instance vs. SHC capabilities, and the shared-responsibility boundary with Splunk Support.

2. Admin Config Service (ACS) API v2 & CLI

Commercial and FedRAMP IL2 base URLs, Bearer JWT authentication for sc_admin, IP allowlists (s2s, hec, search-api, search-ui, idm-api, idm-ui) with 200/230 subnet limits, outbound ports, HEC tokens, indexes CRUD, limits, search head restarts, and read-only maintenance window inspection.

3. Getting Data In: Forwarders, IDM, HEC & Data Manager

Universal Forwarder Credentials Package (splunkclouduf.spl) on TCP 9997, system/local/outputs.conf precedence traps, customer-managed on-premises Deployment Servers (including Splunk 9.2+ client deletion deprecation), Heavy Forwarders vs. Data Manager, and HTTPS :443 HEC URL differences across AWS, GCP/GovCloud, and Firehose.

4. Parsing, Fine-Tuning & Raw Data Manipulation

Source type configuration in props.conf and transforms.conf (TIME_FORMAT, TIME_PREFIX, SHOULD_LINEMERGE, LINE_BREAKER, TRUNCATE), Data Preview, inline masking with SEDCMD, nullQueue filtering, Ingest Actions, and automatic index-time push on Victoria.

5. Index Management, DDAA & DDSS Retention

Event and metric index lifecycle via Web UI and ACS, searchableDays (DDAS), Dynamic Data Active Archive (DDAA 30-day restore and 10%-20% entitlement cap) vs. Dynamic Data Self Storage (DDSS S3/GCS IAM policies, KMS CMK keys, Federated Search for DDSS, external Splunk Enterprise restore), and can_delete / | delete behavior.

6. Self-Service Apps, RBAC & SAML Authentication

Self-Service App Install (SSAI) for Splunkbase and private apps, AppInspect Cloud vetting (private_victoria, private_classic, no /local/ or local.meta or plaintext secrets), Victoria Web UI download restrictions, sc_admin vs. Enterprise admin, protected system accounts (admin, app-installer, index-manager), SAML 2.0 SSO, and auth tokens.

7. Federated Search, CMC, SVC & Troubleshooting

Standard mode (index=federated:, | from federated:, service account) vs. Transparent mode (splunk_federated_provider), fsh_search and fsh_manage capabilities, Federated Search for Amazon S3 (Glue Catalog and Data Scan Units), Cloud Monitoring Console (CMC) dashboards, SVC workload attribution, and _internal/_audit SPL diagnostics.

🎯 Sample SPLK-1005 Practice Questions

Preview 3 questions from our 83+ question bank:

Q1. Why must an organization deploy an on-premises Heavy Forwarder or SC4S collector when onboarding legacy network appliances that only emit UDP syslog?
ABecause Splunk Cloud Universal Forwarders disable TLS encryption on TCP 9997 and require plain UDP transport for network devices
BBecause UDP syslog ingestion requires an Inputs Data Manager (IDM) node that is only provisioned on Victoria Experience stacks
CBecause Splunk Cloud indexers do not open arbitrary UDP/TCP syslog ports, requiring on-prem collection before S2S 9997 or HEC 443✓ Correct
DBecause ACS outbound-ports only permits ICMP health checks and blocks all TCP/UDP forwarding from on-premises security appliances
Explanation: Splunk Cloud does not expose arbitrary UDP or TCP syslog ingestion ports on cloud indexers. Customers collect syslog on an on-premises Heavy Forwarder or SC4S node and forward encrypted traffic over TCP 9997 or HTTPS port 443 HEC.
Q2. Which ACS API v2 request configuration is valid when programmatically provisioning a new HEC token on a commercial Victoria stack?
AAuthorization: Bearer <JWT> issued to an sc_admin user sent to https://admin.splunk.com/{stack}/adminconfig/v2/inputs/http-event-collectors✓ Correct
BAuthorization: Splunk <token> issued to a user holding only the power role and posted to the Enterprise endpoint on port 8088
CHTTP Basic Auth using the built-in index-manager system account credentials posted to https://http-inputs-{stack}.splunkcloud.com/services/collector
DSSH key-pair authentication executed directly against the Search Head Cluster deployer node over management port 8089 using CLI
Explanation: ACS API v2 calls use Authorization: Bearer <JWT> belonging to an sc_admin user against https://admin.splunk.com/{stack}/adminconfig/v2/inputs/http-event-collectors.
Q3. A compliance team needs logs older than 90 days archived in its own AWS S3 bucket with customer-managed KMS encryption and queried occasionally without restoring 30-day slices into main Cloud active storage. Which design meets this requirement?
AEnable both DDAA and DDSS on the same index simultaneously so buckets copy to Splunk Archive and customer S3 in parallel
BRun the | delete command on events older than 90 days so SmartStore immediately exports those buckets into a customer S3 path
CRoute events older than 90 days to nullQueue in transforms.conf and query the discarded raw logs from index=_audit afterward
DConfigure DDSS via ACS self-storage-locations, apply S3 and KMS CMK policies, and query buckets via Federated Search for DDSS✓ Correct
Explanation: DDSS exports rolled buckets to customer-owned S3/GCS storage encrypted with optional KMS keys and supports querying directly through Federated Search for DDSS (or restoring to a separate Splunk Enterprise instance). DDAA and DDSS are mutually exclusive per index.
Take the Full Practice Exam →

💡 Study Tips for SPLK-1005

  1. Contrast every task with Splunk Enterprise: know what sc_admin can do (ACS API, SSAI, CMC, indexes, SAML) versus what Splunk Support owns (OS, clustering, maintenance schedules) and what must stay on-premises (Deployment Server, Heavy Forwarders for syslog/DB Connect).
  2. Memorize the Victoria vs. Classic Experience differences: Victoria eliminates the IDM, runs modular inputs on the Search Head tier, pushes index-time confs automatically during SSAI, uses apps/victoria in ACS, and disallows Web UI app downloads.
  3. Drill ACS API v2 endpoints, quotas, and CLI versions: 200 subnets per IP allowlist feature (230 shared per group), read-only maintenance-windows endpoints, CLI v2.5.0+ for bulk ops, and CLI v2.9.0+ for DDSS self-storage-locations.
  4. Keep Cloud ingestion URLs straight: S2S uses TCP 9997 via splunkclouduf.spl (watch out for system/local/outputs.conf overrides), while production HEC uses HTTPS 443 with http-inputs-<stack> on AWS and dotted http-inputs.<stack> on GCP and GovCloud.
  5. Know DDAA vs. DDSS and Federated Search inside out: DDAA restores to Cloud for 30 days (10%-20% DDAS cap), DDSS writes to customer S3/GCS, and Federated Search uses fsh_search/fsh_manage across Standard (federated:), Transparent (splunk_federated_provider), and FS-S3 (1 DSU = 10 TB).

🏰 Course Curriculum

Our Splunk Cloud Certified Admin course covers all exam topics across 7 dungeon floors:

❓ Frequently Asked Questions

How difficult is the SPLK-1005 exam and how long should I prepare?

SPLK-1005 is a solid intermediate-level certification. Candidates who already hold SPLK-1002 and understand on-premises Splunk administration typically need 3 to 5 weeks of focused study on Splunk Cloud-specific boundaries—especially Victoria vs. Classic Experience, ACS API v2, forwarder/HEC endpoints, AppInspect, DDAA/DDSS, and Federated Search.

How does SPLK-1005 differ from SPLK-1003 (Splunk Enterprise Certified Admin)?

SPLK-1003 tests on-premises infrastructure management such as server installation, SSH/CLI restarts, Deployment Server hosting, and local cluster config files. SPLK-1005 covers Splunk Cloud SaaS administration: shared responsibility, sc_admin capabilities, ACS API v2/CLI, Victoria vs. Classic, HTTPS :443 HEC, SSAI/AppInspect vetting, and DDAA/DDSS retention.

What is the difference between Victoria Experience and Classic Experience in Splunk Cloud?

Victoria Experience is Splunk Cloud's modern architecture that removes the separate Inputs Data Manager (IDM), runs modular and scripted inputs directly on the Search Head tier, automatically pushes index-time configurations from SSAI/ACS apps to indexers, and uses the apps/victoria endpoint (while disabling Web UI app downloads). Classic Experience uses a separate managed IDM and relies more heavily on Splunk Support for tier updates.

How much does the SPLK-1005 exam cost?

Splunk certification exams cost $130 USD per attempt, or $500 USD for a 5-exam bundle ($100 per exam), managed through Learn with Cisco and Pearson VUE.

How do I register for and track my SPLK-1005 certification?

Effective October 20, 2026, Splunk certifications are integrated into the Cisco Certification Tracking System under Learn with Cisco. Candidates no longer use a separate Splunk ID.

How long is SPLK-1005 valid and how do I recertify?

Splunk certifications are valid for 3 years. Coursework-based recertification has been retired — renewal requires retaking the current exam or passing a higher-level Splunk certification exam.

Should I use SPLK-1005 exam dumps, or are there free legitimate practice questions?

Avoid unauthorized SPLK-1005 PDF or braindump sites: they violate the Cisco/Splunk Candidate Agreement (risking score cancellation and certification bans) and frequently teach wrong answers. Instead, use Splunky's 100% free, original SPLK-1005 (Splunk Cloud Certified Admin) practice exam and 83+ blueprint-aligned study questions with step-by-step explanations at getsplunky.com/exam/splk-1005.

📗 Other Study Guides

SPLK-1001
Splunk Core Certified User
Everything you need to pass the Splunk Core Certified User exam — 100% free.
SPLK-1002
Splunk Core Certified Power User
Master advanced SPL and pass the Splunk Core Certified Power User exam.
SPLK-1004
Splunk Core Certified Advanced Power User
Conquer the most advanced core Splunk certification with expert-level SPL mastery.