PEOPLECERT ITIL-DSV Exam Actual Questions
ITIL 4 Specialist: Drive Stakeholder Value (Page 7 )

• IPv6 address types you’ll typically see:

• Unique Local Addresses (ULAs)

• If an address begins with fdXX:… or fc00:…, place it under “Unique Local Address” (ULA).
• If it begins with 2000::/3, place it under “Global Unicast.”
• If it begins with fe80::, place it under “Link-local.”
• If it begins with ff00::, place it under “Multicast.”

• Azure Files is an example of infrastructure as a service (IaaS). No. Azure Files is a managed storage service, typically considered PaaS (Storage as a Service), not IaaS.
• A DNS server that runs on an Azure virtual machine is an example of platform as a service (PaaS). No. Running a DNS server on a VM is IaaS because you manage the OS and DNS software.
• Microsoft Intune is an example of software as a service (SaaS). Yes. Intune is a cloud-based, fully managed service you use over the Internet.

• Windows 10 VMs
• Windows Server 2012 or later VMs
• Running VMs—they do not need to be shut down
• Debian 8.2+ VMs, assuming the specific version is supported
• Stopped or deallocated VMs

• Phishing can map to two MITRE ATT&CK tactics depending on the attacker’s objective.

• Therefore, phishing isn’t confined to a single tactic; it can serve both Reconnaissance and Initial Access, which is why option D (Reconnaissance, Initial Access) is correct.

• Goal: Identify the host that originated the infection, then label each remaining host as infected or clean based on log evidence.

• Logs to review (across hosts and firewall):

• How to identify the origin:

• How to classify other hosts:

• Quick tip: use the Reset All option if you want to re-run the scenario and practice again.

• Ablauf: Er wird in der gleichen Transaktion ausgeführt, bei der z. B. ein Datensatz erstellt oder aktualisiert wird. Der Benutzer wartet, bis der Workflow abgeschlossen ist.
• Stufen: Kann vor dem Vorgang (pre-operation) oder nach dem Vorgang (post-operation) laufen.
• Zweck: Sofortige Validierung oder Anpassung von Daten, ggf. auch das Verhindern eines Vorgangs, wenn Bedingungen nicht erfüllt sind.

• Automatisierte Flows (Power Automate, automatisierte/ Background Flows) laufen asynchron im Hintergrund, nachdem der Trigger erkannt wurde, und blockieren den Benutzer nicht.

• Correct answer: D — AWS Migration Hub

• AWS Migration Hub provides a single location to track the progress of application migrations. It offers a centralized dashboard to view migration status across multiple tools and projects.

• AWS Application Discovery Service helps inventory and map on-prem applications and their dependencies, not a single progress tracker.
• AWS Application Migration Service (formerly SMS) performs the actual lift-and-shift migrations, but isn’t the centralized tracker itself.
• AWS Service Catalog manages catalogs of IT services for self-service deployment, not migration progress.

• Basic support does not include architectural/design assessments.
• Premier support includes advisory services such as architectural reviews/design assessments.

• The solution (subscribe to Premier support) does meet the goal. The correct choice should be Yes (A).
• The provided answer key showing B (No) is likely incorrect for current Azure support plans.

• Global Unicast: These are the IPv6 addresses that are globally routable on the Internet. They’re allocated by Regional Internet Registries (RIRs) and can be reached from anywhere with proper routing (similar to IPv4 public addresses). Example ranges include 2000::/3.

• Link-local: fe80::/10. Used only on the local link; not routable beyond the directly connected network.

• Unique Local Addresses (ULA): fc00::/7. Private addresses for internal use within an organization; not publicly routable on the Internet (like IPv4 private addresses).

• Multicast: ff00::/8. One-to-many addresses used for group communication, not unicast routing.

• A) configure matching hold and delay timers

• B) configure matching key-strings

• C) configure matching priority values

• D) configure unique virtual IP addresses

• Developed and maintained independently
• Deployed without changing the entire application
• Scaled separately based on demand
• More resilient when another service has problems

• A: Functional testing is useful, but it is not the main practice described.
• B: Automation helps deployment, but the scenario focuses on architectural decomposition.
• C: Multiple locations improve availability, not application modularity.

• Answer: False. Agents and managers CAN create knowledge articles from Community questions.

• Why: In ServiceNow, a Community question can be converted into a Knowledge article using the Create Knowledge (or Convert to Knowledge) action. This allows what customers asked to become a reusable article for others.

• How it works (high level):

• Permissions: This ability depends on having the right roles/permissions (e.g., agents or knowledge managers). If you don’t see the option, check your role assignments or the knowledge-management configuration.

• Quick take: If a question in Community is valuable for others, a trained agent can turn it into a Knowledge article, making it available for self-service.

• The question asks why some tasks appear locked in the HR Guided Setup Module’s Task view.
• The options are:

• C) They require other tasks to be completed first. In guided setup flows, tasks are usually gated by prerequisites to ensure proper sequencing and data/configuration dependencies. You typically unlock a task only after the necessary preceding tasks are finished.

• A) Elevated roles can restrict access in some contexts, but guided setup tasks are commonly gated by prerequisites rather than solely by role.
• B) Deprecation isn’t the general pattern for “locked” tasks in the guided setup.
• D) A plugin activation could unlock certain features, but the common gating mechanism is task dependencies, not plugin state.

• The page shows the answer as D, but based on how HR Guided Setup usually works, the more accurate reason is typically C (prerequisites). If you’re studying, treat C as the conceptual answer and be aware the listed key may be incorrect. If you want, I can walk through each option in more detail.

• prompt: the input or instruction given to the model
• completion: the desired response

json 
{"prompt":"Summarize this customer complaint.","completion":"The customer reports a delayed shipment."}

• B: A .txt file containing CSV-style lines is not automatically a valid fine-tuning dataset. The required structure and format must match the selected Bedrock model.
• C: Provisioned Throughput provides dedicated inference capacity; it does not fine-tune a model.
• D: Journals and textbooks might support domain adaptation or pretraining, but they do not provide the prompt-to-answer examples typically required for supervised fine-tuning.

• Context: You’ve enabled auditing in Dataverse and need to trim audit data to free storage. The question asks which deletion options you can use.

• What the options typically mean:

• About the provided answer (A, C, D): The list includes “by column,” which isn’t a typical or supported way to purge audit data. The more plausible trio is A (by record), B (date range), and C (by table older than date). If the exam expects A, C, D, that seems incorrect or mis-stated in the source.

• Practical takeaway: To reduce audit storage, use per-record deletions, per-table purge by date, and/or date-range deletions as supported by the environment’s audit management UI or admin docs.

• What the question asks: Identify the three types of tolerances used in accounting (in SAP FI) for automatic processing and postings.

• The given correct set (A, C, D) corresponds to:

• Why not B (Special account tolerance groups)? “Special account tolerance groups” is not a standard SAP term for tolerance groups. The common categories above are the ones SAP typically uses for automatic postings and clearings.

• Quick tip: Tolerance groups define the maximum allowed difference; if a difference exceeds the limit, manual intervention is required.

• Create Power Query parameters for the Azure SQL server/database—or at least the database name.
• Use the parameter in the PBIX connection.
• Publish the same PBIX separately to the relevant development, test, and production workspaces.
• Set each dataset’s parameter value in the Power BI service so it points to the corresponding Azure SQL database.

• Development dataset ? DevelopmentDB
• Test dataset ? TestDB
• Production dataset ? ProductionDB

• The same PBIX is used for every lifecycle stage.
• Each stage consumes data from its matching database.
• Deployment pipelines are not required.
• Azure SQL is a cloud source, so gateway administration is generally avoided.
• Only the parameter value differs between published datasets, reducing maintenance.

• Context: You’re configuring a Windows Autopilot deployment profile (Profile1) for Windows 11 devices. The hotspot asks you to pick the correct behavior for two statements based on the profile’s settings.

• Box 1: “can modify the desktop settings only for themselves”

• Box 2: “Cortana settings” with options like computer name, keyboard layout, etc.

• Box 1: Azure Lighthouse — ??? ??????? ? ?????????? ????????? ? ?????????? Entra tenants. ??? ??????????? ??? ??? ????? ????? ? VM ? ?????? ?????????/????????.
• Box 2: Azure Monitor Agent ? ?????????????? Data Collection Rules (DCR) — AMA ???????? ??????? Windows (????????, Security Logs) ? DCR ??????????, ????? ??????? ???????? ? ???? ?????????? (? ?????? Log Analytics workspace).

• A — SCIM synchronizes changes to user attributes from the identity provider to GitHub.
• B — SCIM deactivates GitHub accounts when users are removed or deactivated in the identity provider.
• D — SCIM automates user provisioning when new users are added to the identity provider.

• C: SCIM does not delete organization repositories.
• E: SCIM does not generate REST API authentication tokens.
• F: SCIM handles identity lifecycle management, not repository permission configuration based on roles.

• The requirement: SQL authentication cannot be used for any databases on Server1, and the solution must be enforced centrally at the server level.
• Correct choice (C): Enable Microsoft Entra-only authentication for Server1.

• Why not the others:

• 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.

• A Storage Gateway File Gateway provides an on-premises NFS/SMB file share that's backed by objects in S3. This is exactly what you need to migrate an NFS workload: applications continue using NFS, while the actual data moves to and is stored in S3.
• It can cache frequently accessed data locally for performance, while uploads go to an S3 bucket.
• Why the other options aren’t suitable:

• SageMaker endpoint: Not required because the model is being used through Amazon Bedrock.
• SageMaker Model Registry: Used for managing SageMaker models, not for making a Bedrock custom model available.
• Grant access in Amazon Bedrock: IAM permissions may still be needed, but granting access alone does not provide the required inference capacity.

• Correct answer: B — A reservation for the server based on the MAC address.

• Why this is the best choice:

• Why the other options are less suitable:

• Quick takeaway: Use a DHCP reservation to give the file server a fixed IP while still benefiting from centralized DHCP management.

• Recovery procedures actually work
• Recovery time and recovery point objectives can be met
• Staff understand their responsibilities
• Contact details, dependencies, and technical configurations are accurate
• Gaps or conflicts exist in the plan

• Not version-controlled: Creates a risk of using an outdated copy, but the plan might still be effective.
• Contact information needs updating: This is a specific weakness that can be corrected, often identified during testing.
• Not approved by senior management: Approval is important for authority and resource commitment, but an untested plan presents the most direct risk that recovery will fail when needed.

• Alice is co-resident on the same physical host and exploits shared hardware (the processor cache) to infer secrets. This is the classic definition of a side-channel attack—information leakage through implementation details (like timing or cache behavior) rather than by breaking a protocol or injecting code.

• Observing cache timing or access patterns to deduce cryptographic keys or plaintext data from the victim VM.

• Man-in-the-cloud attack: targets cloud trust/auth, not local hardware sharing.
• SQL injection: exploits input to run SQL commands, not a VM/caching vector.
• Service hijacking: takes control of a service, not about covert data leakage via shared hardware.

• Notice phrases like “shared hardware resources,” “co-resident,” or “cache”—these indicate a side-channel vector.

• Control plane: Managed by Databricks and contains the Databricks web application, workspace services, cluster management, and job orchestration.
• Data plane: Runs in your cloud account and contains compute resources such as:

• Worker node: Data plane compute.
• Driver node: Data plane compute.
• JDBC data source: Usually an external data system.
• Databricks Filesystem (DBFS): Provides storage access and is backed by cloud object storage rather than being entirely part of the control plane.

1. Define Power Platform DLP policies
2. Add custom prompt modifications
3. Conduct adversarial testing

1. DLP policies first

1. Prompt modifications second

1. Adversarial testing last

• runParallel is defined as async, so it returns a Promise.
• To use the result, you attach a then handler (or use await inside another async function).

• A: “Async runParallel() .then(data);” is invalid. “async” is a keyword for function declarations, not something you put in front of a call, and you’d need a function as the then-argument.
• B: “runParallel().done(function(data){return data;});” .done is not standard in native Promises (it exists in some libraries). Without a compatible library, this won’t work.
• C: “runParallel().then(data);” is invalid because then expects a function as its argument; data is not a function.
• D: “runParallel().then(function(data){ return data; });” is valid (or equivalently, runParallel().then(data => data);).

• The robust, standard option is D.
• B could work only with a library that provides .done; otherwise it’s not reliable.

• Answer: No.

• Why:

• If you need such an assessment while controlling costs, you’d generally pursue a paid MCS engagement or another option outside of the basic Premier entitlement.

• In Microsoft Teams Phone System, a single Auto Attendant can handle multiple time-based greetings by using separate schedules for office hours, after hours, weekends, and holidays.
• You can configure one Auto Attendant with four distinct greetings mapped to:

• Open the Teams admin center > Voice > Auto attendants, edit or create an Auto Attendant.
• Under Time-based routing, define four rules:

• Create a Holiday schedule with the relevant dates (e.g., Easter, Christmas) and assign the Holiday greeting.
• Save the configuration.

• If your environment cannot separate weekend from after-hours within a single Auto Attendant, you might technically need more than one Auto Attendant.

• The app on EC2 connects to Aurora using DB credentials stored on the instance. Secrets Manager centralizes these credentials and can rotate them automatically, eliminating manual updates on each EC2 host.
• Automatic rotation reduces operational overhead and enhances security because credentials are rotated on a schedule without code changes.
• The app can retrieve the current secret at runtime (e.g., via the AWS SDK) and use it to authenticate to Aurora, avoiding reliance on locally stored files.

• B (Parameter Store) can store secrets but lacks seamless built-in rotation for database credentials like Secrets Manager; rotation often requires more custom work.
• C (S3) would require complex tooling to rotate and securely fetch credentials and still risks exposure if access policies aren’t perfect.
• D (Encrypted EBS volumes) would store credentials locally on each instance and does not automate rotation or centralized management.

• Improve QA testing efficiency: A prototype may help discover defects early, but that is not its greatest benefit.
• Decrease time allocated for user testing and review: Prototyping usually requires additional user involvement and review, not less.
• Minimize scope changes: Prototypes can actually reveal new requirements or cause scope changes. However, discovering those changes early is beneficial.

• Answer: D: Making business cases for improvement action

• Continual Improvement focuses on identifying and planning improvements and ensuring they’re funded and prioritized. Creating a business case for an improvement action is part of justifying and obtaining support/resources to implement improvements.
• A (Identifying the cause of incidents) aligns with Problem Management.
• B (Authorizing changes) aligns with Change Enablement.
• C (Logging/managing incidents that result in improvement opportunities) aligns with Incident Management, not Continual Improvement.

• The Act requires:

• It does not, as a public obligation, mandate publishing a detailed report on the training data used.
• Also, the Act does not specify a fixed “six months” retention for system logs in a way that would clearly make A required; logs for traceability are implied, but the six-month period is not a defined, universal requirement.

• The requirement: the support plan must allow opening new support requests (technical support incidents).
• Azure’s Basic plan does not include technical support incidents—only billing/subscription support and access to community support.
• Therefore, you must choose a paid plan to open new technical support requests: Developer, Standard, Professional Direct, or Premier.

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

• Azure Resource Manager templates: Use ARM templates to define the VM infrastructure and baseline configuration as code. This ensures all Windows Server 2016 VMs are created with a uniform setup, minimizing manual configuration.

• PowerShell Desired State Configuration (DSC) extension for Windows: DSC enforces a defined state across all servers and can automatically remediate drift. This keeps the VMs in the desired configuration with minimal ongoing admin effort.

• Network Security Groups (NSGs) control network traffic to and from Azure resources.
• By applying NSGs to the web tier and the database tier (subnets or NICs), you can:

• NSGs provide the necessary granularity (source/destination, port, protocol) to enforce the desired traffic patterns between tiers.
• For easier management you can use separate subnets for each tier or, optionally, use Application Security Groups to simplify rule management.

• Answer: Record Producer (option D)

• Why: In ServiceNow HR Service Delivery, to make an HR Service usable from the Employee Service Center (self-service portal), there must be a way for employees to submit the request. A Record Producer provides the employee-facing form that creates the underlying HR Case when submitted. Without a linked Record Producer, the HR Service wouldn’t offer a submit form in the Employee Center.

• What the other fields are generally for (not required for exposure):

• Quick check: Look at the HR Service definition and ensure a Record Producer is associated so employees can submit requests from the Employee Center.

• A private IP address on the virtual network
• An associated public IP address

• Basic: billing/subscription support only; no technical support requests can be opened.
• Developer, Standard, Professional Direct, and Premier: include technical support and allow opening new support requests.

• If option A corresponds to “Developer, Standard, Professional Direct, Premier,” that is the correct choice.
• If the option text is really “Premier only,” that would be incorrect per current Azure docs.

• RPO (Recovery Point Objective) — maximum acceptable data loss, measured in time. It specifies how far back in time you can tolerate data loss. Example: RPO of 2 hours means backups must occur at least every 2 hours.

• ARO (Annualized Rate of Occurrence) — expected frequency of a threat occurring per year. It estimates how often a risk is likely to happen on average (used in risk calculations).

• MTTR (Mean Time To Recover) — average time to recover/restore service after an incident. It includes detection, repair, and restoration time, and helps gauge downtime and alignment with RTO.

• Correct options: C and D.

• The AWS Cloud Adoption Framework (CAF) security perspective focuses on capabilities to protect information and manage security risk.
• Observability (A) is primarily an operations/monitoring capability, not a core security capability under CAF.
• Incident and problem management (B) is IT service management/operations, not specifically a CAF security capability.
• Incident response (C) is a security-focused capability: detecting, containing, and recovering from security incidents.
• Infrastructure protection (D) involves applying security controls to protect the underlying infrastructure, which fits the security perspective.

• A limited lifetime
• Permissions defined by an IAM role or policy
• The ability to access AWS APIs without using long-term IAM user credentials

• Amazon API Gateway — Builds and manages APIs; it does not generally issue AWS credentials for applications.
• IAM users — Usually use long-term credentials, which are less suitable for applications.
• IAM instance profiles — Provide temporary role credentials to applications running on EC2 instances, but are specifically tied to EC2. The broader requirement described is best met by AWS STS.

cmd 
powershell.exe -ExecutionPolicy Bypass -File C:\Scripts\Configure-VM.ps1

• GPO logon script: Runs only when a user logs on, so configuration may be delayed and is user-dependent.
• GPO startup script: Can work, but requires the VMs to be domain-joined and introduces GPO dependency. It is not specifically tied to Windows deployment.
• Place scripts in a VHD: Merely makes the files available; it does not execute them.

Why B works

• AWS KMS keys are Regional resources. A normal customer managed key in Region A cannot be used directly in Region B.
• A customer managed multi-Region KMS key (MRK) has related key replicas in both Regions. The replicas share key material and key ID, although each has a Regional ARN.
• With client-side encryption, the application encrypts the data before storing it in S3. Cross-Region replication then copies already-encrypted objects, so S3 does not need to decrypt and re-encrypt them with a different Regional key.

Why the other choices are weaker

• A and C: SSE-S3 uses Amazon-managed S3 keys, not the required customer managed KMS key.
• D: SSE-KMS can work only if the solution creates and configures the appropriate KMS key or multi-Region key replica in each Region. As written, it says to create a customer managed KMS key in each Region, which implies separate keys—not the same KMS key. Replication also requires additional KMS permissions and destination encryption configuration.

• Correct answer: C: Amazon Comprehend.

• Why: The library wants to classify books based on their text content. This is an NLP (natural language processing) task. Amazon Comprehend is AWS’s managed NLP service that can perform content classification (including creating custom classifiers) and extract meaningful information from text. The other services are not focused on text classification:

• Quick note: In practice, you’d store the books in S3, extract text if needed (e.g., from PDFs with Textract), and then use Comprehend to classify the documents into topics or genres.

• The 99.99% availability SLA for VMs is achieved when you run VMs across two or more Availability Zones.
• Two VMs in a single Availability Zone do not meet the 99.99% target (their SLA is lower, e.g., around 99.95% or less depending on configuration).

• Deploy at least two VMs across two different Availability Zones (one VM in each zone, or both in two zones with a load balancer).
• This provides the required zone redundancy and the 99.99% SLA.