Apple SVC-19A Exam Prep
Apple Service Fundamentals Exam (Page 4 )

• User-generated content: precisa ser coletado, filtrado, anonimizado e rotulado.
• Moderation logs: podem conter dados inconsistentes, informações pessoais e decisões que precisam ser revisadas.
• Content moderation guidelines: são regras ou orientações, não dados diretamente utilizáveis para medir o comportamento do modelo.

• Smartphones and tablets
• Laptops and workstations
• Other mobile or endpoint computing devices

• Shared capacity

• Fabric capacity — F SKUs

• Fabric trial capacity

• Existing Power BI Premium — P SKUs

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

• Run the backup with WITH CHECKSUM
• Store the backup on an SMB network share

sql 
BACKUP DATABASE DB1 
TO DISK = '\\FileServer\SqlBackups\DB1_full.bak' 
WITH CHECKSUM;

• DMS does not create the SQL Server backups for you.
• You must provide a valid full database backup.
• You must continue taking transaction log backups while the source database remains online.
• The full backup and subsequent log backups must be available in the SMB share that DMS can access.
• WITH CHECKSUM enables backup checksum validation, helping detect backup corruption.

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.

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

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

• Response and resolution times
• Availability or uptime
• Performance targets
• Support obligations
• Penalties for failing to meet commitments

• SOW (Statement of Work): Describes the work, deliverables, scope, and tasks.
• MOA (Memorandum of Agreement): Documents a formal agreement about roles or responsibilities.
• MOU (Memorandum of Understanding): Records a general mutual understanding, often without detailed service metrics.

• Endpoint Manager: manages hosts and sensor-related settings.
• Falcon Investigator: supports investigation and analysis, but does not necessarily grant RTR access.
• Remediation Manager: handles remediation-related actions rather than interactive host access.

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

• NAT traversal: Helps WAN Edge, vSmart, and vManage devices discover how to reach one another through NAT.
• Initial orchestration: Authenticates and introduces devices when they first join the SD-WAN fabric.
• Connection brokering: Provides information that allows devices to form their required control connections, after which the vBond is generally not in the data path.

• WAN Edge: Forwards user traffic and forms secure tunnels.
• vSmart: Controls the overlay control plane and distributes routes and policies.
• vManage: Provides centralized management, configuration, and monitoring.

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

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

• terraform init is normally required first, especially for a new or changed working directory. It installs providers/modules and configures the backend.
• terraform plan previews the proposed changes.
• terraform apply applies those changes. It also creates a plan internally if you have not supplied a saved plan.

text 
terraform init 
terraform validate       # optional but recommended 
terraform plan 
terraform apply

• Admin access to the deployment pipeline
• Contributor access to the Development and Test workspaces
• Viewer access to the Production workspace

• When the MVP will be defined — the MVP should already be understood sufficiently when assessing the business case.
• What the MVP is — useful information, but not the key requirement tested here.
• That the MVP is the same as project viability — incorrect. The MVP helps test viability; it is not identical to viability itself.

• Dark web: A place where leaked credentials may be sold or shared, not usually the original source.
• Threat feeds: Collections of intelligence about threats, not a typical leakage source.
• State actors: A type of attacker, not an accidental corporate disclosure source.
• Vulnerability databases: Track known vulnerabilities, rather than leaked credentials.

• The server accepts unauthenticated image uploads, which creates an opportunity for an attacker to upload a malicious script disguised as an image or using an unexpected file type.
• A web shell is a malicious script placed on a web server that gives an attacker remote command execution through web requests.
• The suspicious process and outbound connection to a low-reputation IP are consistent with the attacker using the web shell to execute commands or establish communication with command-and-control infrastructure.

• Worm: Usually self-propagates across multiple systems; the scenario focuses on the upload page.
• Cryptocurrency mining: Possible, but there is no indication of resource-intensive mining activity or insider involvement.
• Rootkit Trojan over RDP: The evidence points to the vulnerable upload functionality, not an exposed RDP service.

• Security
• Availability
• Processing integrity
• Confidentiality
• Privacy

• Whether controls are suitably designed, and
• Whether they operated effectively over a period of time

• 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

bash 
OTEL_SERVICE_NAME=foundry-agent

bash 
OTEL_SERVICE_NAME=langchain-service

python 
import os 


os.environ["OTEL_SERVICE_NAME"] = "langchain-service" 


from azure.ai.openai... # import your tracing components 
from azure.monitor.opentelemetry import configure_azure_monitor 


configure_azure_monitor( 
    connection_string=os.environ["APPLICATIONINSIGHTS_CONNECTION_STRING"] 
)

• Agent application: OTEL_SERVICE_NAME=foundry-agent
• LangChain application: OTEL_SERVICE_NAME=langchain-service

• Treatment one – easier to prepare: Convenience for the accounting team is not the main objective of financial reporting.
• Treatment two – fair representation: This is the correct choice because financial statements must faithfully represent the underlying transaction and its economic substance.
• Treatment three – maximises profit: Accounting policies must not be selected simply to manipulate or inflate reported profit.
• Treatment four – easier to understand: Understandability is important, but it cannot justify presenting information that is less faithfully represented.

• C — Create a form extension and implement validation

• D — Use Chain of Command (CoC) with a form extension class

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

• GPS coordinates
• Date and time the image was taken
• Camera or device model
• Exposure settings

• Log data: Records events or activities, such as system or application activity.
• Encrypted data: Information intentionally encoded to prevent unauthorized access.
• Sensitive data: A broad classification for information requiring protection; geolocation may be sensitive, but the technical type stored in the image is metadata.

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

• Determine risk tolerance: Tolerance defines how much variation or exposure the organization is willing to accept. Scenarios may help apply tolerance, but they do not primarily determine it.
• Determine risk appetite: Risk appetite is established at an enterprise or governance level. Scenarios help compare risks with the appetite; they do not normally establish it.
• Develop risk responses: Once risks are identified and assessed, scenarios support response planning. However, response development comes later.

• Minimum and maximum values
• Number of distinct values
• NULL information
• Other metadata used for pruning

• Internal audit: Reviews the organization’s own controls and processes.
• Penetration testing: Actively tests systems for exploitable vulnerabilities.
• Attestation: A SOC 2 report is an attestation product issued by an independent auditor, but the analyst is not performing the attestation. They are reviewing it as part of vendor evaluation.

• Redesign how work is performed
• Deliver services faster and more flexibly
• Scale resources as demand changes
• Improve customer experiences
• Support innovation and new business models

• A: Cloud transformation applies to organizations of all sizes, not only large enterprises.
• C: It affects the entire organization, including business operations, customer service, and strategy—not just IT.
• D: Cloud adoption often requires significant process and cultural change, rather than simply continuing business as usual with lower costs.

• Three DHCP scopes: Each VLAN has its own IPv4 subnet. DHCP scopes are subnet-specific, so create one scope for:

• Two DHCP relays: DHCP client discovery begins as a broadcast, and broadcasts do not cross routers or VLAN boundaries. Therefore, configure a DHCP relay on the router or Layer 3 switch interface for each client VLAN.

• Espionage: Stealing confidential information, often for a competitor or foreign entity.
• Data exfiltration: Unauthorized removal or transfer of data.
• Nation-state attack: A cyberattack sponsored or conducted by a government.
• Shadow IT: Unapproved technology or services used outside IT oversight.

• A — Use a custom controller: An Apex class can contain the page’s logic.
• C — Use a standard controller with extensions: The standard controller provides basic CRUD behavior, while an extension adds custom logic.
• E — Use a standard controller: Useful when the page works mainly with one Salesforce object and needs standard functionality.

• A page with no controller for static or controller-free content.
• A custom controller with extensions; extensions are not limited only to standard controllers.

• Normal or expected input
• Boundary values
• Invalid input
• Potential error conditions

• A is incorrect: it creates test code, not detailed test documentation.
• C is incorrect: it does not primarily integrate external testing frameworks.
• D is incorrect: executing tests requires your development environment or test runner.

• A: It allows for branching and merging...

• C: It allows multiple engineers to work against the same code and configuration files and manage differences and conflicts.

• B: Build automation and infrastructure provisioning are handled by CI/CD and automation tools, not by version control alone.
• D: User Stories and backlogs are managed by project-management tools.
• E: Version control stores and tracks code, but it does not itself ensure that developers write effective unit tests.

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

• Marketing users: Dynamic Forms can show all fields.
• Support users: Field visibility rules can display only the Support preference fields on the record page.
• Reporting: Both profiles can still report on all fields because Dynamic Forms controls page visibility, not the underlying field access.

• A — Two record types and page layouts: Page layouts can control field placement and editability, but they are less flexible for conditional field visibility and would not be the best fit here.
• C — Muting permission set: Permission-set muting is used with permission-set groups; it does not conditionally hide fields on a page.
• D — Field-Level Security: FLS would remove field visibility at the security level. If fields are hidden by FLS, users generally cannot report on or access those fields, conflicting with the requirement that both users report on all data.

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

• Sales processes: Define the available Opportunity stages for each team.
• Record types: Connect each team to its appropriate sales process and page layout.
• Page layouts: Control which fields and related sections each team sees.

• Solar market team 1
• Solar market team 2
• Installation Services team

• One sales process: Cannot provide different Opportunity stages for each team.
• One page layout: Cannot provide different field arrangements or fields by team.
• Three page layouts alone: Page layouts control fields, but not the available stages.

• Footprinting is reconnaissance used to map an organization’s network, hosts, naming conventions, and services.
• A name such as fshare.int.complia.org suggests an internal file-sharing host (fshare) and an internal naming structure (int).
• This can reveal useful information to an attacker before attempting exploitation.

• ISP-assigned address space: Usually determined through public registration and DNS data, not an internal hostname.
• DNS sinkhole bypass: Would involve avoiding redirected malicious-domain queries.
• Initial access: DNS reconnaissance alone does not compromise the server.
• Data exfiltration: DNS tunneling typically generates many encoded or unusually long subdomain queries, not simply a meaningful internal hostname.

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

• Extracted text and images
• Page numbers and bounding polygons for citation or grounding
• Structured tables, including tables that continue across multiple pages
• Document structure such as sections and figures

• Document Extraction: Extracts basic text and images, but does not provide the full layout and structural metadata required here.
• Azure Content Understanding in Foundry Tools: A broader content-analysis service, not the single built-in Azure AI Search skill expected by this question.
• GenAI Prompt: Can transform or interpret content but does not inherently produce reliable document geometry and page-level polygons.

• Process Builder: Automates actions based on record changes; it does not create interactive user forms.
• Approval Process: Routes records for approval and captures approval decisions.
• Outbound Message: Sends information to an external system; it does not provide a user interface.

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

• Limiting the number of MAC addresses learned on a switch port
• Allowing only specific, approved MAC addresses
• Taking action when the limit is exceeded, such as dropping frames or disabling the port

DAX 
Blue Sales = 
CALCULATE( 
    [Total Sales], 
    KEEPFILTERS('Product'[Color] = "Blue") 
)

• CALCULATE evaluates [Total Sales] after applying an additional filter.
• 'Product'[Color] = "Blue" restricts the calculation to blue products.
• KEEPFILTERS ensures the existing filter context is preserved. For example, filters for year, region, or customer remain active. If Color is already filtered, the blue condition is applied as an intersection rather than replacing the existing filter.
• Avoid ALL, because it removes filters and would not maintain the existing context.

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

• CPU: Number of virtual CPUs and, where applicable, CPU reservations.
• Memory: Amount of memory and memory reservations.

• Network interface: Usually configured through the VM or workload networking configuration.
• PCI devices: Specialized hardware and not a standard VM Class resource in this context.
• Storage: Typically selected through storage policies or the VM’s storage configuration.