SAP C_THR70_2309 Exam Prep
SAP Certified Application Associate - SAP SuccessFactors Incentive Management (fka SAP Commissions) (Page 8 )

• Scheduling overlapping working hours for critical collaboration
• Assigning independent tasks that can proceed asynchronously
• Adding clear handoffs between offices
• Documenting decisions, questions, and required inputs
• Building appropriate time into the schedule for responses

• DB1 (500 TB): Azure Data Box Heavy

• Virtual machines: Azure Migrate

• NIDS: Monitors network traffic for suspicious activity and network-based attacks targeting the application or its supporting services.
• HIPS: Protects an individual host by monitoring processes, files, and system activity. It can help secure the web server, but it is not focused specifically on the application’s network attack surface.
• SIEM: Aggregates and correlates logs; it does not directly prevent attacks.
• Honeypot: A decoy system, not the primary protection for a production web application.
• Certificate revocation list: Deals with certificate trust, not application exploitation.

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.

• Regression predicts continuous numeric outcomes, such as house price, temperature, or sales amount.
• Linear regression assumes the target can be estimated from a linear relationship between the input features and the target.
• In Azure Machine Learning, you use a labeled dataset containing:

• Classification predicts a category or class, such as “spam” or “not spam.”
• Clustering groups similar records without a known label; it is an unsupervised learning technique.

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

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

• AWS Network Firewall can inspect and block traffic across a VPC when traffic is routed through the firewall. A Drop action rule can deny traffic from the suspicious source IP.
• GuardDuty findings are sent to Security Hub.
• A Lambda function can be invoked when Security Hub receives a new GuardDuty finding, extract the source IP, and update the Network Firewall policy with a blocking rule.

• GuardDuty threat lists: Used to identify or increase the severity of findings; they do not directly block VPC traffic.
• AWS WAF: Protects supported web applications, such as CloudFront or Application Load Balancers. It does not provide general VPC-wide traffic blocking.
• GuardDuty suppression rules: Suppress or hide findings. They do not block the suspicious traffic.

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

apex 
Set<Id> accountIds = new Set<Id>{ accountId1, accountId2 }; 


List<Account> accounts = [ 
    SELECT Id, Name 
    FROM Account 
    WHERE Id IN :accountIds 
];

• A: LIMIT accepts a number, not a collection of IDs.
• B: Set.containsAll() checks set contents in Apex; it does not filter SOQL results.
• C: Database.query() accepts a dynamic SOQL string, not a Set<Id> directly.

• The job keeps 31 days of regular restore points. A backup from the week of January 1 is older than 31 days by March 20, so it is no longer expected to remain on the performance tier.
• It is also a weekly GFS full backup, retained for 14 weeks. Therefore, it is still protected and has not been deleted.
• In a Scale-out Backup Repository, older backups can be moved from the performance tier to the capacity tier—typically object storage—according to the configured offload policy.
• The archive tier is not selected because the question’s configuration does not indicate that the backup has been archived there.

• Employees can use approved devices from remote locations or worldwide offices.
• Users do not need to carry or insert extra hardware.
• It helps prevent account takeovers from unknown devices.

• Geotagging: Restricts access based on location, which could interfere with remote work and travel.
• Smart cards: Require additional physical equipment and card readers.
• Time-based logins: Limit access according to time but do not strongly bind access to an authorized user device.

• A password cracker would normally be identified by behavior such as loading password hashes or attempting dictionary/brute-force attacks.
• The question describes a routine audit, not password recovery.
• Simply encountering a protected file during an audit is characteristic of a misconfigured or insufficiently privileged FIM.

• Advanced Persistent Threat (APT): A sustained, targeted attack campaign or attacker group—not a vulnerability.
• Trojan: Malware disguised as legitimate software.
• Stealthware: A general term for malware designed to avoid detection; it does not specifically mean an unknown vulnerability.

• MFA: Protects sign-in and authentication.
• Azure Key Vault: Protects deployment secrets and credentials.
• Answer: No (B).

xml 
<apex:page> 
    <apex:stylesheet value="{!URLFOR($Resource.MyStyles, 'styles/main.css')}" /> 
</apex:page>

• <apex:includeScript> is for JavaScript.
• <apex:includeStyle> is not a valid Visualforce component.
• <apex:require> is not the Visualforce tag used to load CSS.

• IaaS: You deploy and manage virtual machines, including the operating system and installed software. Azure manages the physical datacenter, hosts, and networking infrastructure.
• PaaS: Azure manages the infrastructure and operating system, while you deploy and manage your application code. Examples include Azure App Service and Azure Functions.

• Configure row-level security (RLS) using the sales region and the HR manager’s identity.
• Publish the reports and datasets through a Power BI app.
• Grant the HR managers permission to use the app, but do not add them as workspace members.
• App users can view and interact with reports while RLS limits them to their region.
• They cannot modify the report layout because they do not have workspace editing permissions.

• Adding them to the workspace gives them workspace permissions that may allow report or dataset changes, depending on the assigned role.
• Creating copies is unnecessary and creates maintenance and security problems.
• Hosting datasets and reports in different workspaces does not, by itself, provide the required controlled access.

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

• CSIRT: A Computer Security Incident Response Team that handles and coordinates incident response.
• CVSS: A scoring system used to rate the severity of vulnerabilities.
• SOAR: Security Orchestration, Automation, and Response technology used to automate security workflows.

• Import: Copies data into the Power BI model. It requires scheduled or manual refresh, so it may not meet the two-minute requirement.
• Live connection: Connects to an existing Power BI semantic model or Analysis Services model; it is not the appropriate choice for connecting directly to the Azure SQL database in this scenario.

1. Find the subnet-mask increment in the octet where the prefix ends.
2. Identify the network address by finding the subnet boundary at or below the given IP.
3. The first usable address is network address + 1.
4. The broadcast address is one address before the next subnet.
5. The last usable address is broadcast - 1.

• 172.28.228.144/18

• 172.28.228.144/23

• Customer information must not be revealed ? PII Detection
• Malicious instructions embedded in images/documents must be blocked ? Prompt Shields

• If the question allows multiple selections, choose PII Detection and Prompt Shields.
• If it requires one selection specifically for the image-based threat, choose Prompt Shields.

• Set credit quotas for an account or individual virtual warehouses.
• Define monitoring intervals.
• Trigger actions when usage reaches thresholds, such as sending notifications or suspending a warehouse.
• Help control unexpected warehouse spending.

• Account Usage: Provides historical usage and billing data; it does not enforce credit limits.
• Warehouse Limit Parameter: Not the Snowflake object used for account-wide credit controls.
• Credit Consumption Tracker: Not a standard Snowflake object.

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

• Escape to host: A virtualization attack where code escapes a guest VM and accesses the host system. Nothing in the scenario mentions virtualization.
• Browser extension: Can redirect or manipulate web-browser traffic, but not normally database-server traffic.
• Valid accounts: Describes using stolen or compromised credentials, not redirecting network traffic.
• Process injection: Injecting malicious code into a legitimate database or networking process could allow an attacker to alter how that process handles outgoing traffic.

• File1.png — Yes: User1 can apply Label1 with the Microsoft Purview Information Protection client. The client supports labeling image files such as .png in this scenario.

• Folder2 — No: Folder2 is the root folder. The client does not allow labeling the root folder itself. Although the client can label ordinary folders, selecting one applies the label to existing files and subfolders—not automatically to future files.

• File1.docx — Yes: .docx is a supported Microsoft Word file type, so User1 can apply Label1 to it.

• 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

• Input validation: Prevents malicious or malformed input within an application; it does not authenticate a software package.
• Secure cookies: Protect web-session cookies; they do not protect downloadable software.
• Fuzzing: Tests software by supplying unexpected input to find vulnerabilities; it does not verify software integrity.

• A — Tables
• B — Named file formats
• C — Schemas
• E — Databases

Why these are correct

• Tables: Can be cloned using CREATE TABLE ... CLONE. The clone initially uses zero-copy cloning, so storage is shared until changes are made.
• Named file formats: Can be cloned as database objects, preserving the file-format definition.
• Schemas: A schema and its eligible objects can be cloned.
• Databases: A database and its eligible schemas and objects can be cloned.

Why the others are incorrect

• Shares: A share is an account-level data-sharing object, not a normal cloneable database object.
• Users: Users are security principals and cannot be cloned with CLONE.

• A — Too infrequent: Formal strategies are often reviewed only every three to five years. This can make the organisation slow to respond to rapid changes in technology, competitors, regulation or customer needs.

• C — Relies on predicting the future: The approach assumes senior managers can make reasonably reliable forecasts and assumptions. In uncertain environments, these assumptions may quickly become invalid.

• E — Can restrict radical innovation: Formal planning tends to favour existing information, established objectives and incremental improvements. This may discourage experimental or highly innovative strategies that emerge from lower levels of the organisation.

• B concerns the difficulty of achieving competitive advantage through core competences when competing with focused specialists. It is not specifically a drawback of the formal top-down planning process.
• D is an activity organisations should undertake—continuous monitoring—not a drawback of the approach itself.

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

• A — Improved management of storage space: Correct.

• B — Improved supplier relationships: Correct.

• C — Improved pricing decisions: Correct.

• D — Non-product-specific costs must be apportioned: Incorrect.

• E — Profitability of each customer group: Incorrect.

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

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

• A. Periodically rotate responsibilities: May reduce some risks, but it does not directly detect unauthorized changes.
• B. Review segregation-of-duties conflicts: Identifies incompatible access combinations, not whether a specific data change was unauthorized.
• C. Log changes in an outside application: Logs provide evidence, but someone must review and analyze them. Logging alone does not detect misuse.
• D. Independent review: Directly detects unauthorized changes and reduces the risk that the person making the change can conceal it.

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

1. You try to access a cloud application, such as accounting software.
2. The application redirects you to the company’s IdP.
3. You authenticate with the IdP.
4. The IdP sends a digitally signed SAML assertion to the application.
5. The application validates the assertion and grants access.

• The user’s identity
• Whether authentication succeeded
• Roles or group membership
• Access-related attributes

• Fileless malware: Nothing in the command indicates malware executing only in memory.
• Living-off-the-land binaries: Mimikatz is a credential-access tool, not a normal system utility used for LOLBin abuse.
• Social engineering: The command shows technical credential abuse, not manipulation of an accountant.

• A: Not expanding would increase its dependence.
• B: More business from the same corporation would make dependence worse.
• D: Passing work to other minority businesses does not solve its own dependence.
• E: The passage does not suggest that it can force or influence the corporation to give work to others.

• Custom domain: miami.weyland.com requires a paid App Service tier; Free and Shared are unsuitable.
• Two instances: Standard supports scaling to multiple instances.
• SSL: Standard includes SSL support.
• 12 GB storage: Basic provides only about 10 GB, so it does not meet the requirement. Standard provides substantially more storage.
• Cost minimization: Standard is the lowest tier among the choices that satisfies all requirements.

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

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.

• Online payment fraud
• Account takeover
• Fake account creation
• Suspicious transactions

1. Define – establish the project’s objectives, scope, feasibility and requirements.
2. Design – plan how the project will be carried out, including resources, schedules and controls.
3. Deliver – execute the project and produce the required outputs.
4. Develop – close the project formally and capture learning for future projects.

• Filing documentation and records
• Closing project and accounting systems
• Settling costs
• Handing over the completed work and obtaining sign-off
• Reviewing performance and giving feedback

• Vulnerability scanner: Identifies technical weaknesses in systems, applications, or devices.
• Penetration test: Simulates attacks to determine whether vulnerabilities can be exploited.
• SCAP (Security Content Automation Protocol): Uses standardized formats and protocols for automated vulnerability, configuration, and compliance checks.
• Illumination tool: Maps and analyzes broader supply-chain exposure and third-party risk.

• Compute: Not used; no virtual warehouse is required.
• Data Storage: Not scanned again.
• Metadata: May help Snowflake manage and validate cached results, but it is not the Snowflake architectural layer identified as serving the request.
• Cloud Services: Handles query coordination, metadata services, authentication, and result-cache access.

• transform() — modifies every element in an array
• filter() — keeps elements matching a condition
• exists() — checks whether any element matches
• aggregate() — reduces array elements to one result

sql 
SELECT transform(scores, x -> x * 2) 
FROM student_scores;

• A is incorrect because higher-order functions are mainly useful for nested or complex data.
• B is incorrect because they do not convert logic into Python.
• D is incorrect because their purpose is not to fix slow built-in functions, but to process arrays or maps with custom logic.

• MFA adds an additional authentication factor, such as a phone notification or verification code.
• It helps prevent unauthorized sign-ins, even if a password is compromised.
• It does not encrypt, store, or protect credentials used by deployment processes.