CIPS L4M6 Exam Prep
Supplier Relationships (Page 17 )

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

• Deficiency found before patient use: usually does not require an adverse-event report because no patient exposure occurred.
• Event caused solely by the patient’s condition: may not be reportable if the device did not contribute.
• Malfunction protection operated correctly: generally exempt when the device’s safety mechanism worked as intended and prevented harm.

• Orders contains order-level information, such as the order date.
• Order Line Items contains the products, quantities, and line amounts associated with each order.
• Merging them on the order key, such as OrderID, places the order date alongside each line item. This allows you to calculate total order value and analyze it over time.
• Product attributes can remain in the Products table and be related to the resulting line-item table through ProductID.

• Merging line items with products addresses product attributes but does not first provide the order-level date and value needed for time analysis.
• DAX calculated columns or lists add unnecessary model complexity.
• Calculating order counts is not the first requirement and does not combine the required order and line-item data.

• The message came from the claimed sender (authentication)
• The message was not altered (integrity)
• The sender cannot easily deny sending it (non-repudiation)

• Attackers can send unsigned phishing emails.
• Attackers may compromise a legitimate account and send signed malicious emails.
• Users may still be tricked by a validly signed message.

• A. IDS attack signatures: An IDS primarily detects suspicious network activity; it is not the best tool for scanning uploaded files.
• C. Load balancer: Improves availability and distributes traffic but does not inspect files for malware.
• D. WAF: Protects web applications against attacks such as SQL injection and command injection. It may inspect HTTP requests, but malware scanning of uploaded PDFs is the key requirement here.

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.

• A business-hours greeting
• An after-hours greeting
• A holiday greeting

• Weekday evenings/nights
• Saturdays and Sundays

1. Auto attendant 1

1. Auto attendant 2

• netstat -tuln can show listening TCP ports.
• If the web service is not listening, or is bound only to 127.0.0.1, remote browsers cannot connect even though the server responds to ping.

• traceroute: Tests the path to the server, but ping already confirms basic reachability.
• tcpdump: Useful for detailed packet analysis, but it is more appropriate after checking whether a service is listening.
• arp: Helps troubleshoot local IP-to-MAC resolution, not an application-layer web connection.

• 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

• HTTPS: Secure web traffic, not general command-line server administration.
• SNMPv3: Secure network monitoring and management, not interactive server login.
• RDP: Provides graphical remote desktop access. It can be secure, but it is not the direct replacement for Telnet in this scenario.
• SMTP: Used to send email.

• Minimum
• Maximum
• Average
• Count
• Null/empty values
• Distinct values

• Enable column profile
• Enable details pane
• Show column profile in details pane

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

• Required response and resolution times
• Availability or uptime targets
• Performance standards
• Support obligations
• Remedies or penalties for failing to meet the terms

• SOW (Statement of Work): Defines the project’s scope, tasks, deliverables, and schedule.
• MOA (Memorandum of Agreement): Describes agreed responsibilities between parties, often for a specific activity.
• MOU (Memorandum of Understanding): Records a mutual understanding or intention, usually less formal than a contract.

• Additional running costs: $800
• Less depreciation: $300

• The $100 reduction in fixed production overhead absorbed is only an accounting reallocation. It does not represent an actual saving in total fixed overhead.

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

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

• Each team’s Bedrock workflow uses a separate IAM service role.
• The role’s Amazon S3 permissions can be limited to only that team’s customer folder or objects.
• This enforces least privilege and prevents one team’s Bedrock application from accessing another team’s data.
• Access is enforced by AWS permissions, not by asking users to provide a customer name in each request.

• A single role with broad S3 access does not provide team-level isolation.
• Asking teams to specify a customer name is not an access-control mechanism.
• Redacting data does not prevent unauthorized access.
• A bucket policy alone is insufficient unless it explicitly enforces the required team-role restrictions.

• The audience and stakeholders
• The complexity and type of requirements
• The communication method and level of detail needed
• Whether to use diagrams, models, documents, demonstrations, or slides

• B: Authority to host the presentation is not the key preparation activity.
• C: Stakeholder sign-off may occur later; presenting requirements does not always require formal approval beforehand.
• D: A scribe may be useful in a meeting, but hiring one is not a core preparation requirement for presenting.

• QuickVisualize is used to create and render a Power BI report from a DataFrame.
• The typical pattern is:

python 
PBI_visualize = QuickVisualize( 
    get_dataset_config(df), 
    auth=device_auth 
) 


PBI_visualize

• get_dataset_config(df) prepares the dataset configuration.
• auth=device_auth supplies authentication for the Power BI connection.
• Evaluating PBI_visualize renders the report in the notebook.

• Box 1: No
• Box 2: Yes
• Box 3: Yes

• A — Increased call deflection: o KCS disponibiliza conhecimento reutilizável para clientes e agentes, ajudando a resolver dúvidas sem abrir ou continuar chamadas.
• C — Reduced issue resolution time: os representantes reutilizam artigos e soluções já documentadas, acelerando o atendimento.
• E — Optimized use of resources: o conhecimento compartilhado reduz retrabalho e melhora o uso dos recursos da equipe.

• JDBC
• SnowSQL
• Snowflake Web Interface (UI)
• ODBC
• Python connector

• Periodic vulnerability assessments: Identify technical weaknesses but do not establish governance or ensure risks are managed.
• Established information security metrics: Help measure performance and report status, but measurement alone does not make governance effective.
• Advanced security technologies: Support security operations, but governance is primarily about direction, accountability, decision-making, and alignment with business objectives.

• Early units show relatively large time savings.
• Later units still take less time, but the reduction becomes progressively smaller.
• The curve therefore becomes flatter as production approaches 256 units.

• B: The reduction is not constant; learning normally diminishes over time.
• C: Time does not reduce at an increasing rate.
• D: A steady state may eventually be reached, but the question concerns the first 255 units while learning is still occurring.

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

• Behavioral and anomaly detection
• Threat intelligence integration
• User and entity behavior analytics
• Automated response actions, often through SOAR integration

• Virus signatures: Associated primarily with antivirus or endpoint protection.
• Security agent deployment: Usually an endpoint-management or EDR function.
• Vulnerability scanning: Typically performed by vulnerability-management tools, though a SIEM may integrate their results.

• Outer packet: 10.5.1.1 > 52.165.16.154
• IPv4 protocol field: 41, which indicates IPv6 encapsulation
• Inner packet: IPv6 traffic between 2001:... addresses

• MAC address spoofing: Changes Layer 2 addressing; it does not explain the IPv6-in-IPv4 structure.
• Steganography: Hides data inside files or media, not visibly in a tunneled protocol.
• Broken encryption: No evidence of encryption being cracked.
• On-path sniffing: Involves intercepting traffic, not sending data to an external host.

Manager role

DAX 
Country[Manager] = USERPRINCIPALNAME()

• Sales
• Human Resources

CFO role

• See sales for all countries
• See no Human Resources data

• Do not restrict the Country table or Sales table.
• Apply a filter to Human Resources that always returns false, such as:

DAX 
FALSE()

• A — VARIANT "null" values are not the same as SQL NULL values: True

• B — Frequent, single-row DMLs: False

• C — Validate data before loading into the target table: True

• D — Use staging tables to manage MERGE statements: True

• SAML (Security Assertion Markup Language): Commonly used for enterprise SSO between an identity provider and cloud applications. It sends signed authentication assertions to the service provider.
• RADIUS: Primarily used for centralized authentication to network devices, VPNs, and wireless networks.
• EAP: An authentication framework commonly used with network access technologies; it is not typically the SSO protocol for SaaS applications.
• OpenID: Related to identity authentication, but traditional enterprise SSO questions involving cloud applications generally expect SAML. OpenID Connect is a newer authentication layer built on OAuth 2.0.

• A — Securing information assets: This is the responsibility of management and operational/security teams.
• B — Validating protection: Correct. The auditor checks whether controls—such as access restrictions, encryption, retention, and handling procedures—match the asset’s classification.
• C — Ensuring alignment with regulations: Management and legal/compliance functions typically establish classification requirements; the auditor may assess compliance but does not primarily define alignment.
• D — Defining classification levels: This is a management responsibility based on business needs, risk, and regulatory obligations.

• Guest access: Controls external users invited into your teams as guests. It is not the primary setting for restricting federated communication by domain.
• Messaging policy: Controls messaging features, such as chat or message editing, rather than which organizations users can communicate with.
• Org-wide Teams settings: Contains broad Teams-wide configuration, but domain-based external communication is configured under External access.

• Which host first communicated with the suspected malicious source
• Whether that host initiated suspicious traffic or merely received it
• Which other hosts show evidence of infection, such as connections from the originating host
• Which hosts have no related suspicious activity and are therefore clean

• An outbound connection to a suspicious external address
• A downloaded or executed malicious file
• Later lateral connections from that host to other internal systems
• Firewall logs showing the direction and timing of the traffic

• Honeypots: Deliberately vulnerable or attractive systems designed to lure attackers. Legitimate users should not access them, so activity on a honeypot is a strong indicator of compromise.
• DNS sinkholes: Redirect requests for known malicious domains to a controlled internal system instead of allowing the connection. This can identify infected hosts attempting to contact command-and-control infrastructure.

• Tokenization: Replaces sensitive data with non-sensitive tokens; it protects data but does not primarily detect attackers.
• CI/CD: Automates software development and deployment processes.
• Threat modeling: Identifies potential threats and weaknesses before or during system design.
• Data obfuscation: Makes data harder to understand, but it is not an attacker-detection method.

• Labels control access and protection, not blanket exclusion.
• If the user has permission to open a labeled file—especially if the label allows authenticated users to view it—Copilot can use that file in a summary.
• If the label applies encryption and the user lacks the required usage rights, Copilot should not use the file or reveal its contents.
• Copilot honors the user’s existing permissions, so it should not expose labeled content to an unauthorized user.

• Report on the discount approval time for quotes

• Dashboard of opportunity stage duration

• Lead conversion trends measure lead-generation effectiveness, not opportunity closing time.
• Campaign ROI evaluates marketing performance, not delays in the sales process.

• The type of change: standard, normal, or emergency
• The risk, impact, and complexity
• The change model being used

• A standard change may be pre-authorized through its change model.
• A normal change may require assessment and approval by an appropriate change authority.
• An emergency change may be authorized by an emergency change authority, often using an expedited process.

• Change authorities are not only needed for emergency changes.
• They are not assigned only when a change is deployed.
• They are not only required for normal changes.

• A. Continue using the current system: It will eventually fail and offers no recovery strategy.
• B. Virtualize the entire system: Correct. A VM can preserve the old OS, application, settings, and dependencies while running on newer physical hardware.
• C. Containerize the application: Containers generally share the host OS kernel and are not suitable for preserving an entire incompatible legacy OS.
• D. Clone the disks to USB: A disk clone may provide backup or temporary recovery, but it does not solve hardware compatibility or provide a reliable long-term platform.

• Deterrent control: The signs warning people they may be filmed discourage unauthorized or malicious behavior. They may prevent incidents by influencing behavior, but their primary purpose is to deter.
• Detective control: The CCTV system monitors and records activity so security personnel can identify suspicious or unauthorized actions.

• Preventive: Blocks or prevents an incident, such as a lock or access-control system.
• Corrective: Fixes or restores systems after an incident.
• Directive: Tells people what they must do, typically through policies or procedures.
• Compensating: Provides an alternative control when the preferred control cannot be used.

• Identifies which user or department owns the device
• Supports inventory and compliance requirements
• Enables tracking of lost, stolen, retired, or unauthorized devices
• Helps enforce security controls such as mobile-device management and secure configuration

• Least privilege: Limits users to only the access necessary for their job.
• Background checks: Help identify potentially risky individuals before employment.
• Separation of duties: Ensures that one person cannot complete a sensitive process alone, reducing fraud and abuse.

• Insert is used when you are creating a new record. It saves the record to the table and then leaves the form.
• Update is used when editing an existing record. It saves the modifications and then leaves the form.

• Prevention costs – costs incurred to stop defects occurring, such as staff training, quality planning and supplier evaluation.
• Appraisal costs – costs of checking whether products meet standards, such as inspection, testing and quality audits.
• Internal failure costs – costs of defects found before delivery to customers, such as scrap, rework and retesting.
• External failure costs – costs of defects found after delivery, such as warranty claims, returns, complaints and product recalls.

• MTTC: Time required to contain or limit the incident’s impact — best match.
• MTTR: Time required to remediate or recover from the incident; this may include eradication, restoration, and cleanup, which goes beyond merely stopping spread.
• MTTD: How long it takes to discover the incident.
• MTBF: Average time between failures, generally a reliability metric.

• STP elects the switch with the lowest Bridge ID as the root bridge.
• The Bridge ID consists mainly of bridge priority + MAC address.
• If multiple switches have the same priority, the switch with the lower MAC address is preferred.
• STP bridge priority values are configured in increments of 4096, such as 0, 4096, 8192, and so on. 32768 is the standard default value.

• Espionage: Stealing confidential information, often for a competitor or government.
• Data exfiltration: Unauthorized transfer of data outside the organization. This could occur, but the question focuses on using unapproved access methods.
• Nation-state attack: An attack sponsored or conducted by a government.
• Shadow IT: Employees using technology or access methods outside the organization’s approved security controls.

• Third-party enterprise application with embedded AI: The provider manages most security controls. The customer mainly manages users, data, and configuration.
• Application using an existing third-party FM: The customer controls the application and its inputs/outputs, but the provider controls the underlying model and infrastructure.
• Fine-tuning a third-party FM: The customer has additional responsibility for training data, data protection, and model behavior, but still depends on the provider’s base model and platform.
• Building and training a model from scratch: The customer controls the model, training data, application, deployment, and many security safeguards. This creates the greatest security ownership.

• Disabling a compromised account
• Blocking a malicious IP address
• Isolating an endpoint
• Creating or escalating an incident ticket

• Virus signatures: Primarily associated with antivirus or endpoint protection.
• Security agent deployment: Usually handled by endpoint-management or security-agent platforms.
• Vulnerability scanning: Typically performed by vulnerability-management tools.

Correct sequence

1. Merge Sales_Region with Sales_Manager using an inner join

1. Merge Region_Manager with Manager using an inner join

1. Merge Sales_Region and Region_Manager using a right join as a new query

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

• Customers may boycott V’s products.
• Supermarket customers may stop buying from V.
• Investors may view V as having higher legal, ethical and reputational risk.
• V could face fines, lawsuits, contract losses and higher costs.
• Expected future profits may fall.