Salesforce Service-Con-201 Exam Prep
Salesforce Certified Service Cloud Consultant (Page 10 )

• Authentication: Verifies who the user is.
• Authorization: Determines what the authenticated user is allowed to access.
• Accounting: Records login activity and resource usage.

• CIA: Confidentiality, integrity, and availability—the core security objectives.
• ACL: Access Control List; rules that permit or deny traffic or access.
• PEM: A format and standard commonly associated with encoded certificates and keys.

1. Create a temporary Onboarding OU.
2. Move the new account into it.
3. Move the restrictive SCPs from the organization root to the Production OU.
4. Allow the account to update AWS Config.
5. Move the account into Production after onboarding.

• An SCP attached at the organization root applies to every account and OU beneath it.
• An SCP attached to the Production OU applies only to accounts in that OU.
• Therefore, moving the restrictive SCP from the root to Production temporarily exempts the onboarding account without weakening the policies for existing production accounts.
• Once onboarding is complete, moving the account into Production subjects it to the normal restrictions.

• Data only needs to be current at 7 AM each day, so scheduled refresh is sufficient.
• Import mode provides the fastest report interaction because data is stored in Power BI’s in-memory engine.
• It supports row-level security (RLS), including the USERNAME() filter.
• You can limit the imported data to the current year and previous three years to reduce model size.
• DirectQuery would generally provide slower visual response times and is unnecessary here.
• Dual is mainly useful in composite models where some tables use DirectQuery and others use Import. That is not required by this scenario.
• Live connection is not appropriate because you are creating the semantic model.

• 10.2.1.0 — network address
• 10.2.1.1 — usable host
• 10.2.1.2 — usable host
• 10.2.1.3 — broadcast address

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

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

• Reporting relationships
• Organizational structures
• Leadership styles
• Team maturity
• Individual and group behavior
• Communication and motivation

• Acquire Project Team: Focuses on obtaining the people needed for the project.
• Develop Project Team: Focuses on improving team skills, relationships, and performance.
• Manage Project Team: Focuses on tracking performance, resolving issues, and managing changes within the team.

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.

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

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

• Honeypots: Decoy systems designed to attract attackers. Legitimate users should not access them, so activity there is a strong indication of unauthorized access.
• DNS sinkholes: Redirect requests for known malicious domains to a controlled internal destination instead of the real attacker infrastructure. Security teams can then identify infected systems making those requests.

• Tokenization: Replaces sensitive data with non-sensitive tokens; it protects data but does not detect intruders.
• CI/CD: Software development and deployment processes.
• Threat modeling: Identifies potential threats before or during system design, rather than detecting successful infiltration.
• Data obfuscation: Makes information harder to understand, but is not an attacker-detection mechanism.

• Deterrent control: The signs warning that people may be filmed can discourage unauthorized or malicious activity. They do not directly stop the action; they influence behavior.
• Detective control: CCTV records or monitors activity so security personnel can identify events or investigate them afterward.

• Preventive: Stops an incident from occurring, such as access control.
• Corrective: Restores systems after an incident.
• Directive: Instructs people to behave in a certain way, such as a security policy.
• Compensating: An alternative control used when the preferred control is not feasible.

• Accept: Acknowledge the risk and take no additional action.
• Transfer: Shift the risk or financial impact to another party, such as through insurance or a contract.
• Mitigate: Reduce the likelihood or impact using controls, such as firewalls, training, or backups.
• Avoid: Eliminate the activity that creates the risk.

• Microsoft Foundry is an enterprise platform for developers, data scientists, and IT teams.
• It supports the full AI application lifecycle: selecting models, connecting enterprise data, developing, evaluating, deploying, monitoring, and scaling solutions.
• It can include visual tools and low-code experiences, but it is not primarily designed to enable business users to build complete generative AI solutions independently.

• B: You still need to select and configure an appropriate model.
• C: Business users may participate through visual tools, but they are not the primary target audience.
• D: Foundry includes low-code tools, but it is not fundamentally a low-code-only platform.

• Repetitive and time-consuming
• Based on measurable conditions, such as last check-in time
• Easy to automate with alerts, dashboards, or scheduled reports
• Important for ensuring scan coverage

• Assigning custom recommendations usually requires analyst judgment and context.
• Analyzing false positives can sometimes be assisted by automation, but validation often requires human review.
• Rendering an additional executive report increases reporting activity rather than reducing a core operational workload.

• Label applied does not automatically exclude a file from Copilot.
• Encryption/usage rights determine whether Copilot can access the file’s content.
• If the user has no permission under Label2, File3 should be unavailable to Copilot for that user.
• File3’s label might be inherited by derived content only if File3 was actually processed and contributed by an authorized user; it should not be treated as contributing merely because it exists in the source set.

• B — Data source settings in Power BI Desktop:

• D — Formula bar in Power Query Editor:

m 
  Excel.Workbook(File.Contents("new path"))

• E — Advanced Editor in Power Query Editor:

• A: Dataset settings in the Power BI service mainly handle credentials and gateway settings, not changing the local file path embedded in the PBIX.
• C: Current File data-load settings control refresh/load behavior, not the source location.

1. Initiate — establish the project, scope, team, and governance.
2. Plan — develop the detailed plan, schedule, resources, and implementation approach.
3. Execute — configure, integrate, migrate, test, and prepare the solution.
4. Deploy — move the solution into production and support go-live.
5. Close — complete handover, confirm outcomes, and formally close the project.

• 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

• Act as the default gateway for devices in that VLAN
• Route traffic between different VLANs
• Provide management access to the switch

text 
interface vlan 10 
 ip address 192.168.10.1 255.255.255.0

Correct reasoning

• Create storage5 as a General-purpose v2 (StorageV2) account.
• Configure Blob object replication from storage5 to an existing compatible storage account.
• The destination must support object replication—typically another StorageV2 or premium block blob account.
• Blob versioning must be enabled on both accounts.
• Blob change feed must be enabled on the source account.
• The accounts must meet Azure’s object-replication requirements, including being in supported regions and having compatible configuration.

• JobTitle: User1 and User3 only
• UsageLocation: User1, User2, and User3

• For a user whose source of authority is Windows Server Active Directory, attributes such as JobTitle are synchronized to Microsoft Entra ID. You must change them in on-premises AD; editing them in Entra ID is not allowed or will be overwritten.
• UsageLocation is a cloud-managed attribute used mainly for licensing and service availability. It can be set or changed in Microsoft Entra ID, including for synchronized users.

• Distinct values = 69

• Unique values = 4

• Partners first log in to the corporate portal, which uses the shared SAML Identity Provider.
• When they select a Salesforce link, the IdP can send a SAML assertion directly to Salesforce.
• Salesforce validates the assertion and grants access to the Partner Community without requiring another login. This is IdP-initiated SSO because authentication begins outside Salesforce.

• SP-initiated SSO starts when Salesforce sends an authentication request to the IdP. That would be appropriate if users began by visiting Salesforce.
• The Web Server and User Agent OAuth flows are for OAuth authorization, not browser-based SAML federation between an IdP and Salesforce.

• Injection
• Broken access control
• Authentication failures
• Security misconfiguration
• Cross-site scripting

• STIX: A standardized language and format for exchanging threat intelligence.
• OVAL: Used to describe and assess system vulnerabilities and configuration issues.
• Threat intelligence feed: Provides current indicators and intelligence about threats, but not necessarily a structured overview of common application exploitation methods.
• CVE: A catalog of individually identified, publicly disclosed vulnerabilities.

• \Pipeline1
• \Folder1\Lakehouse1

• Pipeline1 remains at the workspace root in Workspace1, so it is deployed to the root of Workspace2.
• Lakehouse1 was moved into Folder1, so its full path is preserved as \Folder1\Lakehouse1.
• Fabric deployment pipelines preserve folder paths because an item’s full path is treated as part of its name.

1. Open File Explorer.
2. Go to View ? Show ? File name extensions

1. Disable Hide extensions for known file types.
2. Rename the complete filename from Document.txt to Document.xml.
3. Confirm the extension-change warning.

• A: Concerns task scheduling and avoiding missed runs, not directly sizing the warehouse.
• B: The amount of data in a stream alone does not reliably determine compute needs; the SQL processing is what matters.
• D: A multi-cluster warehouse addresses concurrency, not the compute size needed for one task execution.

• How quickly the vendor must respond to incidents or requests
• Availability or uptime requirements
• Resolution time targets
• Performance expectations and penalties for failing to meet them

• SOW (Statement of Work): Describes the work, deliverables, scope, and schedule.
• MOA (Memorandum of Agreement): Documents an agreement in which parties commit to specific responsibilities.
• MOU (Memorandum of Understanding): Records a general intention to cooperate; it may not be legally binding.

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

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

• Route table: Controls how traffic is routed within a VPC; it does not use the AWS worldwide network to accelerate internet traffic.
• AWS Transit Gateway: Connects multiple VPCs and on-premises networks through a central gateway, but it is not primarily an internet traffic acceleration service.
• Amazon VPC: Provides isolated virtual networking in AWS, but it does not itself accelerate traffic globally.

• Gathering structured feedback from team members and relevant stakeholders
• Reviewing observed behaviors and completed work
• Using a feedback or performance-assessment method suitable for the project environment

• A — Identify levels of decision-making authority: Concerns governance and delegation, not performance evaluation.
• B — Evaluate demonstrated task accountability: This could be an input to feedback, but it does not establish a complete or fair evaluation method.
• D — Analyze team member influence: Focuses on influence and stakeholder/team dynamics, not overall performance.

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

• A — Technical review by business owner: A business owner may approve the business impact, but a technical review is normally performed by technical personnel.
• C — Cost-benefit analysis after implementation: Cost-benefit analysis should occur before implementation to support the approval decision.
• D — Business continuity testing: This can be appropriate for major changes, but it is primarily part of business continuity and disaster recovery planning—not a universal change-management activity.

1. System prompts can authorize users — No

1. System prompts can reduce TPM consumption — Yes, with qualification

1. System prompts guide generative AI behavior — Yes

• Due diligence: Investigating and evaluating a third party before entering into or continuing a business relationship.
• Attestation: An independent party provides assurance about an organization’s claims or controls. A SOC 2 examination is an example of an attestation engagement, but the analyst requesting and reviewing the report is performing due diligence.
• Internal audit: Reviews the organization’s own internal controls.
• Penetration testing: Actively tests systems for exploitable vulnerabilities.

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

• B. Versioned configuration files — Infrastructure is defined in machine-readable files and tracked in version control, allowing repeatable provisioning and change history.
• D. Docker files — Assuming “Doctor files” is a typo for Dockerfiles, a Dockerfile declaratively defines how to build a container image and is commonly considered infrastructure/configuration as code.

• A. Cloned virtual machine images — These are prebuilt infrastructure artifacts, but cloning an image is not itself a code-based infrastructure definition.
• C. Change management database records — A CMDB records information about infrastructure; it does not define or provision that infrastructure.

• SOSL searches text across objects and is not appropriate for selecting Account table columns.
• describeSObjects() provides metadata about objects and fields, but it does not itself build or execute the query.
• Dynamic Schema binding supports runtime determination of object and field information, which is required here.
• REST API is unnecessary because this is being implemented in Apex.

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

• Containment policy: controls permitted communication during containment.
• Detection/response configuration: determines when containment is initiated.

• Accept: Acknowledges the risk without taking additional action.
• Transfer: Shifts the risk or financial impact to another party, such as an insurer.
• Mitigate: Reduces the likelihood or impact through controls like patching, MFA, or segmentation.
• Avoid: Eliminates the activity that creates the risk.

• Access List: controls whether a client is allowed or denied.
• Connect List: controls which wireless networks/APs a station may connect to.

• Lower order numbers appear first.
• For example, a variable with order 100 appears before one with order 200.
• The Sequence field is not the control used for catalog variable display order.
• The Default Value sets a value, not placement.
• The Choice field defines selectable options, not the variable’s position.

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

• host — simple, human-friendly lookups

bash 
  host example.com 
  host 192.0.2.1

• dig — detailed DNS troubleshooting

bash 
  dig example.com 
  dig example.com MX 
  dig @8.8.8.8 example.com

• nslookup — older, familiar, and widely available

bash 
  nslookup example.com

• Quick answer: host
• Detailed diagnosis: dig
• Compatibility or legacy environments: nslookup