Splunk SPLK-1003 Exam Prep
Splunk Enterprise Certified Admin (Page 11 )

• What the scenario tests: How monitoring paths on a Universal Forwarder (UF) behave when you deploy an app via the Deployment Server.
• How monitoring is configured: Log paths to monitor are defined in inputs.conf (within apps/local on the UF). Splunk on the UF merges inputs from all apps and local config.
• Key point: Deploying a new app that adds a monitor for a log file does not typically remove existing monitors. The UF will continue monitoring any previously configured paths and will add the new ones from the deployed app.

• Correct answer: C) /var/log/maillog and /var/log/messages.

• Step 1: From Power BI Desktop, select Get Data, choose Folder, enter the folder path, and click OK, then choose Transform data to open Power Query Editor.

• Step 2: In Power Query Editor, expand the Attributes column.

• Step 3: From the Power Query Editor, select the Content column and use Home > Combine Files (aka “Combine binaries”) to consolidate the files.

• Copilot??????????
• ???????????????
• ??????????
• ?????????????
• ???????????????????

• Prompts and Suggestions: Retained for 28 days
• User Engagement Data: Kept for Two Years

• Manage multiple organizations from one hierarchy.
• Enterprise-wide policies, including repository visibility, forking, and GitHub Copilot policies.
• Centralized identity and access management, such as SAML SSO, SCIM provisioning, and—where applicable—Enterprise Managed Users.
• Centralized billing and licensing, including organization and Copilot seat management.
• Enterprise audit log, which aggregates activity across organizations.
• Security and compliance oversight, such as organization security visibility and enterprise-wide controls.
• Enterprise support and account management features, depending on the plan.

• Organization: manages its own repositories, teams, members, and local policies.
• Enterprise: governs multiple organizations and can enforce policies across them.

• The AWS Support Concierge is a specialized team within Enterprise Support whose primary role is handling billing and account questions and helping with account setup and getting started.
• They are not the source for architecture guidance or development assistance; those services are provided by Technical Account Managers (TAMs) or Solutions Architects as part of Enterprise Support.
• For technical support cases, customers typically interact with AWS Support engineers or the TAMs, not the Concierge. The Concierge may route or coordinate related requests, but they don’t provide the technical resolution.

• What Concierge does: billing and account inquiries, onboarding help, coordination with AWS support.
• What Concierge does not do: provide architecture/design guidance or in-depth technical support case resolutions.

• The mapping and resolution of endpoint identities (EIDs) to their location (RLOCs) in an SD-Access fabric is handled by the control plane using the LISP protocol.
• Why not the others:

• Leadership and stakeholder commitment
• Business capability and skills
• Organizational culture
• Availability of resources
• Ability to manage and sustain change
• Impact of the proposed transformation

• How ready the organization is
• Which areas require urgent attention
• How difficult each issue may be to resolve
• Risks that could affect implementation

• A: Places the assessment in Phase B and refers vaguely to creating views; this is not the prescribed technique.
• B: An Implementation Factor Assessment and Deduction Matrix is not the primary TOGAF technique described for business transformation readiness.
• D: A Business Scenario helps identify requirements and stakeholder concerns, but it is not the main technique for assessing organizational readiness.

• Amazon Cognito is designed for customer-facing apps to handle user sign-up, sign-in, and access control, and it can federate identities from social providers (Facebook, Google, etc.) or enterprise IdPs via SAML/OpenID Connect.
• You can configure a Cognito User Pool and connect social identity providers, then use tokens (JWT) to authorize backend API calls.

• AWS Directory Service is for connecting your AWS apps to an existing directory (like Active Directory) for enterprise users, not social login for customer apps.
• AWS IAM is for managing access to AWS resources, not end-user authentication for your website.
• AWS IAM Identity Center (AWS SSO) provides SSO for AWS accounts and enterprise apps, not typical social logins for consumer-facing websites.

• In the source query: apply UPPER() or LOWER() to the column.
• In Power Query Editor: use Text.Upper or Text.Lower on the column, then load.

• This fixes the root cause when comparisons/joins depend on case.
• In DirectQuery, transformations are pushed to the source or query layer; ensure the transformation is supported by your data source/connector.
• After normalization, verify relationships and any downstream visuals that rely on that column.

• Correct answer: B (No, it does not).

• A purchase agreement in Dynamics 365 SCM is a vendor-side price arrangement. It sets prices/discounts for what your company buys from suppliers, not for what you sell to customers.
• The objective in Question 2 is to give clients a quantity-based discount on items they purchase from you. To accomplish this, you should configure a sales price / trade agreement (on the customer/sales side), not a purchase agreement.
• In a sales price trade agreement, you can define quantity breaks such as:

• Create a Sales price trade agreement for the item and relevant customer (or customer group).
• Add quantity breaks: 51–100 with 10% discount, 101+ with 15% discount.
• Ensure the agreement is active for the desired date range.

• On-Demand: You pay by the hour with no long-term commitment. This is ideal for workloads that are infrequent or have highly variable usage. Since this job runs only 24 hours once per year, you pay only for those 24 hours, with no wasted upfront or long-term payments.
• Reserved Instances: Require a 1- or 3-year commitment and pay for capacity whether you use it or not. For a workload that runs just 24 hours a year, you’d be paying for most of the term unused, making it far less cost-efficient.
• Spot Instances: Can be interrupted whenever AWS needs capacity, which is unacceptable for an uninterruptible workload.
• Dedicated Instances: Generally more expensive and aimed at licensing or compliance requirements; not needed for this use case.

• Detect risky sign-ins from unfamiliar or unidentified IP addresses
• Evaluate user or sign-in risk
• Automatically require a password change because of a risky sign-in

• User risk policy: Can require a user to securely change their password when the account may be compromised.
• Sign-in risk policy: Can require MFA or block access based on the risk of a particular sign-in.

• As the project progresses, you gain information, refine requirements, and lock down baselines (scope, schedule, cost). This reduces overall risk and uncertainty because more is known and addressed.
• At the same time, changes become more costly over time. Later changes can affect already approved baselines, cause rework, impact the critical path, require more coordination, and incur penalties or delays, all of which raise the cost of making changes.

• AWS Audit Manager continuously collects evidence from AWS services and helps assess whether workloads comply with regulatory frameworks and internal policies. It can produce audit-ready reports.
• AWS Config records resource configurations and evaluates them against compliance rules. For example, it can check whether encryption, logging, or access settings meet company requirements.

• Amazon Inspector identifies software vulnerabilities and unintended network exposure, not general policy or regulatory compliance.
• Amazon CloudWatch monitors metrics, logs, and operational events, but is not primarily a compliance assessment service.
• AWS CloudTrail records API activity for auditing and investigation. It supports compliance, but does not itself provide the structured compliance assessment capabilities of Audit Manager and Config.

• Answer: C – netstat -an

• netstat -an lists all active connections and listening ports with numeric addresses, without resolving names. This lets you spot DoS patterns such as a flood of connections to a specific port or many connections from a single or few IPs.
• The other options don’t help as directly:

• Windows: netstat -an and look for numerous ESTABLISHED connections to a service or many SYNs to a port.
• Filter by port, e.g., netstat -an | findstr :80, or on Linux: ss -tunap | grep ':80'.

• Netstat provides a snapshot. DoS detection often benefits from continuous monitoring, flow data, and IDS/IPS logs.

• The two correct options are:

• The two incorrect options:

• Correct answer: C. AWS CloudFormation

• Why: CloudFormation lets you define infrastructure as code via templates (JSON or YAML). You can create a single template that describes multiple AWS resources and reuse it to deploy consistent stacks across environments. Templates can be parameterized and stored for repeated deployments. Other options (Marketplace, AMI, OpsWorks) don’t provide reusable deployment templates in the same way.

• Admin access to the deployment pipeline (B) – lets the developers use the pipeline and deploy content.
• Contributor access to the Development and Test workspaces (E) – required to deploy items into those workspaces.
• Viewer access to the Production workspace (D) – lets them view Production content without allowing deployment or modification.

• Contributor access to Production (F), because that could allow changes or deployment there.
• Viewer access to Development/Test (C), because Viewer is insufficient for deployment.
• Build permission to Production semantic models (A), because building reports on a semantic model is not required merely to view Production items.

• A: True. You can change the size of a Virtual Warehouse after creation (via UI or ALTER WAREHOUSE).

• B: True. A warehouse can be resized while it’s running; the resize will take effect without needing to stop queries.

• C: True. A warehouse can be configured to suspend after a period of inactivity (AUTO_SUSPEND).

• D: True. A warehouse can be configured to auto-resume when new queries are submitted (AUTO_RESUME).

• Key difference: DirectQuery leaves data in the on-prem SQL Server and queries it live. That means every visual request can trigger online processing on the source, which can be slower and adds load on the on-prem system. In contrast, Import loads data into the Power BI data model, so visuals render from the in-memory engine (faster).

• Why that helps with the requirements:

• Why not A or B: Both rely on live data via DirectQuery, which contradicts the goal to minimize online processing and visuals performance.

• Why not D: It uses Import, but refreshing hourly adds unnecessary processing and complexity when daily refresh already satisfies currency needs.

• You provision the virtual machine.
• You manage the guest operating system, applications, and configuration.
• Azure manages the physical servers, datacenter, and underlying virtualization infrastructure.

• Topic: Conditional Access (CA) policy and MFA for Azure management.
• Policy name: Policy1, created with the template “Require multifactor authentication for Azure management.”
• What the template does: It enforces MFA when signing in to manage Azure resources (Azure management) for the users included in the policy.
• Who is included: The question lists Admin1, Admin2, Admin3, and Admin4 as the admins in the tenant. The template’s default scope for this scenario is to apply to those admin accounts (i.e., all four admins unless you explicitly limit the scope).

• CA policy for “Azure management” targets admin sign-ins.
• If the policy includes Admin1–Admin4, all of them must use MFA on their next sign-in (choice D).

• IPsec: Protects traffic at the network layer, commonly for VPNs; it is not WPA2’s authentication protocol.
• SSL: Protects specific application sessions and has largely been replaced by TLS.
• SSH: Secures remote command-line administration.

• Correct answer: A) Hashing

• Why: Hashing produces a fixed-size digest of the software. If the final build is altered in any way, the hash will change, enabling you to detect tampering by comparing the stored digest with a freshly computed one.

• Why not the others:

• Correct choices: A and D.

• Why not B, C, or E?

• Disabling GPS: Affects location services, not email connectivity.
• Configuring 4G usage only: Does not enable international data access and could prevent connectivity if 4G is unavailable.
• Connecting using a hotspot: Could provide data, but it is not the most direct solution and depends on another network or device.

1. Ingestion Lambda receives requests from API Gateway and places messages in an SQS queue.
2. Processing Lambda is triggered by the queue and loads records into Aurora PostgreSQL.

• Decoupling: API request handling is separated from database loading.
• Buffering: SQS absorbs bursts when incoming traffic exceeds the database’s processing capacity.
• Controlled concurrency: Configure the SQS-triggered Lambda’s concurrency and batch size to avoid overwhelming Aurora or exhausting database connections.
• Automatic retries: Messages that fail processing can return to the queue and be retried. A dead-letter queue can capture persistent failures.
• Lower operational effort: The solution remains serverless and avoids managing EC2 servers or Kubernetes clusters.

• A: EC2 and Tomcat add server-management overhead.
• B: DynamoDB/DAX would require changing the database model and does not solve the Aurora ingestion design.
• C: SNS is useful for notifications and fanout, but SQS is better for durable buffering and backpressure in this producer-consumer workflow.

• Statement 1: Admin1 must approve requests for the Agent ID Developer role — No

• Statement 2: Admin2 can approve requests for the AI Administrator role — No

• Statement 3: Admin3 can assign User1 a two-day active assignment for the Agent ID Developer role — Yes

• Answer: Internal load balancers (ILB) — option C.

• An ILB has a frontend IP address that must be a private IP within the subnet’s address space. You pick this IP when you create the ILB, and it can be Static or Dynamic.
• Other options don’t require a per-subnet IP:

• Two VMs
• Distributed across two separate availability zones

• Answer: A. Use Amazon SageMaker Serverless Inference to deploy the model.

• Why: SageMaker Serverless Inference hosts the model and serves real-time predictions without you provisioning or managing servers. It scales automatically and handles deployment details.

• Why the others aren’t suitable:

• Quick example flow: web app ? SageMaker Serverless Inference endpoint ? model ? response.

• Incidents & alerts — see how the phishing activity was detected, correlated, and investigated.
• Threat Explorer — search for the malicious messages, recipients, URLs, attachments, and campaign activity.
• Email and collaboration reports — assess how many users or messages were affected.
• Remediation details — verify whether messages were quarantined, removed, or otherwise contained.

• Microsoft 365 admin center — general tenant administration.
• Microsoft Entra admin center — identity and access management.
• Exchange admin center — mail-flow and Exchange configuration, rather than full phishing-incident investigation.

• Why Ishikawa:

• Why not the others:

• In the AWS shared responsibility model, AWS manages the security of the “infrastructure,” including the physical hardware and underlying virtualization.
• The customer is responsible for everything else in the cloud stack: the guest OS on EC2, the NoSQL database software running on it, data, patching the OS, and configuring access controls like security groups.
• So, for a self-managed NoSQL database on EC2, AWS would handle the physical hardware, while you would patch the guest OS and manage DB availability, backups, and security.

• Replace the keyboard: More expensive and unnecessary before simpler causes are ruled out.
• Replace the key switch: Laptop keyboards generally aren’t designed for individual switch replacement.
• Replace the circuit board: Excessive for a single nonworking key and not a cost-effective first step.

python 
def add_integers(a, b): 
    return a + b

• Uses def to define a function.
• Accepts two parameters, a and b.
• Uses return to send their sum back to the caller.
• Uses indentation to define the function body.

python 
result = add_integers(3, 4) 
result is 7

• S3 Lifecycle rules automate actions such as transitioning objects to different storage classes or deleting old objects.
• S3 bucket policies control access permissions; they do not preserve earlier object versions.
• S3 server-side encryption protects data confidentiality by encrypting objects at rest, but it does not prevent deletion or overwriting.

• Accidental deletion or overwriting ? S3 Versioning
• Unauthorized access ? bucket policies and IAM
• Data encryption ? server-side encryption

• Answer: Data enhancement.

• Why: Augmenting gold-layer tables with an additional dataset is enriching or enhancing the existing data to support the ad-hoc analysis. The other options don’t capture the idea of adding external data to improve the dataset (ad-hoc improvements = tweaks, last-mile dashboarding = building dashboards, last-mile ETL = ETL steps at the end of the pipeline). In practice, this is often also called data enrichment.

• The correct answer is D: All of the above.

• Snowflake Web Interface (UI): You can create and manage Virtual Warehouses from the UI (resize, suspend/resume settings, etc.).
• SQL commands: You can create and alter warehouses with DDL like CREATE WAREHOUSE and ALTER WAREHOUSE.
• Data integration tools: ETL/ELT tools can create/manage warehouses by connecting to Snowflake and issuing the appropriate commands or using their config to specify a warehouse.

• A private IP address on the virtual network
• A public IP address associated with its IP configuration

python 
import azure.cognitiveservices.speech as speechsdk 


speech_config = speechsdk.SpeechConfig( 
    subscription="YOUR_KEY", 
    region="YOUR_REGION" 
)

Important Azure Speech SDK classes

• SpeechConfig

• AudioConfig

python 
  audio_config = speechsdk.audio.AudioConfig( 
      use_default_microphone=True 
  )

• SpeechRecognizer

python 
  recognizer = speechsdk.SpeechRecognizer( 
      speech_config=speech_config, 
      audio_config=audio_config 
  )

• SpeechSynthesizer

• AudioOutputConfig

 Bogotá, Colombia