Quality Assurance CSQA Exam Prep
Certified Software Quality Analyst (CSQA) (Page 76 )

• Azure Cosmos DB is a globally distributed NoSQL database service. It stores and retrieves application data, but it does not provide the complete environment for building, testing, and deploying predictive analytics models.
• Azure Machine Learning is the appropriate service for this requirement. It supports creating experiments, training and testing models, and deploying them for predictions.
• Azure Machine Learning Studio provides the browser-based interface for these tasks.

• A. PsFile — Correct: Displays files opened remotely on a system. This reveals shared resources and user activity.
• B. UserInfo — Correct: Gathers information about user accounts, supporting account and privilege enumeration.
• C. PsPasswd — Answer key lists it: This is questionable. PsPasswd is primarily used to change passwords remotely, not enumerate information. The key may classify it broadly as a Windows account-management tool, but it is not a strong enumeration example.
• D. WinSSLMiM — Incorrect: Used for SSL man-in-the-middle activity, not enumeration.

• The team should inspect its way of working during retrospectives.
• The team can identify root causes of delays and agree on process improvements.
• The leader facilitates the removal of impediments and provides support, but does not impose solutions.

• A: An impediment log can help track issues, but documentation alone does not resolve them.
• B: Directing the team toward solutions conflicts with agile empowerment and self-management.
• C: Adding impediments to the product backlog may incorrectly treat team problems as product features and delay resolution.

• Accept: Acknowledge the risk without taking additional action.
• Transfer: Shift the risk’s impact to another party, such as through insurance or outsourcing.
• Mitigate: Reduce the likelihood or impact, such as by implementing controls.
• Avoid: Eliminate the activity or situation that creates the risk.

• Prevention costs: Avoiding defects, such as staff training and improved product design. The company has invested in these.
• Appraisal costs: Detecting defects before products reach customers, such as inspection and testing. The planned batch sampling has not been implemented.
• Internal failure costs: Correcting defects found before delivery.
• External failure costs: Dealing with defects after delivery, such as refunds, replacements, complaints and lost sales.

• B — The most significant risks are held by SQ.

• C — SQ should recognise the cars as inventory.

• F — SQ recognises revenue when LM sells a car to a third party.

• A: LM does not hold the most significant risks.
• D: LM does not recognise the cars as inventory.
• E: SQ should not recognise revenue when cars are merely delivered to LM.

• up ? down ? up
• Often happens rapidly or intermittently

• Faulty or loose cable or connector
• Failing transceiver, NIC, or switch port
• Speed/duplex or auto-negotiation problems
• Power or hardware instability
• Layer 1 interference

• Nothing plugged in: the port is simply down
• Latency: does not directly trigger err-disable
• shutdown: administratively disables the port, but that is not the same as an automatically detected err-disabled condition

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.

• Packet capture: Collects and analyzes network traffic; it does not describe the scan type.
• Privilege escalation: Attempts to gain higher permissions after obtaining access.
• System enumeration: Identifies systems, services, or resources, but is not specifically defined by the lack of credentials.
• Passive scan: Observes traffic without actively probing systems. A vulnerability scan is generally an active assessment.

• Response and resolution times
• Availability or uptime requirements
• Performance targets
• Support responsibilities
• Penalties or remedies if requirements aren’t met

• SOW (Statement of Work): Describes the work, deliverables, scope, and schedule for a project.
• MOA (Memorandum of Agreement): Documents agreed-upon responsibilities or cooperation between parties.
• MOU (Memorandum of Understanding): Records a general mutual understanding, often without detailed enforceable service targets.

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.

• The load balancer provides the listener’s frontend IP address.
• The active SQL Server node must also respond to that same listener IP.
• Enabling Floating IP allows the listener IP to be preserved and handled correctly by the active replica.
• Without it, SQL connections may be sent to a node that cannot correctly claim the listener address.

• A health probe for the SQL Server port
• A load-balancing rule using the listener port
• Floating IP enabled on that rule

• Data source: Folder
• Transformation: Remove the Content column (or keep only the file-metadata columns)

Why

• File name
• Extension
• Date modified
• Folder path
• Content — the binary contents of the file

• Sustainability
• Performance efficiency
• Reliability

• 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

• Security groups
• Dynamic security groups
• Cloud-only or synchronized security groups

• Microsoft 365 groups
• Distribution groups
• Mail-enabled distribution groups

• C. Case after-insert trigger that publishes a Platform Event

• D. Custom Apex controller that publishes a Platform Event

• A. Trigger with a callout: Salesforce triggers should not make direct synchronous callouts, and this tightly couples transaction processing to the external system.
• B. Workflow Rule with Outbound Message: This can react to record changes, but it cannot reliably capture a user clicking a menu item. It also does not provide the same flexible event-driven model as Platform Events.

• Tokens: Individual units of text processed by a model, such as words, subwords, or characters.
• Models: Systems that learn patterns and generate predictions or outputs.
• Binaries: Data represented using the binary number system, not semantic representations.

• Share files with the wrong people
• Use public links unnecessarily
• Fail to classify sensitive data
• Upload data to unauthorized services
• Misunderstand company sharing policies

• A — Step-up authentication: Helps protect administrator accounts, but does not directly address improper file sharing by users.
• C — Password complexity: Helps reduce password attacks, not accidental data disclosure.
• D — Mobile device management: Secures managed mobile devices, but does not directly control file-sharing behavior across the organization.

• A — .gitignore: Controls Git tracking; it does not configure Copilot exclusions.
• B — copilot.ignore: This is not the standard GitHub Copilot Business exclusion mechanism.
• D — Renaming files: Adding _no_copilot has no recognized effect.

• Rights issue: Raises new equity from existing shareholders. It does not increase debt or gearing, so it is least likely to breach the covenant.
• Retained earnings: Also equity finance, but the amount available may be insufficient for the required $800 million.
• Private placement of a bond: Creates additional debt and would worsen gearing, increasing the risk of breaching the covenant.
• Bank overdraft: Also debt finance, usually short-term and potentially expensive; it would still increase financial risk and gearing.

• Complex inputs: A queueable job can accept and retain complex data such as Map<Id, Project__c> and List<Account>.
• Callouts: The class should implement both:

apex 
  public class ProjectJob implements Queueable, Database.AllowsCallouts { 
      // execute method 
  }

• Execution confirmation: System.enqueueJob() returns an AsyncApexJob ID. You can use that ID to query job status and confirm whether the job completed successfully.

• @future(callout=true) supports callouts, but future methods have more restrictive parameter types and return no job ID for tracking.
• Database.AllowsCallouts is only an interface that permits callouts; it is not an asynchronous mechanism by itself.
• Schedulable is intended for jobs that run at a scheduled time, not primarily for submitting a long-running asynchronous operation.

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

• Custom domains: Supported by Basic and higher tiers.
• Dedicated compute: Basic and Standard use dedicated virtual machine instances; Free and Shared use shared infrastructure.
• Load balancing between instances: Standard provides scaling across multiple instances with load balancing.
• Storage: Standard provides more storage than Basic.
• Cost: Standard is the least expensive option that satisfies all the stated requirements.

• Free/Shared: Use shared compute and have limited features; they don’t meet the dedicated-compute requirement.
• Basic: Provides dedicated compute and custom domains, but does not provide the required Standard-level multi-instance capabilities in the exam’s feature comparison.

• SQL injection
• Cross-site scripting (XSS)
• Malicious or malformed web requests
• Some application-layer attacks

• Layer 4 firewall: Filters based mainly on IP addresses, ports, and transport protocols; it cannot deeply inspect web application content.
• NGFW: Provides advanced network filtering and may include application awareness, but a WAF is more specifically designed to protect web applications.
• UTM: Combines several security functions in one appliance, but it is not the most targeted solution for a web portal.

1. Append Table1 and Table2 as a new query

1. Select the product column in the appended query.

1. Choose Remove Rows > Remove Duplicates

• An Adj-SID does not necessarily need manual configuration.
• It can often be dynamically allocated by the router, although manual configuration may also be possible.
• The adjacency information is advertised through the IGP, such as IS-IS or OSPF.

• It is identified by an Adj-SID.
• It represents a particular adjacency of a node.
• Its meaning is generally local to the advertising node; unlike a Node-SID, it is not a globally reusable instruction across the network.

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

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

• New investment: $536,500
• Resulting NPV: $0

• Type 1 hypervisor: Runs directly on the physical hardware (“bare metal”).
• Type 2 hypervisor: Runs inside the host OS as an application.

• Bare-metal installation: Type 1
• Local management only: Not a defining characteristic
• Specific hardware requirements: Not the key distinction

• Create a CodeCommit repository in the secondary Region.
• Use CodeBuild to run a Git mirror operation from the primary repository to the secondary repository.
• Use EventBridge to detect relevant repository events, such as a pull request being merged.
• Invoke a Lambda function, which starts the CodeBuild project.

• B: Amazon S3 is object storage, not a Git repository that developers can use as a CodeCommit remote.
• C: CodeArtifact is intended for packages and artifacts, not source-code repository mirroring.
• D: An AWS Cloud9 environment is not an appropriate automated replication mechanism and would require manual or persistent infrastructure management.

• Low: Applies system, tenant, and user-based suppressions. Activity from locations commonly used by that user is more likely to be suppressed.
• Medium: Applies system and user suppressions.
• High: Applies only system suppressions, so more unusual-location activity generates alerts.

• Enable screensaver locks: After inactivity, the workstation locks and requires the user to authenticate again. This prevents someone nearby from using an unattended logged-in computer.

• Apply a BIOS password: A BIOS/UEFI password helps prevent unauthorized users from changing boot settings, booting from external media, or bypassing normal startup controls. It adds protection before the operating system loads.

• Defragment the hard drive: Improves drive organization/performance, not access control.
• Enable SSH: Provides remote command-line access and could introduce another access path; it does not restrict local workstation users.
• Disable iCloud integration: Not a general workstation access-control measure.
• Enable the firewall: Protects against network connections, but does not stop an unauthorized person who is physically using the workstation.

• CBWFQ (Class-Based Weighted Fair Queuing): Creates traffic classes and assigns each class a guaranteed bandwidth or queueing treatment.
• PQ (Priority Queuing): Uses multiple queues with strict priority. Higher-priority queues are serviced before lower-priority queues, making it useful for delay-sensitive traffic—but it can starve lower-priority traffic.

• FRTS: Traffic shaping for Frame Relay; it controls the transmission rate rather than selecting packets during congestion.
• CAR: Polices traffic by rate, typically dropping or remarking packets that exceed a limit.
• PBR: Policy-Based Routing; it selects forwarding paths and is not a QoS queueing mechanism.

• Job Links ? URL ID: Mainly summarizes link performance; it is not the easiest place to retrieve individual email addresses by alias.
• Tracking Overview ? Clicks: Provides aggregate click metrics, not a targeted list for one aliased link.
• Click Activity ? Link View: Focuses on link-level reporting, but the question’s intended workflow for locating clicks tied to a specific placement/alias is Email Overlay.

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

1. Which host originated the infection
2. Whether each other host is clean or infected
3. Which firewall or host logs provide evidence of the infection’s movement

• Find the earliest infection-related event. The host associated with that event is the likely origin.
• Follow the timeline: outbound connections from that host may indicate propagation or command-and-control activity.
• A host receiving suspicious traffic is not automatically infected; look for evidence that it executed or initiated malicious activity.
• A firewall log can show traffic paths, but endpoint logs are usually needed to confirm infection.
• Mark a host clean only when the logs show no indicators of compromise or malicious activity.

• contoso.onmicrosoft.com
• contoso1.onmicrosoft.com

• onmicrosoft.com domains: Maximum of five per tenant.
• Custom domains: Domains that your organization owns and verifies in Microsoft 365.

• A. IDS attack signatures: Detects suspicious network activity, but is not primarily designed to scan uploaded files for malware.
• C. Load balancer: Distributes traffic among servers and improves availability; it does not inspect files for threats.
• D. WAF: Protects web applications from attacks such as SQL injection and command injection, but its primary role is not malware scanning of uploaded documents.

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

• B — Incorporate contextual output encoding/escaping: Encode untrusted data based on its context—HTML, attribute, JavaScript, or URL—so the browser treats it as data rather than executable code.
• D — Run untrusted HTML input through an HTML sanitization engine: Sanitization removes or neutralizes dangerous elements and attributes, such as script-related content, while preserving safe HTML where needed.

• A: Enabling client-side scripts does not prevent XSS. Script restrictions may reduce risk in some environments, but “enable” is not a general XSS control.
• C: Cookie inspection is unrelated to preventing injected scripts.
• E: The SameSite cookie attribute primarily helps mitigate CSRF, not XSS. It should not generally be described as an XSS prevention measure.

• Domínios personalizados.
• Armazenamento suficiente.
• Instâncias dedicadas.
• Balanceamento de carga.
• Menor custo entre os planos que atendem a tudo.

• Warehouse size: Larger warehouses use more credits per unit of time than smaller ones.
• Number of clusters: A multi-cluster warehouse can run multiple clusters, and each active cluster consumes credits. Therefore, increasing the maximum or active cluster count can increase consumption.

• Number of users: More users may cause more workload, but users themselves do not consume credits.
• Amount of data processed: Snowflake warehouses are not charged directly by the amount of data scanned. However, processing more data may cause the warehouse to run longer, indirectly increasing credits.

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

• Required response time
• Resolution time
• Availability or uptime
• Support hours
• Performance targets
• Consequences if targets are missed

• SOW (Statement of Work): Defines the project’s scope, tasks, deliverables, and schedule.
• MOA (Memorandum of Agreement): Describes the responsibilities and commitments between parties.
• MOU (Memorandum of Understanding): Documents a general mutual understanding or intent, often before a formal agreement.

• Create the field in the CRM on the relevant person records—typically Lead and Contact in Salesforce.
• Give the Marketo Sync User read/write access to the field.

• Creating and training machine-learning models
• Testing and evaluating models
• Deploying models as usable endpoints

• Formatting: May remove file-system references but often leaves recoverable data.
• Degaussing: Uses a magnetic field to erase data, but can damage or make magnetic drives unusable.
• Defragmentation: Rearranges data for performance; it does not securely erase information.