Salesforce PARDOT-SPECIALIST Exam Prep
Salesforce Certified Pardot Specialist (Page 8 )

• D — Value analysis: Correct. It examines an existing product to identify ways of reducing its cost while still providing the required functions, quality and reliability.
• E — Kaizen costing: Correct. It involves making continuous, small improvements and cost reductions while the product is already in production.

• Functional analysis: It is not limited to minimizing the cost of the originally defined functions. It examines what functions are required and how they can be provided at the lowest overall cost.
• Value engineering: Usually applies to the design and development of a new product, rather than being a fundamental redesign of existing organisational processes. That description is closer to business process re-engineering.
• Target costing: The target cost is generally established during the product development stage, before production begins. It is not continuously reset while the product is in production.

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

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

• A — Correct: Identify the data required by Salesforce, its dependencies, and how it should be validated. Verification scripts help confirm record counts, relationships, field mappings, and data integrity after migration.
• D — Correct: Use a full sandbox and perform trial migrations using realistic—or appropriately masked—legacy data. This exposes transformation, volume, dependency, and integration issues before production cutover.
• B — Less appropriate: Phased user migration and parallel operation primarily address user adoption and rollout risk, not the technical risks of data migration.
• C — Less appropriate: Although sandbox testing and integration testing are valuable, the option emphasizes test-data generation rather than validating the migration with representative legacy data. “A full sandbox for all systems” may also be impractical.

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

• Disable default accounts: Default or unused accounts may have known usernames or predictable settings, making them targets. They should be disabled, removed, or securely configured.
• Remove unnecessary services: Every running service creates potential vulnerabilities. Removing services the server does not need reduces exploitable entry points.

• Add the server to the asset inventory: Important for asset management, but not a hardening step.
• Document default passwords: Default passwords should be changed or eliminated—not documented for continued use.
• Send server logs to the SIEM: Valuable for monitoring and detection, but generally performed as part of logging/monitoring configuration.
• Join the server to the corporate domain: May be necessary operationally, but does not itself harden the server.

• Suspended an operator who correctly refused to use unsafe equipment.
• Rewarded another operator for using the equipment despite the broken safety guard.

• A — Management is not particularly concerned with managing risks.

• B — Employees will perceive that management does not care about health and safety risks.

• C — This factory’s safety record is likely to be poor.

• B. Deploy to a SageMaker endpoint: This is needed for SageMaker-hosted models, not for a model intended to be used directly in Amazon Bedrock.
• C. Register with SageMaker Model Registry: SageMaker Model Registry is unrelated to invoking custom models in Bedrock.
• D. Grant access in Bedrock: Access permissions may be necessary, but they do not replace the required provisioned capacity.

• The product is already in production.
• The organization is examining the product’s functions and cost drivers.
• The objective is to reduce cost without reducing perceived value or required quality.

• Kaizen costing focuses on continuous, usually incremental, cost reductions during the manufacturing stage. It is not specifically the systematic examination of a product’s functions.
• Standard costing compares actual costs with predetermined standards; it is a control technique, not a product redesign method.
• Process innovation concerns developing significantly improved production processes, rather than analysing the product’s functions and value.

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

• Due diligence: Researching and evaluating a third party before entering or continuing a business relationship.
• Internal audit: Evaluates controls within the organization itself.
• Penetration testing: Actively tests systems for exploitable vulnerabilities.
• Attestation: A formal statement or report—such as a SOC 2 report—provided by an independent party about an organization’s controls.

• The vulnerability scan identifies a vulnerability.
• The administrator verifies that the vulnerability is not present.
• Therefore, the scan produced a false positive.

• True positive: A vulnerability is reported and genuinely exists.
• False negative: A vulnerability exists, but the scan fails to detect it.
• True negative: No vulnerability exists, and the scan correctly reports no issue.

• Streams — track change data for tables or views.
• External tables — reference data stored in an external cloud storage location.

• Role — account-level security object.
• Warehouse — account-level compute resource.
• User — account-level security object.
• Share — account-level object used to share data.

1. The specific table — for example, incident
2. The parent table — for example, task
3. The wildcard table — *, which applies broadly

• Tracking who accessed or changed customer information
• Detecting unauthorized activity
• Supporting accountability and investigations
• Providing evidence for compliance and incident response

• Single sign-on not enabled: SSO improves convenience and centralized authentication, but it is not essential for access control.
• Complex passwords not required: This weakens authentication, but other controls may reduce the risk.
• Security baseline not consistently applied: A concern, but it is less specific and less immediately damaging than having no activity records at all.

spl 
error AND host=WWW3 
status=404 OR status=500 
NOT source=access.log

• Quotation marks are used for exact phrases or values containing spaces.
• Parentheses group parts of a Boolean expression, but they are not required for every Boolean search.

• IaaS: você gerencia a VM e o sistema operacional.
• PaaS: o Azure gerencia a infraestrutura; você se concentra no aplicativo.

• Constrained VMs: VMs whose workloads are experiencing resource pressure, such as insufficient CPU or memory. They may need additional resources or optimization.
• Overprovisioned VMs: VMs allocated more CPU, memory, or storage than their workloads require. Their resources may be reclaimed or reduced.

• Underprovisioned VMs: This is not the predefined view identified for this report question.
• Zombie VMs: These are typically inactive or unused VMs and are useful for cleanup, but they are not the two views specifically intended here to identify inefficient resource allocation.

• Driver node: Coordinates Spark jobs and runs in the compute environment.
• Worker node: Executes tasks and processes data.
• Databricks Filesystem (DBFS): Provides storage access for data used by compute resources.

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

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

• VPC: A logically isolated virtual network within a cloud provider; it describes network design, not the user-access model.
• NFV: Runs network services as software instead of on dedicated hardware.
• SaaS: Delivers software over the internet. Although the application may be delivered as SaaS, the question emphasizes its availability to multiple user groups, which points to multitenancy.

• 25 — Traditional SMTP server-to-server mail delivery; often restricted and not the usual client submission port.
• 110 — POP3, used for retrieving email; normally unencrypted.
• 143 — IMAP, used for retrieving and synchronizing email; normally unencrypted.

• B: Developer Edition has limited user, storage, and data-volume capacity, making realistic community testing difficult.
• C: A Developer Edition org cannot contain sandboxes, so it cannot provide separate environments for development, integration, and UAT.
• E: A standalone Developer Edition org is not part of the production org’s deployment path, so change sets cannot be used to deploy from it directly to that production org. The team would need Metadata API, Salesforce CLI, or another deployment method.

• Preparing and managing datasets
• Building and training machine-learning models
• Testing and evaluating models
• Deploying models as endpoints for predictions

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

• Installing software
• Applying configuration changes
• Calling PowerShell scripts
• Running setup or customization commands

cmd 
powershell.exe -ExecutionPolicy Bypass -File C:\Scripts\ConfigureVM.ps1

• GPO logon script: Runs only when a user logs on and depends on domain/GPO processing.
• GPO startup script: Runs during startup, but requires the VM to be domain joined and receives the applicable GPO.
• Place scripts in a VHD: Merely makes the scripts available; it does not automatically execute them.

• Physical: Protects facilities or equipment, such as locks and security cameras.
• Technical: Uses technology, such as firewalls, encryption, or access controls.
• Operational: Covers day-to-day actions and processes, such as training, backups, or incident response.
• Managerial: Includes policies, standards, risk assessments, and procedures.

• terraform apply
• terraform destroy

1. Append Table1 and Table2 as a new query

1. Select the product column in the appended query.

1. Choose Remove Rows > Remove Duplicates

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

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()

• Reconnaissance: Gathering information about the target.
• Weaponization: Creating or combining a malicious payload with a delivery method.
• Delivery: Sending the payload, such as through phishing.
• Exploitation: Triggering a vulnerability or weakness to gain execution or access.

• Amazon SageMaker — charges apply for compute, storage, and other resources used.
• AWS Config — generally charges for configuration recording and rule evaluations.
• Amazon CloudWatch — has a limited free tier, but many metrics, logs, alarms, and API usage can incur charges.

• Atomicity: a write fully succeeds or does not appear.
• Consistency: table state remains valid.
• Isolation: concurrent operations do not corrupt one another.
• Durability: committed changes persist.

• Flexible schemas: common data lakes often support flexible or schema-on-read data.
• Open-source formats: common data lakes commonly use open formats such as Parquet.
• Scalable storage: cloud data lakes already provide scalable storage.

• Dataset file: Use Import mode. Excel files are imported into Power BI, and the two Sales tables can be combined with Power Query.
• Report file: Use a live connection to the published dataset. This keeps the report separate from the dataset and avoids importing the data again.

• Report file: DirectQuery/live connection
• Dataset file: Import

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

• Ramen is a Linux worm associated with Red Hat Linux 6.2 and 7.0 systems.
• It spreads by scanning randomly generated IP addresses using tools such as synscan.
• It exploits vulnerable network services, including web-related services, and may leave malicious files or altered web content.
• The tar.gz file is also a clue because it is a common Linux archive/package format.

• Code Red: Primarily targeted Microsoft IIS servers running Windows.
• LoveLetter: Spread mainly through email attachments.
• Nimda: A Windows-based worm that spread through email, web servers, and network shares.

• Tokenization: Replaces the value with a nonsensitive token, often reversible through a secure token vault.
• Hashing: Converts data into a one-way fixed-length value, generally used for integrity checks or password storage.
• Obfuscation: A broad term for making data difficult to understand; it is less precise than masking in this context.

• You can configure different pre-shared keys for different device groups.
• All cameras could use one key.
• All scanners could use another key.
• Each key can be associated with an appropriate role or access policy.

• Menerjemahkan soal ke bahasa Indonesia.
• Menyebutkan jawaban yang benar.
• Menjelaskan alasan jawaban tersebut.
• Memberi tahu jika kunci jawaban yang tersedia tampaknya keliru.
• Menjelaskan istilah teknis penting dalam soal.

1. Wireless AP

1. Router

1. Firewall

1. Device placement

• Restrict a port to a defined number of MAC addresses
• Use statically assigned or “sticky” MAC addresses
• Shut down or restrict the port when violations occur

• Load balancer: Distributes application traffic; it does not protect switch MAC tables.
• IPS: May detect suspicious network activity, but is not the primary control for limiting switch MAC entries.
• NGFW: Filters traffic at the network boundary; it does not directly prevent MAC table flooding on access switches.

• File is shared externally ? Access level

• File is labeled “Internal only” ? Sensitivity label

• Microsoft Purview portal: Create and manage sensitivity labels and configure support for sensitivity labels used with Office files in SharePoint and OneDrive.
• SharePoint admin center: Primarily manages SharePoint settings. Older guidance and PowerShell procedures used SharePoint tenant configuration, which can make this question confusing.
• IRM: Concerns Information Rights Management and is a separate protection mechanism; it should not be used to identify the portal for configuring Microsoft Purview sensitivity labels.

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

• Layer 1: Check cables, power, and link lights.
• Layer 2: Check switching, VLANs, and MAC learning.
• Layer 3: Check IP addressing, routing, and gateways.
• Higher layers: Check services, applications, and user settings.

• Create a plan of action: Decide how to implement the fix.
• Implement the solution: Apply the selected fix.
• Verify functionality: Confirm the problem is resolved and systems work normally.

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