PMI DASM Exam Prep
Disciplined Agile Scrum Master (Page 5 )

Why this is correct

• Each user authenticates with their own Google account.
• Google manages the user’s SSH key association.
• IAM controls who can access instances.
• Access can be audited by user identity, so security can determine who accessed a VM.
• Granting the role to a Google group avoids managing permissions individually.

Why the others don’t apply

• A: A shared private key is difficult to distribute securely and cannot reliably identify which employee used it.
• B: Manually collecting and deploying keys on every instance is operationally inefficient and complicates auditing.
• D: A project-wide shared key has the same identity and key-management problems as option A. It also does not provide per-user accountability.

1. Discovery tries the SSH probe first.
2. SSH fails.
3. Discovery tries SNMP, which succeeds.
4. Discovery records SNMP as the preferred service for that IP.
5. Future discoveries try SNMP first.

• Classification identifies the type of device, such as a server, router, or printer.
• Credential affinity remembers which credentials work for a device.
• MID Server affinity associates a device or network with a particular MID Server.
• IP service affinity specifically controls the preferred discovery protocol or service.

• Self-signed certificate: Causes a browser security warning, not incorrect name resolution.
• Nameserver record: A DNS problem would typically affect multiple users, not just one workstation.
• IP helper: Relays services such as DHCP across network segments; it does not resolve website names.

• Disable high concurrency: Changes workspace-wide behavior and is not the targeted way to isolate these workloads.
• Modify the number of executors: Adjusts capacity and performance, but does not provide workload isolation.
• Set the default environment: Controls libraries and runtime configuration, not compute isolation.

• The listener uses a virtual IP address shared by the availability-group replicas.
• Floating IP, also called Direct Server Return (DSR), allows the SQL Server nodes to respond using the listener’s IP address rather than their individual VM IP addresses.
• This is required for the availability-group listener to function correctly with an Azure internal load balancer.

CIMA P3 topics

• IT governance and systems strategy
• Systems development and implementation
• Change and project governance
• Strategic and business risk

• A — Plan for new systems: The committee should help identify and prioritise systems requirements and ensure planned systems support organisational needs.
• D — Consider competitive issues: New information systems may affect Y’s competitive position, service quality and efficiency. These strategic implications should be considered.
• E — Ensure the system meets company goals: This is a key governance responsibility. The committee should ensure the project remains aligned with Y’s objectives and delivers business value.

• B — Develop new systems: Detailed system development should be performed by IT specialists and project teams, not the steering committee.
• C — Manage the project: The project manager should handle day-to-day project management. The steering committee should provide oversight, challenge and key decisions, rather than manage daily activities.

• Third-party attestation: Provides independent confirmation, often for formal compliance reporting, but is not usually performed frequently.
• Penetration testing: Attempts to exploit vulnerabilities; it focuses on technical security, not overall compliance procedures.
• Vulnerability scans: Identify known technical weaknesses in systems, but do not evaluate whether policies and processes meet compliance requirements.

• Job compute isolates production pipelines from interactive development and terminates after the job completes.
• Autoscaling adds and removes workers during telemetry spikes, directly addressing bursty workloads.
• Photon can improve performance and reduce processing time, but it does not provide autoscaling, schema-drift handling, or exactly-once processing by itself.

• A — Shared compute: violates production isolation and can allow development workloads to affect ingestion.
• C — Larger fixed cluster: may improve capacity but cannot adapt efficiently to changing workloads.
• D — Disable autoscaling: directly conflicts with the requirement to handle telemetry spikes.

• Defender for Servers is the Defender for Cloud plan that protects Azure VMs and generates security alerts that can be reviewed in Defender for Cloud.
• Azure Diagnostics extension collects guest OS monitoring data, but it does not onboard VMs to Defender for Cloud or provide Defender security alerts.
• Data connectors are used for Sentinel integrations.
• Azure Storage Analytics and workflow automation do not provide VM protection.

• A — Capacity: The system must handle all current records and anticipated future records. A system that cannot cope with volume will quickly become ineffective.
• C — Accuracy: Academic records are critical, so the new system must be at least as accurate as the existing system and comparable systems. Poor accuracy could cause serious administrative and reputational problems.
• D — Integration: Linking with the university’s financial systems supports consistency and avoids duplicate data entry, especially for registration, deregistration and fee-related transactions.

• B — Parallel running: This is a useful implementation and risk-control technique, but it is not an essential feature of the system itself. It may also be expensive and time-consuming.
• E — Internet access for all information: This creates significant confidentiality and security risks. External access might be needed for selected services, but unrestricted access to all information is not essential and would be inappropriate for student records.

• A. Remove rows where Sales[Status] is Canceled

• E. Remove Sales[Canceled Date]

• B: Removing Sales_Date would remove information users need—the date portion.
• C: Changing Delivery_Time to Integer could alter its meaning or precision and is not necessarily safe.
• D: Splitting the date/time column creates additional columns rather than simply removing unnecessary data.

• Initial Intrusion: The compromised VPN account and stolen phishing credentials describe how the attacker first gained access, but that happened months earlier.
• Persistence: The scheduled tasks and recurring C2 connections show how the attacker maintained and automated continued access.
• Search and Exfiltration: This would involve locating and transferring data. The scenario does not primarily describe data discovery or theft.
• Cleanup: Cleanup involves removing evidence or covering tracks. Obfuscated scripts may make detection harder, but the main behavior here is maintaining access.

• Relationship cardinality:

• Filter direction:

• Active versus inactive relationships: only active relationships automatically propagate filters.
• Blank or unmatched values: a fact-table value without a matching dimension row can create the model’s blank/unknown member.
• Uniqueness: the “one” side must contain unique values; duplicate keys generally belong on the “many” side.

• Liability accounts (2000–2999) would incorrectly require dimensions, although they should have none.
• Expense accounts (6000–6998) would incorrectly require Customer, which should be optional.
• Account 6999 needs a separate rule because it requires all four dimensions, including Customer.

• 2000–2999: no dimensions
• 4000–4999: Department and Division required; Project and Customer optional
• 6000–6998: Department, Division, and Project required; Customer optional
• 6999: Department, Division, Project, and Customer required

• UPS battery-backed outlets: Connect only essential devices needed during an outage:

• Surge-protector-only outlets: Connect nonessential devices, especially the printer. Printing does not need to continue while you are saving work and shutting down.
• UPS power source: Plug the UPS directly into a wall outlet.
• Surge protector power source: Plug it directly into a wall outlet as well. Do not normally plug a surge protector into the UPS, because that creates a daisy chain and can overload the UPS.

• Admin access to the deployment pipeline
• Contributor access to the Development and Test workspaces
• Viewer access to the Production workspace

• One network address
• Two usable host addresses—one for each router
• One broadcast address

• Router A: 10.2.1.1
• Router B: 10.2.1.2

• A is correct: It establishes the revised dates and identifies the effect on the critical path.
• B is premature: Stakeholders should be informed after the impact has been assessed and the updated schedule is understood.
• C is not automatically appropriate: Fast-tracking may introduce additional risk and should be considered only after analyzing schedule options.
• D is premature: Adding resources may not resolve a dependency and could increase costs without addressing the actual constraint.

• Process Builder: Automates actions based on record changes but does not create interactive forms.
• Approval Process: Routes records for approval; it is not designed to collect information through a wizard.
• Outbound Message: Sends information to an external system; it does not provide a user interface.

• Match found: ServiceNow updates the existing target record.
• No match found: ServiceNow normally creates a new target record.
• No Transform Map is created or deleted based on whether a match is found.

• Business risks
• Potential financial, operational, legal, or reputational impact
• How governance reduces risk to organizational objectives
• How much risk the organization is willing to accept

• The server accepts unauthenticated image uploads, which creates an opportunity for an attacker to upload a malicious script disguised as an image or using an unexpected file type.
• A web shell is a malicious script placed on a web server that gives an attacker remote command execution through web requests.
• The suspicious process and outbound connection to a low-reputation IP are consistent with the attacker using the web shell to execute commands or establish communication with command-and-control infrastructure.

• Worm: Usually self-propagates across multiple systems; the scenario focuses on the upload page.
• Cryptocurrency mining: Possible, but there is no indication of resource-intensive mining activity or insider involvement.
• Rootkit Trojan over RDP: The evidence points to the vulnerable upload functionality, not an exposed RDP service.

1. Install a Cassandra-compatible ODBC driver.
2. Configure a data source name (DSN), if required.
3. In Power BI Desktop, select Get Data > ODBC.
4. Choose the configured DSN and connect.

• Microsoft SQL Server database: Connects to SQL Server, not Cassandra.
• OLE DB: Requires a compatible OLE DB provider; this is not the standard choice for Cassandra in Power BI.
• OData: Requires Cassandra data to be exposed through an OData service, which is not the normal direct connection method.

• Identify the causes of delays.
• Improve its workflow and collaboration.
• Adjust tools or development practices.
• Discuss improvements during retrospectives and apply them in future sprints.

• A: An impediment log can help track issues, but merely maintaining one does not remove the impediments.
• B: Directing the team toward solutions reduces team ownership and self-organization.
• C: Adding impediments to the product backlog may be appropriate in some cases, but it does not automatically ensure they are addressed promptly.
• D: Best reflects agile leadership: empowerment, continuous improvement, and removal of impediments.

• Which batches and markets are affected
• Whether the deficiency affects product quality, efficacy, or patient safety
• Whether the issue is an ongoing manufacturing problem
• Whether immediate containment or distribution suspension is needed

• A — Withdraw the product: may be necessary, but is premature before assessing the risk.
• B — “Dear Dr.” letter: may be appropriate later, depending on the risk.
• C — Notify global authorities: may become mandatory, but the scope and urgency depend on the assessment.

• Highly polished, organization-wide presentations
• Advanced dashboard design and customization
• Broader business-user distribution and interaction
• Specialized BI governance and modeling features

• Reduce the training data: Usually makes overfitting worse.
• Add hyperparameters: Hyperparameters already control training; simply adding them does not solve the problem. Proper tuning could help, but that is not what the option states.
• Increase training time: More training can worsen overfitting if the model is already memorizing the training data.

• Structure requirements documents
• Draft user stories and acceptance criteria
• Create templates for functional and nonfunctional requirements
• Turn natural-language descriptions into organized documentation or implementation examples

• A: “Automatically generating detailed requirements documents” overstates Copilot’s role; it assists but does not independently determine complete requirements.
• C: /help provides guidance about Copilot features, not reliable requirements-conflict detection.
• D: Stakeholder communication and meetings remain human responsibilities.

• A is incorrect: Flow Debugger is for debugging Salesforce Flows, not Trust Layer masking.
• B is incomplete/misleading: Requesting audit data may be part of reviewing the results, but collection and storage must first be enabled.
• C is correct: It describes the initial validation step.

• A hypervisor allows multiple virtual machines to run on one physical server.
• Each VM can have its own operating system, so the customer can consolidate Windows, Linux, and Unix servers.
• A Type 2 hypervisor runs on a host operating system and can be deployed on local hardware, helping address data privacy and avoiding ongoing public-cloud charges.

• Containers share the host operating system’s kernel.
• They are well suited to consolidating applications, but they generally cannot independently run a mix of unrelated kernels such as Windows, Linux, and Unix on one host.

• Normal or expected input
• Boundary values
• Invalid input
• Potential error conditions

• A is incorrect: it creates test code, not detailed test documentation.
• C is incorrect: it does not primarily integrate external testing frameworks.
• D is incorrect: executing tests requires your development environment or test runner.

• Custom domains: supported by Standard.
• Dedicated compute instances: Standard runs on dedicated Azure VMs.
• Load balancing: Standard supports scaling the app across multiple instances with traffic distributed between them.
• Storage: Standard provides more storage than the lower tiers.
• Cost control: Standard is cheaper than higher tiers while meeting the stated requirements.

• Free and Shared use shared infrastructure and are intended for basic/testing workloads.
• Basic provides dedicated instances, but the question’s expected answer treats Standard as the minimum tier providing the required load-balancing capability.

• B — Sales staff will tender for riskier contracts:

• C — Sales staff will encroach on other territories:

• D — Sales staff will look for new jobs:

• On-premises resources, such as an existing database
• Cloud resources, such as Azure services or virtual machines
• Connectivity that allows the application to use both environments

• Public cloud: resources are entirely provided through a public cloud provider.
• Private cloud: resources are dedicated to one organization, typically on-premises or privately hosted.

• Due diligence: Investigating and evaluating a third party before entering a business relationship.
• Attestation: An independent auditor’s examination and formal report—such as the SOC 2 report itself. The analyst is reviewing the attestation, not performing it.
• Internal audit: Examines the organization’s own processes and controls.
• Penetration testing: Actively tests systems for exploitable vulnerabilities.

• Determine risk tolerance: Tolerance defines how much variation or exposure the organization is willing to accept. Scenarios may help apply tolerance, but they do not primarily determine it.
• Determine risk appetite: Risk appetite is established at an enterprise or governance level. Scenarios help compare risks with the appetite; they do not normally establish it.
• Develop risk responses: Once risks are identified and assessed, scenarios support response planning. However, response development comes later.

• A user connects with their Google account.
• Google associates the user’s SSH key with that identity.
• IAM roles determine whether they can log in.
• Access can be tied to a specific employee for auditing.
• Removing the IAM role removes their login access.

• compute.osLogin: regular OS login access
• compute.osAdminLogin: OS login with administrative privileges, typically including sudo

text 
enable-oslogin=TRUE

1. insert con; ? 1
2. Database.setSavepoint(); ? 2
3. update con; ? 3
4. Database.rollback(sp_admin); ? 4

• GPS coordinates
• Date and time the image was taken
• Camera or device information
• Image dimensions and software used

• Log data: Records generated by systems or applications, not normally embedded in image files.
• Encrypted data: Information intentionally encoded to prevent unauthorized access.
• Sensitive data: A broad classification, not the specific type of information being extracted.

• True positive: The scan reports a vulnerability that really exists.
• False positive: The scan reports a vulnerability that does not exist.
• True negative: The scan correctly reports no vulnerability.
• False negative: The scan fails to detect a vulnerability that is actually present.

• Internal hostnames and subdomains
• Network structure and naming conventions
• Servers and services
• Relationships between systems

• Determining ISP-assigned address space: Usually involves external registration and DNS information, not internal host discovery.
• Bypassing DNS sinkholing: Would require evidence that malicious DNS requests avoided redirection.
• Initial access: DNS queries alone do not show that the attacker gained access.
• Exfiltrating data: DNS tunneling can do this, but the snippet would typically show encoded or unusually long DNS queries.

• IRR assumes that interim cash flows can be reinvested at the project’s own IRR. This may be unrealistic, especially when the IRR is very high.
• MIRR assumes reinvestment at a specified rate, usually the company’s cost of capital or another realistic reinvestment rate.

• B: MIRR does not specifically favour projects with long payback periods.
• C: MIRR and IRR can rank competing projects differently.
• D: MIRR is not always higher than IRR; it may be higher or lower depending on the cash flows and reinvestment rate.

• Active remediation actions role in Microsoft Defender for Endpoint

• Security Reader role in Azure AD/Entra ID

• Security Administrator is broader than necessary because it grants extensive security-management permissions, violating least privilege.
• Compliance Data Administrator is intended for compliance data management, not Defender for Endpoint remediation approvals.

• A Screen Flow can present a form that inspectors complete and submit on an Experience Cloud page.
• It can collect inspection findings, validate the input, and create or update records.
• An Autolaunched Flow has no user interface, so it cannot directly provide the form.
• A Related List only displays related records, and Record Detail is primarily for viewing or editing an existing record—not for a custom inspection submission form.

• Delete the City column
• Remove duplicates from the Country column

1. ???? City ??? ????? ?? ???? ?????? ???? ?????.
2. ???? ???? Country ?????? Remove duplicates ?????? ??? ?? ???? ??? ?????.

• To identify the number of errors: select Column quality. It shows the percentage and count of Valid, Error, and Empty values for each column.
• To resolve errors: use the appropriate error transformation:

• Unsafe images: Requires image/content moderation before the image is processed.
• Hidden instructions embedded in images: These are indirect prompt injections contained in untrusted image content or extracted text, not necessarily in the user’s typed prompt.

• Enforce organizational rules, such as allowed regions or required tags
• Audit resources for compliance
• Deny noncompliant deployments
• Aggregate compliance results across subscriptions

• C: Develop the rule in the Rules Editor, define the events, match, and condition sections, then use the test rule feature. This directly validates the YARA-L rule without enabling it in production.
• A: UDM Search can help investigate data and refine filters, but it does not fully test YARA-L logic—especially complex event joins, match windows, and conditions.