BCS FCBA Exam Prep
BCS Foundation Certificate in Business Analysis (BH0-013) (Page 10 )

• An Anypoint VPC provides private network connectivity for CloudHub applications.
• An IPsec VPN tunnel or AWS Direct Connect connects that VPC to the customer’s on-premises network without exposing the database to the public internet.
• The VPC and on-premises firewalls must allow the required traffic, routes, and ports.

• Static IP addresses only identify the application’s outbound traffic; they do not create a private network path to the database.
• A Dedicated Load Balancer does not replace the required network connection to the on-premises environment. It is also unnecessary merely to reach individual databases.
• Moving sensitive databases to a DMZ is not the intended architecture and could reduce their protection.

• Identifying the communication strategy: Usually part of a business continuity or incident response plan.
• Evaluating the risk management plan: Part of risk assessment and risk management activities.
• Establishing backup and recovery procedures: Usually part of disaster recovery planning.
• Developing the incident response plan: Part of incident response planning.

kusto 
Event 
| summarize make_set(EventID) by Computer

• summarize groups records.
• by Computer creates one result row per virtual machine.
• make_set(EventID) returns an array containing unique event IDs for that computer.

kusto 
| summarize make_list(EventID) by Computer

• Leaf switches provide access ports for servers, endpoints, and other devices.
• Spine switches form the fabric’s backbone.
• Every leaf connects to every spine, creating a predictable, high-bandwidth, low-latency path.

• A: Adding both a spine and leaf is unnecessary for simply adding access ports.
• B: Adding a spine does not directly provide endpoint access ports.
• D: A single connection to one spine creates a bottleneck and a single point of failure.

• Filtering or reshaping columns
• Joining with an analysis-specific dataset
• Creating calculated fields
• Applying business logic for a particular project

• Data blending: Combining different data sources, not specifically the final processing step.
• Data enhancement: A broad term for enriching data.
• Data testing: Checking data quality or pipeline correctness.
• Last-mile ETL: The precise term for additional transformations performed after the main pipeline, often directly before analytics or reporting.

• Compensating control: The server is end-of-life, so it may no longer receive security patches or support. Placing it on a restricted VLAN provides an alternative layer of protection by reducing who can access it and limiting its exposure.
• Technical control: VLAN segmentation and access control lists (ACLs) are technology-based mechanisms that enforce network access restrictions automatically.

• Managerial: Policies, procedures, and governance—not network configuration.
• Physical: Locks, guards, or barriers.
• Corrective: Restores systems after an incident.
• Detective: Identifies suspicious activity rather than restricting access.
• Deterrent: Discourages behavior but does not enforce access rules.

• Whether a user has a console password
• Password age and last password change
• Whether MFA is enabled
• Access key status
• Access key creation date and last-use information
• Access key age, which helps audit rotation

• IAM Access Analyzer identifies unintended access to resources; it does not report credential age or rotation.
• AWS Artifact provides AWS compliance documents and agreements, not details about your IAM users.
• AWS Audit Manager helps collect evidence for audits, but it is not the direct tool for viewing IAM credential rotation details.

• Forecasting lets sales leaders predict revenue for upcoming fiscal periods, compare forecasts with targets, and review performance by salesperson or team.
• Opportunity Stages help determine the likelihood that opportunities will close. Each stage can have a probability, which contributes to forecast calculations.

• Sales Quotes: Used to present pricing or product proposals to customers; they do not provide revenue forecasting.
• Opportunity List View: Helps users filter and view opportunities, but it is not the forecasting tool.

Question 3: AWS Storage Gateway File Gateway

• A: S3 bucket per user — S3 is object storage, not a traditional shared file system; mounting it requires extra tools and is less efficient.
• B: File Gateway — Provides a local file share using standard file protocols while storing files in Amazon S3. This preserves convenient local access and extends storage capacity.
• C: WorkSpaces and WorkDocs — Designed for virtual desktops and document collaboration, not large shared file storage.
• D: EC2 with EBS — EBS is attached to one EC2 instance and is not designed for direct multi-user file sharing.

• R-squared (R²): mede quanto da variação dos valores reais é explicada pelo modelo. É mais usado em regressão, não em classificação.

• Accuracy (acurácia): mede a proporção de previsões corretas em relação ao total. É adequada para a classificação de imagens da questão.

• RMSE (Root Mean Squared Error): mede o tamanho médio dos erros entre valores previstos e reais, penalizando erros maiores. É usado principalmente em regressão.

• Learning rate (taxa de aprendizado): controla o tamanho dos ajustes feitos pelo modelo durante o treinamento. Não é uma métrica de avaliação; é um hiperparâmetro.

• A recipient who already has a Microsoft account or an organizational account can authenticate by signing in.
• A recipient without a usable Microsoft identity may receive a one-time passcode by email.
• The passcode is sent to the same email address that was invited and is used to verify ownership of that address.

Correct choices

• DB1: Azure Data Box Heavy
• Virtual machines: Azure Migrate

Why

• Replication with minimal downtime
• A test migration
• Final cutover after validation

• Elicited and documented customer requirements
• Converted them into clear, measurable specifications
• Validated the requirements with the customer
• Used them as the basis for design, quality checks, and acceptance

• A: Requirements should reflect the customer’s needs—not the supplier’s standards.
• B: Iteration review planning does not replace proper requirements collection.
• D: A retrospective occurs after work is completed and is mainly for process improvement, not initial requirements definition.

• Exploitability
• Attack complexity
• Required privileges
• User interaction
• Impact on confidentiality, integrity, and availability

• CVE: Identifies and tracks a specific vulnerability; it does not primarily measure severity.
• OSINT: Open-source intelligence gathered from publicly available sources.
• SOAR: Security orchestration, automation, and response technology used to automate security workflows.

• nomes de pessoas;
• organizações;
• locais;
• datas;
• números de processos;
• leis ou contratos.

• NER = identifica informações específicas e classificáveis.
• Sumarização = reduz um documento e apresenta seus pontos principais.

• B: Trigger.Once + scheduled job

• C: 10-minute processing-time trigger

• A: My Domain is required for many SSO configurations, but if SSO works, it is unlikely to be the cause of losing the target record.
• B: HTTP-POST is a valid SAML binding and does not inherently prevent redirection.
• D: An incorrect Federation ID generally causes authentication or user-matching failure—not successful login to the home page.

• 25 — Traditional SMTP server-to-server delivery; often restricted for client submission and not inherently encrypted.
• 110 — POP3 for retrieving email; unencrypted by default.
• 143 — IMAP for retrieving and synchronizing email; unencrypted by default.
• 587 — Authenticated SMTP submission, commonly secured with STARTTLS.

• A. IDS attack signatures: An IDS primarily detects suspicious network activity and usually alerts rather than directly scanning and blocking uploaded files.
• C. Load balancer: Distributes traffic among servers but does not inspect files for malware.
• D. WAF: Protects web applications from attacks such as SQL injection, cross-site scripting, and some malicious requests. It is not primarily a PDF-malware scanning solution.

• If the Facebook user is new, Salesforce invokes createUser.
• If the user already exists, Salesforce can invoke updateUser.
• The handler can read the latest data from Facebook, such as name, email, or other profile attributes, and update the corresponding Salesforce user.

• B: A scheduled job is unnecessary and would not provide real-time synchronization during authentication.
• C: A Facebook signed request is not the standard mechanism for updating Salesforce user records in this authentication-provider setup.
• D: SAML Just-in-Time provisioning applies to SAML identity providers, not Facebook OAuth authentication.

• IKE: Negotiates security parameters for IPsec VPNs; it does not identify switch ports.
• VLAN: A logical network segmentation method, not a discovery protocol.
• netstat: Displays local network connections and listening services, but cannot identify the physical switch or port.

• Issuer: Identifies the party issuing a SAML message—usually the identity provider in the assertion. It is not the Salesforce-specific identifier the architect should provide for differentiating Salesforce.
• Identity Provider Login URL: The endpoint where users are sent to authenticate.
• SAML identity location: Determines where the user identity is found in the SAML assertion, such as the subject or an attribute.

• Writing with Apache Spark, typically as Delta tables.
• Reading with Apache Spark for processing and analysis.
• Reading with T-SQL through the lakehouse’s automatically generated SQL analytics endpoint.
• Reading with KQL through Fabric’s query capabilities that can access lakehouse data.

• Eventhouse: Optimized for real-time and KQL workloads, but it is not the natural destination for Spark-based writes or general lakehouse storage.
• Datamart: Intended mainly for relational analytics and Power BI; it is not designed for Spark-based data ingestion.
• Warehouse: Primarily T-SQL-based and structured. It does not provide the same native Spark write experience or flexibility for semi-structured data.

• Customize Opportunity Contact Role

• Add the Opportunity Contact Role related list to the Opportunity page layout

• Campaign Member Role relates contacts or leads to campaigns, not opportunities.
• Campaign Member related list would expose campaign participation, not the stakeholders for the opportunity.
• Customize Campaign Role also concerns campaigns.

• Multiple nodes: Data is replicated several times in the primary region.
• Separate geography: A copy is asynchronously replicated to a secondary Azure region.
• Readable secondary: RA-GRS provides read-only access to the secondary replica, even when the primary region is available.

• GRS: Replicates to another region but the secondary copy isn’t normally readable.
• ZRS: Replicates across availability zones in the same region, not a separate geographic region.
• LRS: Keeps replicas within a single datacenter or region and provides no geographic redundancy.

• Planning — identify the need, objectives, resources and feasibility.
• Analysis — determine user requirements and examine the existing system.
• Design — specify how the new system will work.
• Implementation — build, test, install and introduce the system.
• Maintenance/evaluation — monitor and improve the system after implementation.

• Create and manage catalogs of approved IT services
• Govern and publish infrastructure-as-code (IaC) templates, commonly AWS CloudFormation templates
• Control which users can deploy specific products and configurations
• Apply versioning, permissions, and deployment constraints

• AWS Resource Explorer: Searches and discovers AWS resources; it does not govern IaC templates.
• AWS Organizations: Manages multiple AWS accounts, policies, and consolidated billing.
• AWS Systems Manager: Helps operate and manage deployed resources, such as patching and automation, but is not primarily a catalog for governed IaC products.

• staff use the new system;
• transactions and reports are checked;
• problems are corrected;
• feedback is collected.

• Phased changeover: different parts or functions are introduced in stages, often according to a planned sequence.
• Pilot changeover: one representative department, branch or group acts as a test site before wider implementation.
• Parallel changeover: old and new systems operate at the same time.
• Direct changeover: the old system is stopped and the new one starts immediately.

• SAML: Enables federated authentication and single sign-on between the IdP and SaaS providers.
• OAuth tokens: Allow delegated application access; OAuth is not primarily the first step for employee SSO.
• Password vaulting: Stores or autofills multiple passwords but does not eliminate the separate credentials or provide true federation.

1. Ingestion Lambda receives requests from API Gateway and places messages in an SQS queue.
2. Processing Lambda is triggered by the queue and loads records into Aurora PostgreSQL.

• Decoupling: API request handling is separated from database loading.
• Buffering: SQS absorbs bursts when incoming traffic exceeds the database’s processing capacity.
• Controlled concurrency: Configure the SQS-triggered Lambda’s concurrency and batch size to avoid overwhelming Aurora or exhausting database connections.
• Automatic retries: Messages that fail processing can return to the queue and be retried. A dead-letter queue can capture persistent failures.
• Lower operational effort: The solution remains serverless and avoids managing EC2 servers or Kubernetes clusters.

• A: EC2 and Tomcat add server-management overhead.
• B: DynamoDB/DAX would require changing the database model and does not solve the Aurora ingestion design.
• C: SNS is useful for notifications and fanout, but SQS is better for durable buffering and backpressure in this producer-consumer workflow.

• Increase/decrease the number of epochs: Changes how long training runs, but does not reuse a pre-trained model.
• Unsupervised learning: Trains from unlabeled data and does not specifically address adapting an existing model.

• Store privileged credentials securely
• Grant the consultant only the access needed
• Provide temporary or time-limited access
• Rotate passwords automatically
• Record or monitor administrator sessions

• TACACS+: Centralizes authentication and authorization, commonly for network devices, but does not primarily provide password vaulting and privileged-session control.
• SAML: Enables web-based federation and single sign-on, not privileged credential management.
• SSO platform: Reduces the number of passwords users need, but does not necessarily protect administrative credentials or control privileged sessions.
• Role-based access control (RBAC): Assigns permissions based on job roles, but does not by itself prevent password sharing or securely broker administrator access.

• 6-phone boxes: 6x
• 8-phone boxes: 8x

• Compare each server’s drive specifications and performance data.
• Identify the drive that is faulty, slow, or mismatched.
• Replace it with a drive that matches the required interface, capacity, and performance characteristics.
• Avoid selecting a slower drive, because storage performance can bottleneck the entire server.
• In a redundant array, use a compatible replacement so rebuilding does not create unnecessary performance degradation.

• An Azure pay-as-you-go subscription follows an operational expenditure (OpEx) model.
• With OpEx, the organization pays for services as they are used, typically based on consumption.
• There is no need to purchase and maintain physical servers upfront.
• This contrasts with capital expenditure (CapEx), where the company makes a significant upfront investment in infrastructure, such as on-premises Hyper-V hosts.

• tag=Priv searches the tag field for values beginning with Priv. The wildcard can match the remaining characters, so it matches Privileged.
• tag=Priv would search for the exact tag Priv, not Privileged.
• tag=priv* uses lowercase priv; tag matching is treated as case-sensitive here, so it may not match the tag Privileged.
• tag=privileged uses the wrong capitalization for the exact tag.

• The requirement explicitly says the organization wants to use SAML to secure Salesforce API access.
• The SAML Bearer Assertion Flow exchanges a SAML assertion for a Salesforce OAuth access token.
• It is intended for server-to-server or other noninteractive integrations where the application has already been authenticated by an identity provider.
• The connected app can be configured so administrators authorize or preauthorize applications that consume the APIs.

• B — JWT Bearer Flow: Uses a signed JWT, not a SAML assertion. It would be appropriate if the requirement specified JWT-based authentication.
• C — SAML Assertion Flow: This is not the standard Salesforce OAuth flow name; the relevant name is OAuth 2.0 SAML Bearer Assertion Flow.
• D — User-Agent Flow: Designed for interactive browser-based authorization, not a SAML-based server-to-server integration.

• Manage multiple organizations from one hierarchy.
• Enterprise-wide policies, including repository visibility, forking, and GitHub Copilot policies.
• Centralized identity and access management, such as SAML SSO, SCIM provisioning, and—where applicable—Enterprise Managed Users.
• Centralized billing and licensing, including organization and Copilot seat management.
• Enterprise audit log, which aggregates activity across organizations.
• Security and compliance oversight, such as organization security visibility and enterprise-wide controls.
• Enterprise support and account management features, depending on the plan.

• Organization: manages its own repositories, teams, members, and local policies.
• Enterprise: governs multiple organizations and can enforce policies across them.

• A — conformant: Incorrect because one explicit requirement is violated.
• B — consistent: “Consistent” is not sufficient where the implementation contradicts a mandatory specification. The RPC mechanism is covered by the architecture, and the implementation differs from it.
• C — consistent: Incorrect reasoning: the RPC mechanism does have a defined architectural requirement, so conformance must be assessed.
• D — non-conformant: Correct because the implementation fails to follow the specified RPC/threading requirement.

• Regional leads — Customer Community Plus

• Capacity planners — External Identity

• Customer Community does not provide the enhanced reporting/dashboard access required by regional leads.
• An Identity license is generally for internal Salesforce identity use and does not fit the external capacity-planning users as well as External Identity.

• Port 515: LPD/LPR line-printer service
• Port 631: IPP — Internet Printing Protocol
• Port 9100: JetDirect/RAW printing, commonly used by network printers

• Linux machine: Linux could run these services, but the three printer-specific ports strongly indicate a printer.
• Router: Routers may use Telnet and HTTP, but normally would not expose ports 515, 631, and 9100 together.
• Windows machine: Windows can share printers, but this particular service combination is more characteristic of a network printer’s embedded operating system.

• A — Can help keep costs down and improve quality: The provider may have specialist expertise, efficient systems and economies of scale.
• B — There is a known fee if agreed in advance: A fixed or agreed fee can make costs more predictable and support budgeting.
• C — Allows management to focus on core operations and issues: Senior managers spend less time supervising routine finance processes and more time on strategic matters.

• Increased control: Control may decrease because the activity is performed externally.
• Increased independence: The organisation becomes dependent on the supplier.
• Increased understanding of the outsourcing business: The internal organisation usually has greater business knowledge; the provider may initially lack it.
• Increased confidentiality: Sharing financial information externally may create confidentiality risks.
• Internal expertise improved: Outsourcing can reduce opportunities to develop internal finance skills.

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

• GPO logon script: Runs only when a user logs on, so configuration may be delayed and is user-dependent.
• GPO startup script: Can work, but requires the VMs to be domain-joined and introduces GPO dependency. It is not specifically tied to Windows deployment.
• Place scripts in a VHD: Merely makes the files available; it does not execute them.

• SageMaker endpoint: Not required because the model is being used through Amazon Bedrock.
• SageMaker Model Registry: Used for managing SageMaker models, not for making a Bedrock custom model available.
• Grant access in Amazon Bedrock: IAM permissions may still be needed, but granting access alone does not provide the required inference capacity.

• Subject: The entity that initiates an action—here, Derrick/user account.
• Object: The resource being accessed— the file.
• Action: Reading the file.

• Restarting the device: may fix software problems, but not a directional connection issue.
• Swollen battery: is a safety concern, but would not typically cause recognition only in one orientation.
• Failing cable: possible in general, but less likely because it works on other similar devices.
• Dirty or damaged port: best matches the symptoms. Inspect and carefully clean the port, or have it serviced if damaged.

• Assign users or their team an appropriate security role.
• Ensure the role has the required table privileges, such as read, create, write, and append.
• Share the app with that security role in the app designer.

• Dynamics administration center: Used for environment and service administration, not routine app access configuration.
• Manage Roles: Not the specific Dataverse area used to define app and data permissions.
• Security Roles: Define what users can access and which operations they can perform.

• Drops packets when traffic exceeds a certain bitrate: This describes traffic policing, not shaping.
• Fragments large packets and queues them: Shaping does not fragment packets as its primary congestion-control action.
• Drops packets randomly from lower-priority queues: Packet dropping may occur if a shaping queue becomes full, but it is not the defining behavior.

• Shaping: buffers and delays excess traffic.
• Policing: drops or marks traffic that exceeds the configured rate.

• A: Person Accounts cannot be merged directly with standard Contact records.
• C: There is no Account Setup option that automatically merges Person Account duplicates.
• D: Matching rules and duplicate rules can help identify or prevent duplicates, but they do not automatically merge Person Accounts. Also, relationship considerations do not change the basic merge capability.